Informatica MDM Multidomain Edition - 10.0.0 HotFix 2 ......For more information about configuring...

Informatica Corporation MDM Multidomain Edition (Version 10.0.0 HotFix 2)

Release Notes

Informatica Corporation MDM Multidomain Edition Release Notes

Version 10.0.0 HotFix 2August 2015

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

Part Number: MDM-HRN-100000-HF2-0002

Table of Contents

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Chapter 1: Installation and Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Before You Install. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Before You Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Create a Database In IBM DB2 On UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Configure the Application Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Registering the MDM Hub Sample Operational Reference Store On IBM DB2. . . . . . . . . . . . . . . . 8

Change List Promotion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Dropped Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Product Usage Toolkit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Process Server Properties for Smart Search. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Enable Match Population On IBM DB2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

WebSphere Clustered Environments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Hub Server Installation in Console Mode in Oracle Environments. . . . . . . . . . . . . . . . . . . . . . . 10

Hub Server Installation in Console Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Hub Server Installation on a WebSphere Application Server. . . . . . . . . . . . . . . . . . . . . . . . . . 10

Hub Store Installation in Oracle 12C Environments with Multitenant Oracle Containers. . . . . . . . . 11

Upgrade from Version 9.1.0 to 9.5.1 HotFix 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Upgrade from Version 9.5.1 to 10.0.0 in Oracle Environments. . . . . . . . . . . . . . . . . . . . . . . . . 11

Hub Server Upgrade from Version 9.7.1 to 10.0.0 HotFix 1 in IBM DB2/AIX/WebSphere Environments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

MDM Hub Master Database Upgrade from Version 9.7.1 to 10.0.0 HotFix 1 in IBM DB2/AIX Environments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Upgrade Installation for Entity 360 View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

After You Install or Upgrade the Hub Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Chapter 2: MDM Multidomain Edition Version 10.0.0 Hotfix 2. . . . . . . . . . . . . . . . . . . 13Fixed Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

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

Entity 360 Fixed Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Informatica Data Director Fixed Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Smart Search Fixed Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Closed Enhancement Requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Informatica Data Director Closed Enhancements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Known Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

MDM Hub Known Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Informatica Data Director Known Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Entity 360 Known Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Smart Search Known Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Table of Contents 3

Informatica Platform Known Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

ActiveVOS Known Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Chapter 3: MDM Multidomain Edition Version 10.0.0 Hotfix 1. . . . . . . . . . . . . . . . . . . 23Fixed Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23


Composite Objects Fixed Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Composite Services Fixed Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24


Resource Kit Fixed Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Smart Search Fixed Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

MDM Hub Integration with Informatica ActiveVOS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26





Resource Kit Known Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Chapter 4: MDM Multidomain Edition Version 10.0.0. . . . . . . . . . . . . . . . . . . . . . . . . . . 29Fixed Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29



Closed Enhancement Requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

MDM Hub Closed Enhancement Requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Informatica Data Director Closed Enhancement Requests. . . . . . . . . . . . . . . . . . . . . . . . 33



Composite Object and Composite Service Known Limitations. . . . . . . . . . . . . . . . . . . . . . 35

Informatica Data Director Known Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36



MDM Hub Integration with Informatica Platform Known Limitations. . . . . . . . . . . . . . . . . . . 40

Informatica Dynamic Data Masking Known Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . 41

MDM Hub Integration with Informatica ActiveVOS Known Limitations. . . . . . . . . . . . . . . . . 42

Chapter 5: Informatica Global Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

4 Table of Contents

IntroductionThe 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.

v

C H A P T E R 1

Installation and UpgradeThis chapter includes the following topics:

• Before You Install, 6

• Before You Upgrade, 7

• Create a Database In IBM DB2 On UNIX, 7

• Configure the Application Server, 7

• Registering the MDM Hub Sample Operational Reference Store On IBM DB2, 8

• Change List Promotion, 8

• Dropped Support, 8

• Product Usage Toolkit, 9

• Process Server Properties for Smart Search, 9

• Enable Match Population On IBM DB2, 9

• WebSphere Clustered Environments, 10

• Hub Server Installation in Console Mode in Oracle Environments, 10

• Hub Server Installation in Console Mode, 10

• Hub Server Installation on a WebSphere Application Server, 10

• Hub Store Installation in Oracle 12C Environments with Multitenant Oracle Containers, 11

• Upgrade from Version 9.1.0 to 9.5.1 HotFix 1, 11

• Upgrade from Version 9.5.1 to 10.0.0 in Oracle Environments, 11

• Hub Server Upgrade from Version 9.7.1 to 10.0.0 HotFix 1 in IBM DB2/AIX/WebSphere Environments, 11

• MDM Hub Master Database Upgrade from Version 9.7.1 to 10.0.0 HotFix 1 in IBM DB2/AIX Environments, 12

• Upgrade Installation for Entity 360 View, 12

• After You Install or Upgrade the Hub Server, 12

Before You InstallIf you want to install the MDM Hub in a JBoss EAP 6.2.0 environment, ensure that you install JBoss from the .zip file. If you install the MDM Hub where JBoss is installed from a JAR file, the MDM Hub installation fails because of JBoss client JAR files missing from the JBoss installation.

(MDM-916)

6

Before You UpgradeVerify that no subject area name begins with a number. If any subject area name begins with a number, change the name so that it begins with an alphabetic character. If a subject area name begins with a number, the composite object configuration generated by the MDM Hub causes Repository Manager validation errors. If you do not use composite objects at all, you can continue to use subject area names that begin with a number.

HORA-51906

Create a Database In IBM DB2 On UNIXThe MDM Hub distribution includes a script to create the database and associated tablespaces. Before you create the database, perform the following tasks:

1. Open the database.properties file in the following directory:

<MDM Hub distribution directory>/database/bin/db22. Update the db2.storage.path property in the database.properties file with the correct database

storage path.

3. Save and close the database.properties file

4. To run the script to create the database, use the following command: sip_ant.sh create_db

(MDM-6415)

Configure the Application ServerTo enhance the performance of the MDM Hub environment, add the following JVM option to JAVA_OPTIONS in the application server startup script:

• On JBoss, add the option for reserved code cache size.-XX:ReservedCodeCacheSize=256m

• On WebLogic, add the option for reserved code cache size.-XX:ReservedCodeCacheSize=256m

• On WebSphere, add the option for JIT code cache size.-XX:codecachetotal=256m

To use Informatica Data Director, you must add the following JVM option to the application server startup script:

-Dfile.encoding=UTF-8

If you do not add the option, you cannot save records that contain UTF-8 characters in the IDD Data View. The option is also required for smart search to work with Unicode characters.

MDM-6661

Before You Upgrade 7

Registering the MDM Hub Sample Operational Reference Store On IBM DB2

Before you register the MDM Hub sample Operational Reference Store (ORS) on IBM DB2, perform the following tasks.

1. In the C_REPOS_DB_CHANGES repository table, find 2015041601_lsc_remove_primary_key_on_strip.sql and change the status, STATUS_STR to Fail.

2. Open an IBM DB2 command window.

3. Connect to the database as the MDM Hub sample ORS user.

4. Navigate to the following directory:

On UNIX. ..database/resources/database/db2On Windows. ..database\resources\database\db2

5. Run the following commands:db2 -vf debug_print.spdb2 -vf cmx_debug_print_proc.spdb2 -vf db_change_start.spdb2 -vf db_change_end.sp

6. Navigate to the following directory that contains 2015041601_lsc_remove_primary_key_on_strip.sql:

On UNIX. ../resources/database/db_changes/db2/ORSOn Windows. ..\resources\database\db_changes\db2\ORS

7. Run the following command:db2 -vf 2015041601_lsc_remove_primary_key_on_strip.sql

For more information about registering the MDM Hub Sample ORS, see the Informatica MDM Multidomain Edition Installation Guide.

(MDM-5530)

Change List PromotionTo promote a change list to an empty Operational Reference Store, the match column length that the MDM Hub adds to the external match input table must not exceed 4000. The match column length is the sum of the lengths of all base object columns that are sources of the match column and the number of source columns.

The change list promotion fails with the following error if the total length of the match column is greater than 4000:

ORA-00910: specified length too long for its datatype HORA-52116

Dropped SupportEffective in version 10.0.0, support is dropped for the following functionality:

8 Chapter 1: Installation and Upgrade

EJB2 Protocol

The EJB2 protocol is obsolete and you must use EJB3 protocol to communicate with the MDM Hub through the Services Integration Framework (SIF) requests.

IBM ILOG Charts

Effective in version 10.0.0, ILOG charts are not supported for new customers or existing customers who previously licensed IBM ILOG chart software.

Product Usage ToolkitThe Product Usage Tookit is disabled in version 10.0 HotFix 2 and will return in a future release.

Process Server Properties for Smart SearchAfter you upgrade the MDM Hub, by default, the <MDM Hub Installation Directory>\hub\cleanse\resources\cmxcleanse.properties file does not include the following Process Server properties for smart search:

cmx.ss.enabled

Indicates whether to enable smart search. Set to true if you want to enable smart search. Set to false if you want to disable smart search.

zookeeper.tickTime

Length of a single tick, in milliseconds. ZooKeeper uses tick as the basic time unit to regulate timeouts. Default is 2000 ms.

search.provisioning.maxshards

Optional. Indicates the maximum number of copies of data that can be created on a single Apache Solr instance when you index the search data. Default is 1.

To work around the issue, manually add the properties to the cmxcleanse.properties file.

For more information about configuring smart search, see the Informatica MDM Multidomain Edition Configuration Guide.

(HORA-51676)

Enable Match Population On IBM DB2After you install the Process Server in an IBM DB2 environment, you must enable the match population to use for the match rules. To enable match populations, contact Informatica Global Customer Support.

HORA-52288

Product Usage Toolkit 9

WebSphere Clustered EnvironmentsWhen you install the Hub Server in a WebSphere clustered environment, the deployment fails with errors.

The issue appears to be related to IBM issue http://www-01.ibm.com/support/docview.wss?uid=swg1PM97149, which is fixed in WebSphere 8.5.5.3. At time of release, Informatica continues to test this release on WebSphere 8.5.5.3. For updates, contact Global Customer Support.

HORA-51571

Hub Server Installation in Console Mode in Oracle Environments

When you install the Hub Server in console mode in an Oracle environment, the pre-installation summary has missing details. If you choose not to install Informatica Platform, a blank appears instead of the word "No" under the Install Informatica Platform heading of the summary.

HORA-51944

Hub Server Installation in Console ModeYou can install the Hub Server in console mode on UNIX.

When you choose to install the Informatica platform as part of the Hub Server installation process, the prompts for the Informatica platform installation file locations do not appear. If you want to install the Informatica platform, perform the Hub Server installation in the graphical mode or silent mode.

HORA-50891

Hub Server Installation on a WebSphere Application Server

When you install the Hub Server on a WebSphere Application Server, the installation component patchInstallSetup fails.

Workaround: Open the file <WebSphere profile home>/properties/soap.client.props file and increase com.ibm.SOAP.requestTimeout, and then restart the WebSphere server profile. Run patchInstallSetup.bat again.

HORA-52021


http://www-01.ibm.com/support/docview.wss?uid=swg1PM97149

Hub Store Installation in Oracle 12C Environments with Multitenant Oracle Containers

When you install the Hub Store in Oracle 12C environments with multitenant Oracle containers, the installation might fail.

Workaround: Do not use multitenant Oracle containers.

MDM-1491

Upgrade from Version 9.1.0 to 9.5.1 HotFix 1When you upgrade from version 9.1.0 to 9.5.1 HotFix 1, timeline granularity is set to day instead of second.

MDM-1699

HORA-47349

Upgrade from Version 9.5.1 to 10.0.0 in Oracle Environments

When you upgrade the Hub Server from version 9.5.1 to 10.0.0 in an Oracle environment, the upgrade completes successfully, but the following error appears in the log:

19:26:22,012 INFO ImporterRole:44 - ddl: CREATE ROLE PROXY_ROLE ORA-01031: privileges insufficient

You can safely ignore this error.

HORA-51980

Hub Server Upgrade from Version 9.7.1 to 10.0.0 HotFix 1 in IBM DB2/AIX/WebSphere Environments

When you upgrade the Hub Server from version 9.7.1 to 10.0.0 HotFix 1 in IBM DB2/AIX/WebSphere environments, the upgrade fails.

Workaround: Delete the JMS messaging queues and messaging bus, and then upgrade the Hub Server again.

MDM-3172

Hub Store Installation in Oracle 12C Environments with Multitenant Oracle Containers 11

MDM Hub Master Database Upgrade from Version 9.7.1 to 10.0.0 HotFix 1 in IBM DB2/AIX Environments

When upgrading the MDM Hub Master Database from version 9.7.1 to 10.0.0 HotFix 1 in IBM DB2/AIX environments, the upgrade fails if you enter a lowercase MDM Hub Master Database schema name.

Workaround: Enter an uppercase MDM Hub Master Database schema name.

MDM-3171

Upgrade Installation for Entity 360 ViewWhen you upgrade Hub Server, the entity360view.ear sometimes fails to install due to a timed out error.

Workaround: You can run the installation components patchInstallSetup or postInstallSetup again.

Alternatively, run the following command from the infamdm\hub\server\bin folder:

./sip_ant.sh -Dentity360view.ear.dodeploy=true deploy.entity360view-ear

HORA-52008

After You Install or Upgrade the Hub ServerWhen using WebSphere or JBoss, after installing or upgrading the Hub Server, you need to delete temporary files from the application server Temp directory and restart the application server.

HORA-51708


C H A P T E R 2

MDM Multidomain Edition Version 10.0.0 Hotfix 2

This chapter includes the following topics:

• Fixed Limitations, 13

• Closed Enhancement Requests, 16

• Known Limitations, 17

Fixed Limitations

MDM Hub Fixed LimitationsReview the Release Notes of previous releases for information about previous fixed limitations.

The following table describes fixed limitations:

Reference Number

Description

MDM-6038 You cannot log in to the Hub Console on a multinode WebSphere cluster.

MDM-6034 Services Integration Framework (SIF) Put calls fail on a WebSphere cluster environment with two cluster nodes.

MDM-5788 When you use the Hub Console to change the password of the LDAP user, the Use external authentication option is disabled, and the existing password is exposed.

MDM-5775 The automerge job fails with the following error:

ORA-00942: table or view does not exist on insert into T$ESTBLSHMT_LSSO

MDM-5756 The performance of the SQL scripts for inserts into the c_repos_mq_data_change table is poor.

MDM-5737 Updates to cross-reference records on one system change the effective period of the records on another system.

13

Reference Number

Description

MDM-4913 If you update a base object with multiple cross-reference records, the MDM Hub sends multiple messages to the message queue.

MDM-4667 The load job updates one record at a time instead of a bulk update.

MDM-4665 When you run a load job, a null pointer exception is generated.

MDM-4629 Duplicate entries exist in the match table.

MDM-4598 When you run multiple load jobs in parallel with low data volume, one or more load jobs fail with the following exception:

"java.rmi.RemoteException: java.lang.Exception: thread is gone"

MDM-4537 Foreign key update is not the same when cascade unmerge in set and when cascade unmerge is not set.

MDM-4190 Batch jobs require container level transaction SIF API requests.

MDM-3966 The unmerge process generates the following exception:

com.siperian.common.SipRuntimeException

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

HORA-52747, MDM-4006

Load job performance is poor when message triggers exist on multiple columns and sources.

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-52601 An update to a cross-reference record in a source system affects the effective period of a record from another source system.

HORA-50599, MDM-5878

After a postLoad user exit SIF request, the MDM Hub fails to process all records and generates an error.

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

Entity 360 Fixed LimitationsReview the Release Notes of previous releases for information about previous fixed limitations.

14 Chapter 2: MDM Multidomain Edition Version 10.0.0 Hotfix 2


Reference Number

Description

MDM-6331 When you have more than one application based on the same Operational Reference Store, and subject areas with the same name, the Informatica Data Director might create tasks incorrectly. To avoid the generation of tasks with incorrect parameters, set IDD2COCSConverter.prefixCoNames to true in the C_REPOS_DS_PREF_DETAIL table. The Informatica Data Director then uses the subject area name prefixed with the Informatica Data Director application name as the composite object name.

MDM-6291

MDM-5738 When you add a child record to a parent that is Hierarchy Manager-enabled, the effective period dialog box does not appear when you save the record. Because of this, Informatica Data Director saves the period_start_date and period_end_date as null in the database.

HORA-52471, MDM-4560

When you save changes to a business entity when it is pending approval, a null pointer exception occurs.

Informatica Data Director Fixed LimitationsReview the Release Notes of previous releases for information about previous fixed limitations.


Reference Number

Description

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

HORA-52567, MDM-3536

When you switch from form to table view and you have a record selected in the Relationships tab, Informatica Data Director closes unexpectedly.

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

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

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

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

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

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

Fixed Limitations 15

Smart Search Fixed LimitationsReview the Release Notes of previous releases for information about previous fixed limitations.


Reference Number

Description

MDM-2765 When you perform a smart search, the Search workspace does not indicate whether the facets ignored any search results based on the facet.infacount property.

MDM-2227 When you configure additional fields as searchable fields, you must redeploy and restart the Informatica Data Director application.

MDM-574 Smart Search is not recommended if your data exceeds three million records. Higher volumes of data cause slower indexing and search operations.

HORA-52232 The Initially Index Smart Search Data job stops responding.

HORA-52223 The first smart search request takes a long time to return results after you configure smart search and run the Initially Index Smart Search Data job for the first time.

HORA-51945 Smart search requests do not display some records after you run a load job, and you get the following error message in the server log file:SIP-52039: Failed to create a collection for the composite object

HORA-51177 When you perform a smart search, the Search workspace cannot display more than 100 facets for a field.

Closed Enhancement Requests

Informatica Data Director Closed EnhancementsThe following table describes closed enhancement requests:

Reference Number

Description

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

HORA-43488, MDM-6039

When you run a search query, you can decide whether to include the Effective Date field. In the C_REPOS_DS_PREF_DETAIL table, set the property isEffectiveDateIncluded to true to display the current date. Set the property to false to hide the Effective Date field.


Known Limitations

MDM Hub Known LimitationsThe following table describes known limitations:

Reference Number

Description

MDM-6414 When you try to promote a changelist, the Repository Manager generates the following exception:

Unexpected exception when running action 'addCleanseFunction. SIP-10324: There was an unexpected exception when attempting to commit data object(s).Workaround: To ensure promote is successful, use a unicode-enabled database. To verify the character set of the database, enter the following command:

SQL> select * from v$nls_parameters where parameter Like '%CHARACTERSET';

MDM-6263 If you stop the first node in a JBoss clustered environment, the Hub Console generates an exception.

MDM-6116 If you include a package that has the SRC_ROWID column from the landing table when you generate and deploy ORS-specific SIF APIs, the following error is generated:

SIP-14202: Unrecognized data type "IDENTITY" received.Workaround: Do not include the SRC_ROWID column from the landing table in packages. If you need to match records in base objects with the associated landing tables, use the PKEY_SRC_OBJECT cross-reference table column in the package.

Known Limitations 17

Reference Number

Description

MDM-5971 When you try to promote a changelist, the Repository Manager generates the following exception:

Query 'QRY_PARTY_READ' is used by put-enabled package 'PKG_PARTY_READ' but does not support the PUT operation.

Workaround 1: In the change.xml file, change the following tag for 'PKG_PARTY_READ' from <putEnabledIndicator>1</putEnabledIndicator> to <putEnabledIndicator>0</putEnabledIndicator>.Workaround 2: After you promote the changelist, enter the following command to fix metadata validation errors:

update C_REPOS_COLUMN set READ_ONLY_IND=1 where Table_name = 'PKG_PARTY_READ' and READ_ONLY_IND =0 ;commit;

MDM-5886 During the registration of an Operational Reference Store (ORS) in a cluster node, the connection times out.Workaround: When you register an ORS in a cluster node, disable administrative security. You can enable administrative security after you register the ORS in the cluster.To disable administrative security, perform the following tasks:1. Open the standalone-full.xml file in the following location:

On UNIX. <JBoss Installation Directory>/standalone/configurationOn Windows. <JBoss Installation Directory>\standalone\configuration

2. Remove the security-realm attribute of the native-interface element in the file.After the change, the native-interface element appears as shown:<native-interface> <socket-binding native="management-native"/> </native-interface>

Informatica Data Director Known LimitationsThe following table describes known limitations:

Reference Number

Description

MDM-5893 When you import the Informatica Data Director (IDD) configuration XML to use an MDM Hub sample Operational Reference Store (ORS) that was upgraded from version 9.5.1, the following fatal error is generated:

SIP-BV-11005: Invalid role(s) 'DataSteward' in task assignment configurationfor task type'ReviewNoApprove' in subject area 'Person.'Also, after you import the IDD configuration XML, metadata validation for the MDM Hub sample ORS fails.Workaround: In the Hub Console, connect to the MDM Hub sample ORS and access the Roles tool. Acquire a write lock and change the name of the Data Steward role to DataSteward.


Entity 360 Known LimitationsThe following table describes known limitations:

Reference Number

Description

MDM-6595 If you open an update task from the Task Manager and then cancel the task, the OneStepApprovalWorkflow instance faults in ActiveVOS if you use the subject area-based ActiveVOS workflow adapter.Workaround: To avoid a faulted task, open the update task and then cancel the task from the subject area-based task inbox.

MDM-6593 If you manually select another user when you reassign an escalated task type, the task remains in the Task Manager inbox.Workaround: When you reassign a task, select the Auto assign task check box.

MDM-6590 The Task Manager inbox displays tasks that do not belong to current user role.

MDM-6583 In the Task Manager, if you escalate a task that migrated from the Siperian workflow adapter, the task does not automatically assign to the appropriate user. Instead, the task appears in the Task Manager as an available task with an unclaimed status.Workaround: The appropriate user can claim the available task and review the task.

MDM-6553 If you swap the primary and secondary workflow adapters, open tasks do not appear in the Task Manager inbox.

MDM-6493 If you create a task through the composite object-based workflow adapter, the pending changes do not appear in the subject area-based task inbox.Workaround: To view pending changes in the subject area-based task inbox, export and edit the Informatica Data Director configuration file bddConfig.xml. Add the attribute pendingBVT="true" to all task types for review.

MDM-6489 If you acquire a lock on the Operational Reference Store, you cannot generate a schema for composite objects and composite services.Workaround: Release the lock from the Hub Console. If the lock is already released, run the following query on your Operational Reference Store:

truncate table c_repos_schema_write_lock

MDM-6452 In the task inbox, the Task Lineage option does not work for ActiveVOS tasks. The Task Lineage option works for tasks created with the Siperian adapter.

MDM-6451, MDM-6379

After you restart the application server, tasks might not display in the Task Manager inbox for the first user who logs in to an Informatica Data Director application.Workaround: Log out of Entity 360 and then log in again.

MDM-6283 In the Task Manager, the Due Date filter sorts tasks differently depending on which ActiveVOS workflow adapter was used to create the tasks.

MDM-6259 In the Informatica Data Director Configuration Manager, if you change the role assigned to a task in a subject area, the old role remains in composite services configuration.Workaround: Use a database tool to delete the content of the C_REPOS_CO_CS_CONFIG table and generate composite services configuration again.


Reference Number

Description

MDM-6228 If you have an Informatica Data Director application linked to more than one operational reference store, the task inbox in the configurable Start workspace does not display.Workaround: Link just one Informatica Data Director application to one operational reference store.

MDM-6185, MDM-6123

When you open a merge task in Entity 360 view, the options Disclaim and Merge are unavailable.Workaround: Perform a merge task through the IDD view.

MDM-6181 When you add data to a business entity and then click Apply, the Hub Server does not clean and correctly format the data.Workaround: For your data to appear in the correct format in Entity 360, click the Save button.

MDM-6119 If you assign a task to a specific user, you cannot reassign the task to a group.

MDM-5715 On Internet Explorer 9 and 10, if you group search results by type, you cannot then expand the search results.Workaround: Use Internet Explorer 11 or alternative browsers such as Chrome, Safari, or Firefox.

MDM-5525 If you import any changelist from 9.7.1 HF3 and it fails to promote, an error that refers to virtualInd is generated.Workaround: Remove all occurrences of the tag <virtualInd>false</virtualInd> from the changelist and then save the file. Retry the promote changelist.

MDM-5354 When you save a record and cleanse transformation fails, an empty validation error appears.

MDM-5353 If you are logged in as the "admin" user, you cannot create a new business entity.Workaround: In the Hub Console, assign a role with the appropriate permissions to the user "admin".

MDM-5333 Match and merge is not supported for business entity child records. If you do try to add match records to a child record, you might corrupt the data.

MDM-2584 Unable to sort tasks by Task ID, Task Type or Task Status in Task Manager.

Smart Search Known LimitationsThe following table describes known limitations:

Reference Number

Description

MDM-5974 In a clustered application server environment, the smart search does not work if you configure the process servers that are part of the cluster to use the SolrCloud feature of Apache Solr.Workaround: Configure a single process server in one of the cluster nodes for smart search, or install and configure process servers outside the application server cluster to use the SolrCloud feature for smart search.

MDM-5785 A smart search request does not facet the dates that are earlier than 1970.


Reference Number

Description

MDM-4355 A smart search request searches only the fields that match the language of the search string and does not support cross-language search.

MDM-3220 The Entity 360 view displays a float value after rounding the value to the first decimal place. A smart search request does not return the rounded float value when you search for it.

Informatica Platform Known LimitationsThe following table describes known limitations:

Reference Number

Description

MDM-724 If you add a column to the staging table, the corresponding mapplet ports are disconnected, and you cannot run the mapping. If you manually connect the affected ports and run the mapping, the following error is generated:

The object is not valid. Choose "Go to Validation Log" to view validation errors or choose "Cancel" to cancel the run

ActiveVOS Known LimitationsThe following table describes known limitations:

Reference Number

Description

MDM-6591 If you created a Siperian BPM unmerge task before the upgrade, you cannot perform the unmerge from the Informatica Data Director data view after the upgrade.

MDM-6517 You cannot open tasks that were created with the composite object-based ActiveVOS workflow engine in the subject area-based task inbox.Workaround: Configure the subject area-based ActiveVOS workflow engine as the primary workflow engine.

MDM-6423 It is possible to set a workflow engine as the primary workflow engine and the secondary workflow engine simultaneously.Workaround: Ensure you do not configure the primary workflow engine and the secondary workflow engine for the same workflow engine.

MDM-6291 Existing subject-area based ActiveVOS tasks do not appear in the subject area-based task inbox after you upgrade.

MDM-6290 Existing subject-area based ActiveVOS tasks do not appear in the Task Manager after you upgrade.

MDM-6065 The Task Manager displays tasks that are claimed by another user with similar rights. You can edit tasks that are claimed by another user if you have access.Workaround: Do not edit tasks that are claimed by another user.


Reference Number

Description

MDM-5052 After you configure the MDM Hub for ActiveVOS in a WebSphere environment, the first test connection takes longer than expected. Also, after you restart the application server, the first task action takes longer than expected.

MDM-537 When you configure ActiveVOS security settings and create a task from Informatica Data Director, the following error message appears:

(401)UnauthorizedWorkaround: Workaround: Configure a trusted user to facilitate secure communication between the MDM Hub and ActiveVOS.


C H A P T E R 3

MDM Multidomain Edition Version 10.0.0 Hotfix 1


• Fixed Limitations , 23


Fixed Limitations

MDM Hub Fixed LimitationsReview the Release Notes of previous releases for information about previous fixed limitations.


Reference Number Description

MDM-1042 Java-based cleanse functions fail.

MDM-925 The ExternalMatch API, Promote API, and ValidateFK API do not complete successfully. An error message is not generated.

MDM-666 When you run the batch unmerge job, the consolidation indicator is not set to 4 for the child record when explode_node_ind is set to 1 for the child base object.

MDM-511 Cannot install the Hub Server on WebLogic environments.

MDM-407 Users can log into the Hub Server when the Lightweight Directory Access Protocol (LDAP) server is not running.

MDM-167 (HORA-52167)

Custom batch jobs do not run.

MDM-166 (HORA-52234)

The merge batch job takes longer than expected on Microsoft SQL Server environments.

23


MDM-160 When you configure a message trigger to promote a pending cross-reference record, the repository table is updated incorrectly.

MDM-75 When you unmerge a record from a task, the unmerged records do not appear as matches.

Composite Objects Fixed LimitationsReview the Release Notes of previous releases for information about previous fixed limitations.



MDM-2174 A lookup base object cannot be the root node of a composite object.

Composite Services Fixed LimitationsReview the Release Notes of previous releases for information about previous fixed limitations.


Reference Number

Description

MDM-2132 The MDM Hub regenerates the Service Data Object (SDO) schema when a new user is created.

MDM-1163 The WriteCO composite service fails to create a Hierarchy Manager relationship.

MDM-927 When you use a composite service to delete a child record that has a many-to-many relationship with a parent record, the composite service fails and an error occurs.

MDM-88 When you use a composite service to delete a child record that has a many-to-many relationship with a parent record, the composite service fails and an error occurs.

MDM-79 When you use a composite service to create a grandchild record, the composite service fails and an error occurs.




Reference Number

Description

MDM-2802 Custom logos do not appear in the header.

MDM-2177 The conversion of an Informatica Data Director application configuration to a composite object and composite service configuration fails if any match key is a foreign key that refers to a ROWID_OBJECT column.

MDM-2175 The composite object schema takes longer than expected to generate.

MDM-2173 When Informatica Data Director Configuration Manager converts an IDD application configuration to a composite object configuration, the incorrect relationship types are applied.

MDM-1127 Hierarchy Manager graphs do not successfully export to JPG files.

MDM-1126 (HORA-50049)

The hierarchy view does not appear for LDAP users.

MDM-1044 Merge tasks are not created when a data type of CHAR(14) is a subtype filter.

MDM-1043 In My Workflows, cannot see the tasks created by user.

MDM-924 Smart Search results and Entity 360 view take longer than expected to appear.

MDM-922 Logging into Informatica Data Director takes longer than expected.

MDM-87 After logging in to Informatica Data Director by using LDAP authentication, when you attempt to open an application that uses Entity 360, the application does not open and an error is displayed.

MDM-82 When you open a task and edit a record in the task, an error occurs.

MDM-81 You cannot approve a pending change from the task workflow.

Resource Kit Fixed LimitationsReview the Release Notes of previous releases for information about previous fixed limitations.



MDM-382 In the Resource Kit, the IDDConfig_ActiveVOS.xml file does not have cleanse configured for the Person subject area. The IDDConfig_ActiveVOS.xml file also includes the wrong create workflow.

MDM-163 (HORA-49003)

The Resource Kit contains the incorrect version of the SSA-Name3 library files.

Smart Search Fixed LimitationsReview the Release Notes of previous releases for information about previous fixed limitations.



Reference Number

Description

MDM-2581 When you run the Initially Index Smart Search Data batch job, the Batch Viewer does not display the status of the job as Completed even after the job successfully indexed all the data.

MDM-2165 In a WebLogic environment, the process server does not create collections when you enable smart search on the process server.

MDM-1322 The Initially Index Smart Search Data batch job fails in an Oracle and WebLogic environment.

MDM-1165 (HORA-52188)

Smart search requests do not return results after you configure a field as a searchable field and run the Initially Index Smart Search Data job.

MDM-963 Smart search request fails for specific search strings.

MDM-962 When you enter a filter value in an integer type field and filter the results, you get the following error:Exception Occurred while getting query the constructor.

MDM-921 When you filter the search results based on dates, you do not get any filtered results.

MDM-920 Smart search results do not display the facet count of the fields that you configure as facets.

MDM-818 When you delete a record from the database, the record details are not deleted from the smart search index.

MDM-804 (HORA-52195)

Smart search requests might fail against large data set.

MDM-352 When you enable smart search on the process server, the process server does not create collections if you set the sollr.allowAdminConsole property to true.

MDM-332 (HORA-51939)

When you enter a filter value in a CHAR type field and filter the results, the Search workspace displays incorrectly filtered results.

MDM-193 (HORA-52189)

Smart search requests return the following error message after you remove a searchable column from a subject area layout in the Configuration Manager:[SearchService_30027] Exception occured while getting query the constructor

MDM-80 When you register an Operational Reference Store in the Hub Console, if the database host name that you specify contains uppercase characters, the batch jobs fail.

MDM Hub Integration with Informatica ActiveVOSReview the Release Notes of previous releases for information about previous fixed limitations.



Reference Number

Description

MDM-1197 When ActiveVOS is configured for two Operational Reference Stores, users cannot see new tasks in their list of tasks it the subject area name only exists on one Operational Reference Store.

MDM-953 The ActiveVOS connection test fails.

MDM-931 When a user logs into Informatica Data Director, the ActiveVOS tasks of the user who was previously logged in appear in the task inbox.

MDM-787 The MDM Hub installer does not validate the ActiveVOS credentials.

Known Limitations


Reference Number

Description

MDM-1578 When you delete an active cross-reference record in the Data Manager tool in the Hub Console, the record is deleted but an error occurs.Workaround: Ignore the error.



MDM-2229 When you expand a record with an intFld value, an error occurs and the Entity 360 view stops responding.



Reference Number

Description

MDM-2765 When you perform a smart search, the Search workspace does not indicate whether the facets ignored any search results based on the facet.infacount property.

MDM-2644 After you enable smart search on the process server, the application server log file does not include any relevant error message if the collection creation fails due to insufficient memory.

MDM-1799 When you search for a negative value, the smart search request returns the positive and negative matching values.

MDM-1651 In the Search workspace, you cannot enter a decimal filter value in a float type field.

Resource Kit Known LimitationsThe following table describes known limitations:

Reference Number

Description

MDM-2136 The sample login provider file for Google single sign-on does not work as of April 20, 2015 when Google dropped support for OpenID 2.0.


C H A P T E R 4

MDM Multidomain Edition Version 10.0.0


• Fixed Limitations, 29

• Closed Enhancement Requests, 33


Fixed Limitations

MDM Hub Fixed LimitationsThe following table describes fixed limitations:

Reference Number

Description

HORA-52070 The Stage job for MDM_sample fails in IBM DB2 and Microsoft SQL Server.

HORA-51811, HORA-51670

When you open the Merge Manager, the following errors appear:SIP-09070: Couldn't get merge information recordsSIP-10322: java.lang.NullPointerException

HORA-51410, HORA-51052

The Enable Distinct feature does not work correctly when PKEY columns pass through three or more levels of functions.

HORA-51178, HORA-50867

Tokenization fails with the following error:SIP-16013: SQL Loader failed while loading file hub3457252008751464588.tmp-keyf0.dat. Return code is 2.

HORA-51044, HORA-50265

When the MDM Hub manages a high number of users, the Users and Groups tool responds very slowly.

HORA-50936, HORA-48825

When you use the SIF API to make a SearchQuery call on a base object, the call does not return effective dates for the BVT.

29

Reference Number

Description

HORA-50771 When you run stage jobs from Batch Groups, a connection leak occurs.

HORA-50770, HORA-49881

When you run an automerge job on Party, the process fails with an Optimistic Lock Failure.

HORA-50769, HORA-49687

Issues with match and merge. For EXACT Match query, the indexes are not created properly. When NULL to NULL Matching is not enabled, the match job still matches records with a NULL value.

HORA-50725 With an iDB Oracle datasource, the unmerge API returns the wrong rowid for unmergeReturn.

HORA-50723, 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-50701, HORA-50628

In SQL Server 2012, the Operational Reference Store validation process runs very slowly.

HORA-50686, 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-50614 When you test an IDQ function, the test generates a run-time exception.

HORA-50340, HORA-49276

The autopromote batch job and cmxsm.auto_promote run much slower than the load process.

HORA-50295, HORA-48145

When running a searchMatch request with a recordsToReturn value, the number of records returned is correct, but the records do not represent the highest match scores.

HORA-50275, HORA-49275

When you use the CleansePut API, the put operation fails with the following error:Unique Value of the Custom Unique Column in the inserted XREF was found in other BO.

HORA-50131, HORA-45172

When you set the landing table column to not nullable, the ORS validation process returns the following error:SIP-MV-10231 for RAW/REJ/PRL/OPL that the column needs to be nullable

HORA-50099, HORA-49824

After you define the task assignment userexit, the task assignment daemon returns errors.

HORA-50052 If you use SIF DELETE to delete pending cross-reference records from an active parent record, active child records are incorrectly soft deleted.

HORA-50050 If you create a base object with a fuzzy and exact match rule and then run the match, the match process fails with the following error:SQL0552N (-552) SQLERRMC=GPM_ORS;IMPLICIT CREATE SCHEMA

HORA-50048, HORA-49442

The UpdateRel API runs very slowly.

HORA-50043, HORA-49667

When sequences are loaded into the cache, a Numeric Overload error appears in the cmxserver log file. ()

30 Chapter 4: MDM Multidomain Edition Version 10.0.0

Reference Number

Description

HORA-49863, HORA-49802

When a validation rule exists on columns that are missing in the stage table, the validation process returns the following message as an error when a warning would be sufficient.SIP-MV-11214

HORA-49853, HORA-48938

The SIF API generation process runs very slowly.

HORA-49011, HORA-47956

Before deleting a message queue, delete any message triggers that are pointing to the message queue.

HORA-48999, HORA-48172

The documentation for fuzzy match rules incorrectly states that, when the Match Purpose is Individual, the Match Column list can contain either ID or Date. In fact, the list must contain both the ID and the Date.

HORA-48979, HORA-47808

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

HORA-48966, HORA-48234

In UNIX environments, the Operational Reference Store upgrade fails.

HORA-48955, 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-48953, HORA-48038

When you run stage jobs, the MDM Hub generates the following error intermittently:java.util.ConcurrentModificationException

HORA-48946, HORA-48624

When a parent table has a child REL table with two foreign keys to the parent table, and you run automerge, the automerge process fails with a deadlock condition.

HORA-48917, 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-48887, HORA-47809

The CleansePut API does not process carriage returns in data.

HORA-48868, 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-48817, HORA-46496

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

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

HORA-41453 L10N DE: Invalid characters are displayed in the sqlplus window when creating an Operational Reference Store.

HORA-41429 Static view creation fails for base objects that have many columns.

HORA-39369, HDBT-26691

When you approve a task, column errors occur in the server log even when the column does not have validation rules.


Reference Number

Description

HORA-37945 When a base object has a putable package, the SearchMatch option is missing from ORS-specific API.

HORA-33267 Javadoc for PromotePendingXREFs SIF API includes the following incorrect information:When a list of column names is provided in the request, only the columns represented by the list of names will be kept on theXREF promoted to the ACTIVE state. Data for columns that are not specified will be lost after the promotion.The actual behavior is that all column values are retained for the promoted XREF.

HORA-31713 In the Data Manager, when you update a column value that meets a validation rule, trust score does not downgrade.



Reference Number

Description

HORA-51565 When you configure data security for auto task assignment, task assignment fails.

HORA-51424 Unable to add hierarchy code and rel type code into the layout of child that is defined as many-to-many and is Hierarchy Manager enabled. When you save the configuration, the following error appears:HM columns are already added to CO/CS definition.

HORA-51035, HORA-50278

After changing the LAST_UPDATE_DATE column to Putable and updating the record by using CleansePut, you cannot pass a value to the LAST_UPDATE_DATE column.

HORA-50664, HORA-49628

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

HORA-50051, HORA-49531

The Mark for Save feature creates a new cross-reference record instead of updating the effective period for the existing cross-reference record.

HORA-42411, HORA-42556

If you search for a record that is in the pending state and then try to add it to the Hierarchy View, the record is not added. The MDM Hub generates an error.

HORA-41999 When you use Internet Explorer to upload a custom Login Provider jar, an error occurs and you cannot upload the file.


Closed Enhancement Requests

MDM Hub Closed Enhancement RequestsThe following table describes closed enhancement requests:

Reference Number

Description

HORA-50935, HORA-45122

With timeline enabled, if you load multiple versions in the same batch, the following error appears:Active Record will create gap.

HORA-48957, HORA-47237

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

HORA-48890, 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-48876, 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-48872, HORA-48230

Implemented encryption in the following ways:- Encrypt data before sending data from IDD to the Hub server- Encrypt data before executing the cleanse functionA sample of DataEncryptor is included in the resource kit. You can use it to encrypt and decrypt CSV files.

HORA-47926 In JBoss, you can set the OFF-SET to support uniqueness of ports when multiple standalone profiles are running under the same server installation. The MDM Hub sets the JBoss remoting port dynamically.

Informatica Data Director Closed Enhancement RequestsThe following table describes closed enhancement requests:

Reference Number

Description

HORA-51461 After updating an IDD application to use the ActiveVOS Server that is installed with the Hub Server in v.10.0.0, an administrative user can view completed tasks for all users.

Closed Enhancement Requests 33

Known Limitations


Reference Number

Description

HORA-52267 The MDM Hub does not support the import of a change list created in one database type into the repository of another database type. For example, you cannot import a change list created in Oracle into a Microsoft SQL Server repository.

HORA-52147 When you use change lists with custom queries to promote changes to metadata, the change list promotion might fail.Workaround: Remove the Operational Reference Store name from the tables that you use in custom queries.

HORA-52123 Enabling state management for a base object that has custom packages does not resolve Repository Manager validation error SIP-MV-10252.Workaround: Drop the custom packages and then enable state management.

HORA-52103 When you register an Operational Reference Store in the Hub Console, if the database host name that you specify contains period (.) or uppercase characters, the batch jobs fail.Workaround: Do not use the IP address or the fully qualified domain name of the remote database as the database host name. Use the host name of the remote database as the database host name without fully qualifying the name. Ensure that the database host name does not contain uppercase characters.

HORA-52062 The MDM Hub does not support case-sensitive database collation for Microsoft SQL Server.

HORA-52061 The MDM Hub does not support the Hard Delete Detection feature for IBM DB2 or Microsoft SQL Server.

HORA-52060 The MDM Hub does not support custom validation rules for IBM DB2 or Microsoft SQL Server.

HORA-52027 When using iDB Oracle, a user with the Security Access Manager (SAM) Proxy Role for an Operational Reference Store has access to functions that are not intended for the role. In particular, a user with the Proxy Role can access the MET promote, the Promote button, and the Import button.

HORA-52023 After creating an ORS and applying a changelist from a previous version, the Base Object Multi Thread Batch Ind property is set incorrectly to 0.Workaround: You can set this property to a value of 1 from the Hub Console.

HORA-52017 If you add a new user in the Hub Console and immediately change the user password, the user cannot log in with the new password.Workaround: Instruct the user to log in with the existing password and then change the password.

HORA-51844 In a Microsoft SQL Server environment, the GetOneHop API request might stop responding.Workaround: For the repository table C_REPOS_SEARCH_RESULT_STATE, set LOCK_ESCALATION to DISABLED.


Reference Number

Description

HORA-51710 On high loads with multiple cleanse servers involved, the automerge job sometimes fails.Workaround: Restart the application server and then run the automerge job again.

HORA-51596 When you run a match job with network speeds of 10 Gbps in full duplex mode, the match job does not complete.Workaround: Set the network speed to 1 Gbps in full duplex mode.

HORA-51439 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 include accented letters or letters with diacritical marks.Workaround: Special characters in keys can cause issues with key duplication. Avoid use of special characters in a primary key. Also, key duplication can occur if you have some primary keys in uppercase and some in lowercase. Ensure all primary keys are in one case.

HORA-51097 When cmx.server.automerge.threads_per_job=1, the automerge process merges conflicts up to a maximum of 1,000 records and cleans the remaining records from the _MTCH table.Workaround: To merge all records, set the value of this property to 20 in the cmxserver.properties file:cmx.server.automerge.threads_per_job=20

HORA-50724 After you install the MDM Hub, the job metrics do not appear in the Hub Console when you run a stage job for the first time. The job metrics appear in the Hub Console for all subsequent stage jobs.

HORA-50068 When you view the Hub Console in the Chinese language, the date format appears in English.

Composite Object and Composite Service Known LimitationsThe following table describes known limitations:

Reference Number

Description

HORA-51932 When you perform a partial promote of components related to composite objects in Repository Manager, validation errors might occur.Workaround: Promote the complete composite object configuration.

HORA- 51931 When you promote a searchable composite object configuration in Repository Manager, validation errors occur.Workaround: Promote the complete composite object configuration that the searchable composite object configuration is associated with.

HORA- 51886 When you run a read composite service for a deleted grandchild record, the composite service call does not return data.

HORA-51824 When you promote a REST service in Repository Manager, validation errors occur.Workaround: Promote the composite services configuration.


Reference Number

Description

HORA-51494 The MDM Hub does not prevent you from creating a child record that does not share the same effective period as the parent record.Workaround: Ensure you maintain timeline consistency within a composite object when you create a record.

HORA-51488 When you read a pending record, the composite service does not return the record and an error occurs.Workaround: Add ?recordStates=ACTIVE,PENDING to the REST URL.

HORA-51470 When you update records in a composite object, more exceptions occur than are expected.

HORA-51437 When you specify a source key and source system to delete a record, the composite service deletes the base object record instead of a cross-reference record.

HORA-51285 The MDM Hub does not prevent you from deleting a record that has an active child record.

HORA-49806 Repository Manager does not handle conflicts correctly during composite object configuration promotion. When multiple objects in a composite object have the same name but their hubObject values refer to different base objects, Repository Manager generates validation errors but successfully promotes the composite object configuration.Workaround: Use unique names for objects that do not refer to the same base objects.

Informatica Data Director Known LimitationsThe following table describes known limitations:

Reference Number

Description

HORA-52088 Some Informatica Data Director menu items are not localized.

HORA-51906 Subject Area names cannot begin with a number.

HORA-51575 After you install Microsoft Windows update KB2998527, you cannot select the first Wednesday of the year in the date selection calendar.

HORA-50579 When you use the Chrome browser, you cannot log in to Informatica Data Director with saved credentials.

HORA-49401 For IBM DB2 Operational Reference Store databases, Task Administration occasionally fails.Workaround: Increase the maximum number of client connections allowed for each database partition through the following command:

db2 UPDATE DBM CFG USING MAX_CONNECTIONS 300 MAX_COORDAGENTS 300

HORA-43191 In Configuration Manager, when you edit a subject area configuration to set the edit style of a column to Checkbox but then cancel the change, a null pointer exception occurs when you open a new subject area entity form.



Reference Number

Description

HORA-52227 If you restart the application server while logged in to the Entity 360 view, you cannot log back in after you refresh the page.Workaround: Enter a valid Entity 360 view URL in your browser.

HORA-51963 If you perform a search in the Entity 360 view and apply an integer field filter on the search results, Informatica Data Director generates an error.

HORA-51951 In WebLogic environments, after you log in to the Entity 360 view and then clear your browser cache, you cannot log in to the Entity 360 view again.Workaround: Clear the cookies from your browser.

HORA-51893 When you view a pending record in the Entity 360 view, there is no indication that the record is pending.

HORA-51879 The GetOneHop component displays entity label data that comes from the cross-reference table instead of the base object.

HORA-51869 Entity 360 access control depends on the base object of the root composite object, not on Subject Area permissions.

HORA-51864 In the Entity 360 view, the GetOneHop Component does not sort related entities.

HORA-51796 If an Operational Reference Store used in Informatica Data Director has a searchable configuration that is invalid, then you cannot log in to the Entity 360 view.Workaround: Ensure all searchable configurations are valid for each Operational Reference Store used in Informatica Data Director.

HORA-51484 In the Entity 360 view, when you open Hierarchy Manager for a record with 100 relationships, Informatica Data Director generates an error.Workaround: To fix Java compatability issues, set the system property java.util.Arrays.useLegacyMergeSort to true.

HORA-51446 In the Entity 360 view, the GetOneHop Component does not show more than 100 relationships for a record. There is no pager button to view more relationships.Workaround: Configure the data view component with a value for size that is smaller than the GetListLimit value in C_REPOS_DATABASE.

HORA-51426 After you set the system property IDD2COCSConverter.prefixCoNames to true, the Entity 360 view configuration fails.

HORA-51298 The Entity 360 view is disabled by default in Informatica Data Director.Workaround: In the cmxserver.properties file, set the cmx.e360.view.enabled property to true. After you update the server properties, you must validate the schema and then redeploy the Informatica Data Director application. Then restart the Hub Console for the change to take effect.

HORA-51203 In the Entity 360 view, the Person.Organization.org record does not appear. After you select a child record of Person.Organization, the Person.Organization.org appears.


Reference Number

Description

HORA-51201 In the Entity 360 view, the details for a base object do not appear correctly for many-to-many child records.

HORA-50993 To configure the Entity 360 view, you need direct access to the C_REPOS_COMPONENT_INSTANCE table to insert data into it. There is no tool in the user interface of Informatica Data Director to configure the components for the Entity 360 view.

HORA-50596 You cannot log in to Informatica Data Director application in Entity 360 view.Workaround: Release the lock in the MDM Hub Console and clear browser cookies.

HORA-50581 The Entity 360 matches component does not display null values correctly.

HORA-50578 The Twitter component loads more slowly than expected.

HORA-50565 When you open Entity 360 view from an entity component, the count in the Matches component is incorrect.Workaround: Open the entity view from search results.

HORA-50562 Entity 360 components in the right hand panel are not formatted correctly.

HORA-50561 If a composite object root node record does not contain data, the child record is not formatted correctly.

HORA-50534 The Entity 360 cross-reference record component does not display pending cross-reference records. The Entity 360 cross-reference record component only displays active cross-reference records.

HORA-50370 You can log in to Entity 360 before Informatica Data Director starts.


Reference Number

Description

MDM-574 Smart Search is not recommended if your data exceeds three million records. Higher volumes of data cause slower indexing and search operations.

HORA-52232 The Initially Index Smart Search Data job stops responding.Workaround: Set the job status to incomplete, restart the application server, and run the Initially Index Smart Search Data job after a few minutes.

HORA-52223 The first smart search request takes a long time to return results after you configure smart search and run the Initially Index Smart Search Data job for the first time.

HORA-52195 Smart search requests might fail against large data set.


Reference Number

Description

HORA-52192 If the composite objects do not include a field named displayName, the Name column in the Search workspace displays random field values when you perform a smart search.Workaround: To set a field for the Name column, use a database tool to open the C_REPOS_CO_CS_CONFIG table and set the displayName property of the composite objects to an appropriate field in the BLOB data of the SEARCHABLE_CO configuration type.

HORA-52189 Smart search requests return the following error message after you remove a searchable column from a layout in the Configuration Manager:[SearchService_30027] Exception occured while getting query the constructorWorkaround: Stop the application server, delete the <MDM Hub Installation Directory>\hub\cleanse\solr folder, and delete all the files in the ZooKeeper data directory that you set when you configured the Process Server. Restart the application server, run the Initially Index Smart Search Data job after a few minutes, and perform the smart search.

HORA-52188 Smart search requests do not return results after you configure a field as a searchable field and run the Initially Index Smart Search Data job.Workaround: Stop the application server, delete the <MDM Hub Installation Directory>\hub\cleanse\solr folder, and delete all the files in the ZooKeeper data directory that you set when you configured the Process Server. Restart the application server, run the Initially Index Smart Search Data job after a few minutes, and perform the smart search.

HORA-52166 In the Informatica Data Director application, if a non-admin user who has the READ privilege on all the subject areas and base objects performs a smart search, the hierarchy view and the data view of a result do not display any data. The non-admin user cannot create a task for a result.

HORA-52165 If a non-admin user who does not have any privilege performs a smart search, the Informatica Data Director application displays an unclear error message.

HORA-52156 After you create an inactive relationship between two entities and run the Initially Index Smart Search Data job, a smart search request returns the entities that have inactive relationship.

HORA-52121 Smart search requests fail in a WebSphere environment if you specify the application server SSL port as the HTTP port when you add a process server.Workaround: Use a non-SSL port as the HTTP port of the application server. The default application server SSL port is 9443, and the default non-SSL port is 9080.

HORA-52117 After you perform a smart search, the Search workspace cannot display more than 2000 results from each composite object when you scroll through the workspace to view the results.

HORA-51945 Smart search requests do not display some records after you run a load job, and you get the following error message in the server log file:SIP-52039: Failed to create a collection for the composite objectWorkaround: Stop the application server, delete the <MDM Hub Installation Directory>\hub\cleanse\solr folder, and delete all the files in the ZooKeeper data directory that you set when you configured the Process Server. Restart the application server, run the Initially Index Smart Search Data job after a few minutes, and perform the smart search.

HORA-51939 Smart search results are not correctly filtered when you enter a filter value in a CHAR type field and filter the results.Workaround: Change the data type of the field to VARCHAR or add spaces to the string when you enter a filter value so that the total character count of the filter value matches the defined field length of the field.


Reference Number

Description

HORA-51758 Smart search requests do not display the merged or unmerged records after you manually merge or unmerge records in the Data Manager.Workaround: Run the Initially Index Smart Search Data job to add the merged or unmerged records to the index and perform the smart search again.

HORA-51752 The Initially Index Smart Search Data job might return incorrect metrics if you run the job more than once.

HORA-51650 When you use a date format such as 11-20-2014 or 11\-20\-2014 as a search string and perform a smart search, the request returns no results. If you use a date format such as Nov 20 2014, the request returns results that match 20, 2014, or November.

HORA-51543 Smart search requests do not return results for a non-admin user.

HORA-51177 When you perform a smart search, the Search workspace cannot display more than 100 facets for a field.

HORA-51074 When you add or edit a Process Server, the Hub Console does not validate the value that you specify for the ZooKeeper data directory.

HORA-50968 After you perform a smart search, when you scroll through the Search workspace to view the next batch of results, you cannot scroll up to view the previous batch of results.Workaround: Perform the smart search again and scroll through the workspace to view the required results.

MDM Hub Integration with Informatica Platform Known LimitationsThe following table describes known limitations:

Reference Number

Description

HORA-52304 If you perform the stage process in the Informatica platform, you cannot use the ClenasePut API.

HORA-52303 If you perform the stage process in the Informatica platform, the MDM Hub cannot detect the records that are hard-deleted in source systems.

HORA-52297 When you enable the option to preserve the source system keys for Informatica platform staging, source system keys are not preserved.

HORA-52296 When you perform Informatica platform staging, you cannot set up delta detection and audit trails for the staging table data.

HORA-51360 When you perform Informatica platform staging, source records that indicate that the last updated date is in the future are inserted into the LAST_UPDATE_DATE column in the staging table.Workaround: Configure transformations for the stage process that can reject records that indicate that the last updated date is in the future.

HORA-51362 After you open a logical data object in Informatica Developer (the Developer tool), the Save button becomes available before you make any changes.


Reference Number

Description

HORA-51075 When you open a logical data object in the Developer tool, the following warning appears:

Model Contains Data Objects from Informatica Analyst.Workaround: You can ignore the warning.

HORA-50574 During the Model repository synchronization process, the MDM Hub does not create a mapping with a logical data object to write to. To run Informatica platform staging, create a mapping that includes a physical data object as the source, a logical data object as the output, and a mapplet for cleanse operations.

HORA-50573 When you synchronize the Model repository with the MDM Hub, the synchronization process creates a customized data object and a relational data object. Do not use either the customized data object or the relational data object as direct targets in any mapping that you define.

HORA-50500 When you synchronize the Model repository with the MDM Hub, the synchronization process creates a logical data object read mapping and logical data object write mapping. If you open one of these logical data objects in the editor and then save them, the objects disappear from the Model repository.Workaround: You can ignore the issue.

HORA-50480 You cannot use the same mapping to transfer data from multiple source systems.

MDM-1516 When you edit, add, or delete a staging table column, the corresponding mapplet ports are disconnected.Workaround: Manually connect the affected ports.

Informatica Dynamic Data Masking Known LimitationsThe following table describes known limitations:

Reference Number

Description

HORA-51568 In Microsoft SQL Server environments, when you try to add a record to a base object that has been blocked by Dynamic Data Masking, the MDM Hub generates the following error:

An unknown error occurred.Workaround: Restart the Dynamic Data Masking service and unregister the Operational Reference Store. Then restart the JBoss application server. In the Dynamic Data Masking management console, remove the current port and add a different listening port. Finally, in the MDM Hub, register the Operational Reference Store and set Dynamic Data Masking to the new port.

HORA-51170 To use Dynamic Data Masking in the MDM Hub, you must have Dynamic Data Masking 9.6.0 and Emergency Bug Fix 14590 installed. Earlier versions of Dynamic Data Masking are not compatible with the MDM Hub.


MDM Hub Integration with Informatica ActiveVOS Known Limitations

The following table describes known limitations:

Reference Number

Description

HORA-51899 In the Task Inbox, task filters do not work as expected.- Title filter. Non-exact match does not work. For example, if you have a task with the title abc1

and you filter by abc, the abc1 task is not found.- Due Date Status filter. The On time value does not work. All tasks are always displayed.- Select Task Type from dashboard. No tasks are displayed.- Due Date filter. All tasks are always displayed.

HORA-51898 In the Task Inbox, unexpected values appear in the Task Type filter list. For example, the list contains only the Review No Approve task type, but the Task Inbox contains tasks with other task types.

HORA-51896 When you configure multiple Operational Reference Stores to use the ActiveVOS workflow engine, the total tasks count in the IDD Task Inbox is incorrect for a particular Operational Reference Store. The tasks count shows the total tasks count across all Operational Reference Stores.

HORA-51895 ActiveVOS tasks created in one Operational Reference Store are visible in other Operational Reference Stores for the admin user.


C H A P T E R 5

Informatica Global Customer Support

You 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/.

43

http://mysupport.informatica.com

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

Date post:	22-Mar-2020
Category:	Documents
Upload:	others
View:	22 times
Download:	0 times

Informatica MDM Multidomain Edition - 10.0.0 HotFix 2 ......For more information about configuring...

Documents