Platform Migration Guide
| Looking for version upgrade guides or a full overview? See the Update, Upgrade & Migration Hub. |
If you have to migrate OMN from a previous to a newer or latest major version (from 4.x to 5.x for example) this guide offers information about migration steps and best practises.
How to migrate…
Oracle or MSSQL to PostgreSQL
Since OMN 5.12 PostgreSQL is supported. Existing Oracle or MSSQL DBs can be automatically migrated
→ Migration to PostgreSQL 15 [OMN-9906]
Oracle 19 support
With OMN 5.12. Oracle 19 is supported. To be able to use Oracle 19 with new or existing OMN systems there are some adaptions on database side necessary.
→ Oracle 19 support requires creation of OMN-User before initialization [OR-783]
RH9 crypto policy
Since RH9 migration the default crypto policy excludes old algorithms, so the client can’t connect to the server.
→ Since RH9 migration default crypto policy excludes old algorithms
Custom XMP metadata definitions
With OMN 7.0 the OMN6 jar-based registration of custom XMP properties was removed. Existing definitions have to be converted to a JSON file.
→ Custom XMP Metadata Definitions
Custom previews to the Lambda synchronizer
The Lambda synchronizer introduced with OMN 7.0 runs custom previews as JavaScript stored in S3 instead of local shell scripts. Existing custom preview scripts have to be converted.
→ Custom Preview Generation with the Lambda Synchronizer