MDM Registry Edition Release Notes

10.2 HotFix 1
- 10.5 HotFix 1
- 10.5
- 10.2
- 10.1 HotFix 1

Back Next

Cumulative Known Limitations

The following table describes known limitations that are carried forward from previous releases:

Reference Number	Description
IR-629	The latest standard population files are not compatible with the earlier versions of MDM Registry Edition .
IR-585	In an IBM DB2 UDB environment, the SSADB_QUERY_TIMEOUT environment variable does not function as expected.
IR-245	The MDM Registry Edition installation package for AIX does not include the MDM Registry Edition security framework. Workaround: Contact Informatica Global Customer Support for an updated installation package that includes the MDM Registry Edition security framework.
IIR-2845	The Relate client fails if the length of the Record Layout field value is greater than 250 characters.
IIR-2844	The Load-IDT job fails if the user source table has a CLOB data type column.
IIR-2828	A system load job might fail if the length of the JOB-LIST parameter value in the loader-definition section is greater than 65 characters. Workaround: A blank space is introduced at the beginning of every line when the JOB-LIST parameter value wraps to the next line. Remove the blank space at the beginning of every line, save the SDF file, and load the system.
IIR-2805	The updsync utility might stop immediately after you start it. Workaround: Remove the stop value in the FIELD column of the IDS_UPD_SYNC_TXN table and run the utility.
IIR-2799	When you perform a search that uses the Filter field in the LWM_FIELDS control, you get the following unclear error message: NAME3V2 match failed 'Could not find field 'Filter<number>'' Workaround: Remove the Filter field from the LWM_FIELDS control because the LWM_FIELDS control does not support the Filter fields.
IIR-2493	After you enable a review option, such as PREFERRED-RECORD-REVIEW or PRE-MERGE-REVIEW, if you create a persistent ID by using the mass load utility, no review records are added in the review tables.
IIR-2385	When you install MDM Registry Edition in console mode, you cannot configure the name and port number for the Secure Search Server and Security Server. Workaround: By default, the installer configures the host name and the port number for the Secure Search Server and Security Server. If you want to change the default values, update the values of the following environment variables in the <MDM Registry Edition Installation Directory>\env\mdmres.bat file on Windows and the <MDM Registry Edition Installation Directory>/env/mdmres script on UNIX: SSA_SSEPORT SSA_SSEHOST SSA_SSPORT SSA_SSHOST
IIR-2117	On Windows, if the installation of MDM Registry Edition in console mode fails, the errorlevel value does not change from 0.
IIR-2160	When you run a multi-search that passes file records in the ids_search_start function, only the first search in the multi-search runs.
IIR-1883	You cannot create more than one system in the SDF Wizard. Workaround: Close the SDF Wizard and open it.
IIR-1660	On DB2 UDB, if you set DB2_COMPATIBILITY_VECTOR=ORA, loading IDT fails during the trigger creation step.
IIR-1677	If you start the Update Synchronizer before you deploy a system through the SDF Wizard, the system does not synchronize the data with the IDT. Workaround: Restart the Update Synchronizer.
IIR-1556	After you deploy a system by using the SDF Wizard, the system is not visible in the MDM Registry Edition Console. Workaround: Restart the MDM Registry Edition Console.
IIR-1547	When you create a system on a computer and deploy it on another computer by using the SDF Wizard, the deployment might fail. Workaround: Try to deploy the system on the computer on which you created the system.
IIR-1539	When you use the Organization purpose for matching records, if the ID field of one record is a subset of the ID field of another record, the ID fields get 100% match score.
IIR-1524	Concatenating multiple source fields into a single IDT field might create a line that is longer than the maximum length of 255 bytes. Loading such SDF fails.
IIR-1486	On Linux AMD64, you can incorrectly use the GNU Compiler for Java (GCJ) to launch the SDF wizard and as a result, the JVM does not respond correctly. Workaround: Include the path to the appropriate Oracle JRE in the PATH variable.
IIR-1035	When an Informatica Data Director application accesses Security Server or Secure Search Server, you might get the following error message: java.lang.OutOfMemoryError Workaround: Set the JAVA_OPTS environment variable to increase the memory available for the Java processes. For example: JAVA_OPTS=-Xms512m -Xmx1024m -XX:MaxPermSize=512m
IIR-994	Search fails and displays the message NAME3V2 ssan3_match_encoded call failed 'Missing matching bracket' . Workaround: Limit Controls parameters to 256 characters.
IIR-586	When you upgrade to the latest version of MDM Registry Edition from an earlier version, the upgrade process fails. Workaround: Install MDM Registry Edition in a new directory.
IIR-584	In the Job Editor, the Execute SQL step lists ssa as one of the supported logon types. You cannot use this logon type because the Execute SQL step does not use the database dictionaries.
IIR-578	The -y option in Dupfinder and Relate does not show flattened and repeating fields correctly.

Rename Saved Search

Table of Contents

MDM Registry Edition Release Notes

MDM Registry Edition Release Notes

Cumulative Known Limitations

Cumulative Known Limitations