Informatica MDM Multidomain Edition - 9.7.1 HotFix 3 ... Documentation/3/MDM… · MDM Multidomain...

Informatica® CorporationMDM Multidomain Edition

Version 9.7.1 HotFix 3Release Notes

May 2015Copyright (c) 1993-2015 Informatica Corporation. All rights reserved.

ContentsHardware Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Installation and Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Dropped Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Configure Oracle Database Drivers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Grant Access to the Database Proxy Role. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Installing the Sample Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Installing the Hub Store in Oracle Database 12c. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Installing the Hub Server on HP-UX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Process Server Installation on AIX or Linux and WebSphere. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Installing the MDM Hub for IBM DB2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Upgrading from Version 9.1.0 or Earlier. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Upgrading an Operational Reference Store to Version 9.7.1 HotFix 3. . . . . . . . . . . . . . . . . . . . . . . . . 5

After You Upgrade Operational Reference Stores. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

MDM Multidomain Edition Version 9.7.1 HotFix 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Informatica MDM Hub Fixed Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Informatica MDM Hub Closed Enhancement Requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Informatica MDM Hub Known Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Informatica Data Director Fixed Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Informatica Data Director Closed Enhancements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Informatica Data Director Known Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

MDM Multidomain Edition Version 9.7.1 HotFix 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Informatica MDM Hub Fixed Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Informatica MDM Hub Closed Enhancement Requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Informatica MDM Hub Known Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15


MDM-HRN-97100-HF3-0002 1

Informatica Data Director Closed Enhancements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17


MDM Multidomain Edition Version 9.7.1 HotFix1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17




Informatica Data Director Fixed Limitations (9.7.1 HF1). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Informatica Data Director Closed Enhancements (9.7.1 HF1). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Informatica Data Director Known Limitations (9.7.1 HF1). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

MDM Multidomain Edition Version 9.7.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20






Informatica Data Controls Known Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Informatica Global Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

The Informatica MDM Multidomain Edition Release Notes provide important information about known limitations of the release. Read this document carefully before you install the Informatica MDM Hub and Informatica Data Director.

Hardware RequirementsThe hardware requirements for an MDM Multidomain Edition implementation are dependent on your data, processing volumes, and business rules.

Installation and Upgrade

Installation

If you are installing for the first time, see the following documents:

• Informatica MDM Multidomain Edition Installation Guide

• Informatica MDM Multidomain Edition Release Guide

• Informatica MDM Multidomain Edition Release Notes

If you are upgrading to MDM Multidomain Edition version 9.7.1 HotFix 3, see the Informatica MDM Multidomain Edition Upgrade Guide.

2 MDM-HRN-97100-HF3-0002

For more information about product requirements and supported platforms, see the Product Availability Matrix on the Informatica My Support Portal: https://mysupport.informatica.com/community/my-support/product-availability-matrices

Dropped Support

Effective in version 9.7.1, Informatica dropped support for the use of IBM DB2 in Oracle-compatibility mode with the MDM Hub. You must use IBM DB2 with Oracle-compatibility disabled.

You must migrate the database from IBM DB2 Oracle-compatibility mode to IBM DB2 with Oracle-compatibility disabled.

For more information about product requirements and supported platforms, see the Product Availability Matrix on the Informatica My Support Portal: https://mysupport.informatica.com/community/my-support/product-availability-matrices

Configure Oracle Database Drivers

The MDM Hub distribution directory contains an incorrect version of the ojdbc6.jar driver file. After you download and extract the installation files, copy the correct version of the Oracle database driver file to the MDM Hub distribution directory.

1. Download Oracle Database 11g Release 2 (11.2.0.4) JDBC Driver from the Oracle website.

2. Replace the ojdbc6.jar driver file in the following directory with the driver file for version 11.2.0.4:

On UNIX. <distribution directory>/database/libOn Windows. <distribution directory>\database\lib(MDM-4075)

Grant Access to the Database Proxy Role

If you created the database proxy role, grant the proxy role access to control permissions. To create and drop base objects, the database proxy role needs access to control permissions.

1. Open an IBM DB2 command window.

2. To connect to the database, run the following command: db2 connect to <database name> user <database user> using <database user password>

3. To grant the proxy role access to control permissions, run the following command: grant accessctrl on database to role PROXY_ROLE;

Installing the Sample Applications

Before you install the MDM Hub sample applications, set up the sample Operational Reference Store. You cannot set up the sample Operational Reference Store in IBM DB2 that runs on UNIX.

(HORA-51554)

MDM-HRN-97100-HF3-0002 3

https://mysupport.informatica.com/community/my-support/product-availability-matrices

https://mysupport.informatica.com/community/my-support/product-availability-matrices

Installing the Hub Store in Oracle Database 12c

When you install Oracle Database 12c, do not create the database as a multitenant container database. If you install the Hub Store in a multitenant container database, the installation fails.

(HORA-48021)

Installing the Hub Server on HP-UX

To install the Hub Server on HP-UX, ensure that the tmp directory has enough space. If the size of the tmp directory is less than 1 GB, the Hub Server installation might fail. If the size of the tmp directory is less than 1 GB, use a directory that has enough space.

1. To use a directory other than the tmp directory and to set the IATEMPDIR variable, run the following command:

export IATEMPDIR=/<directory_name>2. To verify that the IATEMPDIR variable is set, run the following command:

echo $IATEMPDIR(HORA-47962)

Process Server Installation on AIX or Linux and WebSphere

If you configure AddressDoctor 5 as part of the Process Server installation on Linux or AIX, WebSphere stops. You must remove the AddressDoctor 5 configuration and manually run the post-installation setup.

1. Comment out AddressDoctor 5 configuration in the cmxcleanse.properties file.The cmxcleanse.properties file is located in the following directory:

<infamdm_install_directory>/hub/cleanse/resources/2. Start WebSphere Application Server.

3. Manually run the post-installation setup.

(HORA-47417)

Installing the MDM Hub for IBM DB2

After you install the MDM Hub in the IBM DB2 environment, specify the following parameters for the data source by using the WebSphere Administrative Console:

• driverType=4 progressiveStreaming=2

• fullyMaterializeLobData=true

• fullyMaterializeInputStreams=true

• progresssiveLocators=2

• deferPrepares=false

Whenever you register a new Operational Reference Store, set the data source parameters by using the WebSphere Administrative Console.

(HORA-47461)

4 MDM-HRN-97100-HF3-0002

Upgrading from Version 9.1.0 or Earlier

Drop temporary tables and temporary views that the batch processes created. These temporary tables and temporary views can cause errors and warnings during the upgrade process if you do not drop them.

Batch processes, such as the stage process and landing process, create temporary tables and temporary views. In version 9.1.0 and earlier, the MDM Hub might not drop these temporary tables or temporary views when they are no longer required. Drop these tables before you upgrade. The temporary tables and temporary views use the naming convention T$<table or view name>.

Do not drop any custom tables or views that you created.

Upgrading an Operational Reference Store to Version 9.7.1 HotFix 3

Before you upgrade an Operational Reference Store to version 9.7.1 HotFix 3, update the name of the database script. The update ensures that the script does not run multiple times. If you do not update the name of the database script, the upgrade might fail.

1. Connect to the Operational Reference Store.

2. To update the 2013050601_lsc_c_repos_cleanse_match_server.sql database script, run the following command:

update c_repos_db_change set db_change_script_name = '2013050801_lsc_c_repos_cleanse_match_server.sql' where db_change_script_name = '2013050601_lsc_c_repos_cleanse_match_server.sql';

If the c_repos_db_change column contains the 2013050601_lsc_c_repos_cleanse_match_server.sql database script, the command updates the database script to 2013050801_lsc_c_repos_cleanse_match_server.sql.(HORA-52438)

After You Upgrade Operational Reference Stores

After you upgrade Operational Reference Stores, you might need to manually fix metadata validation errors. The repair tool of the Repository Manager fails to fix the metadata validation errors that are generated.

The metadata validation errors are caused by complex queries with Hierarchy Manager joins and the Hub State indicator column. Manually enable state management from the Hub Console for the affected base objects. Alternatively, if the validation errors are not fixed, drop and recreate the queries without the Hub State indicator column.

(HORA-48467)

MDM-HRN-97100-HF3-0002 5

MDM Multidomain Edition Version 9.7.1 HotFix 3

Informatica MDM Hub Fixed Limitations

Review the Release Notes of previous releases for information about previous fixed limitations.

The following table describes fixed limitations:

Reference Number

Description

HORA-52917 In a JBoss cluster where the MDM Hub is deployed, if a node fails, you need to restart all the nodes in the cluster.

HORA-52916 If you enable audit on Services Integration Framework (SIF) API, container transaction fails when it runs through a user exit.

HORA-52915 When the MDM Hub is deployed in a JBoss cluster, remote transaction propagation between JBoss instances fail.

HORA-52888 If records are not present in the match table, the automerge, and the auto match and merge batch jobs fail with an error similar to the following:SIP-16275: Exception occurred when trying to run Automerge. Exception was {0}

HORA-52876 The performance of external match jobs is poor.

HORA-52796 During a load batch job run, the CPU usage of the server is high.

HORA-52787 You cannot create base objects or landing tables in the IBM DB2 environment.

HORA-52769 The userExitContext.getBatchJobRowid() user exit context in the post-merge user exit returns a null value.

HORA-52757 When you run a match job, the MDM Hub uses the search level that you configure for the default match rule.

HORA-52750 When you perform a cascade unmerge, child records unmerge incorrectly.

HORA-52745 When you use hot spots, performance of the unmerge batch jobs is poor.

HORA-52744 When you use hot spots, performance of the unmerge jobs is poor.

HORA-52722 You cannot perform a null update on a base object.

HORA-52711 If you enable cascade unmerge for a parent record, after the unmerge, the foreign key of the child record is set to an incorrect value.

HORA-52697 When you run multiple load jobs in parallel, some load jobs might fail with the following exception:java.rmi.RemoteException: java.lang.Exception: thread is gone

HORA-52652 You cannot specify the timeout value for EJB clients.

6 MDM-HRN-97100-HF3-0002

Reference Number

Description

HORA-52648 When you use hot spots, performance of the load batch jobs is poor.

HORA-52647 When you use hot spots, performance of the automerge jobs is poor.

HORA-52646 When the MDM Hub updates STRP tables during tokenization and automerge, the performance of queries is poor.

HORA-52629 When you perform an upgrade, the following error might occur:SIP-PV-10107 (2) - An extra system column has been found in a table. Extra system column 'TIMELINE_FILL_ON_GAP' in table 'C_REPOS_TABLE' is found.

HORA-52619 When you run the match analyzer for the MDM Hub for Microsoft SQL Server, the match analyzer fails with the following error:MoveToHoldProcessor] [ERROR] com.siperian.mrm.match.MoveToHoldProcessor: SQL Exception in setRangeOnHold processing com.microsoft.sqlserver.jdbc.SQLServerException: Incorrect syntax near 'c'.

HORA-52601 An update to a cross-reference record in a source system affects the effective period of a record from another source system.

HORA-52598 When you run an external match query, an incorrect SQL syntax error might occur.

HORA-52577 When you register an Operational Reference Store that you create in the IBM DB2 environment in the Hub Console, the following error might occur:SIP-10324: There was an unexpected exception when attempting to load data objects. SIP-10322: SQLException while fetching data 'SELECT C_REPOS_DB_RELEASE.* FROM C_REPOS_DB_RELEASE' DB2 SQL Error: SQLCODE=-204, SQLSTATE=42704, SQLERRMC=HMSMET_ORS.C_REPOS_DB_RELEASE, DRIVER=3.64.82

HORA-52512 In the IBM DB2 environment, the import of initial metadata into an Operational Reference Store might fail.

HORA-52509 When you run a batch unmerge job, records might fail to unmerge.

HORA-52505 When you run a batch load job for many records, the application server generates an out of memory error.

HORA-52501 The executeBatchRecalculateBO SIF API does not update the history table associated with a base object.

HORA-52490 After you promote a cross-reference record in the pending state, the MDM Hub does not revalidate the record. The pending records with higher trust score do not survive.

HORA-52469 When you use the HTTPSiperianClient to run a SearchQuery<Resource Name> request to search for records, the search query fails.

MDM-HRN-97100-HF3-0002 7

Reference Number

Description

HORA-52466 The PostMerge user exit generates the following error:Unable to get the User Exit SIF service instance.

HORA-52462 When you use Metcommand with proxy user and password to promote a change list, Metcommand fails.

HORA-52419 When you delete a cross-reference record with a period start date as a state management override system through the Services Integration Framework, the ClassCastException is generated.

HORA-52412 When you add or update a custom java cleanse function, the MDM Hub generates the following error:SIP-09067: Element PARAMS/DATABASE_PORT requires text content.

HORA-52331 When you run match and merge jobs, insert and delete operations are slow and as a result APIs might fail.

HORA-52286 When you run the readiness report with the autocorrect option, the performance of the readiness script is poor.

HORA-52096 When you run the ExecuteBatchRecalculateBo SIF API or the ExecuteBatchRevalidate SIF API with the RecalcBvtInd set to true, the MDM Hub generates the following exception:java.lang.NullPointerException

HORA-52094 In the MDM Hub in an IBM DB2 environment, after you enable or disable trust for a base object column, the save operation is slow.

HORA-51949 During the load process, the MDM Hub does not populate the reject table with the columns of rejected records that capture the data change events.

HORA-51536 When you merge many source base object records into one target base object record, the performance of the automerge job is poor.

HORA-51530 A trusted column value that is loaded as NULL because it is not mapped to a system wins over a value from a system that is not trusted.

HORA-51452 When you use the NVARCHAR data type, the stage job fails with the following error:ORA-12704: character set mismatch.

HORA-51330 The detection of hard deleted records from source systems generates the following error during the initial data load:SIP-10322: Failed to process a User Exit!PRL table is empty for staging table <staging table name>

HORA-50652 Cannot load data into system columns such as CREATOR, CREATE_DATE, and UPDATED_BY.

HORA-50211 During the stage process, the performance of the delta detection operation is poor.

8 MDM-HRN-97100-HF3-0002

Reference Number

Description

HORA-49988 When you a promote pending cross-reference record, the C_REPOS_MQ_DATA_CHANGE table contains incorrect results.

HORA-49536 During the import of the initial metadata for the MDM Hub Master Database in Oracle, the JDBC connect URL might include the db2 character sequence. If the the db2 character sequence is included, the MDM Hub incorrectly registers the MDM Hub Master Database for IBM DB2.

HORA-49394 If you register an Operational Reference Store with an uppercase host name, batch jobs fail with the following error:sequence name is not found: C_REPOS_SEQ

Informatica MDM Hub Closed Enhancement Requests

The following table describes closed enhancement requests:

Reference Number

Description

HORA-52548 In the Security Access Manager, when you assign users to specific groups, the user list that appears is in an alphabetic order.

HORA-52519 The complete tokenization job runs in multithreaded mode.

HORA-52609 MDM Multidomain Edition is available for Oracle Database 12c. You can deploy the MDM Multidomain Edition on Oracle WebLogic Server 12c.

HORA-50106 You can run the Informatica Data Director application in Microsoft Internet Explorer 11 on Microsoft Windows 8.1.

HORA-35790 To create an XML message for a JMS queue, the MDM Hub uses all the rows for a record that are present in the display package.

Informatica MDM Hub Known Limitations

The following table describes known limitations:

Reference Number

Description

HORA-52755 When you run tokenization in the multi-threaded mode, the process does not log errors in the cmxserver.log file.

HORA-52462 When you use Metcommand with proxy user and password to promote a change list, Metcommand generates the following error:Parsing failed. Reason: Unrecognized option: -passwordWorkaround: When you run Metcommand, do not specify the proxy user password.

MDM-HRN-97100-HF3-0002 9

Reference Number

Description

HORA-52131 When you run a load job in a Microsoft SQL Server environment, the MDM Hub fails to process records that contain special characters. Special characters in keys can cause issues with key duplication. Special characters include accented letters or letters with diacritical marks.Workaround: Avoid the use of special characters in primary keys. Also, key duplication can occur if you have some primary keys in uppercase and some in lowercase. Ensure that all primary keys are in the same case.

HORA-51745 When the ActiveVOS Server runs in a different application server than the Hub Server, a user cannot claim a task from the Task Inbox.Workaround: Ensure that the user account has the same password in both systems.

HORA-51537 If the automerge load balancing controller thread times out, the automerge job might complete without merging all the records.

HORA-47198 When you visually promote a repository, the MDM Hub adds the changes to match rule sets in the target repository. The MDM Hub does not replace the existing match rule sets with the updated match rule sets.

Informatica Data Director Fixed Limitations



Reference Number

Description

HORA-52914 When you run a search query, Informatica Data Director searches with an effective date for base objects that are not timeline-enabled.

HORA-52898 It takes a long time to approve a task associated with several child records with many cross-reference records.

HORA-52872 The Hierarchy Manager takes a long time to count entity relationships when the entity has many relationships.

HORA-52844 In Internet Explorer 9, if you create a new record and press Enter, Informatica Data Director clears the text fields you edited.

HORA-52830 The HTML and JavaScript comments in Informatica Data Director could lead to possible security risks.

HORA-52813 When the Data Security filter is enabled on a parent Subject Area, Informatica Data Director does not assign tasks associated with that Subject Area to an appropriate user.

HORA-52709 When you configure many roles for data security, a child record takes longer than expected to open.

HORA-52678 If you sort more than 10 records in the Cross-reference view, Informatica Data Director only displays the first page of results.

10 MDM-HRN-97100-HF3-0002

Reference Number

Description

HORA-52677 Informatica Data Director calls GetMyTask twice when it retrieves a task list from ActiveVOS.

HORA-52626 When you enable Search By rules, Informatica Data Director does not display the Potential Matches screen.

HORA-52555 If you try to save a hierarchy-enabled record, Informatica Data Director does not display the effective period window. Because of this, Informatica Data Director saves the record with period_start_date and period_end_date as null in the database.

HORA-52518 When you navigate to a child tab in history view, Informatica Data Director generates an exception.

HORA-52498 Informatica Data Director does not load candidate children data in Match view.

HORA-52483 The Task Inbox does not filter ActiveVOS tasks correctly.

HORA-52471 When you cancel a task for a pending record, the record is deleted.

HORA-52459 When you send a record for approval, Informatica Data Director does not display the appropriate list of users who can approve the change.

HORA-52445 If you have many lookup fields, it can take a long time to open the Data tab in Informatica Data Director, which made searches slow. The parameter maxParallellSavedQueriesThreads makes queries run faster.

HORA-52437 When you change which record an entity has a relationship with, the old relationship is not deleted.

HORA-52415 When you import a metadata change list and deploy an application, Informatica Data Director generates the following error:ORA-01795: maximum number of expressions in a list is 1000

HORA-52414 The Run Search button sometimes becomes disabled when you run an extended search.

HORA-52403 If you create a Subject Area with a display package that includes a count function, Informatica Data Director generates an error when you run a search.

HORA-52389 Informatica Data Director does not highlight the Date field when there is a validation error.

HORA-52301 When a record you create is opened in an external link, the ROWID_OBJECT value does not appear.

HORA-52300 When you configure a Subject Area child that is part of the primary object, Informatica Data Director displays the incorrect default view.

HORA-52295 If you change a grandchild record and do not immediately send the change for approval, the child entity record remains in the edited state and the Send for Approval button disappears.

HORA-52074 Informatica Data Director displays different values for Manager ID in Base Object view and Cross-reference view.

MDM-HRN-97100-HF3-0002 11

Reference Number

Description

HORA-52051 When you run Informatica Data Director in Internet Explorer, you cannot export search results.

HORA-51981 When you save a non-timeline Hierarchy Manager entity, Informatica Data Director incorrectly displays the Save for Effective period dialog box.

HORA-50792 When you create a new record, some lookup values are missing from dependent lookup fields.

HORA-50756 In the Informatica Data Director Implementation Guide, the instructions for how to replace the application logo were incorrect.

HORA-50502 When you add a record to a subject area with a searchable lookup configured, you cannot use Tab to switch focus to the next text field.

HORA-47971 The property alwaysUpdateExistingPeriod that you add to the C_REPOS_DS_PREF_DETAIL table does not add the Update Existing Period check box to Informatica Data Director.

HORA-36017 When you run custom cleanse functions from the Hub Console, Informatica Data Director sometimes fails and generates the following error:SIP-11084: Problem creating class loader for java library error

Informatica Data Director Closed Enhancements


Reference Number

Description

HORA-52918 Performance for Informatica Data Director deployment has improved. The Informatica Data Director application also saves changes more quickly.

HORA-52625 The Product Usage Toolkit retrieves the customer environment type.

HORA-50106 You can run the Informatica Data Director application in Microsoft Internet Explorer 11 on Microsoft Windows 8.1.

HORA-41491 In the Data View, you can show inactive relationships when entities are version disabled. In the C_REPOS_DS_PREF_DETAIL table, set the property loadInactiveRelationshipsByDefault and specify a comma-separated list of values from subject area, subject area child, or subject area grandchild names.

Informatica Data Director Known Limitations

There are no new known limitations for 9.7.1 HotFix 3.

12 MDM-HRN-97100-HF3-0002

MDM Multidomain Edition Version 9.7.1 HotFix 2




Reference Number

Description

HORA-51878 When you run a java based cleanse function, the MDM Hub generates a ArrayIndexOutOfBound exception.

HORA-51876 You cannot run a custom batch job in the MDM Hub.

HORA-51741 When you update data in a base object for which you track data change events, you do not need to give a start time and end date. When you edit the effective period of a record in a base object for which you track data change events, you can also edit the data.

HORA-51740 When you decrease the effective period of a record version, the MDM Hub generates an error.

HORA-51670 When you display records for a base object for which you track data change events, the MDM Hub generates a null pointer exception.

HORA-51280 When you set consolidation_ind to 9, the automerge process in the MDM Hub takes a long time to run on tables with more than two million records.

HORA-51155 You cannot determine distinct records when primary key columns pass through multiple levels of cleanse function in a mapping.

HORA-51052 You cannot determine distinct records if you use a cleanse function multiple times in a mapping.

HORA-50906 When you run a delete query toward the end of an automerge process, the MDM Hub slows the automerge process significantly.

HORA-50890 Cannot launch the HUB Console in WebLogic 12.1.2 environment where the database used is Oracle.

HORA-50889 Cannot launch the HUB Console in WebLogic 12.1.2 environment where the database used is Microsoft SQL Server.

HORA-50671 When you run a batch job in a clustered environment, the MDM Hub generates null pointer exception.

HORA-50589 When you run a stage job with the "Enable Distinct" option enabled, the MDM Hub generates the following error:Invalid column name 'ROWNUM'

HORA-50265 The performance of the Users and Group tool in the Hub Console is poor.

HORA-49427 The PromotePendingXREF API does not promote child records if you use the same source system and source key in the child base objects.

MDM-HRN-97100-HF3-0002 13

Reference Number

Description

HORA-49105 When you create a Put request for a message trigger-enabled base object, the MDM Hub publishes too many messages to the queue. The MDM Hub publishes more than one message for each insert or update request to the queue C_REPOS_MQ_DATA_CHANGE.

HORA-48825 When you use the SearchQuery<Resource Name> request to search for records in a package, base object, or remote package, the response does not include the period start date and period end date for the timeline-enabled records.

HORA-48651 When you use the Operational Reference Store sample schema, you cannot open the Hierarchies tool in the Hub Console.

HORA-46535 On IBM DB2, when you load the Salesforce login module in the Hub Console, the MDM Hub generates an exception.



Reference Number

Description

HORA-51701 You can configure MDM Multidomain Edition to send customer support management files that contain information about the MDM Hub environment to Informatica.

HORA-51674 You can use proxy roles for MDM Multidomain Edition for IBM DB2. You can use alternative database users, who are not Operational Reference Store users, to access and change the metadata in the MDM Hub.

HORA-50572 You can run batch updates that affect data and batch updates that affect effective periods.

HORA-50108 You can detect hard deletes in the source system for the Microsoft SQL Server or IBM DB2 environment.

HORA-50041 When you add a user from the command line utility through the MDM automation tool, you can set a default database. You can also set users as administrators.

14 MDM-HRN-97100-HF3-0002



Reference Number

Description

HORA-51159 When cmx.server.automerge.threads_per_job=1, conflicts are processed up to a maximum of 1,000 records and the remaining records are cleaned from the _MTCH table.Workaround: To merge all records, increase the value of the property to 20 in the cmx.server properties file:cmx.server.automerge.threads_per_job=20

HORA-49894 The data mart population utility generates an error message on Microsoft SQL Server.

HORA-49809 After you merge records, tasks that have records removed remain in the C_REPOS_TASK_ASSIGNMENT table. When you open a task without data in the _MTCH table of the task, the MDM Hub generates an error.

HORA-49793 When you try to register a user exit in a JAR file, the Hub Console generates an error.Workaround: Add all the user exits in the COM folder and then prepare the JAR file.

HORA-49646 The MDM Hub does not parse the 'CROSS JOIN' SQL query correctly. SQL queries that use the 'CROSS JOIN' class fail.




Reference Number

Description

HORA-52405 You cannot perform an extended search in Informatica Data Director.

HORA-52354 Error messages related to timeline actions are not informative.

HORA-52311 After you select records, the count value at the top of the toolbar does not match the number of selected records.

HORA-52310 After you use Create New Period to create a version of a record, if you edit the record, an error occurs.

HORA-52309 When you edit data in a record, Informatica Data Director generates the following error:SIP-40615: Period correction or period creation should be either from same system or from SMOS system .

HORA-52308 When you edit a record and change a column value, an error occurs.

MDM-HRN-97100-HF3-0002 15

Reference Number

Description

HORA-52248 When creating or editing records, the following issues occur:- When editing a record, the Edit option is misaligned in the list.- When editing a record, all columns are highlighted instead of only the columns with changed data.- When creating a record, all columns are highlighted, instead of only the columns with data.- When attempting to add a child record to a Party base object with timeline enabled, the creation process fails

with an error.

HORA-51789 In Hierarchy Manager, you can create a relationship between two parent entities. However, if one of the entities has a child record with a data security filter, the Hierarchy Manager cannot display the relationship and an error occurs.

HORA-51673 When viewing an entity with a pending child record, the child record is not displayed and an error occurs.

HORA-51449 Opening a merge task can take a long time.

HORA-51368 In Internet Explorer 8, the Export menu of Informatica Data Director does not appear correctly.

HORA-51019 When saving a record from Informatica Data Director with JMS security enabled in WebSphere, an error occurs.

HORA-51010 When you run a search query to search on child records, Informatica Data Director generated an error similar to the following:SIP-14114: User "user3" does not have sufficient rights to runrequest "SearchQueryRequest"

HORA-50958 In My Workflows, you cannot see the tasks that you create.

HORA-50655 You can define a column with an Edit Style of Checkbox and a read-only field. If you edit a record with this column, the word "enable" incorrectly appears beside the check box.

HORA-50180 When saving changes to a base object record with timeline enabled, the save fails with an error.

HORA-49624 If you have a Subject Area with a subtype filter of Char(14), when you match records, Informatica Data Director does not create a merge task.

HORA-48581, HORA-48189

Informatica Data Director does not generate manual merge tasks.

HORA-48040 Unable to launch the Informatica Data Director configure tool with WebLogic 12c.

HORA-46501 When you update an effective period and mark it for save, Informatica Data Director generates an error when it updates the cross-reference record.

16 MDM-HRN-97100-HF3-0002

Informatica Data Director Closed Enhancements


Reference Number

Description

HORA-50336 Add Update Existing Period as an API in siperian-bdd.jar file so that customers can use the option when creating user exits.

HORA-46448 When changes to effective dates are not contiguous with the original effective dates, the Mark for Save action fails.

HORA-38505 In the search screen, set the Effective Date field to the current date by default. If the field is empty, a search returns all data.



MDM Multidomain Edition Version 9.7.1 HotFix1

Informatica MDM Hub Fixed Limitations (9.7.1 HF1)



Reference Number

Description

HORA-50628 If you use the MDM Hub with Microsoft SQL Server 2012, Operational Reference Store validation is slow .

HORA-50602 When you have debug_ind switched on, the MDM Hub generates the following error:ORA-01000: maximum open cursors exceeded

HORA-50566 A batch group with stage jobs causes a connection leak in the application server.

HORA-50313 When creating the MDM Hub Master Database from a remote Windows machine, the build fails if you use spaces in the database path.

HORA-50254 If you use an ORS-specific API to create a PUT request with periodStartDate and periodEndDate, the MDM Hub updates the database with a NULL value.

HORA-49881 When you run an automerge job through MDM Hub, the error OptimisticLockFailure appears.

HORA-49824 The task assignment userexit does not run correctly.

MDM-HRN-97100-HF3-0002 17

Reference Number

Description

HORA-49687 Indexes are not created properly for exact match queries. Also, even though NULL to NULL matching is not enabled, the MDM Hub matches the records with NULL value during a match job.

HORA-49632 You cannot run the data mart population utility in a Linux environment.

HORA-49547 The unmerge API displays an unmergeReturn with incorrect ROWID value.

HORA-49352 When you run a distinct load job, not all records appear in the staging table.

HORA-49263 When you use GetSearchResults API with a custom package, the MDM Hub generates a Searchtoken expired error.

HORA-49186 When you unmerge a child base object, the MDM Hub generates a SIP-10322 exception.

HORA-48773 Table creation fails during the match and merge process.

HORA-48557 When you update a record in Informatica Data Director, the SRC_LUD in the cross reference table does not get updated in the MDM Hub.

HORA-47658 Return value from ExecuteBatch SIF API differs from the return value in c_repos_job_control.return_code.

HORA-45364 Cleanse jobs take a long time to run.

Informatica MDM Hub Closed Enhancement Requests (9.7.1 HF1)

There are no new closed enhancement requests for 9.7.1 HotFix 1.

Informatica MDM Hub Known Limitations (9.7.1 HF1)


Informatica Data Director Fixed Limitations (9.7.1 HF1)



Reference Number

Description

HORA-50351 When you configure a child subject area, the configuration process throws a NullPointerException error.

HORA-50186 When you run the task operation userexit, the task incorrectly assigns the same value to the variables TASK_ACTION_TYPE_NAME and TASK_TYPE_NAME.

18 MDM-HRN-97100-HF3-0002

Reference Number

Description

HORA-50064 You cannot assign a task to a user when a parent object is in the pending state and child filters are configured.

HORA-50063 The task reassignment process throws a NullPointerException error.

HORA-50062 All users can see newly created records in the task assignment dialog box, regardless of the child and grandchild filters.

HORA-50061 When you open an assigned task, a stack trace appears. This issue occurs when a filter is configured on a many-to-many child object.

HORA-50060 If you create a child object when data security is configured for a child at the subject area level and at the child level, Informatica Data Director shows the wrong value in the first column.

HORA-50059 If you create an object with data security configured at the child level and add a new child object to the object, Informatica Data Director does not show the new child object in the record of the object.

HORA-50058 When you configure data security at the child level so that only the first of multiple values can be viewed by users without administrator rights, Informatica Data Director displays all the locked values to all users from a task context.

HORA-49779 When you set the timeline granularity to SECOND and you update the existing period, the Mark for Save action creates an extraneous cross-reference record.

HORA-49665 After you enable a Merge task from the Administration page, it takes longer than expected for the Merge button in the Actions tab to be enabled.

HORA-49664 When you open the Matches view, performance is slower than expected because all child records appear in the Relationships tab.

HORA-49663 When you open a hierarchy, it can take a long time before the hierarchy appears.

HORA-49628 When you save a query from a subject area, the Save Query function fails with an error.

HORA-49447 Russian text does not appear correctly in the Adobe Flash player.

HORA-49353 An LDAP-authenticated user cannot open a hierarchy view.

HORA-49183 When you disable update privileges for a role in the Hub Console Security Access Manager, the role can still use the Delete All Relationship Periods option in Informatica Data Director.

HORA-49181 After you delete a relationship between two Hierarchy Manager entities, you cannot re-create the same relationship.

HORA-48325 When you undo edits, a warning does not appear.

MDM-HRN-97100-HF3-0002 19

Informatica Data Director Closed Enhancements (9.7.1 HF1)


Reference Number

Description

HORA-50083 On the Hierarchy View > Add to Canvas > Search page, you can select the number of records to display on a page.

HORA-50057 To restrict the data that users that belong to a particular role can access, you can configure data security parameters in the BDDConfig.xml file.

HORA-49574 In the Data View, you can expand child details by default. In the C_REPOS_DS_PREF_DETAIL table, set the property tabsExpandByDefault and specify a comma-separated list of values from subject area, subject area child, or subject area grandchild names.

HORA-49514 In the Hierarchy Manager view, you can display inactive relationships by default. In the C_REPOS_DS_PREF_DETAIL table, set the following properties to true: hmInactiveRelationshipsAvailable and loadInactiveRelationshipsByDefault.

Informatica Data Director Known Limitations (9.7.1 HF1)


MDM Multidomain Edition Version 9.7.1




Reference Number

Description

HORA-48624 During a multithreaded automerge, if the MDM Hub updates a child relationship base object that has multiple foreign keys to the parent base object, a deadlock occurs.

HORA-48559 The Process Server poller, which runs every 30 seconds, blocks updates and requires a restart of the application server.

HORA-48420 When you perform a Load job, the MDM Hub rejects all the records in the staging table, and the log file shows a java.lang.nullpointer exception.

HORA-48292 When you perform a multithreaded batch load to a timeline-enabled base object from a staging table with multiple versions of records, some valid record versions are marked as No action.

HORA-48234 Operational Reference Store upgrade in UNIX environments fail.

20 MDM-HRN-97100-HF3-0002

Reference Number

Description

HORA-48213 When you run a match or merge job, the data source connection might fail.

HORA-48038 When you run stage jobs, the MDM Hub generates the java.util.ConcurrentModificationException error intermittently.

HORA-48000 When the user column is of length 4000 and contains multiple apostrophes, a CleansePut request fails with the ORA-06502 error.

HORA-47909 If you acquire a lock in the Hub Console that lasts longer than 60 seconds, the lock does not get released when you release it.Workaround: Request the Informatica MDM Hub administrator to release the lock.

HORA-47809 The CleansePut API does not process carriage returns in data.

HORA-47808 When you import a Common Warehouse Model file, the Repository Manager generates an error.

HORA-47462 When you add tables to a query, the tables do not link even though foreign keys are present, and the MDM Hub generates an error.

HORA-47455 In the IBM DB2 environment, if you define queries with a sort, and cast the sort column to the VARCHAR datatype in the sort clause, queries fail.

HORA-47131 When you run metadata validation after you upgrade the MDM Hub sample Operational Reference Store from version 9.5.0 to 9.7.0, the following errors are generated:SIP-MV-11410(1) - SQL of the root MTIP is incorrect. SIP-MV-11408 (4) -SQL of the MTIP package is not consistent with the path component Workaround: Restart the application server and use the Enterprise Manager tool to regenerate MTIPs.

HORA-47086 When you run the MDM Hub on an AIX operating system with the JBoss application server, the MDM Hub generates an exception because of an incompatible EJB client.

HORA-46597 When you create a base object in an AIX operating system and a JBoss environment, an exception is generated.Workaround: Launch the Hub Console with IBM Java 1.7.

HORA-46548 A batch group with external match jobs and with the isAsync option set to true in the request fails.

HORA-46518 JMS message is not sent if the base object does not have a cross-reference from the triggering source system.Workaround: Enable the source system that contains the cross-reference to trigger messages.

HORA-46496 When you use specific columns to enable delta detection in the MDM Hub, duplicate values from different source systems result in rejects.

MDM-HRN-97100-HF3-0002 21

Reference Number

Description

HORA-46495 When the parent record ID on a Hierarchy Manager column is missing, the Load job fails with the following incorrect error message:SIP-40204:Could not load data into Hierarchy Manager relationship baseobject. Ensure the hierarchy, relationship type, and entity typesthat you specified in the load request exists in the hierarchy configuration for your Operational ReferenceStore.

HORA-46134 You cannot launch the Hub Console if security is enabled for the WebSphere application server.

HORA-45848 In the Microsoft SQL Server environment, when you use a change list to promote a schema, the MDM Hub indicates that the package is not valid.

HORA-45388 If you mark a source system as Distinct and enable auto rules for the merge process, records do not merge.

HORA-45110 The getOneHop and the getEntityGraph APIs fail to fetch relationship records for entities with foreign key relationships.

HORA-44440 Migration script does not enable state management on the Hierarchy Manager relationship base object.

HORA-44020 The RemoveMatchRecords API does not use locking.

HORA-44019 The UpdateMatchRecord API does not use locking.

HORA-42229 If a Put package has state management and timeline enabled, during the visual import process, Hub_State_Ind is not added to the package and an error is generated.Workaround: After a visual promote, delete the package, and then query and manually re-create the package.

HORA-41773 When you start a second node in a JBoss clustered environment, JBossCache generates a ConcurrentModification exception.

HORA-41283 When you validate the XML of a merge event, the Repository Manager generates an error.

HORA-40809 If you enable hard delete detection for an Operational Reference Store and run a Stage job, the MDM Hub might generate an error.

HORA-38528 When you perform a match job, the insert query that populates the T$PM_<Base_Object> table is slow. Also, the size of the temporary tablespace increases.

22 MDM-HRN-97100-HF3-0002



Reference Number

Description

HORA-48230 You can encrypt specific fields in a database and securely send data over a network.

HORA-47954 You can generate ORS-specific APIs for Operational Reference Store objects that you select. The MDM Hub associates a version ID with each ORS-specific APIs client JAR file that it generates.

HORA-47710 You can use IBM DB2 Version 9.7 Fix pack 7 with MDM Multidomain Edition.

HORA-47238 Improved the performance of ORS-specific APIs generation by providing the option to select specific objects for which you want to generate APIs.

HORA-47237 You can use the Hub Console to identify users that have acquired a lock in the MDM Hub.

HORA-46760 You can configure WebSphere administrative security to control the MDM Hub to access the WebSphere administrative console.

HORA-35617 When a Process Server is not running, the MDM Hub turns the Process Server offline and routes all requests to alternative Process Servers that are running.



Reference Number Description

HORA-48770 After you promote a change list and run metadata validation, the Repository Manager might generate the following error:SIP-MV-10252: The state management indicator (STATE_MANAGEMENT_IND) is not enabled for the HM base object.Please enable state management on Base Object <Base_Object_Name> in the Schema Manager to resolve this error.When you enable state management for the base object to fix SIP-MV-10252, the MDM Hub generates an error.Workaround: Drop and recreate queries associated with th base object.

HORA-48768 If you use a query with C_REPOS_SYSTEM as the primary table, and then use the Repository Manager to import or promote a change list, the import or promote operation fails.Workaround: Drop the query before you import or promote the change list, and then re-create the query in version 9.7.1.

MDM-HRN-97100-HF3-0002 23


HORA-48681 When you generate ORS-specific APIs in a WebSphere environment with security enabled, the MDM Hub creates a WSDL URL without HTTPS. If you use the WSDL URL to create a SoapUI project, the SoapUI generates an error.Workaround: If you want to create a SoapUI project, change the WSDL URL to an HTTPS URL before you create the project.

HORA-48679 If you delete a cleanse function and refresh the object status in the SIF Manager tool, the status of the clenase function does not change to Deleted.

HORA-48659 In the IBM DB2 environment, if the user name and the schema name are different, when you acquire a write lock the Hub Console generates an error:An Operational Reference Store proxy user cannot acquire lock on the Operational Reference Store.Workaround: Change the user name to match the schema name before you acquire a write lock in the Hub Console.

HORA-48651 When you use the Operational Reference Store sample schema, you cannot open the Hierarchies tool in the Hub Console.Workaround: Unregister the Operational Reference Store sample schema and register it again.

HORA-48524 If you perform a proximity search with the geocode radius set to 0, no matches are found even if records with the same latitude and longitude values exist.Workaround: To find matches when latitude and longitude with same values exist, set the geocode radius to 1.

HORA-48523 You cannot use the Operational Reference Store sample schema in IBM DB2 that runs on UNIX.

HORA-48318 If you enable WebSphere administrative security, you cannot log in to the Hub Console.Workaround: Use the WebSphere administrative console to set the Common Secure Interoperability Protocol Version 2 to SSL-supported.

HORA-47950 In the WebSphere environment, when you use Data Manager or Merge Manager, the MDM Hub might generate the CORBA TRANSACTION_ROLLEDBACK exception.Workaround: In the WebSphere Administrative console, manually set the -Djava.vendor=IBM Java option in the WebSphere process definitions.

HORA-47895 When you add a unique key relationship to a custom index, the MDM Hub generates the SIP-MV-10244 error.Workaround: Create custom indexes after you set up schemas in the Hub Console.

HORA-47847 When a Services Integration Framework API for which API auditing is enabled is called from within a User Exit, the audit trail stored in C_REPOS_AUDIT is not committed if an exception is generated and the transaction is rolled back. Similarly, for Merge operations, the temp tables that are created are registered for deletion in Search Results Manager and are rolled backed if an exception is generated for the transaction.

HORA-47417 You cannot configure AddressDoctor 5 with the MDM Hub on Linux or AIX, and WebSphere environments.

24 MDM-HRN-97100-HF3-0002


HORA-47356 The PartyWebServiceExample API in the Resource Kit generates an error.

HORA-47128 The DIRTY_IND column might appear in the Get, searchQuery, and searchMatch API responses.Workaround: The DIRTY_IND column is deprecated. Do not use the DIRTY_IND column. Identify base object records to be tokenized by their ROWID_OBJECT values that are updated in the dirty table. The dirty table is a system table associated with the base object.

HORA-47124 After you migrate a schema from version 9.6.1 to 9.7.1, the value in the DIRTY_IND column is 1.Workaround: Ignore the DIRTY_IND column values. Identify base object records to be tokenized by their ROWID_OBJECT values that are updated in the dirty table. The dirty table is a system table associated with the base object.

HORA-47083 If you log in to the Hub Console with an incorrect password when JBoss security is enabled, JBoss generates the following incorrect exception:Error: EJBCLIENT000025: No EJB receiver available for handling [appName:siperian-mrm, moduleName:siperian-server, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@4925d132Workaround: Log in to the Hub Console with the correct password.

HORA-46878 When you perform a load update with data that has non-contiguous effective period, and if the base object is enabled for timeline, the rejected records do not populate all the columns in the reject table.Workaround: The data missing in the reject table is from the landing table. If the data is important, get the values in the missing columns in the reject table from the landing table by using SRC_ROWID.

HORA-46868 In the Microsoft SQL Server environment, caching issue occurs after you set interop_ind to 1 in the Hub Console.Workaround: Restart the application server.

HORA-46535 On IBM DB2, when you load the Salesforce login module in the Hub Console, the MDM Hub generates an exception.Workaround: Run the following command to increase the BLOB column length:SET SCHEMA CMX_SYSTEM; ALTER TABLE C_REPOS_SAM_PROVIDER_FILE ALTER COLUMN PROVIDER_FILE SET DATA TYPE BLOB (10240000); CALL ADMIN_CMD('REORG TABLE C_REPOS_SAM_PROVIDER_FILE');

HORA-46531 The getXrefForEffectiveDate API does not return records when the historyDate value is before HXRF.HISTORY_CREATE_DATE.Workaround: Ensure that the historyDate in the request is more recent than HXRF.HISTORY_CREATE_DATE.

HORA-46421 If you base a relationship on the unique key of a parent record, and enable edit and cascade unmerge for the parent and child records, unmerge of edits to the parent record fails.Workaround: Unmerge the edits to the child record, and then unmerge the edits to the parent record.

MDM-HRN-97100-HF3-0002 25


HORA-46259 When you have records from a child table that are queued for automerge, you cannot use the cascade delete functionality.Workaround: When you perform a cascade delete, do not add parent records in the IN_XREF_LIST_TO_BE_DELETED table that have a target match in the child table.

HORA-46029 When you run an executeBatchDelete request with override_history_ind and recalculateBVT set to false, and if a cross-reference record is deleted, the MDM Hub inserts a record in the history table.

HORA-45637 You cannot drop base objects with more than 90 columns when IBM DB2 is installed on Windows.

HORA-45528 When you register the sample Operational Reference Store in the Hub Console, the MDM Hub might generate an error.Workaround: Ignore the error.

HORA-45174 When foreign key changes at the child record level, the MDM Hub creates an extra history record in the Child_HIST table.Workaround: Ignore the extra history record in the Child_HIST table.

HORA-45061 The match path component filter does not filter the datetime data type.

HORA-44873 If you use the Repository Manager to import the foreign key relationship packages, the Hierarchy Manager does not fetch foreign key relationship.Workaround:1. After you promote change.xml, drop the display and Put Hierarchy Manager foreign key

relationship packages and re-create them.2. Configure the Hierarchy Manager profile by adding the foreign key relationship type and assigning the

display and Put packages.3. Validate the Hierarchy Manager profile, and then add foreign key relationship records and try to fetch one

hop for foreign key relationship records.

HORA-44793 Cannot see log information present in the processUserExit when the postLoad user exit is called.Workaround: Restart the application server whenever you upload an implemented user exit JAR file and run the load job again.

HORA-44791 If an effective date in not specified in a Services Integration Framework (SIF) request for a base object that has timeline enabled, the Get API returns incorrect results.

HORA-44775 If you do not specify an effective date in a SIF request for a base object that has timeline enabled, the Get API does not return the aggregate period start date and aggregate period end date.

HORA-44673 In a Microsoft SQL Server environment, batch jobs fail if an Operational Reference Store is registered with a database name and host name in a different case than the one you use to create it.Workaround: When you register an Operational Reference Store, use the same case that you used for the database and host name when you create the Operational Reference Store.

26 MDM-HRN-97100-HF3-0002


HORA-44569 When you enable a system as an immutable system from the Hub Console, and if you use the Put API, an incorrect consolidation indicator is set.Workaround: After you enable a system as an immutable system from the Hub Console, restart the application server.

HORA-44144 The match process results in duplicate records in the match table.Workaround: Ignore the duplicate records in the match table because the duplicates have no functional impact.

HORA-43920 When you import seed into the MDM Hub Master Database and Operational Reference Stores, the MDM Hub generates the following error in the log file:ERROR Deala:172 - auto commit is on: trueWorkaround: Ignore the error message.

HORA-43819 A parent record in the pending state can have a child record in the active state.Workaround: If you want to promote a child record to the active state, ensure that the parent record is in the active state or promote the parent record to the active state before you promote the child record.

HORA-43792 In the Microsoft SQL Server environment, the MDM Hub generates the following error after the successful promotion of delta-detection changes:SIP-MV-11211 More than one delta column in Staging table.Workaround: Select the staging table and the columns that you need to promote and promote them.

HORA-43245 If the following conditions exist when you promote a source repository to a target repository, the MDM Hub generates a null pointer exception:- The source and target repositories have the same base object names.- The source is not an entity base object.- The target is not an entity base object.Workaround: To avoid a null pointer exception, the source must have the incremental changes of the old source. Also, the target must either be identical to the old source or must have originated from the old source and with the same object configuration.

HORA-42384 In the Hub Console, if you disable privileges for the ALL_BASE_OBJECTS resource group, the changes to the privileges do not save correctly.Workaround: Disable a privilege and save the change before you disable and save another privilege.

HORA-41687 You might have parent and child base objects that are related based on ROWID_OBJECT. You can insert records into these parent and child base objects that are related, and then merge records in the parent base object with a root record. If you then perform a cascade delete of the root record, the child records point to the parent that is deleted.Workaround: Do not use cascade delete in this scenario.

HORA-41463 If you update a database in a time zone that is ahead of the application server time zone, the metadata validation results are not stored. The database results in an unknown state.Workaround: Install the application server in the same time zone as the database server.

MDM-HRN-97100-HF3-0002 27


HORA-41299 The MDM Hub installer does not detect the JNP listener port if you start the JBoss application server by binding it to an IP address.Workaround: Use the following command to start JBoss with the default IP address:run.bat -b 0.0.0.0

HORA-41198 When you enable an option through the Hub Console and then cancel the change, the change is not canceled in the Security Access Manager.Workaround: Refresh Security Access Manager.

HORA-40225 When you call the SearchMatch API with the match type NONE, the SearchMatch API does not work if you did not configure a fuzzy rule.Workaround: Add an arbitrary fuzzy rule to the default match set.

HORA-40168 When you visually promote a schema, roles that inherit roles are promoted, but the inherited roles are not promoted.

HORA-39334 When you perform an incremental promote operation in the Repository Manager, the SIP-MV-10225 error is generated.Workaround: After the promote operation, delete the foreign key relationship that is added, and then configure a profile to add entity or relationship records.

HORA-39098 If you enable the Segment Matching and Segment Matches All Data options for match columns and add a primary key match rule, and save changes, a null pointer exception is generated.Workaround: Save changes after you edit a match rule with the Segment Matches All Data option. Add primary key match rule and save changes again.

HORA-39078 After you save changes in the Paths tab of the Match/Merge Setup Details dialog box, filters do not appear.Workaround: Select the root path component to display the filter.

HORA-38866 You can use the Hierarchies tool to assign display packages associated with old or deleted relationship types to relationship types associated with a profile.Workaround: Create a package and select that as the display package to assign to the relationship type.

HORA-38848 When you promote pending cross-reference records or restore deleted cross-reference records for base objects with history enabled and GBID columns, the <GBID_column_name>_GOV column of the cross-reference history table is null.

HORA-38836 When the MatchType is DBFILTERED for a SearchMatch query, the MDM Hub does not update the query if you edit the match columns.

HORA-38783 When you perform a visual promote of repositories in the Repository Manager, the order in which validation rules and match columns appear in the target repositories differs from that of the sources.Workaround: Manually reorder the validation rules and match columns after you perform a visual promote of repositories. Alternatively, use full promote.

HORA-38426 In the Hierarchy Manager, when you edit a relationship that you create with the start and end date specified, the Start Date and End Date fields in the Relationship Record Editor are null.Workaround: Refresh the Hierarchy Manager, and open the relationship entity.

28 MDM-HRN-97100-HF3-0002


HORA-38291 If you enable timeline for a base object for which a you run a batch job, an error is generated and timeline is not enabled.Workaround: Enable timeline after all the batch jobs for the base object completes.

HORA-37842 The temporary tables are removed at the same time as the search query records from C_REPOS_SEARCH_RESULT_STATE.Workaround: The temporary tables registered as TEMP_TABLE_GARBAGE_COLLECTION and BVT_TABLE_GARBAGE_COLLECTION use the sif.search.result.query.temptableTimeToLive.seconds property. Add the sif.search.result.query.temptableTimeToLive.seconds property to the cmxserver.properties file. The default is 30 seconds.

HORA-37456 Every schema change made through the MDM Hub Console generates a new change.xml change list file in the logs folder.Workaround: When you make changes to a schema from the MDM Hub Console, turn off debug, debug=off, to ensure xxx.change.xml is not generated. If debug=on, xxx.change.xml is generated. Where, XXX is the variable part in the change list file name.

HORA-37454 When you import metadata to an Operational Reference Store or promote changes, the Repository Manager creates .meta files.Workaround: Set the following property to disable generation of .meta files:cmx.server.met.promotion_snapshot=false

HORA-37423 If HFKM, HMXR, and HUID tables exist but are not in the metadata, metadata validation in the Repository Manager lists the following warning, which is reparable:SIP-PV-10202(61) - Thedatabase contains a table that is not present in the metadataIf you click the Repair icon in the Repository Manager, the reparable objects are dropped from the physical database.

HORA-36803 The Tokenize API fails with the following error:SIP-16262 Could not borrow from TokenizeAPIConnection pool.

HORA-36760 A validation rule with a comma in its name always appears as the last rule in the validation rule list.

HORA-36740 In the Repository Manager, you can import objects such as tables, views, and foreign keys from a CWM file generated by using ERwin. During the import, the views in the CWM file are not imported correctly and the following error is generated:Error: java.lang.IllegalArgumentException: argument type mismatchWorkaround: Use ERwin to create base objects. Define views in the MDM Hub.

HORA-36634 The Hierarchy Manager can convert a base object to an entity object of type Bo class Code for which you can use a GBID-enabled column as the foreign key column. No errors are reported in the metadata validation report.Workaround: Do not use a GBID-enabled column as the foreign key column when you convert a base object to an entity object in the Hierarchy Manager.

MDM-HRN-97100-HF3-0002 29


HORA-36538 The Load job fails with the following error message when the Last_Update_Date is older than the year 1900:SIP-20803: C_STG_HAR_TEST last_update_date is in the future or is older than year 1900Workaround: Change Last_Update_Date to 01.01.1900 or store as VARCHAR.

HORA-35507 The XML message that the MDM Hub generates for publishing into the JMS queue does not include all the records that appear in the display package.

HORA-34486 The UpdateTask API permits you to change the task status from Closed back to Open. A task that you reopen is unusable and you lose the task data when you close the task.Workaround: Do not change the status of a task from Closed to Open.

HORA-34280 When you add or change a match rule, and use the Repository Manager to promote it, the MDM Hub deletes and creates all the match rules in the target system.

HORA-34237 When the MDM Hub has a user in addition to a user group named admin, Put or CleansePut generates the following error during data insert:SIP-23038: ERROR:Unexpected SQL Workaround: Do not create a user group named admin.

HORA-33526 The MDM Hub Console does not start if you use a short qualified host name.Workaround 1: Update hosts file to include an IP address mapping of the short host name. For example, 10.1.8.170 caw175221.Workaround 2: To add entry "cmx.appserver.hostname" to cmxserver.properties, use the full host name. For example, cmx.appserver.hostname=caw175221.informatica.com

HORA-33446 When you map the Last Update Date column of a landing table to the Last Update Date column of a staging table through a graph function, the stage job fails with the following error:SIP-28192: Invalid source data columnWorkaround: Map the Last Update Date column of a landing table directly with the Last Update Date column of a staging table.

HORA-33396 If you perform a load by ROWID of a new cross-reference record with the DELETED state, the MDM Hub generates the SIP-28082 error.Workaround: Do not create new cross-reference records with the DELETED state.

HORA-33391 When you delete a graph function that is used in a mapping, the graph function is deleted without a warning message.Workaround: Before you delete a graph function, ensure that the graph function is not used in any mapping.

HORA-33279 Match path filter on a DATE data type column does not filter if the DATE column also includes a time value.

HORA-33219 A custom query with LEFT JOIN as the join syntax generates an Invalid SQL query error.Workaround: Use the LEFT OUTER JOIN statement instead of LEFT JOIN.

30 MDM-HRN-97100-HF3-0002


HORA-33164 After you delete a validation rule, the revalidate process does not recalculate trust for downgraded records.

HORA-33149 When you use the Repository Manager Visual Promote with an HM-enabled schema, the following error occurs:Error SIP-MV-11902 Common HM packages for all Relationship Types … must have same columns in the same order.Workaround: To promote the schema, use a change list instead of the Promote/Visual tab of the Repository Manager tool.

HORA-33085 The Repository Manager does not display a newly registered Operational Reference Store in the repository list.Workaround: From the Repository Manager menu, click Refresh to make a newly registered Operational Reference Store appear in the repository list.

HORA-33061 The Mapping tool does not refresh after a source system is removed.Workaround: From the Mappings menu, click Refresh to force the screen refresh.

HORA-33031 When you select one Hierarchy Manager entity object in the Repository Manager Import tab, all other Hierarchy Manager entity objects are selected.Workaround: Manually clear the entity objects that you do not want to import.

HORA-33018 The metCommand -applyChangeList only accepts the comparison changelist type. The metCommand -applyChangeList does not generate an error if the creation type changelist is the input.Workaround: Do not use the creation type changelist as the input to the -applyChangeList metCommand.

HORA-33006 When an Operational Reference Store is not enabled for hierarchy management, the Hierarchies view does not refresh after you create a relationship base object.Workaround: Navigate away and then back to the Hierarchies tool.

HORA-32908 Match records that are on hold have consolidation_ind=9 and do not merge during automerge.

HORA-32734 The following error message appears in the MDM Hub Console log during metadata validation:ERROR com.delos.cmx.console.gui.ImageSource - ImageSource: Could not load image resources/images//metadatamanager/expand_all.png.Workaround: Ignore this error.

HORA-32555 If you run an environment report on an Operational Reference Store as a user for whom it is not the default database, the following error occurs:SIP-09070: Cannot access database due to connection failureWorkaround: Assign the Operational Reference Store to the user as their default database and then run the environment report, or run environment report with administrative privileges.

HORA-31785 Records with consolidation indicator set to 1 merge into other records after an automerge operation.

MDM-HRN-97100-HF3-0002 31


HORA-31683 If you change a base object column length in the Schema Manager and navigate to another tool without saving the change, the change is not saved. Also, no warning message appears.Workaround: Save changes made to base object column length before you navigate from the Schema Manager to another tool.

HORA-31670 You cannot return to the Data Manager after you run a Synchronize Trust job.Workaround: Manually refresh the Data Manager.

HORA-31646 Schema Viewer does not refresh automatically.Workaround: Go to the Schema Viewer menu and click Refresh to manually refresh the Schema Viewer.

HORA-29052 During manual merges, data stewards can manually override trust scores in the Merge Manager to make record values with low trust scores to win. The winning value with a low trust score finally loses because the refresh BVT procedure does not allow the value with a low trust score to win.Workaround: Do not override a trust score that will finally lose due to the refresh BVT procedure.

HORA-28443 The metadata validation tool does not list the issues that are a result of modifying or renaming entity types in the Hierarchy Manager. The following error occurs during metadata promotion:SIP- 19305: Internal error: No change class of type 1 for HmPackage

HORA-21668 CleansePut SIF ORS-specific APIs fail when system names contains a period, such as "CUST 1.0".Workaround: Use spaces or underscore (_) characters when you register source system names instead of using a period.




Reference Number

Description

HORA-48688 When you export data, the exported data does not include unsaved data.

HORA-48601 Large hierarchies take longer than expected to display in the Hierarchy view.

HORA-48574 When you clear the Show Workflows list, and then click Filter Off, IDD generates a null pointer exception.

HORA-48544 IDD does not decrypt values in the search results.

HORA-48502 When you filter to display tasks with a due date of On Time, tasks with a due date of Overdue also appear.

32 MDM-HRN-97100-HF3-0002

Reference Number

Description



HORA-48409 You cannot restore a deleted child record.

HORA-48286 You cannot edit a child object with the Configuration Manager tool.

HORA-48190 The manual merge task title is not correct.

HORA-48189 IDD does not generate manual merge tasks.

HORA-48120 When you open an entity in a new tab from the Hierarchy view, the effective date is empty.

HORA-47991 You cannot use the date selection tool to change the effective date in the Hierarchy view.

HORA-47983 When you edit a record in the Tasks view, the Cancel button does not appear.

HORA-47941 You cannot merge a record when you hide the Merge Preview panel.

HORA-47933 When your user name contains more than 10 characters, the header height increases.

HORA-47905 You cannot select the Matches view for an entity that does not have match rules.

HORA-47874 When you create an Update With Approval task from search results, the Assign Task dialog box does not always appear.

HORA-47858 When you export data and then save the export profile, an error appears although IDD exports the data and saves the profile.

HORA-47848 You cannot initially select a task when you open the Start page.

HORA-47831 The Actions menu does not appear in the Cross-reference view or in the History view.

HORA-47757 Users who do not have sufficient privileges can access the Actions menu.

HORA-47705 You cannot click the links in the Potential Matches child records.

HORA-47654 When you assign a block of tasks, IDD determines which users are available for each task. If IDD determines a user in not available for a task, IDD does not consider this information when it determines available users for the next task.

HORA-47645 In the Matches view, users can access Action menu items for which they do not have sufficient privileges.

HORA-47626 When you add a match candidate to a record in the Data view, IDD also displays potential duplicates.

HORA-47583 When the Select All check box is enabled in the Matches view and you add match candidates, the match candidates that you add are not selected.

HORA-47571 Empty start dates and end dates appear as ellipses in the Data view.

HORA-47464 When you add a match candidate that IDD also considers to be a match candidate, the record appears twice in the list of potential matches.

MDM-HRN-97100-HF3-0002 33

Reference Number

Description

HORA-47456 The Matches view highlights matching rows after you remove the match candidates.

HORA-47337 IDD does not update the data in the Matches view after you change data in the Data view.

HORA-47333 The Actions menu in the Matches view is missing the Create Task option, the Open for Effective Date option, and the Remove Manually Added Candidates option.

HORA-47331 When you select all match candidates in the Matches view, IDD does not enable the Select All check box. When you enable the Select All check box and then remove a match candidate, the Select All check box remains enabled.

HORA-47322 IDD generates a validation error when you create a one-to-many foreign key relationship from a child record tab. IDD does not create the relationship.

HORA-47247 After you save child record edits in the Cross-reference view, IDD displays the parent record.

HORA-47228 When you edit a value in the cross-reference view, the data view displays the correct value, but the cross-reference view displays an unexpected value.

HORA-46960 After you deploy the IDD application, you must restart the application server for the custom resources to appear in the MDM Hub Roles tool.

HORA-46846 When you export a profile with Export Metadata enabled, the export file does not include row IDs for chile relationship records.

HORA-46014 Users with sufficient privileges cannot edit records in the Cross-reference view.

HORA-44801 When you cancel a Fujitsu Interchange workflow adapter task, pending cross-reference records are not deleted.

HORA-43355 When you click the Details2 tab in the History view, IDD displays an error message.

HORA-43127 When you use the duplicates parameter with a Data view bookmark, the Data view does not display the duplicates.

HORA-39448 When you select an effective date that is not the current date in the Hierarchy view, the Find Duplicates option and the Merge Candidates option are not disabled in the Actions menu.



Reference Number

Description

HORA-48751 When you manually override data with invalid values in the Matches view and then perform a merge, IDD does not display the Merge Preview panel to indicate why the merge failed.Workaround: Click Merge Preview to understand why a merge failed.

HORA-48736 IDD takes longer than expected to respond when you enable the Select All check box in the Matches view and you have many merge candidates.

34 MDM-HRN-97100-HF3-0002

Reference Number

Description

HORA-48609 Hierarchy Manager does not open and the following error message appears in the cmxserver.log file:java.lang.IllegalArgumentException: Comparison method violates its general contract! Workaround: When you start the application server, use the following option:-Djava.util.Arrays.useLegacyMergeSort=true

HORA-48498 When you configure multiple subject area groups on the same base object, automatic task assignment creates tasks for each of the configured subject area groups, but only one task is valid.Workaround: Do not configure more than one subject area group for one base object.

HORA-48451 You cannot configure security filters on encrypted columns.

HORA-48385 IDD does not always enable the Finish button after you successfully import a profile.Workaround: Refresh the page in the browser.

HORA-48106 In IBM DB2 environments, the Jasper report does not display the subject area growth trend for the sample report.

HORA-48056 When you add a child record to a parent object after an ActiveVOS workflow is initiated, you cannot promote the child records.Workaround: Perform Write changes to the database before you perform a task action.

HORA-47948 You cannot change history dates in the date selection tool in Effective Periods view.

HORA-47935 The Data view Actions menu overlaps the Search Form panel.

HORA-47918 In Microsoft SQL Server environments, when you filter ActiveVOS tasks by task type in the inbox, tasks that are not merge tasks do not appear.

HORA-47910 When you click the trust override button in the Merge Preview panel for a sibling lookup, the trust score does not appear.

HORA-47904 After you unmerge a record in the cross-reference view and then go to the Matches view, the merge preview might display values from a previous merge operation.Workaround: Toggle the Merge Preview button to close and then reopen the merge preview.

HORA-47627 The Merge Preview panel does not display child records as a single entity for records with a one-to-one relationship.

HORA-47542 In the Matches view, when the number of child records exceeds the server page size, the child record counter displays the server page size.

HORA-47521 When the Allow non-contiguous effective periods option is disabled for a relationship base object and you try to create a relationship with a gap in the Match view, the relationship is not created, but related entities are removed from the Match view.

MDM-HRN-97100-HF3-0002 35

Reference Number

Description

HORA-47436 After you enter an effective date in the data view that precedes the start date but is the same day as the start date, you cannot use the date selector to select the start date as the effective date.Workaround: Manually type in the date.

HORA-47323 In IBM DB2 environments, when you run a query with a value in a CHAR field that exceeds the maximum number of characters, a modal exception is generated. Informatica Data Director does not provide a descriptive error message.

HORA-47270 Hierarchy manager is slower than expected when you repeat an action multiple times.

HORA-47269 After you approve two tasks, the hierarchy manager is unresponsive.

HORA-46972 A user who is not an administrator can delete the export profile of another user.

HORA-46950 You cannot create a relationship when the package is based on a query that contains a join with a cross-reference table.

HORA-46587 In IDD Configuration Manager, you cannot set the Default Approval Task list back to the default value after you make a selection.Workaround: Edit the value of Default Approval Task in the bdd_config.xml file.

HORA-46553 When you delete an inactive relationship from the relationship flyover, the existing relationship does not appear in the hierarchy view.Workaround: Click Apply for the effective date in the hierarchy view.

HORA-46527 When the hmInactiveRelationshipsAvailable parameter is true and two entities in a group have a foreign key relationship, inactive relationships are not shown in the hierarchy view.Workaround: Specify an effective date in the hierarchy view.

HORA-46478 When you use the ActiveVOS workflow adapter with IDD, the task inbox Task Type filter menu is not populated until you create tasks.

HORA-46458 Case insensitive search filtering does not work for the LAST_ROWID_SYSTEM column.

HORA-46222 In the Create Task dialog box, you can enter text into the list fields.

HORA-46160 If you use system columns that have a date format in the advanced search, no results are returned.

HORA-45243 In Microsoft SQL Server environments, you can extend an entity relationship with a child object where the child object does not exist for a portion of the extended effective period.

HORA-45023 In Microsoft SQL Server environments, data security filters are case-insensitive.

HORA-44766 The entity details in the history view show entities for dates in the past when the entities do not exist.

HORA-43941 The number of frozen columns in the search results is larger than the number of frozen columns configured with the configuration tool.

HORA-43842 Data view displays pending changes.

36 MDM-HRN-97100-HF3-0002

Reference Number

Description

HORA-42411 If you search for a record that is in the pending state and try to add it to the Hierarchy View, the record is not added. The following error is generated:SIP-14229: Either the entity key is not valid, or there are no records that meet the query in the API request GET ENTITYGRAPH. Review the server logs for more details.

HORA-42334 When you import data from a CSV file, Informatica Data Director assigns one-to-one child records an source system value of Admin and a generated primary key, instead of the source system and primary key in the CSV file.

HORA-42262 When you add an entity from a hierarchy view search to the canvas, the entity has the wrong node name in the canvas.

HORA-42137 When you specify an effective date in the hierarchy view, Informatica Data Director considers the inactive relationships when calculating if there are too many relationships to display.

HORA-42069 Hierarchy Manager does not display inactive relationships when you specify the current day as the effective date.

HORA-41999 When you use Internet Explorer to upload a custom Login Provider jar, an error occurs and you cannot upload the file.Workaround: Disable Include local directory path when uploading file to a server in the Internet Explorer security settings.

HORA-41949 When you view inactive relationships for an entity, Hierarchy Manager does not display the number of inactive relationships in the related nodes.

HORA-41458 If the number of records in the Informatica Data Director Hierarchy Manager flyover exceeds the value of sif.api.hm.flyover.max.record.count and you change sorting from ascending to descending, the sort uses a new query instead of the limited results. For example, if an organization has 510 relationships and the limiter is set to 500, an ascending sort displays records 1 to 500. If you change the sort to descending, records 510 to 10 are displayed.

HORA-41362 In Fujitsu Interstage BPM, a merge task remains open after the MDM Hub merges the records.

HORA-41238 Merge tasks that Fujitsu BPM generates do not appear in the Informatica Data Director inbox.

HORA-41226 In Fujitsu Interstage BPM, the inbox can load tasks that do not match the value displayed in the Interstage dashboard.

HORA-41153 If you edit a relationship in Hierarchy Manager and the effective date in Hierarchy View is equal to the relationship start date, an extra relationship appears with an effective period of one day.

HORA-40225 You cannot perform extended search in Informatica Data Director if the default match rule set does not have a fuzzy rule.Workaround: Use the MDM Hub Console to add a dummy fuzzy rule to the default match set.

HORA-39399 When you are viewing only active relationships in the hierarchy view, Informatica Data Director considers the inactive relationships when warning there are too many relationships to display.

MDM-HRN-97100-HF3-0002 37

Reference Number

Description

HORA-39387 The relationship for two pending records remains in a pending state after you approve the records in the relationship.

HORA-39300 The effective period of a child or grandchild of a pending record is displayed as null.

HORA-39286 You cannot edit pending relationships in the Hierarchy View.

HORA-39273 The Hierarchy Manager Change History view does not display events for relationships that you end date or delete.

HORA-39255 In the Hierarchy View, when you change a relationship type the old relationship is deleted instead of being end-dated.

HORA-39222 You cannot view the relationship history even if the user has READ permission on the XREF history table.

HORA-39215 If you view the relationship history after you extend its effective period, incorrect events are displayed.

HORA-39196 Inconsistent results after editing a relationship.

HORA-39129 When you edit a grandchild record to create a version with a gap in its effective period, no warning is displayed. When you save the grandchild record with a gap in its effective period, the following error is generated:SIP-23004: Error in Put process: SIP-28673: Period dates cannot have gaps.

HORA-39117 If a primary object has many-to-many child entities that are enabled for timeline, many-to-many grandchild entities that are not enabled for timeline, and relationship entities that are enabled for timeline, then grandchild records are displayed for an effective date that is not included in the effective period of the relationship.

HORA-39100 Tasks are not sorted in the correct order when you sort tasks by the Owner field.

HORA-39067 In the IDD Configuration Manager, after you delete values in the Maximum number of items to export and Session timeout fields, the values cannot be set again. The fields remain highlighted and a non-informative tooltip is displayed.

HORA-38998 Non-trusted values from active cross-reference records always win, even if PENDING cross-reference records are displayed in Cross References dialog box.

HORA-38989 The Save function is enabled for saving a PENDING record for which effective period is specified. When you try to save the PENDING record, an error is generated.

HORA-38984 When you save changes in the Data View as a user with non-administrative privileges, an error is generated.

HORA-38962 If you add back a chart definition that you removed from the BDDConfig.xml file and import the BDDConfig.xml file into the existing IDD application, the chart does not appear on the IDD Dashboard.

HORA-38804 In the Hierarchy View, the relationship flyover opens slowly for a date other than the current date.

38 MDM-HRN-97100-HF3-0002

Reference Number

Description

HORA-38793 Information displayed in an Entity Details dialog box is inconsistent with the information displayed on a node in the Hierarchy View.

HORA-38792 Null date values are handled inconsistently in the Data View, Hierarchy View, and search functionality. In the Data View, current effective date is applied by default and is inconsistent with the data retrieved by the search functionality.If you open the Hierarchy View from the Data View, effective date that is applied in the Data View is applied to the Hierarchy View as well. You cannot open the Hierarchy View from the Data View for a null date value .

HORA-38789 The Edit Relationship dialog box displays incorrect information.

HORA-38699 When you use the asterisk symbol (*) to filter relationships, the entity filter of the Hierarchy flyover displays incorrect results.

HORA-38625 The paging functionality does not work properly during a page switch in Hierarchy flyover if some relationships are not active in the page from which you switch. The Hierarchy flyover displays duplicate relationships.Workaround: Use <activeRelsOnly>false</activeRelsOnly>.

HORA-38615 If you manually set the effective date for entities for which timeline is not enabled, filtering in Hierarchy flyover is slow.

HORA-38580 You cannot sort by effective dates in the relationship flyover in the Hierarchy view.

HORA-38164 You cannot specify the end date of multiple relationships in a one-step operation.

HORA-38080 The changes made using the Cross References dialog box cannot be saved if timeline is disabled. The following error is generated:SIP-14382: Period start date or end date cannot be specified whentimeline is disabled on a base object . Please review your server log for more details.

HORA-38078 The Use this value instead option amends values in cross-references.

HORA-38077 After timeline is disabled, Unmerge can still be performed for the last two versions.

HORA-38058 Export and Import queries menu items are enabled for users with no rights to create queries.

HORA-38033 The Hierarchy View flyover does not show Rel Start Date or Rel End Date if relationship is active for 1 day.

HORA-38032 An incorrect start date is shown in the Hierarchy View if the start date of a relationship that has been active for 1 day is edited.

HORA-37968 Pending version of a records cannot be opened if an active version exists.

HORA-37948 The Use This Value Instead feature is disabled if the specified effective date does not equal the current date.

HORA-37862 If you configure two different display values for the same base object column, the static lookup list does not display correct values.

MDM-HRN-97100-HF3-0002 39

Reference Number

Description

HORA-37612 The change details for a base object that has timeline enabled does not appear correctly for many-to-many child records.

HORA-37610 When you view History for a base object that has timeline enabled, the Change Details dialog box for a Delete event does not display the changes to the effective period for many-to-many child records.

HORA-37090 In case of base objects that have timeline enabled, when you open a Review task for a record with an effective period in PENDING state and run custom operation, the Available Effective Period list is empty.

HORA-37055 Effective Date calendar is not available in the Show History dialog box in the Hierarchy View.

HORA-36529 Enhanced task context does not work for objects enabled for timeline with nonintersecting active-pending periods. Changed fields are not marked with PENDING indicators and tool tips do not provide the before and after values of the changed fields.

HORA-35606 When you sort data in columns, child, and grandchild records that are not saved are sorted incorrectly.

Informatica Data Controls Known Limitations


Reference Number

Description

HORA-44835 The Delete All Relationship Periods function does not perform a delete operation.

HORA-44834 When cmx.bdd.enable_url_authentication is true, a null pointer exception occurs when open Informatica Data Controls.Workaround: Open the Informatica Data Director login screen before you open Informatica Data Controls.

HORA-42218 You cannot perform an external match.

HORA-40410 The relationship tab appears when you view an entity.

HORA-39318 Hierarchy manager does not warn you when there are too many objects to load in a graph.

Informatica Global Customer SupportYou can contact a Customer Support Center by telephone or through the Online Support.

Online Support requires a user name and password. You can request a user name and password at http://mysupport.informatica.com.

The telephone numbers for Informatica Global Customer Support are available from the Informatica web site at http://www.informatica.com/us/services-and-training/support-services/global-support-centers/.

40 MDM-HRN-97100-HF3-0002

http://mysupport.informatica.com

http://www.informatica.com/us/services-and-training/support-services/global-support-centers/

Informatica MDM Multidomain Edition - 9.7.1 HotFix 3 ... Documentation/3/MDM… · MDM Multidomain...

Documents

Transcript of Informatica MDM Multidomain Edition - 9.7.1 HotFix 3 ... Documentation/3/MDM… · MDM Multidomain...