MDM 17.0.0 Upgrade Notes
End of support for MS SQL, Oracle databases
As announced in version 15.4.0, MS SQL and Oracle RDBMS are no longer supported for MDM Storage.
Migrate your database storage to PostgreSQL before upgrading to version 17. If you upgrade without migrating, the MDM Server will fail to start.
Migration load stuck on commit
While migrating from Oracle to PostgreSQL storage, large migration loads might become stuck during commit with the following error:
ERROR: invalid byte sequence for encoding \"UTF8\": 0x00\n Where: unnamed portal parameter $52This can occur if you have records with null byte (\u0000) values, which cannot be stored in PostgreSQL.
To resolve this issue, add Column Assigner steps in the migration load plan with the following expression for all the string attributes, then rerun the plan:
substituteAll('\u0000', '',source_id)Support for trailing slashes in API URLs removed
As a follow up to version 16.0.0 announcement, using trailing slashes in API URLs is no longer supported.
To prevent request failures, review and update your API calls to ensure there’s no URLs ending in a forward slash (/).
Configuration changelog
This section provides information about the changes in the configuration files that need to be taken into account when upgrading the solution. In certain cases, the newly introduced default is used or some configuration is required.
The following table lists the configuration files that were added, changed, or removed.
| Added files | Changed files | Removed files |
|---|---|---|
/ |
|
/ |
The following sections list the changes in the files: added, changed, and removed properties.
Was this page useful?