Informatica Corporation Informatica Version HotFix 2 Release Notes November Contents

Transcription

1 Informatica Corporation Informatica Version HotFix 2 Release Notes November 2010 Copyright (c) Informatica Corporation. All rights reserved. Contents HotFix Installation... 2 Hotfix Installation and Rollback Complete the Pre-Installation Tasks Properties File Applying the HotFix to the Informatica Services Applying the HotFix to the Informatica Clients Complete the Post-Installation Tasks Roll Back the HotFix Informatica Domain... 7 Informatica Domain Fixes (9.0.1 HotFix 2) Informatica Domain Fixes (9.0.1 HotFix 1) Informatica Domain Fixes (9.0.1) PowerCenter PowerCenter Client Installation PowerCenter Fixes (9.0.1 HotFix 2) PowerCenter Fixes (9.0.1 HotFix 1) PowerCenter Known Limitations (9.0.1 HotFix 1) PowerCenter Fixes (9.0.1) PowerExchange PowerExchange HotFix PowerExchange Fixes (9.0.1 HotFix 1) PowerExchange HotFix Installation Overview PowerExchange Known Limitations (9.0.1 HotFix 1) PowerExchange Adapters PowerExchange for Web Services Fixes (9.0.1 HotFix 2) PowerExchange for JMS Fixes (9.0.1 HotFix 1) IN-RLN-90100HF

2 Informatica Analyst Informatica Analyst Fixes (9.0.1 HotFix 2) Informatica Analyst Known Limitations (9.0.1 HotFix 2) Informatica Analyst Fixes (9.0.1 HotFix 1) Informatica Analyst Known Limitations (9.0.1 HotFix 1) Informatica Analyst Fixes (9.0.1) Informatica Developer Informatica Developer Fixes (9.0.1 HotFix 2) Informatica Developer Known Limitations (9.0.1 HotFix 2) Informatica Developer Fixes (9.0.1 HotFix 1) Informatica Developer Known Limitations (9.0.1 HotFix 1) Informatica Developer Fixes (9.0.1) Data Quality Content Installer Data Quality Content Installer Fixes (9.0.1) Data Quality Integration for PowerCenter Data Quality Integration for PowerCenter Fixes (9.0.1 HotFix 1) Data Analyzer Data Analyzer Fixes (9.0.1 HotFix 1) Data Analyzer Known Limitations (9.0.1 HotFix 2) Metadata Manager Metadata Manager Fixes (9.0.1 HotFix 2) Metadata Manager Fixes (9.0.1 HotFix 1) Metadata Manager Fixes (9.0.1) Metadata Manager Known Limitations (9.0.1 HotFix 2) Metadata Manager Known Limitations (9.0.1 HotFix 1) Informatica Global Customer Support 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. HotFix Installation Hotfix Installation and Rollback Informatica hotfixes contain updates to the PowerCenter, Data Services, Data Quality and PowerExchange adapaters. You can apply a hotfix or roll it back in graphical or silent mode on Windows and UNIX and in console mode on UNIX. 2 IN-RLN-90100HF2-0001

3 When you apply the hotfix, the installer backs up existing directories, installs the updated version of the product, and restores or updates configuration files and run-time files. When you roll back the hotfix, the installer restores Informatica to the previously installed version. Informatica provides a hotfix installer for the Informatica services and the Informatica clients. To apply the Informatica hotfix, complete the following steps: 1. Complete the pre-installation tasks. 2. Apply the hotfix to the Informatica services. Note: To apply the hotfix without user interaction, edit the properties file and set the installation parameters for the Informatica services. 3. Complete the post-installation tasks for the Informatica services. 4. Apply the hotfix to the Informatica clients. Note: To apply the hotfix without user interaction, edit the properties file and set the installation parameters for the Informatica clients. After you apply or roll back a client hotfix, you can view the installation details in the log files in the Informatica client directory. Note: Apply HotFix 1 to the Informatica Developer Client. You cannot connect to the Informatica domain using Informatica Developer from a previous version. Complete the Pre-Installation Tasks Complete the following tasks before you apply or roll back a hotfix: 1. Close the Informatica clients on all machines where you want to apply or roll back the hotfix. 2. Close the Informatica directory and the subdirectories. 3. Stop the Informatica services on all nodes in the domain in the following order: a. worker nodes b. gateway nodes c. master gateway node For more information about stopping Informatica services, see the Informatica Installation and Configuration Guide. 4. Download the hotfix package for your platform. 5. Unzip or untar the contents of the hotfix package. Note: On UNIX, use native tar or GNU tar to extract the installer files. The user that runs the installer must have read and write permissions on the installer files directory and execute permissions on install.sh. 6. Back up the Metadata Manager repository, PowerCenter repository, the domain configuration repository, and any source repository. The back-up files are required to roll back a hotfix. IN-RLN-90100HF

4 Properties File To apply the Informatica services or clients hotfix in silent mode, edit the properties file. Informatica provides a sample properties file that that you can customize for your installation. The properties file is the same for the Informatica services hotfix and clients hotfix. The following example shows the contents of the sample SilentInput.properties file for an Informatica services hotfix: # Use the following guidelines when editing this file: # * Use this file to install without user interaction. Save the file # with the following name: SilentInput.properties # * Any error condition that leads to failure, such as an invalid # installation directory, generates a log file in the SYSTEM_DRIVE_ROOT # directory. For example: C:\silentErrorLog.log # Set the directory for Informatica 9.0.1: USER_INSTALL_DIR=C:\Informatica\9.0.1 # Set the installation type: # 0 -> Select this option to apply HotFix # 1 -> Select this option to rollback to previous installed version INSTALL_TYPE=0 Editing the Properties File To edit the SilentInput.properties file: 1. Find the properties file at the root level of the directory where you extracted the hotfix package. 2. Use a text editor to open and modify the values of the properties in the file. The following table describes the installation properties to modify: Property Name USER_INSTALL_DIR INSTALL_TYPE Directory for the Informatica instance on which to apply the hotfix. To apply the hotfix to the Informatica services, enter the directory for the Informatica services. To apply the hotfix to the Informatica clients, enter the directory for the Informatica clients. On Windows and UNIX, use slash (\)to separate directories. Use 0 to apply the hotfix. Use 1 to roll back the hotfix. 3. Save the properties file. Applying the HotFix to the Informatica Services On UNIX, you can apply the hotfix in graphical, console, or silent mode. On Windows, you can apply the hotfix in graphical or silent mode. Warning: The installation fails when you run the installer and perform one of the following actions: During installation, you close the debug window that runs in the background. You create the BACK_FROM_HF<rollback version> in the Informatica installation directory as a roll back prerequisite. 1. Select one of the following installation options: 4 IN-RLN-90100HF2-0001

5 To install in graphical mode or console mode, run install.bat or install.sh from the root directory where you unzipped or untarred the hotfix package and follow the prompts to complete the installation. On Windows, if you encounter problems when you run the install.bat file from the root directory, run the following file: <InstallerExtractDirectory>/server/install.exe To install in silent mode, run silentinstall.bat or silentinstall.sh from the root directory where you unzipped or untarred the hotfix package. 2. Review the installation and debug log files in the Informatica directory. Applying the HotFix to the Informatica Clients You can apply the client hotfix in graphical or silent mode. Apply HotFix 1 to the Informatica Developer Client. You cannot connect to the Informatica domain using Informatica Developer from a previous version. Warning: The installation fails when you run the installer and perform one of the following actions: During installation, you close the debug window that runs in the background. You create the BACK_FROM_CLIENT_HF<rollback version> folder in the Informatica installation directory as a roll back prerequisite. 1. Select one of the following install options: To install in graphical mode, run install.bat from the root directory where you unzipped or untarred the hotfix package and follow the prompts to complete the installation. To install in silent mode, run silentinstall.bat from the root directory where you unzipped or untarred the hotfix package. 2. Review the installation and debug log files in the Informatica directory. Complete the Post-Installation Tasks After you apply the Informatica services hotfix, complete the post-installation tasks. Configure Metadata Manager 1. Disable the Metadata Manager Service. 2. Use the Administrator tool to upgrade the Metadata Manager repository to HotFix For Netezza resources, download or copy nzjdbc.jar to the following directory: <Informatica Installation directory>\services\metadatamanagerservice\mmapps\mm\web-inf\lib 4. Effective in HotFix 1, set the Miti_Client_Version property to in the Metadata Manager Properties file. The Metadata Manager Properties file is located in the following directory: Installation directory>\tomcat\shared\classes\imm.properties For more information, see the Metadata Manager Administrator Guide. 5. Enable the Metadata Manager Service. IN-RLN-90100HF

6 6. Download and install the Metadata Manager Agent. For more information, see the Metadata Manager Administrator Guide. 7. Before an upgrade to HotFix 1, if Metadata Manager displayed errors while browsing or performing data lineage analysis on objects in a reloaded resource with deleted objects in the source, reload the resource again. 8. If you upgrade from 8.6.x to HotFix 1, purge and reload PowerCenter resources to remove the links from relational tables to the source definitions. 9. After you upgrade to HotFix 2, update the IMM.Properties files to enable sorting elements by name in a lineage diagram. The IMM.Properties file is available in the following location: <INFA_HOME>\tomcat \shared\classes\. Update the file to include the following lines of code: #Sort Elements in Lineage diagram by name Lineage.DataNode.SortElementsByName=Y 10. If you upgrade from 8.6.x to HotFix2, you must reload all resources. For all other upgrades, reload the following resources: PowerCenter resources Data Modeling resources Business Intelligence resources Configure Operating System Profiles on UNIX Reconfigure pmimpprocess in the following directory: <PowerCenter installation directory>\server\bin For more information about configuring pmimpprocess, see the Informatica Administrator Guide. Registering the PowerCenter Web Services Provider Plug-In Effective in HotFix 1, you must register the Web Services Provider plug-in. 1. Configure the PowerCenter Repository Service to run in exclusive mode. 2. Connect to the PowerCenter Repository Service with the pmrep Connect command using a user account with Admin Repository privilege 3. Locate the pmwsprovider.xml plug-in file in the following directory: <PowerCenter installation directory> \server\bin\native 4. Use the pmrep RegisterPlugin command to update the repository. The RegisterPlugin command uses the following syntax: registerplugin -i <registration_file> -e -N Roll Back the HotFix You can roll back the Informatica hotfix in graphical mode or silent mode. When you roll back a hotfix, the installer returns Informatica to the previously installed version. Use the hotfix installer to roll back to the previous version. You can use the same procedure to roll back the hotfix for Informatica services or clients. The installer does not remove any backup folders or logs created when applying a hotfix. 6 IN-RLN-90100HF2-0001

7 Warning: When you run the installer, a console launcher window opens and runs in the background. If you close this window, the roll back will stop. 1. Complete the pre-installation tasks. 2. To roll back in silent mode, perform the following steps: a. Edit the properties file and set the INSTALL_TYPE to rollback. b. Run silentinstall.bat or silentinstall.sh from the root directory where you unzipped or untarred the hotfix package. 3. To roll back in graphical mode, run install.bat or install.sh from the root directory where you unzipped or untarred the hotfix package and follow the prompts to complete the rollback. 4. Review the installation and debug log files in the Informatica installation directory. 5. If you have a Metadata Manager service, restore the Metadata Manager repository, PowerCenter repository, and any source repository from the back up files you created before you installed. Informatica Domain Informatica Domain Fixes (9.0.1 HotFix 2) The Integration Service is not resilient to an MQ source queue and fails the session that is processing messages from the MQ source queue if the connection to the queue manager is in the quiescing state A user can bypass Administrator tool security by copying the Administrator tool URL from another tool to gain full access to the Administrator tool , The PowerCenter Repository Service shuts down unexpectedly when Informatica services fails to authenticate users in groups for a login request from a client tool The Installer does not copy files from the following directory: <Informatica installation directory>\services\dqcontent \INFA_Content\av , , The REG_REPLACE function in an Expression transformation ignores records that contain Traditional Chinese codepage data. Semi-join conditions in Joiner transformations do not work correctly for Sybase and ODBC sources A node in the domain fails to start if the password of an Administrator user is not Administrator The Informatica JDBC driver fails a SQL statement that sets the maximum row fetch size to The Data Integration Service cannot profile data in a Java transformation The Repository Service shuts down unexpectedly while reconnecting to the repository when the locks for the previous connection to the repository are being released The Model Repository Service cannot be created if the schema used is not the default schema and contains a slash character (/). IN-RLN-90100HF

8 The SQL data service displays an error when you use the Informatica Data Services ODBC driver to connect to Business Objects version On AIX, you cannot use the domain object Permissions view to assign permissions on the object The Service Manager shuts down with a java heap space error when more than 100 users are online using services that require user privileges. Informatica Domain Fixes (9.0.1 HotFix 1) After an upgrade from version 9.0 to version 9.0.1, the Model Repository Service is not upgraded The Integration Service sometimes shuts down unexpectedly when running a session on a grid If you install the Informatica sevices 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 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 On AIX, you cannot use the domain object Permissions view to assign permissions on the object You cannot edit an application service in the Administrator tool after you delete an associated application service The RestoreDomain command generates an exception if you set the -tc option After you create an application service, the new service does not appear in the service name filter on the Logs tab The Administrator tool hangs if you create a folder when you select the location in which to create an object After you restart the domain, the modified log directory path reverts to the default value You cannot use the Administrator tool to edit the Log Directory Path property for the nodes in the domain The infacmd dis CreateService command generates an exception when you create a Data Integration Service with a port that is out of range LDAP user privileges assignments are lost when you upgrade a PowerCenter Repository Service Users can add scripts in Informatica Administrator to allow users without credentials to access the Administrator tool The Administrator tool might display a blank screen instead of the login page You must specify the Java memory values in megabytes. You cannot specify gigabytes or kilobytes The $PMRootDir service process variable shows unknown location after you add a node to a grid. 8 IN-RLN-90100HF2-0001

9 Informatica srvices shut down when a remote user logs into or logs out of the Administrator tool Non-administrator users cannot connect to an application service after a master gateway failover if the application service does not have a backup node. Informatica Domain Fixes (9.0.1) 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 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. IN-RLN-90100HF

10 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 W 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. PowerCenter PowerCenter Client Installation The installation structure of the PowerCenter Client changed in HotFix 1. As a result, the wizard fails to launch when you import sources or targets for the following java based adapters: PowerExchange for Server, PowerExchange for JDEdwards OneWorld, PowerExchange for LDAP, and PowerExchange for Siebel. The import source or import target wizard fails to launch after you update the Informatica environment to any hotfix. After you install the hotfix, you must copy the java folder from <PowerCenter Client Installation Directory>\ to <PowerCenter Client Installation Directory>\PowerCenterClient. (246815). PowerCenter Fixes (9.0.1 HotFix 2) The Designer hangs when you drag a port from the source to the Source Qualifer with the same datatype Importing a workflow multiple times causes the flat file lookup session attributes to revert to the session attributes in the mapping properties instead of the attributes specified in a session override The PowerCenter Integration Service fails a session on grid that is configured to retry on deadlock The Workflow Manager shuts down unexpectedly when view a pushdown optimization session that contains a Union transformation followed by a Router transformation Session fails because a hash auto-keys partition gets added to the Joiner transformation when you copy, export, or import a workflow from the Repository Manager The Integration Service shuts down unexpectedly when Filewatch event-wait tasks are stopped or aborted for multiple workflows An unexpected condition error occurs when you use the Repository Manager or Workflow Manager to copy a folder that contains a mapping with an unconnected source to another folder in the repository The ADD_TO_DATE function does not work correctly for a Netezza session configured for pushdown optimization Partitioned sessions shut down unexpectedly when connected and unconnected lookups share the same cache Configuring the Java SDK code to list all sources also returns shortcuts to the sources The FIELDPROPERTY for the Java SDK code is set for PowerCenter versions prior to version The Designer cannot import an exported XML target definition that has the Long datatype with a precision of IN-RLN-90100HF2-0001

11 The Repository Service shuts down unexpectedly while purging deleted objects from the Repository Manager PowerCenter change data capture sessions consistently fails during a warm start Deployment fails with a unique constraint error because of a naming conflict for a shortcut to an object in the deployment group that matches a shortcut in the target folder, which points to an unrelated object Some ports are missing from the XML views after you import an XML Sshema file into the Designer using the Hierarchy Normalized view Web Service consumer session generates a SOAP request without data fields in the SOAP request elements The Workflow Monitor displays an unexpected condition error message while opening the latest 20 worflow runs Some ports are missing from the XML views after you import an XML schema file into the Designer using the Hierarchy Normalized view Oracle session in bulk mode adds extra bytes to the column with a Timestamp datatype. PowerCenter Fixes (9.0.1 HotFix 1) The Repository Service encounters a deadlock while deploying a deployment group to the target repository Mapping variable values are not retained when you use the pmrep deploydeploymentgroup command to deploy a deployment group to the target repository Mapping Architect for Visio cannot link Source Qualifier transformation ports to the Expression transformation ports if the Expression transformation contains the %ALL% expression function , Web service session fails with an RPC encoded WSDL during SOAP request conversion from DOC to RPC The target repository is corrupted when you copy oy a deployment group that contains mappings with shortcuts to the source repository When you run a PowerCenter session on Windows, the PowerCenter Integration Service can fail to connect to the database The Integration Service fails PowerCenter sessions that use an IBM DB2 9.7 client to access an IBM DB2 target table Partitioned session does not fail even when session cannot locate the.zip file specified in the command input The Portuguese PowerCenter Designer cannot find the XML templates when you select a menu item in the slowly changing dimensions mapping template wizard Teradata ODBC session on UNIX fails when you use the update system operator and set the OptimizeTeradataUpdate custom property The Integration Service on Windows 64-bit Itanium shuts down unexpectedly The DTM process fails with an unexpected condition when Repeat Null Characters contains double byte characters for fixed-width flat files. IN-RLN-90100HF

12 PowerCenter Known Limitations (9.0.1 HotFix 1) If you import a Mapping Analyst for Excel mapping specification that contains a rule, the Repository Manager marks the mapping as not valid and displays the following message: Byte code for the transformation is not in the repository. Java transformation is invalid. Workaround: Use the Designer to compile the Java transformation. Then validate the mapping. PowerCenter Fixes (9.0.1) Java Mapping SDK fails to retrieve mapping objects if there are multiple source or target instances in the same mapping The PowerCenter Integration Service terminates when multiple PowerCenter Clients start workflows at the same time Incorrect message appears when a file in a file list does not exist The DTM process fails with an unexpected condition when Repeat Null Characters contains double-byte characters for fixed-width flat files. PowerExchange PowerExchange HotFix 2 For release information about PowerExchange HotFix 2, see the following publications: PowerExchange Version HotFix 2 Release Notes PowerExchange Version and Hotfixes Cumulative Release Notes PowerExchange Fixes (9.0.1 HotFix 1) CDC sessions with DB2 for i5/os sources and PWX CDC Real-Time application connections might fail if you use offloading and override DB2 library or journal names. This failure can occur in continuous extraction mode with PowerExchange Condense or in real-time extraction mode The DB2 for z/os EC abends with message PWXEDM177588E when reading a table from a partitioned table space that is not EA-enabled The IMS log-based EC ends abnormally with the error message PWX when processing an IMS RECON data set that contains an entry for a SLDS data set with the name of "COMPRESSED DATA SET." The IMS log-based EC ends abnormally with the error message PWX when processing an IMS RECON data set that contains spanned records of type x'05'. 12 IN-RLN-90100HF2-0001

13 CDC sessions with Oracle sources might fail with error message PWX if the sources include small-sized FLOAT columns. The failure occurs because PowerExchange incorrectly registers the FLOAT columns as NUM32 columns and then detects too many decimal point characters for these columns Memory corruption occurs on the source system during CDC sessions that use an event table with a registration tag name longer than 18 bytes PowerExchange Client for PowerCenter (PWXPC) workflows that include source definitions based on PowerExchange data maps with VARBIN columns fail to load VARBIN data to the targets. However, the workflows successfully load data for columns with other datatypes When Informatica Data Explorer sends a request for data to PowerExchange using a PowerExchange ODBC connection, PowerExchange returns message PWX-07015, which indicates a column fetch error. The error occurs because PowerExchange detects a column length error in the SQL call A CAPXRT database row test on an extraction map for a DB2 for i5/os table fails with message PWX when the table includes DATE, TIME, or TIMESTAMP columns that have long mixed-case column names that are enclosed in double quotation marks A bulk data movement session that uses group source processing and a PWX NRDB Batch application connection fails to read the last block of data for a VStream file that has multiple record types A bulk data movement session that uses a PWX NRDB Batch connection fails to load data to a VSAM RRDS data set when the Insert Only session property is selected. PowerExchange issues the following error message: PWX AMVSM UPDATEMODE not supported with RRDS access method A CAPXRT database row test of an Adabas source that includes MU and PE fields fails with a SOC4 abend code In the PowerExchange Navigator, when you open or create a personal metadata profile that includes metadata for an Oracle materialized view, the metadata request fails with multiple error messages in the PowerExchange message log and PowerExchange Navigator 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 On z/os, output from the PowerExchange Listener LISTTASK command in the JES job log might contain truncated PowerExchange messages. Truncation occurs at 125 characters in long messages such as PWX PowerExchange HotFix Installation Overview To install a PowerExchange hotfix, you can complete a first-time installation, an upgrade installation, or a hotfix installation. To determine which type of installation to perform, use the following criteria: If PowerExchange is not currently installed, complete a first-time installation. Use the install files that are provided for a first-time or upgrade installation. If a PowerExchange version earlier than is installed, complete an upgrade installation. Use the install files that are provided for a first-time or upgrade installation. If PowerExchange or a hotfix is currently installed, complete a hotfix installation. Use the hotfix install files. PowerExchange hotfixes are cumulative. The latest hotfix includes changes from all previous hotfixes on the current version. IN-RLN-90100HF

14 These release notes list the names of the install files to use by installation type and operating system. If you perform a first-time or upgrade installation of PowerExchange on a Linux, UNIX, or Windows system, you can use a localized version of the PowerExchange installer. When you run the installer, you get localized PowerExchange messages. On Windows, you also get a localized version of the PowerExchange Navigator. If you copy the localized help files to the helpdoc folder, you can get localized help through the PowerExchange Navigator. For more information about each installation procedure, see the latest PowerExchange Installation Guide. For upgrade and migration considerations and software requirements, see the PowerExchange Planning Guide for Installation and Migration. First-Time and Upgrade Installation Files (9.0.1 HotFix 1) Use the following files from the software folder of the CD image to perform a first-time or upgrade installation of the PowerExchange software, including HotFix 1: Operating System AIX (64-bit) HP-UX Itanium (64-bit) i5/os Linux Itanium (64-bit) Linux x86 (32-bit) Linux x86 (64-bit) Solaris (64-bit) Windows (32-bit) Windows (64-bit) Windows Itanium (64-bit) z/os File Name pwx901_01_aix64.tar pwx901_01_hpux_ipf64.tar pwx901_01_i5os.exe pwx901_01_linux_ipf64.tar pwx901_01_linux32_x86.tar pwx901_01_linux_em64t.tar pwx901_01_solaris_sp64.tar pwx901_01_win32_x86.exe pwx901_01_win_x64.exe pwx901_01_winipf64.exe pwx901_01_zos.exe HotFix Installation Files (9.0.1 HotFix 1) If you have PowerExchange currently installed, use the following files from the patches folder of the CD image to install HotFix 1: Operating System AIX (64-bit) HP-UX Itanium (64-bit) i5/os File Name pwx901_hotfix1_aix64.tar pwx901_hotfix1_hpux_ipf64.tar pwx901_hotfix1_i5os.exe 14 IN-RLN-90100HF2-0001

15 Operating System Linux Itanium (64-bit) Linux x86 (32-bit) Linux x86 (64-bit) Solaris (64-bit) Windows (32-bit) Windows (64-bit) Windows Itanium (64-bit) z/os File Name pwx901_hotfix1_linux_ipf64.tar pwx901_hotfix1_linux32_x86.tar pwx901_hotfix1_linux_em64t.tar pwx901_hotfix1_solaris_sp64.tar pwx901_hotfix1_win32_x86.exe pwx901_hotfix1_win_x64.exe pwx901_hotfix1_winipf64.exe pwx901_hotfix1_zos.exe PowerExchange Known Limitations (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 If you have multiple CAPI connection definitions in the dbmover.cfg file on the PowerCenter client and try to preview data in Designer for a remote source, the preview operation might fail. Workaround: In the dbmover.cfg file, remove or comment out all of the CAPI connection definitions except the one for the remote source. Then try to preview data again PowerExchange cannot use SSL when running with a Linux 64-bit operating system on an Itanium machine. PowerExchange issues the following error message: PWX Can't read certificate chain file. Key=key 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 Dictionary Page found. Image copy reading not supported for compressed TS 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 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. IN-RLN-90100HF

16 PowerExchange Adapters PowerExchange for Web Services Fixes (9.0.1 HotFix 2) Web Service Consumer transformation returns NULL for fields with xsi:type referring to an user defined simpletype. PowerExchange for JMS Fixes (9.0.1 HotFix 1) The Integration Service does not write a batch of JMS messages to the target after aborting a session that contains a JMS source and an Oracle target. Informatica Analyst Informatica Analyst Fixes (9.0.1 HotFix 2) A profile log entry omits the name of the Data Integration Service that ran the profile The Analyst tool cannot run a scorecard that does not contain a column in the default group The Data Integration Service shuts down unexpectedly during profile execution if a profiled column has the same name as an internal property in the profile The infacmd rtm import command does not display the correct message for some errors The Analyst tool cannot create a reference table over a trusted connection in a Microsoft SQL Server database 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. Informatica Analyst Known Limitations (9.0.1 HotFix 2) Informatica Analyst does not return an accurate error message if the Data Integration Service fails to run a profile when you do not have write permission on the temporary directory used for profile operations. 16 IN-RLN-90100HF2-0001

17 Informatica Analyst Fixes (9.0.1 HotFix 1) The Analyst tool returns intermittent null pointer exceptions when running profiles 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. Informatica Analyst Known Limitations (9.0.1 HotFix 1) A Data Integration Service on Windows Itanium shuts down if you run a profile on a single database column or a single rule column when the profiling warehouse is Microsoft SQL Server. Informatica Analyst Fixes (9.0.1) A scorecard does not show the total number of valid or not valid records The Analyst Service on SuSe Linux 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 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. Informatica Developer Informatica Developer Fixes (9.0.1 HotFix 2) The Data Integration Service can shut down unexpectedly when you run a mapping with a Key Generator transformation that contains a NYSIIS strategy The Data Integration Service shuts down unexpectedly on a Suse10 Linux machine when you run a mapping that contains an Address Validator transformation. IN-RLN-90100HF

18 The Association transformation generates different results in an Developer tool mapping and a PowerCenter mapping The Data Integration Service shuts down unexpectedly when you run a profile if a profiled column has the same name as an internal property in the profile When you connect to a repository and open a Key Generator transformation that contains multiple strategies of the same type, only one instance of each configured strategy type is visible The Data Integration Service shuts down unexpectedly if the Developer tool processes a Decision transformation that contains an ISNULL function that is not valid The Open with Informatica Analyst option fails in the Developer tool if the Informatica services are installed on a worker node in a multi-node domain The infacmd rtm export command exports a reference table that contains a single column as a dictionary file with a single column that PowerCenter cannot read The Match transformation does not write cache files to the cache directory specified in the transformation. This issue has been observed in the Developer tool and in mappings deployed to PowerCenter A Match transformation that reads data from a Router transformation may not assign records to the correct output clusters The Comparison transformation cannot use Simplified Chinese and Traditional Chinese identity population files The Data Integration Service can crash when it runs a mapping that contains a Standardizer transformation if the transformation reads a very large reference table, for example a table that contains more than 10 MB of data The Developer tool shuts down unexpectedly when you open a Labeler transformation that is configured to read a reference table if the reference table is not present in the Model repository The Developer tool does not display Chinese characters if the operating system is configured for Traditional Chinese characters. Informatica Developer Known Limitations (9.0.1 HotFix 2) A Match transformation that uses a Romanized Japanese population file with a PersonName strategy requires both Romanized Japanese and Kanji inputs. The transformation does not perform match operations between Romanized Japanese and Kanji inputs. Informatica Developer Fixes (9.0.1 HotFix 1) A Match transformation that reads data from two data sources and creates clustered output is not valid in a PowerCenter repository The Decision transformation does not recognize the concatenation symbol ( ). 18 IN-RLN-90100HF2-0001

19 Brazilian dictionary files are not in the UTF-8 file format In mappings upgraded from version 9.0 to 9.0.1, users cannot edit the strategy settings specified in Token Labeler transformations In the Decision transformation, nested TRIM statements do not pass script validation In the Decision transformation, correctly formatted IF-THEN statements do not pass script validation Users cannot delete large profiles due to excessive writes to the database transaction log The Standardizer transformation throws an exception if the transformation strategy does not include a reference table Using multiple parsing strategies with the same input and output ports crashes the Data Integration service When profiling an ODBC data source using random sampling, the profile does not load data from the staging database Dragging transformation ports onto the output group of the Standardizer transformation does not create output ports The Address Validator transformation throws an exception when processing ZIP codes longer than 11 characters In the Match transformation, the Select Link Path option points to the wrong output port Stack overflow exception occurs when you resize a virtual table created from a customized data object that contains multiple related tables The Model Repository Service returns no results when you search for a relational data object in the Model repository 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 The Informatica Content rule rule_translate_diacritic_characters does not use the context sensitive option During upgrade from Informatica 9.0 to Informatica 9.0.1, the profile warehouse grows excessively on Oracle databases Mapping operations that use dictionaries do not run successfully against non-ascii lowercase characters 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 The Parser transformation cannot read a CSV file created from Labeler transformation output data In the Address Validation transformation, the data viewer does not display port names and field names in the same order as the Ports view 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 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 If a user creates a profile in the Developer tool and applies a rule to that profile in the Analyst tool, the Analyst tool cannot run the profile The Decision transformation does not validate that the datatype returned by a transformation function is compatible with the datatype on the associated output port. IN-RLN-90100HF

20 You cannot preview a relational resource if the resource, schema, or column names contain ASCII characters In the Decision transformation, the XOR function works only if arguments are within parentheses Ports dragged to the Association transformation do not preserve the original datatype The Parser transformation does not successfully parse Unicode strings in a Linux environment A mapping that uses multiple Association transformations to associate record clusters in a flat-file data set of 10 million records or greater may generate a cache memory error 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. Informatica Developer Known Limitations (9.0.1 HotFix 1) The following misleading error message occurs when you connect a client to a HF1 domain: Failed to get services in domain [NewDomain]: [DTF_0017] An error occurred during deserialization: [bad string length: [16,777,216 ]]. You must upgrade the Developer tool to the same version as the domain. Informatica Developer Fixes (9.0.1) 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. 20 IN-RLN-90100HF2-0001

21 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. Data Quality Content Installer Data Quality Content Installer Fixes (9.0.1) The Server Content Installer cannot read a zip file if the path to the file contains one or more character spaces. Data Quality Integration for PowerCenter Data Quality Integration for PowerCenter Fixes (9.0.1 HotFix 1) Using address validation with the Data Quality Integration for PowerCenter crashes PowerCenter sessions that run on Red Hat Linux version The Data Quality Integration for PowerCenter uses the ASCII encoding to read dictionary flat files, and Informatica Developer exports dictionary files in the encoding used by the target PowerCenter repository In the Data Quality Integration for PowerCenter 9.0, mappings that perform address validation can cause PowerCenter sessions to shut down unexpectedly. Data Analyzer Data Analyzer Fixes (9.0.1 HotFix 1) If a Reporting Service fails to enable because the port is in use, you cannot enable any other Reporting Service. IN-RLN-90100HF

22 Data Analyzer Known Limitations (9.0.1 HotFix 2) After you apply HotFix 2 to the HotFix 1 domain, the Data Analyzer help files are missing from the following directory: <Informatica installation directory>//tomcat/jboss/server/informatica/work/jboss.web/localhost/immhelp Workaround: Disable the Reporting Service. Create a Reporting Service in the Administrator tool using the same repository and data sources as the previous Reporting Service after you apply HotFix 2. Metadata Manager Metadata Manager Fixes (9.0.1 HotFix 2) When you create a resource, the Auto Assign Connections check box is selected by default If the Metadata Manager repository is on DB2, running the 861HotFix10.sql script makes a few views invalid After installing HotFix 1, the default Metadata Manager Agent installation on Windows does not work because it uses an incorrect path to the application PowerCenter resource load fails with signal exception when parsing certain SQL scripts When the Metadata Manager repository is on Microsoft SQL Server, PowerCenter resource load fails to parse the parameter files if the number of parameter files is very large S_M_PC8X_WIDG_ATTR_PARTITION_STAGE, S_M_PC8X_LKP_FLDS_IN_COND_EXTRACT, and S_M_PC8X_FF_WIDGET_FIELD_STAGE sessions in a PowerCenter resource load run for a longer time In Custom Metadata Configurator, the Template Summary tab does not display properly The mmcmd updateresource command fails for a PowerCenter resource that has more than 1,000 folders Resource load for Microsoft SQL Server fails if there are table names with special characters Lineage between versioned PowerCenter resource and target table does not appear Import of a Business Glossary fails when an Excel sheet containing duplicate business terms is imported You cannot provide encrypted password when you run the mmcmd and mmbackuputil commands S_M_PC8X_TGT_PAR_CONN session in a PowerCenter resource load runs for a longer time Metadata Manager warehouse database password is stored in plain text in the context.xml file Metadata Manager does not support trusted connections to Microsoft SQL Server using native connections Advanced search does not filter results properly When you load a Rational Rose resource, incorrect value for a bridge parameter is passed Formatting in the Business Term description is not retained during display in the user interface. 22 IN-RLN-90100HF2-0001