9.5.0 HotFix 1 Fixes... 1 Known Limitations... 2

Transcription

1 Informatica Identity Resolution Version HotFix1 Release Notes September 2012 Copyright (c) Informatica. All rights reserved. Contents HotFix 1 Fixes... 1 Known Limitations HotFix 1 Fixes This section lists the Fixed issues of the Informatica Informatica Identity Resolution HotFix 1. Jira Issue IIR-1068 IIR-972 IIR-955/899 IIR-954 IIR-945 IIR-932 IIR-919 IIR-898 IIR-879 IIR-876 IIR-868 IIR-852 IIR-847 IIR-835 Description New command line output option is now available for relate. The error messages for an invalid null-field value does not describe the exact problem. Rulebase Server Groups do not shut down properly. The PK definition from the original System Definition File does not create correct Persistent-IDs in the intermediate System Definition File. Create PID added duplicate MC table entries when Quick Select and Member Is Preferred is enabled. The System Definition File Wizard generates incorrect format of KEY-DATA. Due to an undocumented limitation, table cells and other fields on the browser screen is limited to 1,000 characters. A DCE-based Seed clustering is slow on Windows platform. On Screen Help is not available for Persistent-ID fields in the System Editor. The Persistent-ID-Merge-Rules in the System Editor has an empty drop-down list and does not have proper help. If merge rules are not defined, the Persistent-ID creation generates incorrect cluster numbers. Match Explain functionality in the NAME3 Workbench does not work with multiple Purposes. Persistent-ID cluster numbers are incorrectly set to zero in the membership table. You can access Simple Search only with HTTP search client. IIR-RLN HF

2 Jira Issue IIR-830 Description You cannot use Create PID with multi-search definitions. IIR-826 When the system performs a MATCH_OPTIONS control, the following error appears: SSA Rsp Code: ( ) E SSAQSSA BAD FUNCTION SYNTAX IIR-797 IIR-775 IIR-746 IIR-740 IIR-713 IIR-707 If you need to change the default server timeout value to 300 sec, start the connection server separately. When two searches with same IDX is given in a multi-search, the Create PID intermediate sdf generation results in the following: - duplicate IDX - duplicate views - duplicate fields in key data view During the Load IDT process, compression logic does not remove trailing Unicode spaces from IDXs. Create PID generates invalid results. The Population Override Manager crashes with an exception on Solaris_AMD64. This bug is a known limitation in Java versions 1.6.0_23 or later. When you run a Frequency Report using the Edit Rule Wizard, it fails. The following error is reported in a log file in the work directory: genrep> ssacopy error (9) rc=-2 (-181) IIR-701 DCE scripted install does not interpret the command line parameter, server-cs-dce. IIR-684 IIR-680 IIR-671 NSA transaction validation has been improved. The No Source Access Table query requires improvement. The batch installer does not set host:port values to the command line values. IIR-580 IIR-424 IIR-352 You cannot add fine control of the score for a transposition. Use bind variables in Rulebase Server Groups to improve performance and reduce usage of database resources. The FLATTEN-KEYS limitation of 36 is not imposed and the loadit process fails with inappropriate error. IIR-205 IIR-66 IIR-15 The lockmgr utility does not provide detailed error messages. The score is calculated incorrectly in the Name3 Workbench s match report when the Purpose includes a Best group. The SDF Wizard crashes when processing PID Link Rules. Known Limitations This section lists known limitations of the Informatica Identity Resolution HotFix 1. We provide temporary workaround for the known issues. These issues will be fixed in a future release or fix-pack. 2 IIR-RLN HF1-0001

3 Installer Installer fails to start Installer fails to start (Windows) Installer fails to perform a new installation into an existing directory Upgrade does not work The SSA_JAVA_OPTS requires -d64 option The operating system displays a message that Java cannot be found in the current PATH. If you see the following message when you launch the installer: The system cannot execute the specified program, then it is likely that you do not have the required Microsoft Visual Studio 2008 runtime library installed on the target computer. The installer reports that it cannot open an env script. This is because the installer assumes that an existing directory contains an installation of the product. When you use the GUI installer, the upgrade installation does not work. You need to append -d64 to SSA_JAVA_OPTS. The bin directory of the JRE in use (which was specified during installation) must be in the PATH of the environment used to start the clients. You can download the required library from Microsoft web site: Microsoft Visual C SP1 Redistributable Package (x86). Specify a directory that does not exist for a new installation. Use the command line interface. Set SSA_JAVA_OPTS=-Xmx512m -d64 on a 64 bit platform. Java Clients Java clients fail to start on HPUX IA64 SDF Wizard launched with incorrect JVM on some UNIX Platforms The operating system displays a message that Java cannot be found in the current PATH. When you launch the SDF Wizard, it displays a message indicating that the JRE cannot be located in the current path. The and displays the message: The SdfWizard executable launcher was unable to locate its companion shared library. On Linux AMD64, you can launch the SDF Wizard using GCJ. This is incorrect and JVM does not respond correctly. SDF Wizard does not work on Solaris AMD64 and IBM AIX 64 platforms. The bin directory of the JRE in use (which was specified at install time) must be in the PATH of the environment used to start the clients. Before launching the SDF Wizard executable, modify the script $SSABIN/sdfwiz to add the jre/bin directory. Add executable permission on the associated Eclipse library: cd $SSATOP/iirworkbench/plugins/ cd org.eclipse.equinox.launcher.motif.hpux.ia64_3 2_1.0.2.R34x_v chmod a+x eclipse_1116.so The PATH variable must include the path to the appropriate Sun JRE. Install and run the SDF Wizard on a Windows machine. IIR-RLN HF

4 UDB Database Prefetch feature does not work Synchronization Server does not work Informatica Identity Resolution does not work on Windows AMD64 using UDB The database Prefetch feature does not work when using UDB on Windows AMD64. Disable the Prefetch feature. Note: The Prefetch feature works correctly in all the other configurations. The Synchronization Server does not work correctly when run against UDB on Windows AMD64. There is a bug in UDB (IC62500) where indicators are treated as 32bit values instead of 64bit. Add the following line to $SSATOP/env/envs: set SSA_DB_SQLCACHESIZE=0 None. Do not use Synchronization Server in this configuration. Set the environment variable, SSA_UDB_BUG_IC62500=YES in the server environment script (env\envs or env\mdmres). SQL script dbscripts/ udb/create_schema.sql does not run The SQL script, dbscripts/udb/create_schema.sql has Windows line endings under Unix. Run dos2unix create_schema.sql before you run the SQL. ssan3sp.dll is missing from the distribution The dll ssan3sp.dll, which allows UDB Stored procedures access to the Name3 API is not packaged with this release. The dll can be made available for any supported platform on request. SSA-Name3 ASM Client fails to start In a Name3-only installation, the ASM Client does not start. Edit $SSABIN/asmcli and replace the string amsclie.jar with asmclienm3.jar. Name3 Workbench does not start on HPUX Itanium In a Name3-only installation on HPUX Itanium, the workbench does not start. Edit $SSABIN/wrkbench and add -d64 after SSAJAVA ($SSAJAVA -d64). japan and japan_i populations may fail to load The NAME3 Workbench has an issue when toggling hex format view If your installation is using either of these populations from a previous release, it fails to load. The NAME3 Workbench has an issue when toggling hex format view. The toggle to non-hex view may not convert the hex data correctly. The NAME3 Workbench has an issue in the ssan3_match tab. When using the Scatter-Gather input data format, the last two characters in the search and file fields are being overwritten by asterisks (*). Install the latest version of the population from the HotFix 1 distribution. Append two extra characters to the search and file fields. 4 IIR-RLN HF1-0001

5 General Windows line endings under Unix The dbscripts/udb/create_schema.sql has Windows line endings in Unix Run dos2unix create_schema.sql before you run the file Microsoft SQL Server 2000 is not supported. If you use MSQ2000, the following warning appears: The table 'IDS_FDT_META' has been created but its maximum row size (9171) exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a row in this table will fail if the resulting row length exceeds 8060 bytes. To be provided based on a Emergency Bug Fix request. The HF1 folder does not contain all the PDF documents When you download the Hotfix1 Documentation DVD, the HF1 folder consist of documents that were updated for the Hotfix 1 release. After you download the Hotfix1 Documentation DVD, copy PDF documents from both the and HF1 folders. The HF1 folder has PDF documents that were updated for the Hotfix 1 release. If your PDF document is not in this folder, copy the file from the folder. MySQL OBBC client is or greater MySQL is built and test3ed using MySQL server version: and MySQL client The recommended MySQL OBBC client is or greater. IIR-RLN HF