In WebSphere environments, when you log in to the Hub Console, the following misleading error might appear:

In WebSphere version 8.5.5.9 environments, a stack trace error appears in the cleanse log. The stack trace error begins with the following text:

When you run the Extract BVT Version batch job for multiple base objects, the last extract date is not set.

When a master record is edited, the value in the lookup column is set to the default column value.

When the database contains partitioned tables, the metadata validation process generates the following warning: You can safely ignore this warning.

When you unmerge a record with a large number of cross-reference records, the Process Server generates an out of memory error.

To promote a change list to a schema that has hierarchies enabled, you must have MDM Hub administrator privileges.

When 'Enable History of Cross-Reference Promotion' is enabled for a base object, the history of cross-reference record promotion is not maintained.

When you refresh an Informatica Data Quality cleanse function which has two mapplets with different ports using WebSphere, the following error appears:

When you promote an empty change list to an Operational Reference Store with a business entity configuration, the promote fails with the following error:

You cannot import or promote a changelist from MDM Multidomain Edition version 9.6.1.

The MDM Hub log file,

cmxserver.log

, increases beyond the maximum specified file size.

When you import or promote a changelist from MDM Multidomain Edition version 9.7.1, an proxy role error is generated. The changelist is not imported or promoted.

After adding a new role to a user, the Operational Reference Store is marked as invalid.

A source system that is not mapped to a column in the base object can override a valid value in the column with a null value. For example, SourceA and SourceB contribute to BaseObjectC. SourceA is mapped to ColumnX with minimum and maximum trust settings of zero. SourceB is not mapped to ColumnX and has no trust setting for it, but it is mapped to other columns in BaseObjectC. When SourceB updates BaseObjectC, ColumnX is incorrectly updated with a null value.

After installation of the MDM Hub, the WebSphere application server username and password are visible in the installation logs.

When you delete an active cross-reference record in the Data Manager tool in the Hub Console, the record is deleted but an error occurs.

The MDM Hub does not support the import of a change list created in one database type into the repository of another database type. For example, you cannot import a change list created in Oracle into a Microsoft SQL Server repository.

Enabling state management for a base object that has custom packages does not resolve Repository Manager validation error SIP-MV-10252.

The MDM Hub does not support case-sensitive database collation for Microsoft SQL Server.

The MDM Hub does not support the Hard Delete Detection feature for IBM DB2.

The MDM Hub does not support custom validation rules for IBM DB2 or Microsoft SQL Server.

When using iDB Oracle, a user with the Security Access Manager (SAM) Proxy Role for an Operational Reference Store has access to functions that are not intended for the role. In particular, a user with the Proxy Role can access the MET promote, the Promote button, and the Import button.

In a Microsoft SQL Server environment, the GetOneHop API request might stop responding.

On high loads with multiple cleanse servers involved, the automerge job sometimes fails.

After you install the MDM Hub, the job metrics do not appear in the Hub Console when you run a stage job for the first time. The job metrics appear in the Hub Console for all subsequent stage jobs.

When you view the Hub Console in the Chinese language, the date format appears in English.