Release Notes

10.3

Back Next

MDM Hub Known Limitations (10.3)

The following table describes known limitations:

Reference Number	Description
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-22777	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.
MDM-22691	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.
MDM-22528	After you remove a parameter from a cleanse transformation mapping and apply the change, you cannot add a parameter to the mapping.
MDM-22255	When a message trigger is enabled for the Delete base object data event and the Delete XREF data event on child tables, during a soft delete batch load operation, messages are not generated.
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-21986	Forward matching records are created during the Automerge process, which can cause the process to run slowly.
MDM-21984	When you use the MdmKeyStore class, a file descriptor leak causes FileNotFoundException errors.
MDM-21894	When you have both Auto and Manual match rules and the data matches both rules, the Match table contains duplicate entries.
MDM-21644	After the automation tool is finished running, the tool retains a write lock on the schema.
MDM-21437	After you select a record as not a match in Data Director , when you run the Auto Match and Merge job with the Accept All Unmatched Rows as Unique option, the record that you marked as not a match has a consolidation indicator of 2 instead of 1.
MDM-21436	For custom queries, after you run a Load job with the Force Update option and a Revalidate job, the validation rule does not execute correctly.
MDM-21431	If you run a Multi Merge job on records where the trust has been downgraded for a field, and then you unmerge the resulting XREF record, the HIST table can contain a value for the field that is not present in the XREF record.
MDM-21426	When you have Auto and Manual match rules, if the data matches both types of rules, the Match table contains duplicate entries.
MDM-21394	After all the jobs in a batch group complete, the batch group status remains as processing .
MDM-21376	In an Oracle RAC database environment with the Zero Downtime feature, the extract process generates an Oracle Golden Gate error.
MDM-21351	When you run CreateUsers.cmd with a user name in mixed case, the user is stored in mixed case instead of lowercase.
MDM-21178	If a custom query contains many joins and filters, when you open the Packages tool, the Hub Console becomes unresponsive.
MDM-21008	In a DB2 database environment, if you modify a base object in the database, and then try to add a new column through the Hub Console, the following error occurs: SIP-10313: Exception while executing change list: SIP-09089: Error in SQL update: DB2 SQL Error: SQLCODE=-20211, SQLSTATE=428FJ, SQLERRMC=null, DRIVER=3.69.24. DB2 SQL Error: SQLCODE=-20211, SQLSTATE=428FJ, SQLERRMC=null, DRIVER=3.69.24
MDM-20892	After you set the password policy and enable the Restrict password reuse limit option, when you add a new user, the following error occurs: SIP-10318: Cannot manage password history due to data access error.
MDM-22070	The cmx.server.properties file does not contain the properties that were introduced in this release. Workaround: Add the properties to the file after you upgrade.
MDM-19768	Occasionally, when you run SIF commands on cross-reference records, the following error occurs: SIP-40609: Cannot edit the record. The PERIOD_REFERENCE_TIME that you specified is not within the effective period for the record you are editing.
MDM-19652	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.
MDM-19610	The Stage job rejects some records with the following error: SIP-11083: Cannot load class.
MDM-19587	After the executeBatchUnmerge SIF API runs, the relationship between C_B_PARTY and C_B_PARTY_ALT_ID is not set correctly.
MDM-19586	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.
MDM-19004	The automation properties file in the Resource Kit does not contain the property to configure a user email address, which is required to create a user.
MDM-18436	The Delete Business Entity REST API cannot delete child records in a business entity. The REST API fails with a null pointer exception.
MDM-18353	When you have multiple Operational Reference Stores, the post-load user exit processes fail on some of the Operational Reference Stores.
MDM-18166	If you use the depth parameter when you implement pagination, a REST API request does not return any results.
MDM-17744	REST calls fail when the global identifier (GBID) contains the hyphen (-) character.
MDM-15369	When Chinese characters are loaded into a staging table, some Chinese characters get corrupted.
MDM-14943	In WebSphere environments, when you log in to the Hub Console, the following misleading error might appear: SIP-11101: The Cleanse Match Server license is either not valid or expired. Workaround: Before you log in to the Hub Console, ensure that the -Dcom.ibm.crypto.provider.DoRSATypeChecking Java option is set to false . The Java option specifies whether data encryption is allowed and is required for password hashing to work.
MDM-13617	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 You can safely ignore the error.
MDM-13372	In Microsoft SQL Server and JBoss environments, when you restart the application server after deployment of the MDM Hub, an error occurs. You can safely ignore the error.
MDM-12164	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.
MDM-12129	Even though the required message trigger are enabled, the Restore API does not trigger MQ messages.
MDM-11898	When you run the Extract BVT Version batch job for multiple base objects, the last extract date is not set.
MDM-10792	When the database contains partitioned tables, the metadata validation process generates the following warning: SIP-PV-10233(31) - The tablespace of a table in the database differs from the tablespace specified in the metadata. You can safely ignore the warning.
MDM-10476	When you unmerge a record with a large number of cross-reference records, the Process Server generates an out of memory error.
MDM-10201	To promote a change list to a schema that has hierarchies enabled, you must have MDM Hub administrator privileges.
MDM-9902	When 'Enable History of Cross-Reference Promotion' is enabled for a base object, the history of cross-reference record promotion is not maintained.
MDM-9816	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
MDM-9604	When you promote an empty change list to an Operational Reference Store with a business entity configuration, the promote fails with the following error: Object cannot be deleted because 'CO CS Configs\TaskConfiguration\Task Types\AVOSBeNotification\Task Roles\DataSteward' is depending on it. (deleteRole[id:ROLE.DataSteward]) Workaround: Remove the DataSteward role from the target Operational Reference Store, and then promote the change list.
MDM-9220	You cannot import or promote a changelist from MDM Multidomain Edition version 9.6.1.
MDM-8738	The MDM Hub log file, cmxserver.log , increases beyond the maximum specified file size.
MDM-8588	The first time that you import a schema in the Hub Console, the following error might appear: missing initial moveto in path definition You can safely ignore the error message.
MDM-8060	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.
MDM-7786	After adding a new role to a user, the Operational Reference Store is marked as invalid.
MDM-7592	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. Workaround: Change the minimum trust setting for SourceA to at least 2.
MDM-6419	After you use the Hub Console to run a batch group that contains load jobs, the logs do not identify the load jobs that were run. In the Control & Logs panel, the Job Name column of the logs contain information other than the load job names.
MDM-5830	After installation of the MDM Hub, the WebSphere application server username and password are visible in the installation logs.
MDM-1578	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.

Rename Saved Search

Table of Contents

Release Notes

Release Notes

MDM Hub Known Limitations (10.3)

MDM Hub Known Limitations (10.3)