informatica mdm multidomain edition for oracle - 9.0.1 hotfix 4 - … documentation... · 2016. 7....

MDM Multidomain Edition for OracleVersion 9.0.1 HotFix 4

Release Notes October 2014

Copyright (c) 1998-2014 Informatica Corporation. All rights reserved.

ContentsIntroduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

End of Support Notice. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

HotFix Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Post Hub Server Update Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Installing the Hub Server HotFix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Installing the Cleanse Match Server HotFix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Installing the Database HotFix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Installing the Resource Kit HotFix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Closed Enhancement Requests and Fixed Bugs 9.0.1 HotFix 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

MDM Hub Closed Enhancement Requests and Bug Fixes (9.0.1 HotFix 4). . . . . . . . . . . . . . . . . . . . 10

MDM Hub Emergency Bug Fixes (Post-HotFix 3). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

IDD Closed Enhancement Requests and Bug Fixes (9.0.1 HotFix 4). . . . . . . . . . . . . . . . . . . . . . . . . 11

IDD Emergency Bug Fixes (Post-HotFix 3). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12







MDM Emergency Bug Fixes (Post 9.0.1 HotFix 1). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16




Known Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Known Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Informatica Global Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

MDM-HRN-90100-HF4-0003 1

IntroductionThe Informatica MDM 9.0.1 HotFix 4 (Oracle) Release Notes contain procedures for applying the Hub Server update, the Cleanse Match Server update, the database update, and the Resource Kit update to an existing Informatica MDM installation. These release notes also provide important information about closed enhancement requests, fixed limitations, and known limitations. Do not apply this HotFix without carefully reading this document.

End of Support NoticeThis release of MDM Multidomain Edition is approaching the end of its lifecycle.

The following table summarizes the end of support details for all active releases of MDM Multidomain Edition:

Version End of Support End of Extended Support

9.0.x December 31, 2015 December 31, 2016

9.1 December 31, 2015 December 31, 2016



9.7.x June 30, 2017 June 30, 2018

For more information about product support policies and product end of life notices, see the Informatica GCS Guide to Services, Policies and Procedures and the End of Life (EOL) and Extended Support Notices page at https://mysupport.informatica.com/community/my-support/support-statements/end-of-life-and-extended-support-notices.

HotFix InstallationRefer to the Platform Availability Matrix (PAM) for this release for details of the supported platforms. The PAM specifies the exact versions and combinations of database, operating system, application server, and other environment components that are supported. The MDM Multidomain Edition 9.0.1 HotFix 4 (Oracle) PAM is available on the Informatica customer support portal.

MDM Hub 9.0.1 Oracle GA must be installed before applying this HotFix. New customers who are installing MDM Hub 9.0.1 for the first time should refer to the Informatica MDM Hub 9.0.1 Installation Guide, the Informatica MDM Hub 9.0.1 What's New document, the Informatica MDM Hub 9.0.1 Release Notes, and the Informatica MDM Hub 9.0.1 Upgrade Guide for complete installation information.

The HotFix 4 installation requirements vary for different customer types:

2 MDM-HRN-90100-HF4-0003

https://mysupport.informatica.com/docs/DOC-3015

https://mysupport.informatica.com/community/my-support/support-statements/end-of-life-and-extended-support-notices

https://mysupport.informatica.com/community/my-support/support-statements/end-of-life-and-extended-support-notices

New customers

Install MDM Hub 9.0.1 Oracle GA, then apply the MDM Hub 9.0.1 Oracle GA HotFix 4 (the Hub Server, Cleanse Match Server, Database, and Resource Kit updates) on top of MDM Hub 9.0.1 Oracle GA. The HotFix 4 installation also applies HotFix 1 fixes, HotFix 2 fixes, HotFix 3 fixes, and the Emergency Bug Fixes (EBFs).

Existing customers on MDM Hub 9.0.1 Oracle, any EBFs, and any HotFix level

Apply the MDM Hub 9.0.1 GA Oracle HotFix 4 (the Hub Server, Cleanse Match Server, Database, and Resource Kit updates) on top of MDM Hub 9.0.1 Oracle GA, any EBFs, and any HotFix.

Existing customers on XU SP2 Patch B Rollup1 GA, XU SP2 Oracle Patch B Rollup1 HF30, and any HotFix level

Upgrade to MDM Hub 9.0.1 Oracle GA, then apply the MDM Hub 9.0.1 GA Oracle HotFix 4 (the Hub Server, Cleanse Match Server, Database, and Resource Kit updates) on top of MDM Hub 9.0.1 Oracle GA.

Existing customers neither on XU SP2 Patch B Rollup1 nor on XU level

Upgrade to XU SP2 Oracle Patch B Rollup1 GA, then upgrade to MDM Hub 9.0.1 Oracle GA, then apply the MDM Hub 9.0.1 GA Oracle HotFix 4 (the Hub Server, Cleanse Match Server, Database, and Resource Kit updates) on top of MDM Hub 9.0.1 Oracle GA.

Post Hub Server Update Tasks

Perform the following tasks after installing the Hub Server update.

For Customers Using Message Triggers in the Schema

1. Restart the application server.

2. Log into the Hub Console.

3. Regenerate the configured JMS schemas or ORS-specific APIs for each ORS.

4. Restart the application server.

For Customers Using Informatica Data Director (IDD)

Perform the following steps to modify the MessagesBundle*.properties files.

1. Export the IDD configuration.

2. In all the MessageBundle*.properties files, remove the asterisk symbol (*) from the following keys:

• task_assign_comments

• task_create_add_comments_field_label

3. Upload the modified bundles into IDD using the option Import to existing IDD application.

MDM-HRN-90100-HF4-0003 3

Improving IDD Performance

Effective in version 9.0.1 HotFix 4, you can configure the number of parallel threads to increase performance when IDD calculates the Best Version of the Truth (BVT). The default number of parallel threads is 1.

Considerations When Setting the Number of Parallel Threads

You must consider different factors unique to your environment when you set the number of parallel threads.

Consider the following factors, ordered by importance, when you set maxParallelBvtThreads:

• The number of available CPU cores and general system resources. The more cores and resources you have, the higher you can set the number of parallel threads.

• The number of concurrent IDD users. The number of parallel threads you set is the number of parallel threads for each user. The total number of threads is the number of parallel threads you set multiplied by the number of concurrent IDD users.

• The expected number of pending records in a Review task. When you open a Review task, IDD calculates the BVT for each of the pending records in parallel. IDD determines the number of pending records in the Review task based on the value you set for maxParallelBvtThreads. If the number of pending records is equal to the value of maxParallelBvtThreads, IDD calculates the BVT for all records in parallel.

Configuring the Number of Parallel Threads

To configure the number of parallel threads, add the maxParallelBvtThreads parameter to the C_REPOS_DS_PREF_DETAIL table and set the number of parallel threads.

Gradually increase the number of parallel threads and then test the results to determine the optimal value for maxParallelBvtThreads. Set a relatively low number for maxParallelBvtThreads and do a performance test and load test. You can increase maxParallelBvtThreads if you notice an improvement in performance after each increase.

1. In SQL*Plus, connect to cmx_system.

2. To add the maxParallelBvtThreads parameter to the C_REPOS_DS_PREF_DETAIL table and set the number of parallel threads, run the following command in SQL*Plus:

insert into C_REPOS_DS_PREF_DETAIL (ROWID_DS_PREF_DETAIL , ROWID_DS_PREF , NAME , VALUE)select rowid_ds_pref , rowid_ds_pref , 'maxParallelBvtThreads' , '<number_of_parallel_threads>'from C_REPOS_DS_PREF where name = '___SYSTEM_PREFERENCES_ROOT___';

COMMIT;

4 MDM-HRN-90100-HF4-0003

Installing the Hub Server HotFix

Install the Hub Server HotFix using the following steps:

1. Copy the Hub Server HotFix executable file to your local disk.

• For Windows: hub_hotfix_install.exe• For UNIX: hub_hotfix_install.bin

2. Set the PATH environment variable using the following commands:

• For Windows: PATH=<infamdm_home>\server\jre\bin;%PATH%• For UNIX: PATH=<infamdm_home>/server/jre/bin:$PATH

3. Run the executable file from your local disk to begin installation. If you are on a WebLogic clustered environment, run the file using the following commands:

• For Windows: hub_hotfix_install.exe -DSIPERIAN_INSTALL_PREREQ_VALIDATION=false• For UNIX: hub_hotfix_install.bin -DSIPERIAN_INSTALL_PREREQ_VALIDATION=falseThe Introduction screen appears.

4. Click Next.

The Choose Install Folder screen appears with a default installation location selected.

5. Click Choose... to select the Hub server installation location where you want to apply this HotFix, if necessary. Click Restore Default Folder to reset to the default installation location if necessary.

6. Click Next.

If your application server is WebLogic, the WebLogic Password screen appears. Otherwise, the Deploy screen appears.

7. If the WebLogic Password screen appears, enter the WebLogic password. Click Next.

After the WebLogic password has been confirmed, the Deploy screen appears.

8. Perform one of the following actions from the Deploy screen:

• If you are in a non-clustered environment, select Yes, run the script during installation and click Next.

• If you are in a clustered environment, select No, I will run it myself later and click Next.

The Pre-Installation Summary screen appears.

9. Verify the information on the Pre-Installation Summary screen. Click Previous to return to previous steps in the installation and review or make changes, if necessary.

10. Click Next.

The Installing Informatica MDM Hub Server HotFix screen appears. When the installation is complete, the Install Complete screen appears.

11. Click Done.

The Install Complete screen closes.

12. If you are in a clustered environment, perform steps 13 and 14. Otherwise, proceed to step 15.

13. Repackage the EAR file.

MDM-HRN-90100-HF4-0003 5

• In the Windows terminal, go to <infamdm_home>\server\bin and execute the following command: sip_ant.bat repackage.

• In the UNIX terminal, go to <infamdm_home>/server/bin and execute the following command: sip_ant.sh repackage.

14. Once the EAR is repackaged, manually deploy the new EAR through the application server admin console.

15. Stop the application server.

16. Copy siperian-api.jar to all client application machines if you have any applications that call the MDM Services Integration Framework (SIF) API.

17. Start the application server.

The Hub Server upgrade is complete.

Installing the Cleanse Match Server HotFix

Install the Cleanse Match Server HotFix using the following steps:

1. Copy the Cleanse Match Server HotFix executable file to your local disk.

• For Windows: hub_cleanse_hotfix_install.exe• For UNIX: hub_cleanse_hotfix_install.bin

2. Set the PATH environment variable using the following commands:

• For Windows: PATH=<infamdm_home>\cleanse\jre\bin;%PATH%• For UNIX: PATH=<infamdm_home>/cleanse/jre/bin:$PATH

3. Run the executable file from your local disk to begin installation. If you are on a WebLogic clustered environment, run the file using the following commands:

• For Windows: hub_cleanse_hotfix_install.exe -DSIPERIAN_INSTALL_PREREQ_VALIDATION=false

• For UNIX: hub_cleanse_hotfix_install.bin -DSIPERIAN_INSTALL_PREREQ_VALIDATION=falseThe Introduction screen appears.

4. Click Next.


5. Click Choose... to select the Cleanse Match Server install location where you want to apply this HotFix. Click Restore Default Folder to reset to the default installation location if necessary.

6. Click Next.

If your application server is WebLogic, the WebLogic Password screen appears. Otherwise, the Deploy screen appears.

7. If the WebLogic Password screen appears, enter the WebLogic password. Click Next.

After the WebLogic password has been confirmed, the Deploy screen appears.

8. Perform one of the following actions from the Deploy screen:

• If you are in a clustered environment, select No, I will run it myself later and click Next.

6 MDM-HRN-90100-HF4-0003

• If you are in a non-clustered environment, select Yes, run the script during installation and click Next.


9. Verify the information on the Pre-Installation Summary screen. Click Previous to return to previous steps in the installation and review or make changes, if necessary.

10. Click Next.

The Installing Informatica MDM Hub Cleanse Match Server HotFix screen appears. When the installation is complete, the Install Complete screen appears.

11. Click Done.


12. If you are in a clustered environment, perform steps 13 and 14. Otherwise, proceed to step 15.

13. Repackage the EAR file.

• In the Windows terminal, go to <infamdm_home>\cleanse\bin and execute the following command: sip_ant.bat repackage.

• In the UNIX terminal, go to <infamdm_home>/cleanse/bin and execute the following command: sip_ant.sh repackage.

14. Once the EAR is repackaged, manually deploy the new EAR through the application server admin console.

15. If you are using the Address Doctor cleanse engine and have not applied 9.0.1 HotFix 1, manually upgrade the AddressDoctor library by performing the steps described in the following files:

• For Windows: <infamdm_home>\cleanse\lib\upgrade\libupdate_readme.txt• For UNIX: <infamdm_home>/cleanse/lib/upgrade/libupdate_readme.txt

16. Stop and then start the application server.

The Cleanse Match Server upgrade is complete.

Installing the Database HotFix

Install the database HotFix using the following steps:

1. Backup your customized user exit stored procedures: cmxue_pack.sql and cmxue_body.sql.

2. Copy the database HotFix executable file to your local disk that is running Oracle client software.

• For Windows: sip_db_hotfix_install.exe• For UNIX: sip_db_hotfix_install.bin

3. Run the file from your local disk to begin installation.

The Introduction screen appears.

4. Click Next.


5. Click Choose... to select an empty folder other than the default installation location, if necessary. Click Restore Default Folder to reset to the default installation location.

MDM-HRN-90100-HF4-0003 7

6. Note the installation directory. Click Next.

The Choose Shortcut Folder screen appears.

7. Set the product icon options as required. Click Next.


8. Verify the information on the Pre-Installation Summary screen. Click Previous to return to previous steps in the installation and review and make changes, if necessary.

9. Click Next.

The Installing Informatica MDM Database HotFix screen appears. When the installation is complete, the Install Complete screen appears.

10. Click Done.


11. From the terminal window, change to the bin folder in the installation directory noted in Step 6.

For example: cd <db_installation_dir>/bin.

12. Execute the following command:

• For Windows systems, run sip_ant.bat updatedatabase_hotfix_400.

• For UNIX systems, run sip_ant.sh updatedatabase_hotfix_400.

13. Enter the following information when prompted:

• Oracle Connection Type for the Master database

• Master database host name

• Master database port number

• Master database Service or SID name (as applicable)

• Oracle Net connect identifier for the Master database

• Master database user name

• Master database user password

• CMX database user name

• CMX database user password

• Oracle Connection Type for the ORS database

• ORS database host name

• ORS database port number

• ORS database Service or SID name (as applicable)

• Oracle Net connect identifier for the ORS database

• ORS database user name

• ORS database user password

If you want to apply this HotFix to another ORS schema, proceed to step 14, otherwise, proceed to step 17.

14. Execute the following command to update another ORS schema:

8 MDM-HRN-90100-HF4-0003

• For Windows systems, run sip_ant.bat updateorsdatabase_hotfix_400.

• For UNIX systems, run sip_ant.sh updateorsdatabase_hotfix_400.

15. Enter the following information when prompted:

• Oracle Connection Type for the ORS database

• ORS database host name

• ORS database port number

• ORS database Service or SID name (as applicable)

• Oracle Net connect identifier for the ORS database

• ORS database user name

• ORS database user password

16. Repeat steps 14 and 15 for each additional ORS schema.

17. If you are using Batch Unmerge in your environment:

a. Copy the files cmxum_pack.plb and cmxum_body.plb to a location on your local disk. Note this location.

b. Connect to the ORS database using SQL*PLUS.

c. Execute the following commands in SQL*PLUS, substituting [PATCH_DIR] with the location noted in Step 17a. Ensure the commands are entered in the following order.

@[PATCH_DIR]\cmxum_pack.plb@[PATCH_DIR]\cmxum_body.plb

18. If you have not installed HotFix 2 and you are using Hard Delete Detection in your environment:

a. Copy the file MRM_HARD_DELETE_DETECT.sql to a location on your local disk. Note this location.

b. Connect to the ORS database using SQL*PLUS.

c. Execute the following command in SQL*PLUS, substituting [PATCH_DIR] with the location noted in Step 18a.

@[PATCH_DIR]\MRM_HARD_DELETE_DETECT.sql19. Manually recompile invalid database objects, if necessary.

The database upgrade is complete.

Installing the Resource Kit HotFix

If you have not installed HotFix 3, install the Resource Kit HotFix using the following steps:

1. Back up the existing siperian-bdd.jar files in the following locations:

• For Windows: <resourcekit_home>\samples\BDDUserExit\lib• For UNIX: <resourcekit_home>/samples/BDDUserExit/lib

2. Copy the HotFix siperian-bdd.jar file to the following locations:

• For Windows: <resourcekit_home>\samples\BDDUserExit\lib• For UNIX: <resourcekit_home>/samples/BDDUserExit/lib

3. Back up the existing siperian-api.jar files in the following locations:

MDM-HRN-90100-HF4-0003 9

• For Windows: <resourcekit_home>\deploy\lib• For UNIX: <resourcekit_home>/deploy/lib

4. If you have installed Hub Server HotFix, copy the following files:

• For Windows: Copy the siperian-api.jar file to <resourcekit_home>\deploy\lib on the server and to all client application machines, if applicable.

• For UNIX: Copy the siperian-api.jar file to <resourcekit_home>/deploy/lib on the server and to all client application machines, if applicable.

Closed Enhancement Requests and Fixed Bugs 9.0.1 HotFix 4

MDM Hub Closed Enhancement Requests and Bug Fixes (9.0.1 HotFix 4)

HORA Number

Bug Description

36658 In WebLogic environments, siperian-api.jar is not in the following locations:- In Windows: <infa_install_directory>hub\server\lib- In UNIX: <infa_install_directory>/hub/server/lib

37120 The Hub allows you to add a filter when you have not selected a match path, resulting in a null pointer exception during Metadata Manager export.

37280 SearchMatch API calls of type DBFILTERED do not include a NO_EXPAND hint.

37221 When you create a record from a load job, the Hub does not update C_REPOS_MQ_DATA_CHANGE the same way as when you create a record from Data Manager.

37906 A long base object name that results in a VARRAY of more than 200 characters results in ORA-066502.

38199 The system reads the XSD files you generate for ORS-specific SIF APIs in native encoding which generates additional NULL symbols at the end of the files.

38402 For large and complex schemas, bulk unmerge results in errors.

38498 The default parallel thread for the maxParallelBvtThreads parameter is not 1.

38499 The Best Version of the Truth (BVT) calculation takes longer than required for schemas with no trust rules or validation rules.

10 MDM-HRN-90100-HF4-0003

MDM Hub Emergency Bug Fixes (Post-HotFix 3)

HORA Number Bug Description

35438 In JBoss environments, a repository snapshot causes JBoss memory leaks and JBoss startup issues.

36791 DBFILTERED-type SearchMatch API calls do not handle exact match rules correctly.

36810 In some environments, Metadata Manager validation fails.

36821 DBFILTERED-type SearchMatch API calls cause a memory leak.

38459 A Metadata Manager promote results in an error for large change lists.

IDD Closed Enhancement Requests and Bug Fixes (9.0.1 HotFix 4)

HORA Number

Bug Description

36521 IDD does not support HTTPS.

36779 Errors and the wrong column layout occurs when you click the Apply button with a customer schema.

36855 You can edit a non-editable field when you view cross references.

36901 IDD displays the dependent lookup column value instead of the display value when you revert and cancel an edit of the parent lookup value.

37054 Lookup-enabled fields do not show description values in the Merge candidate search results page.

37212 IDD displays a null pointer exception for a subject area entity that has a Hierarchy Manager relationship for which the user has no permissions.

37375 IDD always selects the first search result regardless of which search result you choose when you search for a person from the Assign Task screen.

37668 Hidden fields are visible in the 1-1 child subject area.

37874 IDD does not display an error message if you enter a field value that the cleanse function does not consider as valid.

38016 An IndexOutOfBounds exception occurs when you run a query with attributes common to all subject areas.

38112 The Find Duplicates function returns incorrect information if a parent subject area and child subject area share the same column name when the child column name is on the match path.

38696 The cleanup process after multimerge does not clean up the correct tasks.

MDM-HRN-90100-HF4-0003 11

IDD Emergency Bug Fixes (Post-HotFix 3)

HORA Number

Bug Description

34428 IDD falsely identifies some graphs as having too many relationships to display in Hierarchy View.

36437 In some environments, a java.lang.ArrrayIndexOutOfBoundsException occurs when you click the Search button.

36574 The deleted attribute value reappears when you delete an attribute value and then edit and approve a change to another attribute in the same record,.

36664 The TaskHandler user exit does not update a child column upon approval. Instead, the TaskHandler user exit creates a pending XREF.

36975 You lose your changes when you use a SIF API outside IDD to create a task and then update the child record and approve the task within IDD.

38066 You cannot use the numeric key pad to enter numbers.

38157 Open Review task performance is slower than expected.



HORA Number

Description

35651 SearchMatch does not return results if the match column is a date.

35673 SearchMatch takes longer than expected to complete when the fuzzy search terms are non-selective, such as common names.The new MatchType DBFILTERED addresses this issue.

35768 A backfill executes when SearchQuery is run on packages that are based on an XREF table.

35785 Hierarchy Manager validation results in an error when a child base object has an alias name.

35791 Revalidating a BO with CM_DIRTY_IND set to 1 results in an error when API Batch Interoperability is enabled.

35896 Cannot open packages when launching the Hub Console from a URL in some environments.

36180 Running more than one Auto Match and Merge job in parallel results in an error.

36224 Promoting a large number of pending XREFs results in an error.

12 MDM-HRN-90100-HF4-0003

HORA Number

Description

36392 Metadata Manager migration results in an incorrect column order in the STRP tables.Regenerate match tokens on base objects configured for fuzzy matching after applying this HotFix to fix any existing column order issues.

36397 Oracle hints in SQL statements decrease batch job performance.

36493 Metadata Manager validation results in a null pointer exception in some environments.

36544 Hub is not able to initialize the Security Access Manager cache.

SearchMatch using the DBFILTERED MatchType

The DBFILTERED MatchType increases performance when a fuzzy search based on a nonselective term, such as Name="JOHN", also provides values for exact match columns. Nonselective fuzzy search terms provide excessive search results which cause SearchMatch to take longer than expected to complete. When the MatchType is DBFILTERED, SearchMatch performs in one of two ways:

• If the fuzzy search term is selective, for example, JONATHAN LIVINGSTONE, SearchMatch functions as it does when MatchType is set to BOTH. Initial filtering is performed using the match key ranges generated by the Hub, and then additional filtering is performed by the Cleanse Match Server using the exact match columns. This reduces the number of database joins required and provides optimal SearchMatch performance for selective fuzzy search terms.

• If the fuzzy search term is nonselective, for example, JOHN, initial filtering is done in the database on the exact match columns and match key ranges. This results in fewer records being returned to the Cleanse Match Server for matching than would occur using the MatchType AUTO or BOTH. This provides optimal SearchMatch performance for nonselective fuzzy search terms.

Consider the following when using the DBFILTERED MatchType:

• A DBFILTERED match cannot be performed using the following types of exact match columns:

- Exact match columns that have match subtype, non-equal matching, null matching, or segment matching enabled.

- Exact match columns that are based on a concatenation of base object columns.

• Ensure the lock on the schema has been released. API performance decreases when the schema is locked.

• DBFILTERED SearchMatch performance decreases as the number of fuzzy match rules increases. Create a match rule set to use specifically for DBFILTERED SearchMatch that is limited to the match rules essential for database filtering.

• Ensure low cardinality (preferably 1:1) between the base object providing the match key and the exact match columns used for filtering to increase database filtering performance.

• Add custom column indexes to some of the exact match columns used for filtering to improve database filtering performance. Use as few custom column indexes as possible to avoid decreasing batch job performance.

MDM-HRN-90100-HF4-0003 13


HORA Number

Description

34882 Duplicate ID for a component exception occurs intermittently in some environments.

35425 User exit cannot retrieve the grandchildren of a new child record.

35432 The incorrect user is assigned a task when the user list is sorted.

35702 Raw records are not displayed properly in Safari.

35858 Non-editable columns that are populated by cleanse functions cannot be saved to the base object.

35864 Changes made in the Resolve Merge Conflict window do not change in the base object.

35935 The grandchild record does not update when you create a new child record.

35971 An inconvenient amount of whitespace exists between Label and Field in the subject area.

36015 Foreign key column hyperlink disappears after modifying BDDConfig.xml to automatically populate columns.

36023 User account name is not completely visible in Internet Explorer.

36157 View Entity Details does not display new changes to the base object in Informatica Data Controls (IDC).

36272 IDD merge does not complete in some environments.

36437 Clicking on the search button results in an exception in some environments.



HORA Number

Description

33237 If a Base Object with a pending ROWID has one pending XREF, ROWID_OBJECT has an empty value when PromotePendingXrefs API is called.

33850 Data validation tool configuration returns with errors.

34203 SearchQuery error when filter criteria contains special characters.

34866 If a cleanse job in a batch process fails, the stage job is still executed, resulting in records not being staged.

14 MDM-HRN-90100-HF4-0003

HORA Number

Description

35143 Updating a look-up table description causes a cascade update on the child table during a load job, taking a long time.

35186 The Cleanse function does not migrate properly. Promoting changes from the source to the target does not promote changes successfully for an existing function on the target side because the literals are trimmed internally in Cleanse function comparison.

35238 ZDT process backfills the Validation Control Table (VCT), increasing time required for migration process.Now, revalidate job backfills the VCT, so migration process is not impacted.

35338 Invalid identifier error occurs when a PUT package that includes an EXCLUDE_FROM_MATCH column is opened in Merge Manager.

35377 Search APIs (SearchQuery, SearchHMQuery, SearchMatch, SearchLookupValues) have TransactionAttributeType set to REQUIRED instead of SUPPORTS. This increases processing time unnecessarily because a transaction is not required for these APIs.

35390 PUT call causes full table scans, increasing time for query to complete.Now, hints are not used for API calls.


HORA Number

Description

33239 Saving a record throws a timeout exception. SIF calls are limited to a 300 second transaction time.This transaction time is now configurable.

33671 Editing a relationship throws a stack trace.

33928 A sibling reference is unable to display the lookup display name as configured in config.xml. Instead the ID value is displayed.

34567 In table view, a one-person record with multiple address results in error ORA-01427: 'single-row subquery returns more than one row' when a sort is initiated by clicking on a column heading.The list of records in Address child now sorts without an error.

34571 Opening a record with grandchild subject area values results in a null pointer exception.

34637 When a new record is created in IDD with an empty validation rule field, the trust value in Hub Data Manager is null, even if there are validation rules that state the trust should only be downgraded instead of being set to null.

34644 Cannot view SRC_LUD column.

34882 User gets exception when trying to view Search results in either Hierarchy Manager canvas or Data View screen.

35165 User with read-only permissions is able to edit a task that was rejected after being submitted for approval.

MDM-HRN-90100-HF4-0003 15

HORA Number

Description

35172 Unable to Export a search result with a large number of records.

35174 A record with many relationships takes longer than expected to open in Hierarchy View.

35198 Merge dialog shows incorrect trust values.PreviewBVT and Get requests now use the same numeric type. Correct trust values are now shown in Merge dialog.

35202 After a Merge, the ROWID_OBJECT value in the trust dialog and in the data view are not the same.

35203 IDD displays incorrect ROWID_OBJECT in Override Merge window when merging two records.

35237 In a subject area containing child and grandchild subject areas, if the user performs the following steps:1. Create a new subject area by entering new values,2. Create a new child subject area by entering new values,3. Create a new grandchild subject area then,4. Try to save the subject areas created in steps 1 through 3.An error occurs and the grandchild record is not added.

35276 If you have an object with matches pending, an error occurs when you try to sort by clicking on a column heading in the Potential Matches tab.

35303 Cannot log into IDD after completing a batch job in MDM Hub and then restarting the application server.

35518 IDD applications cannot be accessed if Metadata Manager validation is in an unknown state or validation errors exist. This is an inconvenience when running in development mode.

MDM Emergency Bug Fixes (Post 9.0.1 HotFix 1)

EBF Number

HORA Number

System Description

1 33247 IDD If the column of a Subject Area is set to hidden, the hidden column appears in the Cross Reference screen and the data is misaligned.

33404 IDD Do not see target ROWID_OBJECT using afterEverything method.

2 33093 Hub Error in Data Manager when a date value in a base object column is updated.

33532 Hub Cleanse job does not able to start due to a null pointer exception while retrieving a list of Hub systems.

33388 Hub A null pointer exception occurs when trying to do a metadata promotion from source to target through Metadata Manager.

3 33466 Hub CMXMM Unmerge performance is very slow.

33151 Hub CMXUM is missing. User cannot run a batch Unmerge.

16 MDM-HRN-90100-HF4-0003

EBF Number

HORA Number

System Description

33127 Hub In Merge Manager, the manual merge insert hint considers ROWID_OBJECT, resulting in a query that takes longer than normal to complete.

4 33712 Hub SearchMatch call over a network is not optimized and is taking longer than expected.

5 33531 Hub An Authenticate call using the wrong password returns a blank page instead of an error message for LDAP users.

33597 Hub Unable to deploy custom button in Data Manager console.Now works as outlined in the Deploying Custom Buttons procedure in the Informatica MDM Hub Administrator Guide.

33734 IDD Relationships are not displayed in History View.

33609 IDD With UNIX server and Windows client, cannot import file using Internet Explorer. Receive the following error: File name does not match the required file name.

33553 Hub Values in tables are inconsistent because Java is casting from Float to Double.Now fixed so Java is casting through a String, so there is no loss of precision.

33555 Hub JMS event schema (XSD) generated by the Hub does not include schemaLocation in the import statements.Fixed, but xml generated from delete-related events still causes errors when validating against XSD file.

33789 IDD A user is unable to see updates done by another user.

6 32816 IDD Child subject area in table view has large null column.Fixed so column size is smaller.

33653 IDD When charts are enabled in IDD, java.lang.ClassCastException occurs.

33790 IDD When Explorer View is exported to JPEG, a blank file is saved.

33791 IDD With non-English characters enabled (NLS_CHARACTERSET=UTF8): when query results are exported to a CSV file, non-English characters are replaced by stray characters.Fixed so the CSV file is now created in UTF8 encoding. The file must be opened in Excel using the "Data - from Text" option.Old CSV files exported prior to applying the fix will still have issues with stray characters.If old CSV files are resaved as UTF8, you must redeploy the local language files.You are still required to reimport the language-dependant metadata files.

33810 IDD HashMap.get method can go into a loop, driving CPU utilization to over 100% even when no user is logged into IDD.Fixed by upgrading UI components.

MDM-HRN-90100-HF4-0003 17

EBF Number

HORA Number

System Description

33628 Hub Cannot use encrypted password in calls to CMXBG procedure to manage batch groups.

33710 IDD Changes in a SendForApproval task are not present if the task has not been submitted for approval before a second SendForApproval task is created.Fixed so the second task cannot be created until the previous task is approved.

7 32667 IDD Dependent drop-downs store wrong values.Fixed so search criteria and result set are now matched.

33766 IDD The width of the lookup drop-down in the customer environment is too small to fully display the items in the drop-down list.

33841 IDD If the same saved query is used in more than one search tab, different search results are returned for each tab.Now, new values entered in Run Search tab do not affect search condition when switching to a new tab.

33848 IDD If the same IDD application is deployed on more than one application server, an error regarding duplicate names appears in the CMXSERVER.LOG file.

33906 Hub Cleanse operation in IDD fails with error ORA-00933.

8 33257 Hub XML validation error 'ROWID_PREVIOUS_TASK' is not found in table 'C_REPOS_TASK_ASSIGNMENT_HIST' in action 'addQuery'.

33907 Hub Visual promotion results in an error when delta detection is selected for a non-date column.

32581 Hub Revalidate job results in an invalid identifier error when 'I' is used as an identifier (for example, I.ROWID_SYSTEM).

33851 Hub Search token is not generated for ORS-specific SIF API when using SearchMatch call.

9 33804 IDD Opening the Product/LookupQuery and selecting the blank drop-down option (that is, the very first item in the drop-down list) can result in stray characters being placed in the field.

34005 Hub If a SIF call is made using an ORS-specific API and a null value is set for a non-nullable column, the error message does not provide the name of the column. This can make it very difficult to debug the issue.Column name is now identified in the error message.

10 34035 Resource Toolkit

getOldValue() and isChanged() objects are missing from 9.0.1.

11 34009 IDD When an advanced query search is saved with an apostrophe (') in its name, a tool tip is not displayed when the mouse pointer hovers over the query.Replaced apostrophes (') with backslashes(\) in tooltip so they can be displayed.

18 MDM-HRN-90100-HF4-0003

EBF Number

HORA Number

System Description

33898 Hub The JMS message generated does not conform to XSD because of wrong case in Event element.

12 34122 IDD If search data in an embedded search screen is updated, the results in the main search screen are incorrect.

33917 IDD The "Load Image Failed" error message pops up while fetching one hop on the entity.

34173 Hub Load job fails when base object column Create_Date is set to Putable.

34049, 34050

Hub Performance Optimization required for BVT logic, which affects Merge and Update operations.

34273 Hub When you load a child base object, the debug log always prints the statement, "Set as DIRTY 0 parent records for C_B_PARTY.ROWID_OBJECT data change on child".The current count is now displayed.

13 34409 Hub JMS message does not conform to XSD when there are two ORS databases involved in generating the message.

34407 IDD User without permissions to edit Base Object should still be able to Create Task; however, the Create Task action is disabled.

34535 IDD Bar chart is displaying numbers instead of string values configured in dsi-config.xml .

14 33841 IDD If the same saved query is used in more than one search tab, different search results are returned for each tab.

15 34641 IDD If an HM profile is created in MDM Hub with multiple hierarchies and multiple relationship types, IDD throws a null pointer exception when the user tries to view relationships but does not have privileges to view all relationships.The Relationship tab now opens successfully without any exception. The Relationship tab only shows records that the user is permitted to see.

34851 IDD Pending changes are not applied to 'PART_OF' child records.Changed PartOfManyToMany class to apply pending changes to children.

34865 IDD If Child defaultView is set to FORM, a java.lang.NullPointerException error is created when attempting to create a new record.

16 34030 IDD Cannot edit the subject area when there is a logical 1:1 relationship between a parent and child if the user has permission to edit and send for approval. This happens when an Admin user creates a record having a value only for the parent and a user with limited permissions opens the record (The Edit button in Data View is disabled).Fixed Create and isCreatable methods to check for correct permissions.

MDM-HRN-90100-HF4-0003 19

EBF Number

HORA Number

System Description

17 35136 IDD The HM Relationship Types are showing English default if the localized names in the MetadataBundle.properities file include spaces.Ensure spaces are replaced with underscores for MetadataBundle entries.

35151 IDD IDD merge user exit method receives the parameters mergeTarget (containing the BVT) and sourceRecords (containing all records involved in the merge). However, the initial record to be merged is missing from the sourceRecords list.

35158 IDD The CreateTask function is not populating the list of users correctly.Selection in TaskType drop-down list now correctly reflects user list.

18 35137 Hub CMXZDT.CONFIGURE_GGS_REPLICAT(CMXZDT.zdt_local) session hangs.

19 34641 IDD If an HM profile is created in MDM Hub with multiple hierarchies and multiple relationship types, IDD throws a null pointer exception when the user tries to view relationships but does not have privileges to view all relationships.The Relationship tab now opens successfully without any exception. The Relationship tab only shows records that the user is permitted to see.

35131 Hub CleansePut is taking longer than normal to execute at Grandchild level because of full table scan during update parent dirty_ind process.

35161 IDD When a record is added through IDD, Trust values are not calculated correctly.



HORA Number

Description

30303 In Data Manager: Unmerge Failure: ORA-06502: PL/SQL: numeric or value error: character string buffer too small

31422 Extra space on siperian-core.xsd batchGroupUid cause parsing errors on wsdl

31452 URL: http://:/cmx/admin is misleading

31478 CWM import error - the unique columns are imported as non unique and the non uique as unique

31581 Username and passwords are logged in clear text in the Weblogic Logs and cmxserver log when making SIF calls

20 MDM-HRN-90100-HF4-0003

HORA Number

Description

31722 LINK & UNLINK performance SIF calls are throwing SIP-14264

31802 Validation rule configuration for source specific requirement

31950 Load & Match/merge jobs are running slow due to DBMS_STATS gathering stats on temp tables

31953 SQL error ORA-00001: unique constraint (CLIENT_HUB.M4SVR1_2210UK) violated

32040 Cleanse Put Call on User defined date column fails when message queues are configured stating 'expression must have same data type as corresponding expression'

32086 Delete xmls are not getting generated during load job

32100 JVM crashes during large Stage job running JBoss5 on Redhat with AddressDoctor libJADE.so 4.1.15.472

32122 Delete transactions are getting duplicated in c_repos_mq_data_change table

32200 No records are getting displayed when using Extended search

32209 Error during execution of Sync job from console for Trust rules

32216 SIF Merge calls take 7+ minutes after message triggers are enabled

32251 SIF call for Search Query is throwing error if custom query is used

32289 CleansePut does not work with Batch jobs when Interoperability flag is Enabled

32291 Poor exception handling in MRM-Cleanse Process

32330 Error returned when running the "Generate match tokens" process for Party

32402 Not able to acquire lock using proxy_user on console for Informatica V9.0.1

32466 Incorrect wsdl spec for ORS specific API generated

32493 Error with external match for c_bo_party (Dev env)

32517 Error "END_DELTA_MAITENANCE" is getting raised while executing stage job

32550 Clicking on package runs the custom query and it takes 20-30 min

32572 Matching/Tokenize throwing exception

32585 Cascade unmerge is not cascading to the child for some records. Needs UE custom code implementing

32724 In Save Handler in AfterSave should be Child entry with "is removed = true" flag

32726 Delete message triggers not working as expected

MDM-HRN-90100-HF4-0003 21


HORA Number

Description

30493 Calendar Localization Results in inability to use Calendar

31250 SIP-14159 Data Access Error when trying to process "PROMOTE PENDING XREF"

31291 RelationShipEndDate and StartDate column values are not populated in the relationships tab of a SA

31749 Not Able to display multiple UserExit messages

31757 Impossible to create HM enabled Many2Many rel

31882 Enhancement: support IDC/IDD for v9.01

31921 Relationship Start date and End date not visible on relationship child tab in IDD.

31946 Error while validation IDD config

31972 Slow IDD Login

32012 Custom validation messages in user exits popping up twice

32030 Cannot configure user role to enforce "Send for Approval" when updating an existing record in IDD

32038 Need for a new feature "Environments differenciation"

32048 Interation ID Lock Error - Parent Pending Xref does not get deleted once the child task is canceled

32064 HM crash issue

32073 Unable to save new parent/child entity

32091 Modal popup window shown when using External Link action with callback is not fully visible

32101 Getting SIP-14123: GET ONEHOP" error when clicking relationship tab in IDD application

32144 On creating a new HM relationship , userexit call to hmrelationshiphandler throws nullpointerexception

32172 Issue with Calling custom classes from IDD user exits

32175 Advanced query throwing stack trace if it includes a column from child BO which had a many-many relationship basing on another BO

32180 Comments added when 'Reassign' the task were not displaying in Task details window

32196 Special Character display issue persists for Mexico in Informatica MDM 9.0.1

32213 Find Duplicates not working correctly in IDD

32286 Child Subject Area field defaulting is not happening properly

22 MDM-HRN-90100-HF4-0003

HORA Number

Description

32297 Workflow CancelTask action does not clean up Pending records for record creation

32303 Error in relationships child tab

32307 Not getting rel start date and end date in getchangedcolumns list in bdd

32310 DB user exit message on IDD screen

32319 Getting error: No data is associated with the task that has id 330 . This task cannot be used.

32325 The IDD ISaveOperationPlugin User Exit does not provide SAVE_IN_PENDING_STATE value

32332 The IDD ISendForApproveOperationPlugin User Exit does not provide the INTERACTION_ID

32355 Username not getting populated in IDD assignable users list

32360 GUI Issues in task detail page after downsizing the window

32436 NullPointerException in log file while updating SAM cache

32437 In task administration tab, filter for the column OWNER is not working properly

32455 Changes are lost lost when user chooses Task Action without pressing the Apply button

32461 Dates in child subjectarea when edited are not replicated in getchangedcolumns

32472 Setting null values from IDD Java User Exit throws NullPointerException

32486 Typo in AllUsersAsignmentDataProvider class name

32488 Comments field in the Task Reassignment window not a mandatory field

32576 Repeated paging through Account related Contact and Relationship tabs causing IDD application crash

32584 Labels for search criteria columns not showing up in local language

32627 Basic Search Query Not giving result

32658 Task Details popup becomes too big (even with 1280x1024 resolution settings) when title is large

32664 Unnecessary dependency of RelationshipHierarchyRelType to HmRelationship

32676 BDD date columns on child or grandchild subject area cannot be sorted

32691 Error while clicking contact tab under Account

32702 BDD application is taking around 90 seconds to open the Saved queries tab

32722 Interaction ID is not maintained in the C_REPOS_TASK_ASSIGNMENT_HIST table

32723 Fields out of alignment in search query in Internet Explorer Browser

MDM-HRN-90100-HF4-0003 23

HORA Number

Description

32725 Grandchild Record issue in user exit

32728 Unable to fetch interaction id in Save handler user exit

32744 Getting an error while saving the BDD application

32749 Roles without explicit Merge capabilities within a SA cannot create merge tasks

32834 IDC fails to process a request

32846 Task Administration filters not working properly

32875 Search for active records is not showing correct data

32880 After Adding records to child tab during FinalReview throws HSI (0) insufficient error

33015 HM Entity with 1000+ relationships displays zero rels in HM Viewer

33042 Date columns on child or grandchild subject area cannot be sorted

Known Limitations

Known Issues

This section lists known issues in this release.

Note that all numbers listed below are Informatica MDM's internal issue tracking numbers. Refer to this number when making enquiries to Informatica MDM Support.

Admin Console

Bug Description

29199 The ALLOW NULL UPDATE flag is not supported for DELETE* system columns.

Batch Jobs/Batch Group Management

Bug Description

15713 A warning from a job within a Batch Group will cause the Group Job to return a status of "Completed With Errors." This error message returned by the Batch Group should be investigated by viewing all statuses within the group and can be ignored.

15949 When converting a Link-Style to a Merge-Style Base Object, the Auto-Link job will not be automatically removed from the Batch Group. This will need to be done manually. This is applicable for any BO configuration change that would modify the available jobs in the Batch Group Manager.

24 MDM-HRN-90100-HF4-0003

Bug Description

20845 Errors are thrown when accessing the Batch Group Manager when deployed using a WebLogic Application Server and a schema that contains greater than 100 Base Objects.

21587 Removing a Base Object or Staging table will not remove the job from a Batch Group. If users attempt to execute the batch group, a NullPointerException error will be thrown. (Related to 15949)Workaround: After removing the object from the Schema Manager, go to the Batch Group Manager and force a refresh through the file menu which will remove the job from the Batch Group.

28915 A timeout error occurs when the console refreshed while batch group is in progress.Workaround: When running batch groups/batch jobs in parallel, the connection pool (max) needs to be increased. This is basic setup that would need to be done in a production environment.

29859 Batch Job execution will fail silently (in the debug logs) if the machine ID is greater than seven (7) characters, for example "M2M2SVR1S".

29796 Error while accessing batch groups: MaxMessageSizeExceededException : Incoming message of size: '10000080' bytes exceeds the configured maximum of: '10000000' bytes.

Batch API interoperability

Bug Description

24151 Temp table are not removed after load update on child has failed.

23125 Put Update does not have a proper error message.When you use interoperability, set the distributed_lock_timeout parameter on the ORS database to a longer period than your highest lock wait times.

Informatica Data Director

Bug Description

General

25848 Error dialog appears when trying to open an IFRAME tab linked to Siperian SHARE portal.

27693 Unable to save a record with a relationship again when DB transaction was rolled back (required field left empty).Workaround: Configure BDDConfig.xml with all required attributes.

26578 Need to document exact match rule behavior in IDD. With exact match rules, the fuzzy match key is completely ignored. This is a problem because BDD uses the SIF API call, searchMatch , when running Find Dups and searchMatch *requires* the fuzzy match key in order to operate. This is (currently) an unavoidable consequence of using searchMatch in IDD.Workaround 1: Change any exact match rule to a filtered rule (i.e. change the Match/Search Strategy from Exact to Fuzzy).Workaround 2: Use Find Merge Candidates instead of Find Duplicates. Create a new query that only contains the columns you wish to search and use basic search to find records.

MDM-HRN-90100-HF4-0003 25

Bug Description

28240 Charts Documentation bug - IDD Bar Chart display inconsistent with documentation examples.

21913 App name context not maintained after login.

24603 IDD unable to launch if EAR file deploy manually.

29812 Dot symbol in physical names is not supported by IDD.

25072 Tokenize error occurs under certain security configurations.

24099 UNIX machine needs to adjust ulimit size for SIP_SAMPLE fuzzy search.

21910 java.lang.ClassCastException: java.util.Date error in stack trace when View history.

Configuration

24531 Configuration tool UI uses the locale of the active IDD application.

27679 Importing "complete IDD application (Zip)" fails for certain browser settings. When browser uploads a file it sends "Content-type" header parameter and if this does not match local environment settings the import fails.

30749 Not all custom fields are shown for existing relationships on Edit Relationship.

30729 Import into existing application works even it's cancelled.

23185 hmSettings section is not generated in BDD_CONFIG.xml.

Customization

25163 Custom actions are not available for XREF.

Dashboard and Tasks

24056 Opening an unmerge task should highlight the XREF row at the bottom.

Data View

24501 Autogenerated Tasks for Potential Matches.

27076 IDD - From and To date calendars in History screen are disabled for the first time and gets enabled either by moving up or down one month and coming back.Note: It works fine in Firefox after installing flash. But might still have issue in IE7 even after installing flash.

29724 Remote data is unavailable for empty bounded column.

24089 Missing child record when copying.

24367 Prompt to Save shows up when it shouldn't on View XREFs.

21613 Unable soft delete Address Entity with demo schema.

HM and Hierarchy View

26 MDM-HRN-90100-HF4-0003

Bug Description

23232 Zoom redraws whole page in IE7.

27672 Unable to jump to selected profile in HM configuration.

31210 HM Child Tab in Data View that references same subject area PO results in customer relationship field not be saved.

27594 Many-to-many HM record is unable to display more than one type of relationship record.

30233 Remove code constraint that only allows one relationship of a given type between 2 nodes.

23481 MessagesBundle localization requires values hard-coded in UTF-16.

Search Operations

27524 Search return duplicate records if the value is duplicate of another child record.

27551 Record is unexpectedly added to canvas when searching from HM.

24284 Search fails if a column has alias in package.

Security

24397 User can see merge history events even if user has no history permissions.

25233 Get a stack trace at IDD login for user with Administrator access.

28204 IDD cannot Merge/Unmerge Records with 'MERGE' Privilege if no 'UPDATE' privilege.

31254 Extended search doesn't apply security filter to the search results.

23666 "There is no ROWID_OBJECT value" exception if ROWID_OBJECT has no READ privilege.

Tasks and Workflow

24585 SubmitForApproval Task possible without FinalReview taskAssig configuration.

27488 Multimerge failure (due to interaction id) - message 40550 not found.Workaround: Approve records before merge.

28705 Weblogic - MetaDataFactory can't find the configured workflow engine.

23812 RowID_USER missing after escalate.

23334 Automatically created merge task does not have a due date.

Validation

24712 Application validation does not call out security inconsistencies.

25249 There is no validation being done on subTypeQualifier tags when used within columnLookup or columnI18nLookup tags.

MDM-HRN-90100-HF4-0003 27

Bug Description

26838 After changing a password for a user, a fatal error occurs when validating the IDD configuration.

28000 The GETLIST_LIMIT value is not being validated which could lead to not displaying all potential values.Workaround: Manually update C_REPOS_DATABASE.GETLIST_LIMIT.

IDD Exadel Components

24385 Changes to CALENDAR_LONG fields are not recognized when viewing cross references.

24988 Table sorting is not compatible with long-running operation.

Cleanse Process

Bug Description

7512 Informatica MDM Hub does not connect to next available cleanse server if the cleanse_url is not valid.

7592 The cleanse daemon does not go offline automatically once the sqlloader command fails so that consecutive requests do not go to this server.

10835 The start_cleanse function runs asynchronously if in_run_synch is not TRUE. This value is case-sensitive.

12785 When testing Trillium Director on WebLogic 9/ WebSphere there is an issue with the Trillium Director shared library that may cause a core dump. This issue has been raised with Trillium Support.

20376 An error will be thrown when importing match string in a Cleanse List if the source table contains NULLs.

21457 CMXCL.START_CLEANSE stored proc signature has changed XU SP1 and beyond. See the Informatica MDM Hub Administrator Guide for details.

20978 Default value for landing table will is not encapsulated with single quotes.Workaround: Use constant values in mappings.

25660 Running parallel cleanse jobs may cause the server to run out of memory - causing job failures.

27575 The WSDL Library's "Add parameter" option/functionality currently has not been implemented.

30094 Rejects are removed from the REJ table when the number of runs is greater than the number of audit loads.

28 MDM-HRN-90100-HF4-0003

Database Tool

Bug Description

19082 When a datasource is created with the incorrect settings, removal of the datasource will be done in the Informatica MDM Console. However, the datasource is not removed in WebSphere or WebLogic Application Servers.Workaround: Manually remove the datasource through the application server's admin console.

Data Manager, Merge Manager

Bug Description

8526 A manual Merge/Unmerge process does not terminate in a clustered environment when one of the managed servers is down.Workaround: Mark the process as incomplete and repeat the merge/unmerge.

13211 If you are running on a clustered WebLogic 9 application server, you may receive an unmarshalling exception when scrolling through records in the data manager.Workaround: Stop the process running the Hub Console and restart it. Alternatively, wait and the problem will resolve itself.

13358 A user who does not have Informatica MDM administrator rights can set a batch job status to incomplete.

17853 Modifying an FK value for a child record that has a default value may fail.Workaround: Remove the default value on the FK as we do not recommend this type of action.

Delta Detection

Bug Description

10970 Online previous landing (OPL) tables are used for delta detection for CLEANSE_PUT operations. The size of these tables is not managed by Informatica MDM Hub. In order to prevent the tables from becoming excessively large, you must manage their size manually.

25807 Delta detection works incorrectly when DD on date_col , date_col has NULL value and pkey_list contains date_col.

30632 Delta Detection using a Date Column is failing when any other date column is selected instead Last Update Date.

Delete Management

Bug Description

20993 Cascade Delete XREF on the child is not available when executing the Delete functionality on a Parent Base Object.

MDM-HRN-90100-HF4-0003 29

FirstLogic (also known as SAP Business Objects Direct)

Bug Description

13099 If you are using HP-UX with the FirstLogic adapter, you will receive an error. This is an issue with the FirstLogic installation. The HP shared object links in the incorrect runtime environment files.Workaround: You must install the 'Runtime Environment for International Address Engine' to workaround this issue.

Hierarchy Manager

Bug Description

10092 After adding relationships, the relationship count may not be updated. This is benign.

10639 It is not possible to sort on entity grids.

11808 The view related entities feature can give inconsistent results if you have sandboxes. This issue applies to the view feature; it does not reflect any inconsistency in the underlying data.

12902 You must include all HM required columns in the staging table, or the load process will fail.

19140 FK constraint that are not valid are not caught and reported by validation.

21000 Firewall security settings may block the access to the hm_default.zip file through HM Manager.Workaround: Copy the file manually to the client machine.

21279 Errors thrown when configuring HM as a non-admin user.

19295 HM package columns cannot be read only, put enabled required.

23201 Load to HM BO might fail with ORA-00903: invalid table name since the packages have to be configured and HM validated before running load.

Install

Bug Description

8753 If you have a debug_file_path that is not valid and debug is enabled, it will fail to apply the 2004102202_ldc_ConInd_DirtyInd_change.sql.

9199 Null pointer exception thrown intermittently when launching the console. This error is benign and has no effect on the operation of the console.

9673 If you choose to not run postinstall setup, the Installation logs indicate the installation failed. This is not the case. This error is benign.

12276 When you create a new ors, Informatica MDM Hub uses the CMX_DATA and CMX_INDX tablespaces.

12453 The installer adds two extraneous files to the Informatica MDM Hub for Oracle installation. These files are create_ors.bat and create_system.bat and they apply to the DB2 version of Informatica MDM Hub. This is completely benign.

30 MDM-HRN-90100-HF4-0003

Bug Description

13002 If you are using the WebSphere application server, you must stop and restart the application server after creating a datasource for an ORS from the Hub Console. Otherwise, the newly-created ORS datasource won't work.

15188 If you provide the incorrect path for JBoss during a silent install, the postinstallsetup script will say the install was successful even though the installation failed with the wrong JBoss path.Note: There is no validation in silent install.

16198 During a first installation on WebSphere 6.1, the postinstallsetup fails for both auto and manual options. Related to issue 13002.Workaround: Restart the application server, go to the AppServer Console and verify that the siperian.mrm.ear exists. The file will then show active status.

19162 Cancellation of a patch install during the file copying phase will cause issues for subsequent installs - users will need to complete a full install in a new directory to proceed.

19244 Users using WebSphere 6.1.0.11 and below which are upgrading to XU SP2+ will be required to execute a full installation of the product. The Patch Install cannot be supported due to library changes in IBM WebSphere 6.1.0.21

14380 Postinstallsetup will fail on Linux if installed as root. This is a limitation by InstallAnywhere as the root user does not have a .profile.Workaround: Contact your administrator to create a user profile to install the Informatica MDM Hub.

16460 Installer will not launch correctly on Windows x64 in the Standard View appearance.Workaround: Change display settings to Classical View.

18730 Modifying the log4j.xml while the application server is running in Redhat/JBoss will not update the log level (dynamic logging).

19056 When importing a schema using the Oracle IMP command, users will see various Oracle Type Object messages - these messages are benign and are due to a limitation of the Oracle IMP command.

19288 The Database HotFix installer does not install/copy the CMX_ORS and CMX_SYSTEM dmp files into the correct folder.Workaround: Copy the dmp files from the HotFix install folder to <server_home>/resources/database/oracle.

19950 Patch installing an environment that has been upgraded to WLS 10 will fail due BEA scripting changes - a full install is required in this scenario.

20653 The postinstallsetup process may fail on an environment in which the CMX_SYSTEM data source was created manually on the Application Server.

20849 During a patch install, the Server deployment may cause an NPE message to be thrown.Workaround: Restart your application server after a full or patch install as per Install Guide instructions.

20969 Removing a datasource that is not valid from the Admin Console when using WebLogic 9 and 10, changes may not be fully committed on the application server.Workaround: Login to the Application Server console and press the "Undo Changes" button.

20319 Users will encounter deployment and datasource creation issues when using JBoss with a non default deploy directory path.

MDM-HRN-90100-HF4-0003 31

Bug Description

22987 When using WebSphere in UNIX environment, errors may occur during installation/deployment if insufficient privileges are not granted to user being used. Verify with the System Administrator to ensure the correct directory and file privileges are given.

26007 Unable to register ORS with hostname containing "_".

26526 Unable to launch Hub Admin Console on MAC OS with WebSphere.

26821 Console/JNLP will fail to launch with using WebSphere and a client-side Java6 JRE.

29053 Postinstallsetup could fail on WebSphere Application Servers with the following error: Exception received while running file "wsjmsconfig60.jacl". This is due to an OutOfMemory issue on the Application Server.Workaround: Ensure that the JVM initial heap size are set to a sufficient size (512m and 1024m)

29308 Users who are using the WebLogic 10.3.2 and FirstLogic combination will require to do a full installation of the Cleanse Match Server install due to a library conflict.

31135 FileNotFoundException error when registering database in MRM console with JBoss-5.1 on Redhat. You can just ignore it.

31222 Registration or unregistration of database in MRM console might error out with JBoss-5.0.1 on Redhat5.3: SIP-10314: unexpected database exception: SIP-09005: Deployment error: Could not get database connection from DataSource.Workaround: Restart JBoss server to refresh the list of datasources.

31248 Installation on Sun Fire V120 hardware may cause deployment issues when using WebLogic 10.3.2 due to resource issues.

30600 Some instances of an upgrade when using WebLogic 10.3.2 may fail - a full install may be required.

Load Process

Bug Description

9933 Load process aborts rather than rejecting records with a date in the future. The assumption is that once records have been staged, dates that are not valid should not exist in the staging table.

13337 Load can fail with a deadlock error. This is an Oracle bug that may happen on certain platforms (not all).Workaround: Set Parallel=1 on the base object.

18951 Load process can fail when attempting to load non-unique due to unique constraints issue. This will cause a transaction rollback to occur in the ORS.

22227 Load process may fail if a shadow column was left behind with no XREF lookup defined.Workaround: Drop the shadow column and execute Load process.

27584 Load insert fails if base object has 120+ trust/validation enabled columns.

32 MDM-HRN-90100-HF4-0003

Bug Description

28806 Load update overwrites existing columns with NULL when the columns do not exist in the mapping.

30121 When using Oracle's Data Pump when importing a schema, the ORA-39117 error will be thrown due to the REPDYN_TABLE_CACHE table that contains data. This error is benign as the cache table will be repopulated by the application.

Match Process

Bug Description

10298 The consolidation indicator is incorrect after a match executed with no rules set. This error is benign. The records with the inaccurate consolidation indicator are picked up in subsequent match jobs.

10928 The ROWID_USER columns are not populated in the match table.

11412 If you have records on hold (consolidation indicator = 9), as from a Match Analyze operation, refining your match rules should trigger the Reset Match, resetting the records that are on hold. This expected behavior does not happen.Workaround: You must reset the consolidation indicator to 4.

12450 The generate match tokens process can fail with a stack overflow error when the match key (set in the match columns UI) is set to a column of a child base object and that child base object contains approximately 500 or more records that belong to a single parent record.

12829 If you are using a clustered WebLogic configuration, and you bring a managed server down while a job is in progress, the job does not terminate. For stage and match jobs, an error code is written to the database log. For loads and merges, an error is sent to the console.Workaround: Mark the process as incomplete and redo the match.

14065 If your tokenization table fails due to lack of tablespace, you will not be able to recreate it. You can manually solve recreate the STRPT table with this command example:alter index SVR1_7UW_TMP rename to SVR1_7UW.alter TABLE c_address_strp rename constraint SVR1_7UW_TMP to SVR1_7UW;The index names are unique so they won't be the same every time.

20662 External Match tables that were created prior to XUSP1 may causing execution failures and MET validation errors.Workaround: Edit a match column for the BO which will trigger the recreation of the EMI table. Note that existing data in the _EMI truncated. Contact Informatica MDM Support for alternate methods of resolution.

24688 When using different JVM version in a distributed match environment, matches may vary. For consistent results, ensure that the same JVM version is used for all Cleanse-Match Servers.

25818 Automerge using BVT views instead of tables in the interop mode.

27676 Errors in log file while running match job on link style enabled BO (example: "Exception Name: CANT_GET_TEMP_SRC_TABLE". These messages are benign and can be ignored.

30103 Application Server might fail when running match using the Japanese Population.

MDM-HRN-90100-HF4-0003 33

Merge

Bug Description

15813 Automerge in batch jobs fails if a base object has more than 200 columns. This is a limitation of automerge . Currently Informatica MDM supports up to 200 user columns in the automerge process.

27208 Column name of GROUP_ID in a BO causes a failure in Automerge.

Message Queues

Bug Description

6747 The Schema Manager doesn't allow you to select which columns you want to monitor on an Insert trigger rule as it does for an update trigger.

13070 If you have message queues configured, operations in the schema manager can take a long time. The reason this is that for each data change that is associated with a message queue message, the monitoring thread will query the message package.Workaround: Manage the volumes in the message queue tables.

16403 The event triggers do not exist for the Link/Unlink functionality.

31125 MQ messages not generated for update,only xref changed trigger-loadByRowid.

31127 Number of tuples generated in C_REPOS_MQ_DATA_CHANGE for LoadByRowid and CleansePutByRowid actions are not equal.

MET Validation

Bug Description

17350 Metadata tool does not report views/packages that are not valid.

21873 MET validation is able to throw error for the incorrect setting on C_REPOS_DB_RELEASE.DEBUG_FILE_PATH at the first time of MET Validaiton check. However, MET Validation succeeds on the subsequent calls.

MET Migration

Bug Description

18012 Errors may occur while executing an Import in one console and registering/unregistering an ORS in another console in WebLogic, this is a global transactional issue.

18526 MET does not support the importing/promotion of Custom Packages and Queries. See the Appendix in the Metadata Manager Guide for a full list of not supported objects.

19157 Currently, the MET Import functionality does not support incremental imports (1 object at a time).Workaround: Users can use the MET Visual Promotion functionality to accomplish this if required.

34 MDM-HRN-90100-HF4-0003

Bug Description

19239 MET does not support the importing/promotion of Users. See the Appendix in the Metadata Manager Guide for a full list of not supported objects.

19552 Removing/Modifying objects during the MET migration process are causing excessive logging to the C_REPAR tables.

20834 If you attempt to export from a repository that is locked by another user, the following error is displayed in "an unexpected error occurred" message window:SIP-10313: Cache is NOT enabled for database CMX_myDB release all write locks on this DB. This is not an "unexpected error" but expected behavior when attempting to export from a locked repository.

20959 For visual promotion, you can revert changes one design object at a time. You cannot select multiple objects to revert in a single operation.

20960 In MET Migration, when table/indexes exist in one tablespace on the source but that tablespace does not exist on the target, there is potential for data loss when these tables cannot be created on the target side.Workaround: Ensure that both source and target have privileges to all required tablespaces before running MET migration.

20976 When importing from a source schema that uses Geographic/Noise Filter cleanse library functions, Metadata Manager displays the following type of message:Object "Cleanse Functions/..." conflict between source and target. Before continuing with the import process, you need to resolve the conflict by renaming the cleanse function library according to the instructions in "Renaming the Selected Object" in the Metadata Manager Guide.

21044 In the case of a Rollback of a MET Import/Promotion on a schema that has HM enabled, there may be warnings left on the target schema. These will have to be manually fixed - note warnings to will not impede users from executing additional MET Import/Promotion jobs.

21046 After a MET Rollback, the Valid state of the ORS does not get refreshed. Note that users should run MET Validate again to verify the integrity of the data.

21679 Function description for custom user lib missing in promote for conflict resolution.

21775 After Visual Promotion of a package, the conflict icon may not change due to the require promotion of the query which the package is based on.

24196 Custom match populations included in export or changelist XML files will not load in the MetaManager Tool.Workaround: Remove the custom match population element from the xml file and modify the target schema manually or use direct database import/changelist options.

24197 Remote Packages that exist in export or changelist XML files will not load in the MetaManager Tool.Workaround: Remove the remote package element from the xml file and modify the target schema manually or use direct database import/changelist options.

25742 MET full rollback may not happen on WebLogic if the stuckthreadtimeout parameter is not sufficient when working with large schemas. If a struck doesn't finish its job in the default of 20 minutes, the app server will consider the thread dead and kill the connection between console and server. There is no way for the server to perform rollback under this situation because the working thread doesn't know it has timed out.Workaround: You need to adjust "Stuck Thread Max Time". Recommendation is to set it to 1 hour.Workaround: Update the validation rule order in the target after the promote.

MDM-HRN-90100-HF4-0003 35

Bug Description

28048 Null child values with default values reporting as orphaned when calling TEST_FK.Workaround: Alter the BO_CLASS_CODE to nullable with no default value.

28055 MET promote cannot create Custom packages with * in SQL, causes metadata inconsistency after failure.Workaround: manually recreate the custom package on the target after the promote operation.

28056 cannot promote changes after disabling trust on columns using Visual promote.Workaround: Use the changelist promote option if you need to disable trust and promote the changes.

28068 Custom query does not get created through changelist.

28070 MET Migration does not rollback cleanly after Out of Memory error.Workaround: Ensure heap size and memory settings are configured properly on the appserver before running MET migration operations.

28082 MET migration deletes and recreates stage table columns, mappings if the source and target systems have different rowids.Workaround: Synch up the source and target system rowids in C_REPOS_SYSTEM before running MET promote operations. This can be done by updating the source systems using the rowids from the target so that the source and target have the same rowids for the same systems.

28106 MET may thrown a NullPointerException during promoting changes from Source to Target.Workaround: The error in the log may an OutOfMemory exception. For this case and other NullPointerExceptions that have silent OutOfMemory issues, increase the jnlp.max-heap-size setting for the console in the <sip_home>\hub\server\resources\cmxserver.properties.Note: The AppServer will need to be restarted.

28150 Duplicate records based on HIST_CREATE_DATE, ROWID_XREF got created in HVXR tables after upgrading to Patch B.

28324 Unable to find FieldDescriptor for 'modifyForeignKey' error when applying MET change list.Note: Prior to XUSP2, modifyForeignKey was not supported because all attributes are read-only. On SP2, a mutable property was introduced, modifyForeignKey (lookup name) but you still get an invalid section in the xml. The xml generator does not read/write modifyForeignKey flawlessly. This affects comparison change list xml only, not import/export.

28617 The Console only allows BOs to be converted if they have no data. There is no way to know how to populate this column when it is being converted. Converting a BO in production filled with data to HM entity object is not supported by design. The entity type values would be defined after the BO is converted to an HM entity.

28639 Optimize validation checks during promote/import: MET operations on large schemas are very memory intensive. Ideally should have at least 1g or more on the appserver and 1g or more on the client side (jnlp settings need to be over a gig). Recommend launching the console from a machine other than the appserver and running the client operations from there.

28692 Changelist generated by Informatica MDM Hub contains Custom Query Definition but no table definition that the Query references.Workaround: After the MET migration, the custom table has to be recreated on the target.

36 MDM-HRN-90100-HF4-0003

Bug Description

28973 MET rollback failure: When rollback has to restore a non-nullable column in a BO and that BO is not empty, the column will be restored as nullable column in the database, resulting in MET validation error indicating that the column was nullable in the database but not in the metadata. The data will be lost and cannot be restored.

29041 The MET Guide doesn't specifically say that when you want to Promote--> Visual deleted objects such as base object, system, staging table, and column. you need to use the "Replace the target design object completely with the source design object" option to resolve conflicts. This is because the MET:Promote-Visual will not generate a changelist to promote -- delete objects -- staging table/system/columns , if these Automatic Merge options or selected: "Use source to resolve conflicts" OR " Use target to resolve conflicts". Choose "Replace option" to resolve conflicts to promote Deleted objects.

29382 Indexes created on supporting tables(such as XREF, HXRF, and HFKM) are NOT getting migrated to the target environment during MET promotion since MET does not look at indexes that are registered through the proc on non-BOs

30024 Changelists created in previous releases did not verify that when a column is used in a validation rule was present in the staging table. After applying the changelist in the target schema, MET Validation would log this as an error.Workaround: Add the column to the staging table and rerun MET Validation.

31189 Already existing BOs and Indexes are giving index already existin error, while applying some complicated incremental ChangeList.

Migration

Bug Description

9645 When migrating from MRM 3.6.2 SP1 or Siperian Hub XR to Siperian Hub XS or above, Siperian Hub inserts dummy values into the staging src_rowid. This will cause an error when populating the reject table. To correct this situation, repeat the stage process to generate the correct src_rowid.

10392 The migration script does not remove legacy DataFlux pipelines.

11621 If you are migrating from XR to XT SP2 and have "Leave Match Hit" enabled in the pipeline, after migration the cleanse list setting for "Leave Match Hit" is incorrect.

16918, 16923, 17082

XU migration might take longer to process an update SQL in 2007050902_ldc_upd_tree_unmerge_struct_data.sql.

19475 Migration will fail if the ORS has SilverCreek metadata which was previously added through a HotFix release. Contact Informatica MDM Support for steps to resolve.

20611 Schemas may contain PRL tables that have the online_ind defined as a number instead of an int. If this causes any issues, call Informatica MDM Support.

21717 When migrating an ORS that contains a custom index prior to XUSP1, expect the custom index to be renamed to the Hub naming convention. This will be done automatically if the original custom index was not registered in the REPOS tables. Note that in XUSP1 and above, custom indexes should be created through the Informatica MDM Admin Console.

MDM-HRN-90100-HF4-0003 37

Bug Description

22431 Schemas that are pre-XUSP1 which are migrated to XU SP2+ will contain extra metadata that will cause MET Validation messages related to Cleanse Function Resources that are not associated with any Roles. These messages are informational and are benign. To remove the extra metadata, contact Informatica MDM Support.

26618 2007120401_mig_add_hub_state_ind.sql may fail if a custom index exists.Workaround: Remove the custom index and continue with the ORS upgrade.

ORS Users and Groups

Bug Description

9749 All ORS groups not listed due to unknown error. If the schema has multiple users in the C_REPOS_USER table that do not exist in the CMX_SYSTEM you may see this behavior.

Other

Bug Description

9332 Removing the datasource from Informatica MDM Hub does not remove the datasource entry from WebLogic.

10910 In a clustered environment, if the application server that received a request to match, stage, or generate tokens fails, the match, stage or generate tokens job does not terminate.Workaround: Terminate the jobs manually.

12764 In the metadata, the updated_by field of cmx_ors.c_repos_user is always set to CMX.

12767 When you update a user to assign a different ORS to that user, the update may not be reflected in the metadata.

16307 The console currently allows Anti-match (not equal match) and null matches non-null as coexisting options. This is not a valid combination.

21873 An incorrect debug_file_path in C_REPOS_DB_RELEASE when debug is enabled will cause execution errors in batch jobs as well as console side activities such as MET Validation. Users will have to set the correct path before continuing.

23949 The Post Merge user exit parameters have changed; see the Administrator Guide for details.

24990 Need to add cascade support for promote/delete of pending data.

28482 Cache issue: Trust score is not updated in BO when doing PUT API from command line after changing BO setting.Workaround :1. Cache should be refreshed2. App server restarted3. Db connections reconnected (such as SQL*plus, and toad)

38 MDM-HRN-90100-HF4-0003

Bug Description

28396 In WebLogic 10.3, when acquiring an exclusive lock while a shared lock is already acquired, the following error may be thrown: "ReposException" Workaround: Release all locks and immediately acquire the Exclusive Lock

28832 When user exists are invoked, the error "ORA-06510: PL/SQL: unhandled user-defined exception" may be found in logs after a job failure. This error can be ignored.

Performance

Bug Description

20875 An ORDERED hint is causing long running executions on validation rule queries.

21384 Users no longer need to reset the degree of parallelism when switching between API and batch mode. This has been resolved in XU SP2 with the latest DOP changes.

Package and Query Manager

Bug Description

19270 Removing a Custom Query from the Query Manager does not drop the physical view in the database.

20948 Currently in Custom Packages, users are allowed to bind multiple rowid columns, however users will not be able to tell which binding the data is being retrieved from.

19534 Custom packages are read-only, not put enabled.

19673 Display packages with conflicting names and with no alias errors out with invalid identifier.Workaround: Add alias entries for columns.

Resource Kit

Bug Description

24152 The versionInfo utility in the Resource Kit does not execute properly due to Java path issues.

24526 The PartyWebservice sample does not work on JBoss

25827 Metcommand utility usage - run "ant build" to generate the class file. You can now run the Met command utility as described in the doc.

25828 MetModelConverter usage - run "ant build" to generate the class file. You can now run the MetModelconverter utility as described in the doc.

MDM-HRN-90100-HF4-0003 39

Bug Description

25829 CleanseAdapterExample Usage - you will need to set the classpath before running this sample.For example:"C:\infamdm\hub\resourcekit-wl-xurp1\samples\CleanseAdapterExample\AdapterTest>java -cp ./bin;.;../AdapterImports/log4j-1.2.8.jar;../AdapterImports/siperian-common.jar;../AdapterImports/siperian-cleanse.jar;../AdapterExample/bin;../AdapterImports/commons-pool-1.3.jar; Runit"

28549 Some Oracle import warnings might be displayed when running setup_ors.sql to create new ORS using SIP_Sample.dmp.Workaround: It is OK to ignore these warnings.

Roles

Bug Description

15560 SAM privilege matrix has changed from XT to XU-SP1. Roles may be converted when upgrading from XT to XU. Verify permissions for roles after upgrade.

Schema Manager

Relationship tables have been deprecated. Use relationship base objects for this functionality instead.

Bug Description

6874 The default value is blank after you enable the "Has Default" checkbox. If you add a default value for one column, and then enable the "Has Default" checkbox for the same column, the default value you entered is gone and the checkbox is not enabled.

8857 If saving the match rules fails because of network outages or connectivity issues, the indexes may get dropped on the STRP tables. Contact Informatica MDM support.

10258 It is possible to create nonsensical match rules, such as a match rule with 1 exact match column with segment match. Informatica MDM Hub will not stop you from doing this.

10923 After creating a Staging Table, the "Edit Lookup Column" button is enabled for ALL columns but should only be enabled for those which have a lookup defined.

14296 Console allows a mixture of Merge-Style and Link-Style Base Objects to be related. This is not a supported model.

17441 Creating user defined base objects that start with a physical name of C_RBO_* may cause issues if HM is enabled.

20049 An NPE may be thrown when accessing the Match Properties tab on a migrated schema - this is caused by a manually created _EMI (External Match Input table) from a previous release. Contact Informatica MDM Support for workaround.

20693 Match Tree information is incorrect when viewing for Link-Style Base Objects.

20978 The Default value for landing table will fail to save due to the value not being encapsulated with single quotes.

40 MDM-HRN-90100-HF4-0003

Bug Description

23951 Creating Base Objects which contain "XREF" in the physical name will cause downstream effects during execution time.Refer to the Administrators Guide for a list of reserved words.

27344 searchQuery got "HUB_STATE_IND": invalid identifier on a package that is based on a put-enabled package and didn't include hub_state_ind col.

28057 Removing BO column deletes packages, queries,roles and secure resource group dependent on it.

Security Access Manager

Bug Description

17059 Large schemas with many inherited Base Object and Packages in a role will cause a performance issue when loading the role.

19634 If a user attempts to edit an object that has been recently deleted in the ORS, a NullPointerException may occur.Workaround: Use the console’s refresh button in the file menu to refresh to object list in the tool.

19412 SAM Authentication Provider configuration: if custom code had an exception, there is no way to unregister it except through backend.Workaround: Remove the entry corresponding to the failing provider from C_REPOS_SAM_PROVIDER table in CMX_SYSTEM).

Informatica MDM Sample

Bug Description

15613 To use the Informatica MDM Sample installer and schema you must have a valid license for Hierarchy Manager in the Hub.

16237 When manually deploying the sipsample.ear file, the deployment name will be “sipsample (${sip.version} build #### release XU.” This is a labeling issue and will not affect functionality and usage.

15980 Deployment of the Informatica MDM Sample will fail if the Sample application is already deployed (upgrade/update).Workaround: Manually undeploy the Informatica MDM Sample application using the application server Console and rerun postinstallsetup.

18359 After running MET validation, various warnings appear in the results – these are expected warnings and are benign.

Security

Bug Description

12296 When enabling Secure IIOP transfer (IIOPS), the ORBTC log file will grow drastically on the desktop where the Informatica MDM Console is launched - this is a known IBM WebSphere issue. Workaround: Add a fake certificate to the SiperianKey JKS file.

MDM-HRN-90100-HF4-0003 41

Services Integration Framework (SIF)

Bug Description

7113 The GETLIST verb ignores the page size if the page number is 0. The number of rows returned default to the GETLIST default page size (200). If the page number is 1 or greater, it returns the page size requested.

10330 When you use the PUT verb, Informatica MDM Hub does not reject rows with an invalid value in the dep_rowid_system column.

12015 The MATCH API disregards the value of the distinct system setting on the base object.

13371 The generation of ORS-specific SIF APIs fails if the JDK is not available in the classpath. Workaround: Add the JDK to the classpath.

13110 If the ORS API generation fails hangs, open the Task Manager and kill the "javadoc" process. This action then allows the ORS-specific API generation to complete. Note that while this action precludes the addition of the javadoc for the ORS-specific API, the source will be generated correctly and loaded into the application server.

16324 If an underlying package changes, the changes are not propagated through all package layers. Workaround: Do not create a package on a package OR rebuild the top package when changing the bottom query.

17110 describeSiperianObject API for HM-SANDBOX can be executed without privilege.

17177 SearchMatchRequest API fails with error "SIP-14105: Unexpected error processing request" if a package is defined on an XREF table instead of BO. Workaround: Change the packages to be based on BO instead of XREF.

18813 The generation of ORS-specific SIF APIs may fail during the Javadocs creation Workaround: Clear the CLASSPATH to only include the JDK. This is a known Javadocs issue.

19116 Accessing the SIF Manager Tool may fail with the following error: "GENERATED_OBJECT_TYPE" invalid identifier. This is cause by having registered ORSes that have not been migrated to the current level of the Console. Workaround: Deregister the old ORSes from the console or migrate to the level using the Informatica MDM ORS update process.

20904 the executeBatchGroup can be executed by a user with no privileges with Asynchronous in SOAP and HTTP protocols.

21027 The SIF ORS API Generation will fail on a WebSphere Cluster Environment.

21668 ORS Specific SIF API CleansePut failing when system name used contains a period (.)

21728 Have to specify MATCH_RULE_SET.Ruleset with prefix in SIF SearchMatch. Admin or non-admin records use the format:<q0:matchRuleSetUid>MATCH_RULE_SET.APIMatch</q0:matchRuleSetUid>For admin users SearchMatch should work without the pre-fix MATCH_RULE_SET.

24142 The date returned from the getDependentObject will be in a different format to the date that was passed in.

21928 When two identical schemas exist and are registered in the Informatica MDM Console, potential errors may occur during SIF calls.

42 MDM-HRN-90100-HF4-0003

Bug Description

26743 The getSearchResults API call gives inconsistent results for search with sortCriteria.Workaround: Add a sortCriteria.

28423 LUD in BO are not consistent CleansePut API and Load.

28482 Trust score might not updated in BO when doing PUT API from command line after changing BO setting.Workaround:1. Refresh Cache2. Restart App server3. Reconnect to the database (using applications such as SQL*plus, and toad)

MDM-HRN-90100-HF4-0003 43

Staging Process

Bug Description

18096 Records which contain a NULL FK that are defined as unique columns and have lookups based on PKEY or XREF will show as "No Action" instead of rejecting.Workaround: Build a cleanse graph or mapping to execute a lookup and reject by using the Informatica MDM Read Database and Reject cleanse functions.To process FKEYs tht are not valid as NULL, add the read database in the mapping and set "Allow NULL FKEY" = ON in the stage table.The default value for Clear Cache in the read database cleanse function is false if no value is specified. The "Clear Cache" flag would generally never be set to "true" in any kind of real mapping. If set to true, then the cache is cleared for every single lookup. The only time the cache ever needs to be cleared is when the reference data is changed in the database. The call to clear cache should be done after updating the reference data. If the clear cache = false in read database function of the mapping and the lookup values have been changed after they are cached, you can choose two options to lookup up-to-date values depending on your situation:- If you are running a single cleanse server, you can call the read database function with the clear cache = true and the cache

will be cleared.- If you are running several cleanse servers, you need to execute a stored PL/SQL proc that will make a call to all cleanse

server to request them to cleanse their cache's.The procedure signature from cmxcl is below:PROCEDURE clear_cleanse_servers_cache(out_result OUT cmxlb.cmx_big_str, out_error_code OUT INT ); out_error_msg OUT cmxlb.cmx_message, For example, you can call the following store proc to clear the caches on all cleanse servers:DECLAREOUT_RESULT VARCHAR(1024);OUT_ERROR_MSG VARCHAR(1024); OUT_ERROR_CODE NUMBER; BEGIN CMXCL.CLEAR_CLEANSE_SERVERS_CACHE ( OUT_RESULT, OUT_ERROR_MSG, OUT_ERROR_CODE ); DBMS_OUTPUT.Put_Line('OUT_RESULT = ' || OUT_RESULT); DBMS_OUTPUT.Put_Line('OUT_ERROR_MSG = ' || OUT_ERROR_MSG); DBMS_OUTPUT.Put_Line('OUT_ERROR_CODE = ' || TO_CHAR(OUT_ERROR_CODE)); COMMIT; END; /Note: If you get "Record Found" = false and "Found in Cache" = true after read database function, that means that the record had already been looked up and not found. So when the subsequent lookup occurs it says no record found in the DB and it tells us that this info (that no record was found) came from the cache.

44 MDM-HRN-90100-HF4-0003

State Management

Bug Description

31257 Unique constraint error when attempting to change Hub State indicate value in Data Manager.

31285 Error on build_bvt for T$BVX when attempting to change active and pending to Deleted on BO record in DM.

23411 Bad update on Hub_State_Ind in DM when update active xref to delete on on record which has active and pedning xrefs for the same pkay_src_object.

System and Trust Tool

Bug Description

20843 Database constraint errors may be thrown when creating a System with similar physical names.

26485 Need to manually recalculate trust score on BO and Xref after change validation rule and run revalidate batch job.

Tool Configuration

Bug Description

12767 When you re-assign users to an ORS using the USERS tool, the creator and the updated_by values are not updated in the ORS.

Unmerge

Bug Description

20054 The unmerge SP on multi-generation cascade unmerges may exceed the Stored Proc's parameter OUT_TEMP_TABLE_LIST ability to maintain the list of temp tables it generates and fails due to error. Contact Informatica MDM Support for the recommended workaround.

20987 When the in_unmerge_all_xrefs_ind is set to "1", the out_unmerged_rowid returns the target rowid_object instead of a the list of srcrowid's being unmerged.

Unicode

Bug Description

10427 A base object column of type nvarchar or nchar is not available to be selected as a match column. Only varchar columns are available to be match columns.

10434 If you have the regional font set to something other than English, when you’re using the Mapping tool, the text on the warning dialogs switches to the local language.

10542 You cannot store dates in a non-English format for UTF8 data.

MDM-HRN-90100-HF4-0003 45

Users

Bug Description

5438 When you edit one user and click save, all users get saved.

ZDT

Bug Description

28827 Fail to configure GGS queue on an upgraded schema.Workaround: If you upgrade non-ZDT schemas for use in ZDT-enabled environment, you need to run update_javasp.sql after you upgrade the schema to 9.0 (using the sip_ant process).

29083 CM_DIRTY_IND might incorrect in _HIST table after executing the Backfill at target side of replication environment.

29362 Schema change to switch between link style BO and merge style BO in replication environment is not support.

29335 You might occasionally notice "resource busy and acquire with NOWAIT specified or timeout expired" errors in database log, ignore them since they have no functional impact.

29340 GG replication could fail if roles are assigned to new users.

29405 Extract generation fails if previous generation process timed out.Workaround: Stop all the GGS processes, remove the files and redo the configuration again.

29445 Link API on target does not trigger a backfill when the records to be linked are not in _LINK table. It is by design as there is no bvt or anything else that might require backfill.

29464 You might see update cm_diry_ind=0 statement was called twice from database log after backfill task completed in api call, just ignore it, it is a redundant debug print call.

29465 Cache issue might be run into when backfill tasks are triggered by APIs.

29597 When upgrading schema, you might run into the error - unsupported add/drop column operation on compressed tables if tablespace created with compress option

29623 Tablespaces created with compress option - GG process abends.

29724 Match batch job doesn't flip cm_dirty_ind flag to 1 after replicated into target environment. This is by design.

29725 The cm_dirty_ind is not set to 1 for the records that only update the XREF.

29744 Reset matches does not happen when CL that affects match is applied on target.

29811 GoldenGate setup failed with Proxy user - SQL Error 1031: ORA-01031: insufficient privileges.

30076 Dry run of incremental CL might fail on ZDT target after swing/cleanup process.

30090 When doing PUT inserts if the OTS is not provided and the trust score has not been set, the OTS value will be 0, which gets used in trust calculations. In such cases, the BO trust score will be 0 while the XREF score could be higher. This is expected behavior.

46 MDM-HRN-90100-HF4-0003

Bug Description

30230 Edit Child in DM might fail with small buffer error if there are a large number of cm_dirty_records in the parent BO and backfill is registered. This only happens in DM since edit popup window has a drop-down box to list FKEYs. PUT update on Child using API call doesn't have same issue.Workaround: Run backfill on cm_dirty_records.

30267 Backfill batch might fail when it concurrently runs with multi-merge API if tokenize backfill is registered with other 3 backfill tasks.Workaround: setup a longer API cleanup timeout.

30270 The use of "Order By" clauses are currently not supported when passed into SIF calls.Workaround: Don't pass any criteria to sort the results.

30437 GG Setup fails when NULL in DB_REPLICATION_USERNAEM/PASSWORD using proxy user.

30795 Row count and number of records returned from searchQuery API might not consistent if backfill is called with searchQuery.

30827 SearchMatch API with JIT backfill fails if the generated backfill SQL string is over 32K. This is limitation, you need to limit the record numbers in this case.

31164 Processes ABENDED while Configuring Event Queue on Target side. This issue happens rarely.

31201 Multi-merge might occasionally fail with NPE when it is concurrently running with backfill batch. It happens when database cannot give a connection to the requester within the configured 30 seconds max time it will wait.Workaround: increase API lock wait time. It is 30 seconds by default.

31203 Some of the temp tables are not getting dropped after backfill.

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.

MDM-HRN-90100-HF4-0003 47

http://mysupport.informatica.com

Use the following telephone numbers to contact Informatica Global Customer Support:

North America / South America Europe / Middle East / Africa Asia / Australia

Toll Free Brazil: 0800 891 0202Mexico: 001 888 209 8853North America: +1 877 463 2435

Toll Free France: 0805 804632Germany: 0800 5891281Italy: 800 915 985Netherlands: 0800 2300001Portugal: 800 208 360Spain: 900 813 166Switzerland: 0800 463 200United Kingdom: 0800 023 4632 Standard RateBelgium: +31 30 6022 797France: +33 1 4138 9226Germany: +49 1805 702 702Netherlands: +31 306 022 797United Kingdom: +44 1628 511445

Toll Free Australia: 1 800 151 830New Zealand: 09 9 128 901 Standard RateIndia: +91 80 4112 5738

48 MDM-HRN-90100-HF4-0003

informatica mdm multidomain edition for oracle - 9.0.1 hotfix 4 - … documentation... · 2016. 7....

Documents