Upgrade¶
In this section you will find information about how to upgrade a previous installation of GeoNetwork Enterprise.
Minor updates may be performed in place:
GeoCat Recommends backing up your database and data directory.
For major updates or migrating from an earlier version of GeoNetwork:
GeoCat recommends backing up your database and data directory.
We do not recommend upgrading on a production server. Instead perform a new installation and transfer your data and settings to the new machine.
References:
Minor Update¶
Release |
GeoNetwork |
Updates |
Standard |
Premium |
|---|---|---|---|---|
GeoNetwork Enterprise 2020.5.6 |
3.10.9 |
2020 |
2023 |
2025 |
GeoNetwork Enterprise 2020.5.5 |
3.10.8 |
|||
GeoNetwork Enterprise 2020.5.4 |
3.10.7 |
|||
GeoNetwork Enterprise 2020.5.3 |
3.10.6 |
|||
GeoNetwork Enterprise 2020.5.2-1 |
3.10.5 |
|||
GeoNetwork Enterprise 2020.5.1 |
3.10.4 |
|||
GeoNetwork Enterprise 2020.5 |
3.10.3 |
Major Upgrade¶
Release |
GeoNetwork |
Updates |
Standard |
Premium |
|---|---|---|---|---|
GeoNetwork Enterprise 2020.5 |
3.10 |
2020 |
2023 |
2025 |
GeoNetwork Enterprise 2019.5 |
3.6 |
2019 |
2022 |
2024 |
GeoNetwork Enterprise 3.4 |
3.4 |
2018 |
2021 |
2023 |
GeoNetwork Enterprise 3.2 |
3.2 |
2017 |
2020 |
2022 |
Troubleshooting¶
During the first startup after an update, GeoNetwork performs a database migration adjusting any tables to reflect all changes required.
Scripts used:
initial setup:
WEB-INF/classes/setup/sql/create/initial data:
classes/setup/sql/data/migration:
classes/setup/sql/migrate/
Table structure is also adjusted to reflect any changes to the GeoNetwork data model. To monitor these changes add the following to log4j.xml:
<!-- Set hdm2ddl to information to see database setup -->
<logger name="org.hibernate.tool.hbm2ddl" additivity="false">
<level value="INFO"/>
<appender-ref ref="consoleAppender"/>
<appender-ref ref="fileAppender"/>
</logger>