If you run the Support Tool with the HTTPS protocol, when you navigate from the Match Analysis Tool to the CSM tab, an error occurs.

After you customize search results to display lookup columns, and you run a search with no values on a package that contains the lookup columns, the lookup columns do not appear in the search results.

After you run a match job that matches a parent record with a child record, the merge task in the ActiveVOS Console references the child record instead of the parent record.

After you remove a parameter from a cleanse transformation mapping and apply the change, you cannot add a parameter to the mapping.

When you integrate

Multidomain MDM

10.3 for IBM DB2 with

Dynamic Data Masking

9.8.4, and then create a security rule set for DB2, the affected master data is not masked.

Forward matching records are created during the Automerge process, which can cause the process to run slowly.

When you use the MdmKeyStore class, a file descriptor leak causes FileNotFoundException errors.

In an Oracle RAC database environment with the Zero Downtime feature, the extract process generates an Oracle Golden Gate error.

The

cmx.server.properties

file does not contain the properties that were introduced in this release.

After you unmerge a record that has more than two cross-reference records associated with it, only one cross-reference record reflects the correct last updated date.

When pattern validation rules with WHERE clauses are applied, trust is downgraded for all records instead of only the records that match the patterns in the WHERE clause.

When Chinese characters are loaded into a staging table, some Chinese characters get corrupted.

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:

v01/installedApps/INCMDMHUBQANode01Cell/siperian-mrm-cleanse.ear.ear/siperian-mrm-cleanse.war/WEB-INF/lib/com.informatica.mdm-siperian-cleanse-10.2.0-SNAPSHOT.jar!/resources/infinispanConfig.xml

When you delete cross-reference records associated with base object records that were updated, the delete operation might fail. This is caused by the PUT_UPDATE_MERGE_IND crossreference table column.

Even though the required message trigger are enabled, the Restore API does not trigger MQ messages.

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

When the database contains partitioned tables, the metadata validation process generates the following 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:

SIP-11134: Compile failed for compile command

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.

missing initial moveto in path definition

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. You can safely ignore the error.