Multidomain MDM
- Multidomain MDM 10.4 HotFix 3
- All Products
Reference Number
| Description
|
---|---|
MDM-31423
| When you run multiple match and merge jobs or merge jobs in parallel for different base objects, the jobs fail.
Workaround: Run the match and merge jobs or merge jobs sequentially.
|
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-22528
| After you remove a parameter from a cleanse transformation mapping and apply the change, you cannot add a parameter to the mapping.
|
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-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-16869
| In the Hub Console, non-administrative users cannot create Hierarchy Manager entities.
|
MDM-15369
| When Chinese characters are loaded into a staging table, some Chinese characters get corrupted.
|
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:
|
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-8588
| The first time that you import a schema in the Hub Console, the following error might appear:
You can safely ignore the error message.
|
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-5830
| After installation of the MDM Hub, the WebSphere application server user name 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.
|