When the display names of base object columns in an Operational Reference Store (ORS) use special characters, the upgrade script fails to update the ORS.

The RESTORE message trigger fails to publish messages to the queue with the following error:

ArrayIndexOutOfBoundsException:18

The

mdmsupport.war

file does not contain the latest jackson JAR files.

When you delete landing table columns, memory leaks occur.

In a IBM Db2 environment, when many concurrent batch jobs run, thread connections remain open. The database crashes because Db2 cannot recycle the logs.

When you run a match job on a data set with a large number of matching records, the performance of the match job is poor.

In a Microsoft SQL Server environment, the stage job can process only one record.

When the base objects names in the MDM Hub contain less than 5 characters, the External Match job fails with the following error:

Error executing job:Invalid length parameter passed to the LEFT or SUBSTRING function. 

During a match batch job, if you use the dynamic match threshold to determine the search ranges to skip, the performance of the match batch job is poor.

During a match job, if the

_STRP

table is corrupted, the match job can fail.

ORA-01407: cannot update ("ORS"."C_TABLE"."COL<n>") to NULL

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

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

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

If a PUT update comes from a source system other than the Admin source system, the cross-reference record that is created can be unmerged. The cross-reference record unmerges, even though all the other cross-reference records for that base object are the result of PUT calls.

The Match Analyze report does not show tradeoffs between match quality and performance.

Blowfish is visible to MDM users.

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

In WebLogic environments, when you start the WebLogic server, the MDM Hub might generate an error.

After you close the Hub Console, the processes associated with the Hub Console continue to run on the machine.

During transitive matching, incorrect values appear in the ROWID_MATCH_RULE column of the HMRG table.

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