ERDAS APOLLO provides comprehensive data management and delivery which includes organizing geospatial and business data into a centralized library with cloud or on-premise distribution options.
Unforuntately there is no direct upgrade path from 2014 to 2016. User's upgrade from 2014 to 2016 will fail due to database compatibility issue.
Line 2286: Error: The upgrading path is not supported from version 4 to version 10. Please contact our support team.
…
2017-04-07 16:27:22:172 [13412] ERROR com.erdas.iws.config - Current database version(4) does not match the current Apollo Essentials release which requires database version(10).
2017-04-07 16:27:22:173 [13412] ERROR com.erdas.iws.config - Unable to copy database file (QSQLITE) to the backup file (QSQLITE.backup) and a new database is created. Please upgrade the existing database backup if needed.
There are two options: [1] Install Apollo essential 2016 from scratch, delete the filelist.db, and then generate all services manually again in Apollo essential 2016.
[2] Upgrade Apollo essential in incremental level. Each of the database upgrader can upgrade from the previous version without issues, so if you install each new version of APOLLO Core/Essentials, and perform the upgrade, it should work. In order to upgrade from 2014.0 to latest 2016.2, you have to follow the following order:
1. 2014.0/2014.1 -> 2015.5 2. 2015.5 -> 2016.2
Basically for users upgrading from v2014.x, they need to update to the v2015.x version first, then from there upgrade to the a later version. To upgrade to the latest version, the above workflow is recommended, Version 2015.5 should be the intermediate version.
Or user can always follow the complete upgrade path:
When installing, you also need to go through the entire installation processing, install the files and run the configuration wizard. The upgrade of the dataset happens during configuration wizard stage. When uninstalling, keep the configuration.
Unfortunately this workflow is not documented in the Apollo essential 2016 user guide. Here are the installers:
The upgrade from 14 to 15 was a big change in the catalog schema. I am not sure why the suggest goining from 15.0 to 15.3 then 15.5. 15.5 is cumulative. I recently installed 15.0 then went straight to 15.5 with no issues. Then you can go from 15.5 to 16.0 then 16.2.
Their is a minor patch (6.3) this summer and the next major release will b 16.5 and not 17.0
Thanks Joe Bob, Just to clarify while we install complete we are also directly using essentials component for anon access - I think article is refering to essentials config database rather than the seperate full catalog db. Sounds like both went through major changes. Article explains why I lost the essentials config content going direct from 14 to 16 (phew - 'wasn't me'). Just getting to grips what I need to budget for next upgrade (possible number of uninstall/reinstall cycles) and whether can skip major upgrades. e.g. steps from 15.0 to ?16.5? for another client.
I believe this issue is only when upgrading a version 4 database (v14.0.1.211)
There is a problem going from 4 to 5
After you get to version 5 (v15.0.0.214) you should be able to upgrade to any version.
Although there is one exception, there appears to be a problem in the v16 EP03 release that has trouble upgrading the database from 5 to 11 but it can be worked around by installing v16.0, 16.1 or 16.2 first.
