Multidomain MDM
- Multidomain MDM 10.2.2 Service Pack 1
- All Products
ASK INFAPreview
Please log in to access Bolo.
ASK INFAPreview
Reference Number
| Description
|
|---|---|
MDM-18380
| A CleansePut API request does not update a child foreign key with the correct cross-reference record.
|
MDM-18379
| A SIF API call that runs a multimerge batch job fails with the following error:
|
MDM-17682
| If you generate configuration files for business entities multiple times, the MDM Hub generates an out of memory error.
|
MDM-18285
| In the infrastructure version of WebLogic 12.2.1.3.0, deployment of the
siperian-mrm.ear file fails with the following error:
|
MDM-18232
| When you use Microsoft Active Directory as a security provider for the MDM Hub, you can log in to the Hub Console without a password.
|
MDM-18910
| You cannot open the Batch Viewer in the Hub Console.
|
MDM-17782
| When you use Services Integration Framework (SIF) to run the MDM Hub operations in a JBoss environment, an out of memory error might occur.
|
MDM-17697
| When you save changes to role privileges, the performance of the save operation is poor.
|
MDM-17661
| When you run a stage job with delta detection enabled on specific staging table columns, all the records might not be written to the RAW table. Records with null values in the columns that are mapped to the PKEY_SRC_OBJECT staging table column are skipped.
|
MDM-17641
| When you search for a record by providing the Rowid_Object value, the record is not found even though the record exists.
|
MDM-17439
| When you have multiple Operational Reference Stores, the post-load user exit processes fail on some Operational Reference Stores.
|
MDM-17437
| In a
PromotePendingXrefs SIF API request, when the
ROWID_XREF value is used as the record identifier, the child subject area records are not promoted.
|
MDM-17416
| A potential SQL injection vulnerability exists in the SearchQuery and SearchMatch APIs.
|
MDM-17369
| After you unmerge a record that has more than two cross-reference records associated with it, only one of the cross-reference records reflect the correct last updated date.
|
MDM-17288
| When you run a load job, null values might override values that are not null in columns that do not have trust enabled and in columns that are not selected in the staging table.
|
MDM-17281
| The SIF ExecuteBatchAutoMatchandMerge call does not return an error message even though errors are logged in the Hub Server log.
|
MDM-17261
| If you use the SIF ExecuteBatchDelete call to delete over 1000 records, the request fails with the following error:
|
MDM-17229
| When you update multiple cross-reference records associated with one base object, only one cross-reference record is passed to the post load user exit.
|
MDM-17184
| The automation properties file in the Resource Kit does not contain the property to synchronize user email addresses during an LDAP user synchronization.
|
MDM-17117
| In an IBM DB2 environment, when you drop more than three base object columns, the transaction might time out.
|
MDM-17092
| When you have multiple Operational Reference Stores (ORS), the post-load user exit processes fail on some ORS.
|
MDM-17082
| A Promote API call updates all fields in a record instead of updating only the fields in a pending cross-reference record specified in the SIF request.
To specify that the MDM Hub only applies BVT calculation to fields that are part of the SIF request, set the
cmx.server.selective.bvt.enabled property to
true in the
cmxserver.properties file.
|
MDM-17080
| When you synchronize users with long first names, middle names, and last names through LDAP servers, the synchronization process fails.
|
MDM-17064
| 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-17066
| When you enable trust and validation rules on a base object column, the MDM Hub drops any custom index that you created for the column in the associated cross-reference table.
|
MDM-17049
| If you use the depth parameter when you implement pagination, a REST API request does not return any results.
|
MDM-16892
| A load job end-dates relationship records for all source systems even when the source system end-dating relationship is not a State Management Override System (SMOS).
Fix: For a load job, to end-date a relationship in the same way as an SMOS system, set the
cmx.server.load.nonsmos.sourcesystem.enddate.like.smos property to
true in the
cmxcleanse.properties file.
For a Put call, to end-date a relationship in the same way as an SMOS system, set the
cmx.server.load.nonsmos.sourcesystem.enddate.like.smos property to
true in the
cmxserver.properties file.
|
MDM-16873
| When you run a manual match task and match multiple records, multiple records can have the same ROWID task entry in the match table.
Fix: To create one task for each match entry, set the
cmx.server.task.grouppotentialmergebyruleid property to
false in the
cmxserver.properties file.
|
MDM-16863
| Cleanse function calls fail and generate an error.
|
MDM-16804
| In WebLogic environments, when you start the WebLogic server, the MDM Hub might generate an error.
|
MDM-16801
| If a stage job mapping includes a Data Quality cleanse function, the MDM Hub does not process records correctly.
|
MDM-16788
| The synchronization job fails when a base object name exceeds the maximum of 24 characters.
|
MDM-16780
| If you edit the period dates of a record, an extra cross-reference record appears on the XREF view of the record.
|
MDM-16772
| A CleansePut call that passes a null foreign key value fails.
|
MDM-16771
| You cannot revert a relationship base object to a base object if the staging table has lookup columns that contain data exceeding the maximum character, char (14). A database error is generated.
|
MDM-16764
| If you use Microsoft Active Directory as a security provider, you can log in to the Hub Console without a password.
|
MDM-16763
| When multiple threads run a custom cleanse function, multiple JAR files are created in the temporary directory.
|
MDM-16737
| When you test a Data Quality cleanse function, the following error appears:
|
MDM-16736
| When you refresh a Data Quality cleanse function, the following error appears:
|
MDM-16729
| In the WebSphere environment, the Dun & Bradstreet adapter fails and generates multiple exceptions.
|
MDM-16689
| After installing 10.2 HotFix 1, the online help pages appear in Chinese.
|
MDM-16685
| The Restore API does not have a REST equivalent.
Fix: You can restore records through Business Entity POST service with the Update action.
|
MDM-16682
| When you run a manual match task and match multiple records, multiple records can have the same ROWID task entry in the match table.
Fix: To create one task for each match entry, set the
cmx.server.task.grouppotentialmergebyruleid property to
false in the
cmxserver.properties file.
|
MDM-16668
| If you use an API call to return ActiveVOS tasks for a user, the call fails if you specify the
dueDateBefore parameter.
|
MDM-16620
| In Microsoft SQL Server environments, the performance of the automerge job is poor.
|
MDM-16601
| A SIF Restore call fails with the following error message:
|
MDM-16560
| After you update a record that is enabled for smart search, an error message appears in the MDM Hub log file,
cmxserver.log .
|
MDM-16557
| When you run a match job or tokenization batch job at the same time as a tokenization API call, the following error message appears:
Fix: To enable the MDM Hub to run tokenization when there is a match job on a large number of records, set the
cmx.server.stripDML.useDeleteInsertLock property to
true in the
cmxcleanse.properties file.
|
MDM-16556
| A SIF Put call fails to update a foreign key value.
|
MDM-16541
| Automerge batch jobs and Auto Match and Merge batch jobs fail.
|
MDM-16522
| When a match path component is included in a search query, the performance of the query is poor.
|
MDM-16500
| When you use a change list to import data and promote changes to hierarchies, the import and promote operations fail with a null pointer exception.
|
MDM-16455
| By default, a Put or Cleanse Put call applies BVT calculations to all fields in a record instead of updating only the fields specified in the SIF request.
Fix: To specify that the MDM Hub only applies BVT calculations to fields that are part of the SIF request, set the
cmx.server.selective.bvt.enabled property to
true in the
cmxserver.properties file.
|
MDM-16449
| In WebSphere environments with SSL encryption enabled, when you refresh a Data Quality cleanse function, the following error appears:
|
MDM-16448
| Cascade unmerge does not unmerge child cross-reference records correctly.
|
MDM-16433
| Null values are not written to the base object record even when the following conditions are met:
|
MDM-16424
| When you run multi-threaded batch jobs, database connection leaks might occur.
|
MDM-16422
| The Delete Business Entity REST API cannot delete child records in a business entity. The REST API fails with a null pointer exception.
|
MDM-16414
| In the IBM DB2 environment, when you add base object columns, the transaction might time out.
|
MDM-16410
| A foreign key update is different when the Cascade Unmerge option is enabled versus when the Cascade Unmerge option is disabled.
|
MDM-16404
| When you merge and then unmerge a record that has multiple cross-references, the MDM Hub deletes the record after the unmerge.
|
MDM-16371
| In the IBM DB2 environment, when you drop base object columns, the performance is poor.
|
MDM-16370
| When you merge and then unmerge records, the merge history does not display correctly in the Hub Console.
|
MDM-16367
| Cascade unmerge does not unmerge child cross-reference records correctly.
|
MDM-16362
| Informatica MDM Multidomain Edition supports ActiveVOS 9.2.4.3.
|
MDM-16359
| In a clustered environment, the MDM Hub might generate duplicate JMS messages.
|
MDM-16179
| The Parse Float data conversion cleanse function fails to convert numeric string data to the float data type.
|
MDM-16123
| In the Hub Console login page, when an incorrect user name or password is entered, the following unclear error message appears:
|
MDM-16096
| The Informatica Platform application file does not contain all necessary JAR files.
|
MDM-16036
| You cannot log in to the Hub Console through Microsoft Active Directory.
|
MDM-15991
| When a load process inserts records into a relationship base object, the parent records might not be marked dirty. The issue occurs where the parent base object has match columns based on the child base object. The load process does not insert the ROWID_OBJECT value of the record into the dirty table associated with the base object.
|
MDM-15870
| If you run a mapping that uses a cleanse function, the MDM Hub generates the following error:
|
MDM-14830
| A CleanTable request fails when the
useTruncate parameter is set to
true .
|
MDM-14690
| REST calls fail when the global identifier (GBID) contains the hyphen (-) character.
|
MDM-14389
| When you configure the MDM Hub column properties, if you save the column configuration of a non-nullable column without specifying a default value, the MDM Hub does not generate a validation error.
|
MDM-13704
| In the Hub Console, when you use the Enterprise Manager or the Repository Manager, a null pointer exception is generated when fetching roles.
|
MDM-11089
| When a master record is edited, the value in the lookup column is set to the default column value.
|
MDM-10614
| When a message trigger is enabled for the Delete BO data event and the Delete XREF data event, during a soft delete batch load operation, messages are not generated.
|
MDM-10161
| After an unmerge operation with the Cascade Unmerge option disabled, the history table of the child record is not populated.
|
