In a DB2 environment, when you run an external match job, you get the following error message:

SIP-16013: SQL Loader failed while loading 
file hub3023453059841591887.tmp-matchf10.dat. Return code is 4

The users can access the business entity service resources in Data Director even though they do not have privileges to access them.

You cannot change the host and port information required to launch the Hub Console.

When you run a query that runs large batch load jobs, the performance is poor.

If the business entity records are configured with dependent lookup fields, the batch automerge job fails.

When you update a base object record, the LAST_UPDATE_DATE column value does not update.

When you use multiple threads to load data into the repository, the performance is poor.

When you modify the base object field value settings, the following error message displays:

SIP-09089: Error in SQL update: ORA-00910: specified length too long for 
its datatype

When you run a multi-threaded SIF API call after acquiring the write lock on the MDM Hub Master Database, all threads are in the blocked state.

When you enable SSL in an Oracle environment, the load job fails with the following error message:

jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCPS)
(HOST=localhost)(PORT=2484))(CONNECT_DATA=(SERVICE_NAME=orcl)))

An automerge job merges records from distinct source systems with other matching records.

In Task Manager, when you approve a child or grand child record, the yellow icon next to the record does not display.