Informatica Corporation Informatica Version 9.0.

1 Release Notes
June 2010
Copyright (c) 1998-2010 Informatica Corporation . All rights reserved.

Contents
Informatica Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Informatica Domain Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Informatica Domain Fixes (9.0.1). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Informatica Domain Known Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 PowerCenter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 PowerCenter Compilers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 PowerCenter Fixes (9.0.1). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 PowerCenter Known Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 PowerCenter Third-Party Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 PowerExchange. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 PowerExchange Fixes (9.0.1). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 PowerExchange Known Limitations (9.0.1). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 PowerExchange Closed Enhancement Requests (9.0.1). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Informatica Analyst. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Informatica Analyst Fixes (9.0.1). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Informatica Analyst Known Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Informatica Developer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Informatica Developer Fixes (9.0.1). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Informatica Developer Known Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Informatica Developer Third-Party Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Data Quality Content Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Data Quality Content Installer Fixes (9.0.1). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Data Quality Content Installer Known Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Data Quality Integration for PowerCenter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Data Quality Integration for PowerCenter Known Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Data Analyzer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

IN_RLN_90100_0005

Data Analyzer Known Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Metadata Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Metadata Manager Fixes (9.0.1). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Metadata Manager Known Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Informatica Global Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 This document contains important information about installation, fixed limitations, and known limitations for the Informatica domain, PowerCenter, PowerExchange, Data Analyzer, Metadata Manager, Informatica Data Quality, Informatica Data Services, and Data Quality Content.

Informatica Domain
Informatica Domain Installation
Informatica Domain Patches and Libraries
Platform Linux-x64 Linux-x86 Linux-x64 Operating System Redhat 5.3 Redhat 5.3 SuSe 10 64- bit Operating System Patch 2.6.18-128.1.6.el5 2.6.18-128.el5 SUSE Linux Enterprise Server 10 (x86_64) VERSION = 10 PATCHLEVEL = 3 SUSE Linux Enterprise Server 10 (i586) VERSION = 10 PATCHLEVEL = 3 SUSE Linux Enterprise Server 11 (x86_64) VERSION = 11 PATCHLEVEL = 0 SUSE Linux Enterprise Server 11 (i586) VERSION = 11 PATCHLEVEL = 0 U6 10/08- kernel-patch 137137-09 SP2 and above Java 6 Patch 1.6.0_13 1.6.0_13 1.6.0_13

Linux-x86

SuSe 10 32-bit

1.6.0_13

Linux-x64

SuSe 11 64-bit

1.6.0_13

Linux-x86

SuSe11 32-bit

1.6.0_13

Solaris-sp64 Win-x64 Win-x86 Win-x64 Win-x86 AIX 64-bit

Solaris 10 Windows 2003

1.6.0_13 1.6.0_13 (win x64) 1.6.0_12 (win x86) 1.6.0_13 (win x64) 1.6.0_12 (win x86) IBM Java for AIX 1.6.0 SR5

Windows 2008 64-bit Windows 2008 32-bit AIX 5.3

SP1 SP1 OS level 5300-08 bos.adt.debug Version 6.1.0 (Fileset bos.adt.debug) OS level: 6100-00 bos.adt.debug Version 6.1.0 (Fileset bos.adt.debug)

AIX 64-bit

AIX 6.1

IBM Java for AIX 1.6.0 SR5

IN_RLN_90100_0005

Platform HP

Operating System HP-UX 11i v3

Operating System Patch QPKAPPSB.11.31.0909 QPKBASEB.11.31.0909 PHSS_34041

Java 6 Patch 1.6.0.04

HP

HP-UX 11.23

To run the AXIS samples or any client application developed with AXIS, you need AXIS 1.4. You can find AXIS libraries in $INFA_HOME/server/samples/WebServices/lib/axis-1.4.

Upgrading the Informatica Model Repository Service

When you upgrade to version 9.0.1, apply EBF 5405 to complete the upgrade of the Model Repository Service. Apply this EBF after you upgrade your Informatica 9.0 services to version 9.0.1. The Informatica Data Quality 9.0.1 electronic software download includes the EBF file and installation instructions.

Upgrading the Informatica Identity Resolution Transformation

When you upgrade to version 9.0.1, you must register the Identity Resolution transformation if you are upgrading from versions 7.x, 8.x, or 9.0. 1. Configure the 9.0.1 Repository Service to run in exclusive mode. 2. Connect to the 9.0.1 Repository Service with the pmrep Connect command using a user account with Admin Repository privilege. 3. Locate irtransform.xml in the following directory: $INFA_ROOT\server\bin\native $INFA_ROOT is the Informatica 9.0.1 installation directory. 4. Use the pmrep RegisterPlugin command to update the repository. The RegisterPlugin command uses the following syntax:
Registerplugin -i <input_registration_file_name_or_path> -e -N

Upgrading the Unstructured Data Transformation

When you upgrade from 8.6.1 to version 9.0.1, the Relational Hierarchy tab is disabled. You must register the Unstructured Data transformation. 1. Configure the 9.0.1 Repository Service to run in exclusive mode. 2. Connect to the 9.0.1 Repository Service with the pmrep Connect command using a user account with Admin Repository privilege. 3. Locate pmudt.xml in the following directory: $INFA_ROOT\server\bin\native $INFA_ROOT is the Informatica 9.0.1 installation directory. 4. Use the pmrep RegisterPlugin command to update the repository. The RegisterPlugin command uses the following syntax:
Registerplugin -i <input_registration_file_name_or_path> -e -N

IN_RLN_90100_0005

Upgrading Metadata Manager on IBM DB2

When the Metadata Manager repository is on IBM DB2 9.1, 9.5 or 9.7, the upgrade of the Metadata Manager Service might fail with the following error:
[DB2 JDBC Driver] [DB2] CANNOT ADD COLUMN TO TABLE; TABLE HAS EDIT PROCEDURE.

Workaround: Run the following DB2 command on the Metadata Manager repository:
REORG TABLE IMW_CONNECTION

Then, re-upgrade the Metadata Manager Service using the mmcmd upgradeRepository command. mmcmd is located in the following Informatica Services installation directory:
<Installation directory>\services\MetadataManagerService\utilities\mmcmd

Configuring the Reporting Service

After you install or upgrade the Informatica domain, complete the following task to run the Reporting Service on a Windows node. Add the following path to the Path environment variable on each Windows node that runs the Reporting Service:
%SystemRoot%\system32

If you do not add the path, the Reporting Service does not start and the following error appears in the Console-Redirect.log file in the tomcat/jboss/server/Informatica/log directory:
'findstr' is not recognized as an internal or external command, operable program or batch file.

(CR 237423) (added 9/2/2010)

PowerCenter Installation
Orchestration server configuration fails on HP-UX and Solaris 64 during the Informatica Services installation or upgrade. The installer cannot find the libjli.so library. Before you run the Informatica installer, set the library path environment variable: HP-UX
setenv SHLIB_PATH <installer_location>/source/java/jre/lib/IA64W/jli

Solaris 64
setenv LD_LIBRARY_PATH <installer_location>/source/java/jre/lib/sparcv9/jli

The installer location is the path to the directory where you extracted the Informatica installer.

Informatica Domain Fixes (9.0.1)

CR 233608 233607 231620 Description Domain logs do not contain complete stack trace for exception messages. Domain logs did not always report errors updating master gateway node. infasetup command fails without execute permissions.

IN_RLN_90100_0005

CR 231365

Description The Navigator in the Administrator tool does not list all services if a PowerCenter Integration Service is configured to run on a grid with no node. Trusted connection not stored for Microsoft SQL Server connections. HTTP port number for some services not displayed in logs. Port number used by Data Integration Service not displayed in logs. On IBM AIX 64-bit, queries to the SQL data service that return very large numbers of rows can fail. Cannot configure permissions for operating system profiles. The script for the Informatica Services uninstaller fails to start when you run it on machines with a Turkish locale. When the master gateway node fails over to another node, all other gateway nodes shut down. When you create a PowerCenter Integration Service through infacmd and you do not specify the code page process option, you cannot view or change the code pages in the Administrator tool. When the gateway node fails over, the Model Repository Service continues to try to connect to the previous gateway node. infacmd considers case for parameters such as node name when you create a service. The service appears in the Navigator but not in the domain perspective. An error may appear when you expand a folder of users in the Administrator tool and the folder contains a lot of users, such as 2,000 users. The infasetup isp defineDomain command does not have a parameter to configure the schema for a Microsoft SQL Server database. The DTM hangs when you connect to mySQL through ODBC to preview columns of the bit datatype with a precision greater than 8. You cannot import a Sybase table through ODBC when the table name contains more than 30 characters. For more information, contact DataDirect and refer to issue WR W911130019.a. The master node shuts down if it does not have enough file descriptors. Some master domains may require more than 1,024 file descriptors.

231034 230714 230712 227368 225983 227145 224807 224493

223691

223153

221578

221539

220645

220092

216498

IN_RLN_90100_0005

Informatica Domain Known Limitations

CR 238030 Description If you install the Informatica services after you install the Informatica clients and you install the services in the same directory as the clients, the DataDirect ODBC 6.0 drivers are not installed. Workaround: Copy the folder that contains the ODBC 6.0 drivers from the <Informatica_Installation_Dir>\clients\tools directory to the root directory. For example, if you install Informatica on c:\Informatica901, copy the directory c:\Informatica901\clients\tools\ODBC6.0 to the root of the Informatica installation directory so you have the following directory: c:\Informatica901\ODBC6.0 (fixed in 9.0.1 HotFix 1) The BackupDomain command generates an exception if you set the -tc option. The Restart the Domain Configuration Upgrade option is not available for failed upgrades from Informatica 9.0 to 9.0.1. When you run the installer to fix a failed upgrade, the Restart the Domain Configuration Upgrade option does not display. You cannot select whether to override an upgrade contention when more than one administrator upgrades Informatica 9.0 at the same time. The fix to the upgrade fails and the log files display exception messages. Workaround: Restore the domain configuration repository from backup. Verify that no other administrator is upgrading the domain configuration repository and run the installer again. (fixed in 9.0.1 HotFix 1) The Model Repository Service intermittently fails on IBM DB2 9.5 and 9.7 when fetching a very large number of objects from the Model repository through the Data Direct drivers. Workaround: Restart the Model Repository Service. On AIX, you cannot use the domain object Permissions view to assign permissions on the object. Workaround: Click Manage > Permissions to use the Manage Permissions dialog box or use the infacmd command line program to assign permissions. (fixed in 9.0.1 HotFix 1) The domain upgrade fails when you run the installer a second time under the following conditions: - You upgrade from PowerCenter 8.1.x, 8.5.x, or 8.6.x. - The domain upgrade failed the first time due to a database issue. - You ran the installer the second time using the restart the domain configuration upgrade option. Workaround: To upgrade the domain, run the installer a third time using the restart the domain configuration upgrade option. You cannot edit an application service in the Administrator tool after you delete an associated application service. Workaround: Assign another associated application service, re-create the dependent application service, or create the associated application service with the same name. (fixed in 9.0.1 HotFix 1) The RestoreDomain command generates an exception if you set the -tc option. The Service Manager shuts down with a java heap space error when more than 100 users are online using services that require user privileges. Workaround: Increase the default memory allocation. After you create an application service, the new service does not appear in the service name filter on the Logs tab. Workaround: Refresh the domain by selecting the domain and clicking Actions > Refresh. Or, select a service type on the Logs tab, and then select the new service from the service name filter. (added 07/14/2010) The Administrator tool hangs if you create a folder when you select the location in which to create an object. Workaround: Refresh the browser. When you export user activity log events in the Administrator tool, the exported file includes log events completed by your user account only. The file should include log events completed by all users.

237763 237738

237627

237576

237497

237473

237379 237321

237281

237189

237087

IN_RLN_90100_0005

CR 237028

Description If you create a Data Integration Service with a user other than the repository administrator for the Model repository connection, you are prompted to upgrade the service. Workaround: Delete the Data Integration Service, and create it with a user that has the Model repository Administrator role. You cannot use the Administrator tool to edit the Log Directory Path property for the nodes in the domain. When you restart the domain, the property uses the default value configured in the nodemeta.xml file. (fixed in 9.0.1 HotFix 1) The infacmd dis CreateService command generates an exception when you create a Data Integration Service with a port that is out of range. (fixed in 9.0.1 HotFix 1) Reporting Service user privilege assignments are lost when you restart the domain. Workaround: Use roles to assign user privileges. If you delete the node associated with a Model Repository Service, the JVM Command Line Options advanced service property is set to null. As a result, you cannot edit any Model Repository Service properties. Workaround: Add the following default value to the JVM Command Line Options property: -Xms256m -XX:MaxPermSize=128m -Dfile.encoding=UTF-8 LDAP user privileges assignments are lost when you upgrade a PowerCenter 8.1.1 Repository Service. (fixed in 9.0.1 HotFix 1) Model repository databases on IBM DB2 contain inconsistent data when the service upgrade fails. Workaround: Complete the following steps to retry the Model Repository Service upgrade: 1. Delete the contents of the Model repository database. Use infacmd mrs DeleteContents or the IBM DB2 database client to delete the contents of the database. 2. Use the IBM DB2 database client to restore the 9.0 Model repository from a backup. 3. Use the upgrade wizard to upgrade the Model Repository Service. If you run three or more Reporting Services on an HP-UX 11.31 node, the JBoss process that runs the Reporting Services fails. Workaround: Allocate more memory to JBoss. 1. Use a text editor to open the run.conf file in the following directory: <Informatica_Installation_Directory>/tomcat/jboss/bin 2. Search for the following text:JAVA_OPTS="$JAVA_OPTS -Xms 3. Set the values for Xms and Xmx to 1024 or more. For example:
JAVA_OPTS="$JAVA_OPTS -Xms1024m -Xmx1024m -XX:MaxPermSize=256m -Dsun.rmi.dgc.client.gcInterval=3600000 Dsun.rmi.dgc.server.gcInterval=3600000"

236884

236486

236273

236261

235652

234580

234182

4. Restart the Reporting Services. 231425 The Service Manager cannot upgrade or import LDAP subgroups that have the same name. For example, you have the following groups in an 8.6.1 LDAP security domain or in an LDAP directory service: - Parent_Group1 - Child_Group - Parent_Group2 - Child_Group When the Service Manager upgrades the 8.6.1 LDAP security domain or imports the LDAP users and groups, the Service Manager removes the first Child_Group and keeps the second Child_Group. The second Child_Group becomes the subgroup of both parent groups.

IN_RLN_90100_0005

CR 229556

Description Informatica fails to start if you create the domain configuration repository on a Microsoft SQL Server database and you select the following options during installation: - Use a trusted connection to connect to Microsoft SQL Server. - Run the Informatica Windows service under the user account that installed Informatica. Workaround: - If you use a trusted connection to connect to Microsoft SQL Server, run the Informatica Windows service under a different user account. - If you use a trusted connection and run the Informatica Windows service under the same account, start Informatica from the command line. Use the following command: infaservice startup The Administrator tool might display a blank screen instead of the login page. The Administrator tool log is empty and no errors appear. Workaround: Stop Informatica services. Delete the following folders in the <INFA_HOME>/services/AdministratorConsole directory: - adminhelp_en - adminhelp_pt_BR - administrator Restart the Informatica services. (fixed in 9.0.1 HotFix 1) Domain upgrade, domain restart, and LDAP user synchronization processing time increases proportionally with the number of users in the domain. When the domain contains more than 1,000 users, the domain may shut down unexpectedly and the Edit Roles and Privileges dialog box fails to launch for LDAP users. Workaround: Increase the system memory used by the domain. Complete the following steps on each gateway node to increase the system memory for the domain: 1. Go to the <901InstallationDir>/tomcat/bin directory and open infaservice.(bat|sh) in a text file editor. 2. Update the -Xmx value for INFA_JAVA_OPTS. In infaservice.bat, update the following line of code: set INFA_JAVA_OPTS=%INFA_JAVA_OPTS% -XX:GCTimeRatio=9 -Xmx512m In infaservice.sh, update the following line of code: INFA_JAVA_OPTS="${INFA_JAVA_OPTS} -XX:GCTimeRatio=9 -Xmx512m" For example, to set the system memory to 2 GB, use -Xmx2048m. If the Administrator tool is configured to use HTTPS and the keystore file is deleted, you cannot access the Administrator tool. Workaround: Create a keystore file for the Administrator tool in the directory indicated in the following log file: <Informatica_Installation_Dir>\tomcat\temp\_AdminConsole\logs\catalina.<Date>.log View the log file and search for the log message that shows the expected location of the keystore file:
LifecycleException: service.getName(): "_AdminConsole"; Protocol handler start failed: java.io.FileNotFoundException: <KeystorePathAndFileName> (No such file or directory)

225063

224148 234076 234101 236215 236242

224060

For example:
LifecycleException: service.getName(): "_AdminConsole"; Protocol handler start failed: java.io.FileNotFoundException: /export/home/901/source/isp/bin/keystore_lin64 (No such file or directory)

In this error message, the expected location of the keystore file is /export/home/901/source/isp/bin and the keystore file name is keystore_lin64. 222640 You must specify the Java memory values in megabytes. You cannot specify gigabytes or kilobytes. (fixed in 9.0.1 HotFix 1) You cannot convert an existing master gateway node to serve as a worker node. The infasetup isp defineDomain command returns incorrect error messages when the command contains tablespace errors. The $PMRootDir service process variable shows unknown location after you add a node to a grid. (fixed in 9.0.1 HotFix 1) When you create a grid, the Administrator tool displays the following inappropriate messages: - You need to set up a codepage and enable the process on this node for each Integration Service that runs on this grid. - Removing node(s) will abort Integration Service processes running on it. You can ignore these messages.

222472 222403 222181

219577

IN_RLN_90100_0005

CR 218937

Description An application service may not work correctly when you make changes to the service. - The Analyst Service may be in an ambiguous state when you change the Model Repository Service, Data Integration Service, or staging database connection associated with an Analyst Service. Workaround: Restart the Analyst Service. - The PowerCenter Integration Service may be in an ambiguous state when you change the PowerCenter Repository Service associated with a PowerCenter Integration Service. Workaround: Restart the PowerCenter Integration Service. - An application service may be in an ambiguous state when you change the node on which the service runs. Workaround: Restart the application service. An LDAP security domain that is recently added to the domain does not appear when you create or edit a PowerCenter Integration Service. Workaround: Refresh the page where you create or edit the PowerCenter Integration Service. The first time that you select an application service and click Actions > View Logs for Service, the Logs tab displays log events for all service types. Each subsequent time that you view the logs for a service, the Logs tab displays log events for the selected service only. (added 07/14/2010) You cannot edit the Analyst Service in the Administrator tool after you delete the associated Data Integration Service and Model Repository Service. Workaround: Re-create the Analyst Service, or create the associated application services with the same name. Non-administrator users cannot connect to an application service after a master gateway failover if the application service does not have a backup node. Workaround: Recycle the application service. (fixed in 9.0.1 HotFix 1)

215864

210758

203073

198708

PowerCenter
PowerCenter Compilers
You can use any C compiler for Custom transformation procedures. Use the C++ compiler versions that appear in the Product Availability Matrix. The Product Availability Matrix is available on the Support page at http://mysupport.informatica.com. Use C++ compiler versions for any External Procedure or Custom transformation, and when you develop with PowerExchange SDK. If you compiled the DLL or shared library with a C++ compiler version that does not appear in the Product Availability Matrix, you need to recompile it. You do not need to recompile a Java transformation if the JDK is compatible with the version that you used for the previous compile.

IN_RLN_90100_0005

PowerCenter Fixes (9.0.1)

CR 223801 213003 202370 Description Java Mapping SDK fails to retrieve mapping objects if there are multiple source or target instances in the same mapping. Integration Service terminates when when multiple PowerCenter Clients start workflows at the same time. Incorrect message appears when a file in a file list does not exist.

PowerCenter Known Limitations

CR 238006 Description When the Integration pushes a UNION ALL clause to a Sybase 15.0 database, the database server returns the wrong results. Workaround: Disable pushdown optimization for this session. Data Transformation source and target sessions fail on HPUX computers because a library is missing from the PowerCenter installation. When you run a PowerCenter session on Windows, the PowerCenter Integration Service can fail to connect to the database. This problem can occur when the database driver directory in the PATH environment variable is set incorrectly. Workaround: Verify that the path for the database driver in the PATH environment variable is correct. Search for the following path in the PATH environment variable:
\tools\datadirect

237620

237413

Remove the backslash (\) at the end of the path before the semicolon (;). For example, this path is incorrect:
c:\Informatica\9.0\tools\datadirect\;c:\oracle\bin

Remove the backslash at the end of the DataDirect driver path:

c:\Informatica\9.0\tools\datadirect;c:\oracle\bin

(fixed in 9.0.1 HotFix 1) 236462 The Integration Service displays an invalid user and password error if you run a workflow with the following conditions: 1. Create a workflow and assign an Integration Service to the workflow. 2. Delete the Repository Service. 3. Create a Repository Service with the same name. 4. Connect to the Integration Service from the Workflow Monitor. -orRun the workflow from the Workflow Manager. Workaround: Recycle the Integration Service. The Designer does not highlight text in the Java Code tab when you define an expression for a Java transformation.

236247 236244 235961

The DTM process fails with an unexpected condition when Repeat Null Characters contains double byte characters for fixed-width flat files. The PowerCenter Repository Service on HP-UX 11.31 causes memory leaks when you perform continuous operations against the PowerCenter repository. Continuous operations include running workflows, importing and exporting objects, and connecting to the repository. When the Repository Service leaks memory, it hangs when you delete a folder.

231642

228457

10

IN_RLN_90100_0005

CR 226107

Description The Portuguese PowerCenter Designer cannot find the XML templates when you select a menu item in the slowly changing dimensions mapping template wizard. Workaround: Copy directory PowerCenter\client\bin\pmmaptmplimp\Templates\pt_BRto a new directory and name the directory PowerCenter\client\bin\pmmaptmplimp\Templates\pt. Keep both folders. Run the mapping wizard again. (fixed in 9.0.1 HotFix 1) You cannot enter tab keys on the Java Code tab of the Java transformation. A PowerCenter Integration Service that runs on Windows 64 shuts down unexpectedly when you debug a mapping and the Create a Debug Session Instance option is enabled. The Integration Service writes an incorrect decimal number to a DB2 target decimal column when the precision is 19 or greater and PowerCenter is running on Linux 32-bit. Workaround: Enable high precision. In Mapping Architect for Visio, an error occurs when you edit a PowerExchange source definition or links between mapping objects where the group name property of PowerExchange database contains special characters. A session uses an increasing amount of memory when a Java transformation passes rows to the Unstructured Data transformation. Pushdown optimization session fails when Source Qualifier transformations are based on the same source. When you enter a date range for a random data mask, the Designer accepts invalid date values.

224015 222189

221152

213504

195470

194945 180718

PowerCenter Third-Party Limitations

CR 221008 Description Teradata ODBC session on UNIX fails when you use the update system operator and set the OptimizeTeradataUpdate custom property. For more information, see Teradata incident<RECDCHD82>. (fixed in 9.0.1 HotFix 1)

PowerExchange
PowerExchange Fixes (9.0.1)
CR 235951 Description If you import a COBOL copybook when creating a data map in the PowerExchange Navigator, PowerExchange incorrectly creates a dummy column named FILLER_REDEF_1 if it encounters a REDEFINES clause within an OCCURS clause. When you run a database row test on the data map, an error occurs. A bulk data movement session that writes to a VSAM relative record data set might fail with message PWX-00784, indicating that update mode is not supported, even though the transaction type for the PWX NRDB Batch connection is defined as insert only. During a cold start of the Datacom table-based ECCR, an inflight dummy UOW (FFFFFFFFFFFFFFFFF0000) causes the ECCR to fail.

235950

235007

IN_RLN_90100_0005

11

CR 233627

Description For DB2 for i5/OS CDC in real-time extraction mode, PowerExchange incorrectly sets the value of the DLT_CAPXRRN column in many change records to 2147483647 when offload processing is enabled. PowerExchange issues error message PWX-10232 during an Oracle CDC session that extracts changes in continuous extraction mode from PowerExchange Logger for Linux, UNIX, and Windows log files. If you try to register a DB2 for i5/OS table that was created in the i5/OS SQL interface and has a long file name in mixed case, the PowerExchange registration process fails. PowerExchange expects the long file name to be in uppercase. When you run a PowerCenter session with a flat file target and a z/OS source that uses a German code page for the source application connection, fields that are defined as ZONED and UNZONED are converted to zeros. Oracle sends backout records for a failed update to the PowerExchange UOW Cleanser for CDC in an order that PowerExchange does not expect. As a result, extraction processing stops. When a CDC session tries to extract changes from a PowerExchange Logger for Linux, UNIX, or Windows log file in continuous extraction mode, it might fail with error messages PWX-10232 and PWX-23046 because of unnecessary checking of sequence information. In a PowerExchange Navigator database row test and in a PowerCenter session run, Hebrew characters are displayed in reverse order. During a change from daylight savings time to standard time, PowerExchange Condense processing fails with the message PWX-10232, which indicates an internal error occurred. The default DBTYPE for database row tests should be CAPXRT. The IDMS ECCR abends with message PWX-00999 when processing a journal. The message indicates the following program logic error: "UOW Hash Table - Unexpected primary AREA duplicate for run unit id." The DB2 for z/OS ECCR abends with message PWXEDM177588E when reading the catalog for a table space defined in a storage group that uses an extended-addressing-enabled SMS data class. When a PowerCenter workflow includes a Lookup transformation for a PowerExchange source with a != condition in a SQL WHERE clause, PowerExchange issues an error message indicating that the != condition is not supported. The IDMS ECCR abends with an EC6 error code, indicating a CPU usage timeout, when processing a journal. During DB2 for z/OS ECCR processing, share locks that the DB2 IFI306 interface obtains on the catalog, the work table space, and various customer table spaces are not released. IMS synchronous CDC processing abends after patch P519776 is applied. When the security feature is enabled, that is, the first parameter in the SECURITY statement is set to 1 or 2 in the DBMOVER file for both the source and target PowerExchange Listeners, the DTLURDMO utility requires the same USER and PASSWORD values for both the source and target. The PRESTLIB JCL that you run when installing a hotfix on z/OS does not reflect changes to DB2 for z/OS members in the DBRM library. As a result, a bind error occurs. Some SQL Server registrations that are created with the DTLUCBRG utility do not appear in the PowerExchange Navigator. After you restart a PowerExchange Logger for Linux, UNIX, and Windows process that ended abnormally, the process fails with message PWX-10232, which indicates a sequence error. Workflows might fail to restart when RESTART1=CURRENT_RESTART and RESTART2=CURRENT_RESTART are specified in the restart token file.

233219

232461

231543

230693

230539

228144

227871

227385 227232

226398

226322

225074 225031

224554 224547

224236

222198 221990

221371

12

IN_RLN_90100_0005

CR 220028

Description Multiple CDC sessions that use the CAPXRT access method and have Oracle sources might write the Oracle catalogs to the log files at the same time, resulting in reduced performance and unnecessary write activity. When an Oracle database uses a Japanese code page, Oracle messages that indicate a connection error and are issued during a PowerCenter session are not translated correctly. A memory leak occurs during IMS synchronous CDC processing when units of work (UOWs) from an external subsystem are mixed with BMP processing in a DBCTL environment. PowerExchange does not support IMS 7 for CDC processing. If you use PowerExchange Condense or the PowerExchange Logger for Linux, UNIX, and Windows and set its NO_DATA_WAIT parameter to a time interval, in seconds, that is less than the FILE_SWITCH_VAL time interval, in minutes, condense processing might become erratic. The PowerExchange Condense task might end abnormally on i5/OS if you receive the following message and enter a response other than Y or N:
PWX: Error 1 on Delete of file PWX860CND2CHKPT(V0). Retry? (Y/N)

219964

219776

218743 214526

211661

203745

If you use PWXPC with an extraction map source that contains BI or CI columns and attempt to extract change data from full condense files that contain before and after images, PowerExchange incorrectly issues message PWX-04548.

PowerExchange Known Limitations (9.0.1)

CR 236713 Description Bulk data movement workflows that load data to VSAM RRDS data sets fail when the Write Mode attribute on the PWX NRDB Batch application connection is set to Confirm Write Off. (fixed in 9.0.1 HotFix 1) If you use the DTLURDMO utility REG_COPY statement to copy Microsoft SQL Server capture registrations on a 32-bit Windows machine, an unhandled win32 exception might occur in DTLURDMO.exe. This error occurs when the REG_COPY operation tries to use a MODIFY statement that includes the MSSOPTS parameter with the DBNAME option. You can successfully perform this type of REG_COPY operation on a 64-bit Windows system. PowerExchange cannot use SSL when running with a Linux 64-bit operating system on an Itanium machine. PowerExchange issues the following error message:
PWX-31054 Can't read certificate chain file. Key=key.

223756

186226

183354

PowerExchange is not able to read DB2 for z/OS image copies for partitioned table spaces. In this situation, PowerExchange issues the following message:
PWX-09263 Dictionary Page found. Image copy reading not supported for compressed TS.

178628

Oracle change data that PowerExchange extracts in conjunction with Oracle LogMiner might be incomplete if you run PowerExchange in an Oracle RAC environment. Oracle LogMiner might not extract all change data when performing continuous mining across log sequences that contain points in time where one or more instances have been stopped or started. As a result, the application of change data to target tables can either fail or be incomplete. Workaround: For information about the problem, refer to Oracle bug number 6596564 or contact Oracle Support for assistance. Oracle supplies patches to fix this problem for Oracle 10.2.04. Oracle has incorporated the fix into Oracle 10.2.0.5 and 11.2. If the lowest level segment in an IMS database is not keyed, the Update all matching segments option on the IMS Options tab of the Table Properties dialog box in the PowerExchange Navigator does not work. Workaround: Do not select the Update all matching segments option if you have non-keyed segments.

177405

IN_RLN_90100_0005

13

CR 176411

Description When concatenated key (CCK) fields are passed from IMS to PowerExchange to create SSAs, PowerExchange does not use a lower-level CCK field unless you provide the CCK of the ROOT. The absence of the root key causes unqualified GN calls to scan IMS databases. Workaround: Always specify the key of the root. When a DB2 for z/OS bulk data movement operation fails, PowerExchange might not write an error message to the PowerExchange message log or PowerCenter session log to notify you of the situation. The PowerCenter session appears to complete successfully.

151818

PowerExchange Closed Enhancement Requests (9.0.1)

CR 233368 Description Define the TIMEZONE statement in the DBMOVER configuration file to read or write Adabas date-time values in your local time for bulk data movement sessions. This statement applies only to Adabas 8.2.2 data sources or targets that include datetime fields for which the Adabas TZ option is specified in the field definitions. For an Adabas 8.2.2 source, a data map for which you import field metadata from an FDT can include mixed-case field names. Previously, the Adabas field names in data maps were in uppercase only. If you configure a cache size, PowerExchange caches NRDB data maps on the system where they are used by a single PowerExchange Listener, or by multiple PowerExchange Listener, netport, and batch jobs. If you use Oracle materialized views, PowerExchange can capture change data from the tables that underlie those views. PowerExchange CDC supports any type of materialized view. For DB2 for i5/OS CDC sources that include multiple data members, you can populate the DTL__CAPXUSER column of each change record with the member name as well as the library and file names. To do so, set the LIBASUSER parameter to M on the AS4J CAPI_CONNECTION statement. Bulk data movement sessions for z/OS DB2 image copies support uncompressed table spaces in reordered row format. The DTLURDMO utility writes the unmasked value of the encrypted password to the PowerExchange log file. For a data map record defined for a nonrelational data source, the GetCurrentFileName function gets the name of the source data file. Use this function to determine from which data file the data for a record was read.

231529, 230427 229493

227383

227359

223386 222195 221532

Informatica Analyst
Informatica Analyst Fixes (9.0.1)
CR 227649 225375 Description A scorecard does not show the total number of valid or not valid records. The Analyst Service on SuSe Linux 10 32 bit shuts down unexpectedly when you create a flat file data object or import a reference table from a flat file in the Analyst tool and preview the data.

14

IN_RLN_90100_0005

CR 225171

Description To enable the prebuilt Informatica rules to function correctly when installed to the Model repository, the staging database read by the rules must be named "Staging" and the user name and logon details of the application user must match the staging database connection details. When you create the Analyst Service on a worker node in the Informatica domain, a user cannot log in to the Analyst tool URL because the URL uses the host name for the gateway node instead of the worker node. The profiling warehouse can store a maximum of 85 Unicode characters (255 bytes) in a column value. If a column value exceeds this number, the value is truncated. The Analyst tool cannot drill down on column patterns in profiles that have UTF-8 data.

224498

224303

209742

Informatica Analyst Known Limitations

CR 242791 Description The Audit Trail on a bad record or duplicate record table omits data from staged data columns if the column names are not stored in upper case. In this scenario, the Audit Trail table shows data in the Status, User, and Last Updated columns only. Workaround: store column names in upper case in any database table you analyze for bad or duplicate records. (added 09/03/10) You cannot create an ODBC connection in the Analyst tool or import tables using ODBC connections in the Analyst tool if the Analyst Service runs on HP-UX IA. Workaround: Rename the libpmjodbc.sl library in the INFA_HOME/services/shared/bin directory to libpmjodbc.so. (fixed in 9.0.1 HotFix 1) If you drill down on profile results, null values are shown as empty cells. The drill-down results do not distinguish between null values and empty cells and both appear as empty cells. If you run a profile with a reusable rule in the Analyst tool and later change the rule name and rerun the profile, the Analyst tool does not display the new name. If you open the Analyst tool in Mozilla Firefox version 3.6 or later, do not resize the Run Profile dialog box. If you attempt to resize this dialog box, the browser may fail. You cannot preview a database table during table import if the table name begins with a digit. The Analyst tool displays a message that the table is not valid. If you complete the wizard, the table imports successfully. A scorecard may report problems with a data column if the column contains more than 200 unique values. Workaround: Set the profile data sampling options to return fewer than 200 rows. The Analyst tool cannot find and replace null values in a reference table if a column name in the table contains a lower case character. The Analyst tool cannot find and replace non-null values on a reference table column that you select from the menu if the selected column name contains any lower case character. You can select all columns in the reference table and perform search and replace operations on non-null values. The Analyst tool does not update the scores displayed in a scorecard that reads a logical data object if you delete some columns from the logical data object and rerun the scorecard. Profiling results do not read the time stamp for a record to subsecond level when generating value frequency data. When multiple records have common time stamps to hh:mm:ss level but differ at subsecond level, the value frequency results show data from one of the records only. If you drill down on the value frequency results, you can view the values that do not display.

237964

237113

235819

233703

233416

229428

224632

223614

217082

IN_RLN_90100_0005

15

Informatica Developer
Informatica Developer Fixes (9.0.1)
CR 236202 Description When you use an SQL data service as an ODBC data source for a Lookup transformation in a PowerCenter mapping, the associated session fails. You cannot preview an IBM DB2 table with an orderby clause. You cannot import a column with a space in the column name. You cannot propagate the datatype for Association or Consolidation transformation output groups. The Jaro Distance algorithm does not identify transposed characters. Application deployment fails when the project name and application name are identical. The Navigator lists duplicate table names when you connect to an ODBC datasource using WinSQL. A null pointer exception occurs when you preview a logical data object with an attribute that contains a list of values, a minimum value, a maximum value, or an expression. You cannot run a query against a virtual table if the virtual table mapping contains a Consolidation transformation. A Match transformation that uses a matching rule to generate identity match scores fails if the identity key field is not used in a matching strategy. The process does not display an error message. The Informatica JDBC Driver does not support the use of SQL escape sequences for date and time literals. A Parser transformation may not parse values correctly if you configure it in token parsing mode and select Reverse Enabled parsing. The Data Integration Service truncates data when it reads data from and writes the data to a column with a negative scale. Windows Authentication requires a user name and password for trusted connection. Matching operations can generate incorrect clusters when non-matching transformations are added to a matching rule. This issue has been observed when a Standardization transformation is added.

233174 232392 232063 231881 230645 230443 225495

225328 224912

224592 224445

223562 222287 216175

Informatica Developer Known Limitations

CR 238073 Description Mapping is not valid when you paste an input port that has a default value as an output port in an SQL transformation. Workaround: Re-create the output port. The Model Repository Service returns no results when you search for a relational data object in the Model repository. (fixed in 9.0.1 HotFix 1)

237798

16

IN_RLN_90100_0005

CR 237996

Description Stack overflow exception occurs when you resize a virtual table created from a customized data object that contains multiple related tables. Workaround: Close the editor and reopen it before you resize the virtual table. (fixed in 9.0.1 HotFix 1) If you delete a reference table object from a project folder in the Developer tool or Analyst Tool, the reference table data remains in the staging database. If you configure a Labeler transformation to replace reference table entries with custom text, and you later open the transformation and select the same reference table, you must enter the custom text again. (fixed in 9.0.1 HotFix 1) The Mapping Service shuts down unexpectedly when you run a mapping with a large number of transformations, for example, 100 or more, on AIX. If you create two profiles that read different native metadata objects, you cannot define a join analysis on the native metadata objects across the two profiles. (fixed in 9.0.1 HotFix 1) The Developer tool cannot find a reference table that is specified in a parameter path if the path contains a forward slash separator. The Developer tool may consume unexpected amounts of memory if you open a reference table multiple times in succession. The memory consumption may increase to a point where the Developer tool becomes unresponsive and other machine processes are affected. Workaround: Close and reopen the Developer tool to view the reference table, or view the reference table through the Analyst tool. The Developer tool can specify a reference table as a parameter. It reads the parameter setting from a different tab depending on whether you run the mapping or run a profile on the mapping. When you run the mapping, the Developer tool looks for the parameter on the Parameters tab. When you profile output from a mapping object, the Developer tool looks for the parameter on the Configuration tab. The Data Integration Service does not update connection properties when you use database connection pooling and you change connection properties other than user name, password, and connection string between data previews. Workaround: Restart the Data Integration Service after you change connection properties. (fixed in 9.0.1 HotFix 1) If you enter a custom SQL query that contains a DDL statement in a customized data object, the Developer tool might execute the query against the database when you validate the query. Because the Developer tool does not retain key field information for nonrelational data sources, you cannot include an Update Strategy transformation in a Developer tool mapping for a nonrelational data source. You cannot preview data on a transformation that reads data from a mapping object that has multiple output groups. When you create a parameter that specifies a reference table, you cannot include the Model Repository Service name in the path to the reference table. The Decision transformation does not validate that the datatype returned by a transformation function is compatible with the datatype on the associated output port. (fixed in 9.0.1 HotFix 1) You cannot preview a relational resource if the resource, schema, or column names contain ASCII characters 0-30. Workaround: Enable the Support Mixed Case Identifiers option and specify the SQL identifier character for the connection. These options place quotes around the resource, schema, or column names in the SQL query the Data Integration Service uses to read data from the resource. (fixed in 9.0.1 HotFix 1)

237792

237476

237399

237200

236499

236286

235924

234981

234898

234419

234186 234117

234064

233660

IN_RLN_90100_0005

17

CR 233117

Description A profile created and run on a database table column in the Developer tool fails if the column name has changed since import and the column belongs to a table imported through the Developer tool. You cannot import a resource into the Developer tool if the resource name is null. You cannot preview an Oracle relational resource if the resource, schema, or column names contain a question mark character (?). A mapping that uses multiple Association transformations to associate record clusters in a flat-file data set of ten million records or greater may generate a cache memory error. (fixed in 9.0.1 HotFix 1) You cannot run a mapping that contains two side-by-side Match transformations when both transformations are set to identity match mode. Workaround: Configure the mapping to run the transformations serially. If you run a mapping that writes data to a SQL Server resource using the ODBC driver for SQL Server, the Data Integration Service rejects all records that contain data of type hierarchyid. Workaround: Use the native SQL Server driver instead of the ODBC driver. Bulk loading fails when you run a mapping that loads long varchar for bit data to an IBM DB2 database and the database server version is 9.1, the database client version is 9.5, and the Data Integration Service runs on 64-bit SUSE Linux. Address validation and profiling operations run slowly on Solaris. If you run multiple profiles on large files concurrently in the Developer tool, you may experience decreased profiling performance and profiling processes may consume excessive disk memory. (fixed in 9.0.1 HotFix 1) Mapping generates a core file on Solaris 64-bit if you enable Truncate Target Table for an IBM DB2 9.5.x target and you set the number of rows you want to preview to 0. The configuration settings for data quality transformations in mappings deployed to PowerCenter are not visible and cannot be edited. You cannot use Auto Link to connect ports to the Address Validator transformation if the linked ports define an address template that is not valid. Workaround: Connect ports to a single input port group on the Address Validator transformation.

230251 227301

224876

224728

224341

222982

221351 215837

215419

214641

202706

Informatica Developer Third-Party Limitations

CR 235359 Description When you import a Teradata resource with a large object datatype column through a customized data object custom SQL query, the Developer tool sets the column precision to 1. (fixed in 9.0.1 HotFix 1) When you create a relational data object from a MySQL resource, the Developer tool imports YEAR, TEXT, and BLOB columns differently when you import the same resource as a relational data object or through a custom SQL query. The affected columns might differ in datatype or precision value. If you use a custom SQL query to read data from Sybase or MySQL resources with unsigned integer columns, data loss might occur because the DataDirect ODBC Driver for Sybase, version 6.0, and the DataDirect ODBC Driver for MySQL, version 6.0, retrieve unsigned integers with the same precision as signed integers.

235200

235211, 235197

18

IN_RLN_90100_0005

CR 235000

Description If you use the Developer tool to enter an SQL query against a SQL Server resource that contains a hierarchyid column, the query fails. The query fails because the DataDirect JDBC Driver for SQL Server does not support the hierarchyid data type. The Developer tool does not display IBM DB2 tables when you connect to the database through a user account that is assigned to a role with privileges on the tables. The Developer tool does not display the table because the DataDirect JDBC Driver for IBM DB2 does not support role-based privileges. The Developer tool does not display IBM DB2 tables when you connect to the database through a user account that is assigned to a group with privileges on the tables. You cannot import or preview MySQL resources if the resource contains a database reserved word or special character other than the dollar sign ($) character. The DataDirect ODBC Driver for MySQL, version 6.0.0.130 SP3, does not support database reserved words or special characters other than the "$" character. When the Developer tool reads data from Sybase resources with unsigned integer columns, data loss might occur because the DataDirect ODBC Driver for Sybase, version 6.0, retrieves unsigned integers with the same precision as signed integers. Workaround: After you import the resource into the Developer tool, change unsigned int columns to bigint columns. Change unsigned bigint columns to numeric(20,0) columns.

233177

229593

229431

219756

Data Quality Content Installer

Data Quality Content Installer Fixes (9.0.1)
CR 221160 Description The Server Content Installer cannot read a zip file if the path to the file contains one or more character spaces.

Data Quality Content Installer Known Limitations

CR 237756 Description Installing the North America Accelerator to the Model repository invalidates some reference tables installed by the Data Quality Content Installer. Workaround: Reinstall the reference tables included with the Content installer. (added 09/01/10)

Data Quality Integration for PowerCenter

Data Quality Integration for PowerCenter Known Limitations
CR 240343 Description Data Quality transformations do not configure the scale defaults that PowerCenter expects for numeric ports. Workaround: In Informatica Developer, set the scale settings for Data Quality transformations and export the transformations. (added 09/01/10)

IN_RLN_90100_0005

19

Data Analyzer
Data Analyzer Known Limitations
There are no known limitations for Data Analyzer.

Metadata Manager
Metadata Manager Fixes (9.0.1)
CR 231388 229603 228336 227810 227362 227312 226867 226426 225452 224653 224366 Description Business glossary export performance is low. Metadata catalog is not visible after upgrading from 8.6. Metadata Manager encounters an XMI parsing error while reloading a Business Objects resource. Cannot import metadata catalog with the period (.) in the name. Lineage does not show source tables when a parameterized sql override query contains another parameter. Metadata Manager imports all Cognos personal folders with the name My Folder. Cannot load Oracle resource in Metadata Manager. Importing duplicate terms resulted in Business Glossary inconsistencies. The Informatica installer does not set the INFA_HOME variable in the MIRSetup.xml file used by the Metadata Manager Agent. Importing a business glossary Excel file that has terms shared with other business glossaries throws an exception. When you view data lineage, Metadata Manager occasionally displays the following error:
java.lang.IllegalStateException: Cannot create a session after the response has been committed

223542

Cannot enable the Metadata Manager Service on a worker node when the worker node is on a UNIX machine and the gateway node is on a Windows machine. The Metadata Manager File Location property for the Metadata Manager Service uses the incorrect file path separator. Importing a business glossary XML file fails to import related catalog objects for custom class objects. If you import a business glossary XML file and the user that created the links or comments for a business term does not exist in the target Metadata Manager instance, Metadata Manager does not import the links or comments created by the user. Metadata Manager displays that the import succeeds and does not notify you that the links or comments were not imported. Resource load fails for Microsoft SQL Server with encrypted procedures and triggers. If you upload more than 200 PowerCenter parameter files, the browser may hang during the file upload process. Load Monitor does not display session statistics for all sessions for a custom resource load. When you view data lineage for a business term and expand a class or export the diagram to Excel, an exception occurs.

214565 214211

211344 210853 210666 206900

20

IN_RLN_90100_0005

Metadata Manager Known Limitations

CR 237928 Description If you upgrade from version 8.6.1, data lineage displays links between source relational tables and PowerCenter source definitions and Source Qualifier transformations. Data lineage should display links between source relational tables and PowerCenter Source Qualifier transformations only. Workaround: Purge and then reload all PowerCenter resources. Recreate relationships from custom objects and business terms to PowerCenter metadata objects. If you back up the Metadata Manager repository using the backupCmdLine command program and then restore the repository as a different user, you cannot view profiling information for database management resources. Workaround: Run the following SQL statements on the Metadata Manager repository depending on the database type, and then commit the changes: - Oracle.
INSERT INTO IDP_WH_VERSION VALUES (5,2,3)

237743

- Microsoft SQL Server.

INSERT INTO IDP_WH_VERSION VALUES (5,2,5)

- IBM DB2.
INSERT INTO IDP_WH_VERSION VALUES (5,2,6)

(fixed in 9.0.1 HotFix 1) 236963 You delete a user in the Informatica domain who is a data steward or owner for a category or a business term. However, Metadata Manager does not remove the deleted user from the data steward or owner assignment. Workaround: After deleting a user who is a data steward or owner for a category or business term, reassign another user as the data steward or owner. A PowerCenter resource can contain multiple instances of a mapplet where each mapplet instance is linked to a different source relational table. When you launch data lineage or view the impact summary for one of the source relational tables, lineage and the impact summary display all instances of the mapplet. Data lineage and the impact summary should display only the mapplet instance linked to the source table. When the Metadata Manager repository is on a database that contains multibyte data, Metadata Manager cannot send an email notification when you propose a business term for review. After you upgrade, the Metadata Manager Advanced User role does not include the Draft/Propose Business Terms privilege. Workaround: Use the Administrator tool to assign the privilege to the role. If a PowerCenter mapping contains mapping parameters with default values and if session level overrides are provided in a parameter file for the same property, Metadata Manager does not display the session level overrides in the mapping object properties. However, the session level override values are used to display lineage correctly. If you concurrently load two resources to a Metadata Manager repository on IBM DB2, Metadata Manager may fail one of the resource loads with the following error: Could not perform post load task. Cause:PreparedStatementCallback; SQL [INSERT INTO MM_ELEMENT_PATH (ELEMENT_UID, REPOSITORY_UID, NAME_PATH, ID_PATH) VALUES (?, ?, ?, ?)]; [informatica][DB2 JDBC Driver][DB2]ROLLBACK DUE TO DEADLOCK/ TIMEOUT;REASON 2; If you create a business glossary in Microsoft Excel and do not specify the security domain that the data steward user account belongs to, Metadata Manager does not give the data steward user account full control on the business term when you import the business glossary. When Metadata Manager runs on UNIX and uses ODBC drivers to connect to a Microsoft SQL Server 2005 source, Metadata Manager fails to load the Microsoft SQL Server 2005 resource with the following error:
SQL Error [FnName: Fetch -- [Informatica][ODBC SQL Server Driver]20205].

233569

232802

232624

224880

224817

224787

224717

223885

For a Microsoft Analysis and Reporting Services resource, Metadata Manager does not extract reports that use a relational database as the data source if the data source path is specified in the Report Server Content property. Workaround: In the Report Server Content property, specify the report folder path instead of the data source path.

IN_RLN_90100_0005

21

CR 219822

Description On an Oracle repository, Metadata Manager occasionally hangs while creating links between connected resources. Workaround: Analyze the Metadata Manager repository on Oracle to improve performance in the Metadata Manager application. If you assign a connection to multiple schemas, Metadata Manager creates links between matching objects for only one schema. On a Microsoft SQL Server repository, indexing for an SAP R/3 resource fails with an SQLException when an extracted application component does not have a unique name. Workaround: When configuring the SAP R/3 resource, do not extract application components that have a child or parent with the same name. If you create a struct relationship between an object class and a business term class in the Custom Metadata Configurator, you cannot create a field relationship between the business term and another object class type. A resource load fails if the associated Integration Service uses the IBM DB2 9.5 client and you load metadata from IBM DB2 9.1. If you change the direction of a relationship for a custom class, Metadata Manager does not update the direction for the relationship between the corresponding metadata objects in the catalog. Workaround: Reload the custom resource.

218523 215847

197074

196699 193949

Informatica Global Customer Support

You can contact a Customer Support Center by telephone or through the Online Support. Online Support requires a user name and password. You can request a user name and password at http://mysupport.informatica.com. Use the following telephone numbers to contact Informatica Global Customer Support:
North America / South America Toll Free Brazil: 0800 891 0202 Mexico: 001 888 209 8853 North America: +1 877 463 2435 Europe / Middle East / Africa Toll Free France: 00800 4632 4357 Germany: 00800 4632 4357 Israel: 00800 4632 4357 Italy: 800 915 985 Netherlands: 00800 4632 4357 Portugal: 800 208 360 Spain: 900 813 166 Switzerland: 00800 4632 4357 or 0800 463 200 United Kingdom: 00800 4632 4357 or 0800 023 4632 Asia / Australia Toll Free Australia: 1 800 151 830 New Zealand: 1 800 151 830 Singapore: 001 800 4632 4357

Standard Rate North America: +1 650 653 6332

Standard Rate India: +91 80 4112 5738

Standard Rate Belgium: +31 30 6022 797 France: 0805 804632 Germany: 01805 702702 Netherlands: 030 6022 797

22

IN_RLN_90100_0005