Informatica Corporation PowerCenter Version 8.6.

0 HotFix 4 Release Notes

November 2008
Copyright 1998-2008 Informatica Corporation

This document contains important information about the fixed limitations included in 8.6.0 HotFix 4 and how to apply the hotfix.

Contents
PowerCenter Client Fixed Limitations ........................................................................................................... 1 PowerCenter Services Fixed Limitations ....................................................................................................... 1 Metadata Manager Fixed Limitations............................................................................................................. 3 Applying a HotFix.......................................................................................................................................... 4 Complete the Pre-Installation Tasks........................................................................................................... 4 Edit the Properties File (Silent Mode) ........................................................................................................ 4 Apply the PowerCenter Services HotFix.................................................................................................... 5 Apply the PowerCenter Client HotFix ....................................................................................................... 6 Rolling Back the HotFix................................................................................................................................. 7 Contact Information........................................................................................................................................ 7

PowerCenter Client Fixed Limitations

CR 193980 192807 Description You cannot import XML source definitions after exporting them from the Designer or Repository Manager. The Administration Console displays an error message and cannot generate the web service reports when the Web Services Hub is enabled with the HTTPS protocol. The Administration Console does not update the login information for a batch web services user on the Web Services Hub and retains the log in information of the previous user. The Reference Table Manager cannot create or import a reference table in a Microsoft SQL Server database because the user name required to connect to the database and the database schema name are different.

192406

191200

PowerCenter Services Fixed Limitations

CR 193607 Description The Integration Service fails a Change Data Capture recovery that has variable ports in the mapping.

PC_RLN_860004_0001

-1-

193561 193257

Domain that has a Reporting Service hangs when you run the infacmd AddUserToGroup command. The Integration Service sometimes hangs when it runs the Timer task. {RS: As of 10/15 status is forwarded but fix is checked in}

193239 193233

The Repository Service shuts down unexpectedly and causes the domain to shut down. Session configured to roll back messages fails and still takes messages from the JMS Queue when it uses a connection variable for the JNDI application connection. Lookup sessions hang because of a database deadlock on the lookup source. Session running a Data Masking transformation in verbose mode fails even though the data is written to the target. When you configure key string masking, the Data Masking transformation creates duplicate keys in the target. Real-time web service workflows do not appear in the Web Services Hub when they are copied from a deployment group to a target repository that contains workflows. Web Services Hub session hangs when running a workflow that processes a SOAP message attachment exceeding 64 KB. PowerCenter web service sessions fail when processing MIME attachments. {RS: as of 10/15, status is still forwarded}

193192 192996

192995

192903

192846

192777

192719 192694

The Web Services Provider workflow does not stop when it reaches the error threshold. Session that uses a parameter file for user name and password for the Microsoft SQL Server Stored Procedure connection fails. A session and workflow that has no entries in the parameter file terminates. Session that processes UTF-8 data in lookups and expressions fails once for every 200 runs. When you configure key string masking, the Data Masking transformation creates duplicate keys of 15 bytes or more. The Integration Service process shuts down unexpectedly when a session fails because of a large XML file that has complex parent and child relationships. When a Web Services Provider workflow fails and cannot be restarted, other real-time Web Services Provider workflows send invalid responses to the client during high load. The Integration Service cannot run a workflow that is checked out from a versioned repository by a user who is not the Administrator. [Added 10/22/08]

192524 192342 192241

191953

191658

191538

191535

If a real-time Web Services Provider session fails during high load, the workflow does not restart on the next request and subsequent client requests are not processed. Joiner transformation sessions with sorted input fail if the joiner data cache is manually set to large sizes. The Integration Service does not invoke the post-session failure command after it fails a session due to invalid user name and password for a relational lookup connection.

188653 187592

-2-

PC_RLN_860004_0001

Metadata Manager Fixed Limitations

CR 190896 186740 105845 Description If you do not install the Metadata Manager Agent in the C:\ drive, the Windows service for Metadata Manager Agent is not created. The Restore backupCmdLine command cannot restore the Metadata Manager repository that has shortcuts. Lookup in the data lineage diagram includes too many columns. Load the resource again to view the data lineage diagram. The Restore backupCmdLine command cannot restore the Metadata Manager repository from a backup file that is greater than 5 GB.

192591

PC_RLN_860004_0001

-3-

Applying a HotFix
PowerCenter hotfixes contain updates to PowerCenter and Metadata Manager. You can apply a hotfix or roll it back in graphical mode on Windows and in console mode on UNIX. The console mode may be silent or interactive. When you apply the hotfix, the installer backs up existing directories, installs the updated version of PowerCenter, and restores or updates configuration files and run-time files required by PowerCenter. You can apply this PowerCenter hotfix to the following PowerCenter versions: PowerCenter 8.6.0 PowerCenter 8.6.0 HotFix 1 PowerCenter 8.6.0 HotFix 2 PowerCenter 8.6.0 HotFix 3 When you roll back the hotfix, the installer restores PowerCenter to the previously installed version. To apply a PowerCenter hotfix, complete the following steps: 1. Complete the pre-installation tasks. 2. Edit the properties file. 3. Apply the PowerCenter Services hotfix. 4. Complete the PowerCenter Services configuration tasks. 5. Apply the PowerCenter Client hotfix. 6. Complete the PowerCenter Client configuration tasks. After you apply or roll back a hotfix, you can find details in the log files. The installer generates debug and installation log files in the PowerCenter installation directory.

Complete the Pre-Installation Tasks

Complete the following tasks before you apply or roll back a hotfix: 1. Stop PowerCenter Services on all nodes in the domain in the following order: worker nodes, gateway nodes, and then the master gateway node. For more information about stopping PowerCenter Services, see the PowerCenter Installation Guide. 2. Close the PowerCenter installation directory and the subdirectories. 3. Stop the PowerCenter Client on all machines where you want to apply or roll back the hotfix. 4. Download the hotfix package for your platform. 5. Unzip or untar the contents of the hotfix package.

Edit the Properties File (Silent Mode)

Informatica provides a sample properties file that includes the PowerCenter Client upgrade properties. To apply the hotfix on PowerCenter Services and PowerCenter Clients in silent mode, you need to edit the properties file. The following example shows the contents of a sample installer.properties file for a services hotfix:
# Installation mode (Silent) INSTALLER_UI=SILENT ##### put the correct path of existing PowerCenter installation######## USER_INSTALL_DIR=/home/Informatica/PowerCenter8.6.0 # Installation type (install/rollback) INSTALL_TYPE=install ################################################################

-4-

PC_RLN_860004_0001

To edit the installer.properties file: 1. 2. Locate the properties file at the root level of your extracted hotfix package. 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

Description PowerCenter Services or PowerCenter Client installation directory. On Windows, use \\ to separate directories. On UNIX, use / to separate directories. Use install to apply the hotfix. Use rollback to roll back the hotfix.

USER_INSTALL_DIR

INSTALL_TYPE

3.

Save the properties file.

Apply the PowerCenter Services HotFix

You can apply the hotfix in an interactive mode or a silent mode. To apply the PowerCenter Services hotfix: 1. If you are installing in interactive 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. -orIf you are installing in silent mode, run silentInstall.bat or silentInstall.sh from the root directory where you unzipped or untarred the hotfix package. Caution: When you run the installer, a console launcher window opens and runs in the background. If you close this window, the installation will stop. Review the installation and debug log files in the PowerCenter installation directory.

2.

Configuring Operating System Profiles on UNIX

Reconfigure pmimpprocess in the following directory after you apply the hotfix:
<PowerCenter installation directory>/server/bin

For more information about configuring pmimpprocess, see the PowerCenter Administrator Guide.

Configuring Metadata Manager for PowerCenter Services

1. Update the files used by the Metadata Manager application. By default, Metadata Manager files are stored in the following directory:
<PowerCenter installation directory>\server\tomcat\mm_files

2.

If you stored the Metadata Manager files in a different location, complete one of the following tasks: Copy the mm_files folder to the new server directory. Make sure that the Metadata Manager File Location property indicates the directory where you store the Metadata Manager files. If you configured HTTPS for PowerCenter Services or Metadata Manager and placed the keystore file in the server directory, you must copy the keystore file to the new server directory. The hotfix installer does not copy the keystore file to the new server directory. Copy the keystore file from the following directory:
server<Version>_HF<Version>

3.

For SAP resources in Metadata Manager, download the SAP libraries to the following directory:
<PowerCenter installation directory>\server\bin

PC_RLN_860004_0001

-5-

4.

For Netezza resources in Metadata Manager, download or copy nzjdbc.jar to the following directory:
<PowerCenter installation directory>\server\tomcat\mmapps\mm\WEB-INF\lib

5.

Before you copy or download nzjdbc.jar, disable the Metadata Manager Service. Enable the Metadata Manager Service after you copy or download this file. To update the Metadata Manager repositories, run 860HotFix2.sql and 860HotFix4.sql on the Metadata Manager repositories. These scripts are located in the following directory:
<PowerCenter installation directory>\server\tomcat\mdrepo\scripts\HotFix\MM_Repo_Scripts\<database type>

6.

To update the PowerCenter source repositories, run 860HotFix1.sql and 860HotFix4.sql on the PowerCenter source repositories. These scripts are located in the following directory:
<PowerCenter installation directory>\server\tomcat\md-repo\scripts\HotFix\PCResource-Views\<database type>

7.

Import 860HotFix1.xml, 860HotFix2.xml, and 860HotFix4.xml into the PowerCenter repository for Metadata Manager. These files are located in the following directory:
<PowerCenter installation directory>\server\tomcat\mm-etl\HotFix

8.

Save and reload Metadata Exchanges after you run and import these scripts.

Configuring Data Masking

If you are applying the HotFix on a Solaris machine, apply Sun Microsystems kernel patch 118833-36 to improve random masking performance. Download the patch from the following location: http://sunsolve.sun.com/search/document.do?assetkey=118833-36

Configuring Data Transformation

To update symbolic links for Data Transformation, run configureCDE.sh. This script is located in the PowerCenter installation root directory.

Apply the PowerCenter Client HotFix

You can apply the PowerCenter Client hotfix in an interactive mode or a silent mode. To apply the PowerCenter Client hotfix: 1. If you are installing in interactive mode, run install.bat from the root directory where you unzipped or untarred the hotfix package and follow the prompts to complete the installation. -orIf you are installing in silent mode, run silentInstall.bat from the root directory where you unzipped or untarred the hotfix package. Caution: When you run the installer, a console launcher window opens and runs in the background. If you close this window, the installation will stop. Review the installation and debug log files in the PowerCenter installation directory.

2.

Configuring Metadata Manager for the PowerCenter Client

To preview the source files in Microsoft Office Excel with the Metadata Manager Custom Metadata Configurator, verify that the path to the Microsoft Office installation directory is included in the Path environment variables. By default, Microsoft Office is installed in the following location:
C:\Program Files\Microsoft Office\OFFICE11

-6-

PC_RLN_860004_0001

Rolling Back the HotFix

You can roll back the PowerCenter hotfix in interactive mode or silent mode. When you roll back a hotfix, the installer returns PowerCenter to the previously installed version. You can use any hotfix installer to roll back to the previous version. To roll back the hotfix: 1. 2. 3. Complete the pre-installation tasks. If you are rolling back in silent mode, edit the properties file so that the INSTALL_TYPE is specified as rollback. If you are rolling back in silent mode, run silentInstall.bat or silentInstall.sh from the root directory where you unzipped or untarred the hotfix package. -orIf you are rolling back in interactive 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. Caution: When you run the installer, a console launcher window opens and runs in the background. If you close this window, the installation will stop. Review the installation and debug log files in the PowerCenter installation directory.

4.

Contact Information
North America / South America Informatica Corporation Headquarters 100 Cardinal Way Redwood City, California 94063 United States Europe / Middle East / Africa Informatica Software Ltd. 6 Waltham Park Waltham Road, White Waltham Maidenhead, Berkshire SL6 3TN United Kingdom Asia / Australia Informatica Business Solutions Pvt. Ltd. Diamond District Tower B, 3rd Floor 150 Airport Road Bangalore 560 008 India Toll Free Australia: 1 800 151 830 Singapore: 001 800 4632 4357 Standard Rate India: +91 80 4112 5738

Toll Free +1 877 463 2435

Toll Free 00 800 4632 4357

Standard Rate Brazil: +55 11 3523 7761 Mexico: +52 55 1168 9763 Spain and Portugal: +34 93 480 3760 United States: +1 650 385 5800

Standard Rate Belgium: +32 15 281 702 France: +33 1 41 38 92 26 Germany: +49 1805 702 702 Netherlands: +31 306 022 797 United Kingdom: +44 1628 511 445

PC_RLN_860004_0001

-7-