Release Notes

Back Next

MDM Hub Known Limitations (Cumulative)

The following table describes known limitations that are carried forward from previous releases:

Reference Number	Description
MDM-25297	Informatica Multidomain MDM Installer creates two JMS queues, one for the internal SIF calls (SiperianQueue) and another for search requests. Both queues are a part of the Multidomain MDM installation. Intermittently, when you save a record in Data Director (IDD), the saving request goes to the search queue and an error appears. Workaround: Create a new destination of type Queue, under SiperianBus. For example, create SiperianQueue 1. Map it as a queue under xxx.sss.xxx queue. Restart the WebSphere application sever.
MDM-24156	If you use SAML based authentication, users cannot search for records in Data Director and access the Hub Console. Workaround: To use SAML based authentication, create the users in the MDM Hub as externally authenticated users.
MDM-22756	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.
MDM-22143	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.
MDM-5830	After installation of the MDM Hub, the WebSphere application server user name and password are visible in the installation logs.