PC 861 HotFix11

Informatica Corporation PowerCenter Version 8.6.
1 HotFix 11 Release Notes

May 2010
Copyright 1998-2010 Informatica Corporation
This document contains important information about the fixed limitations included in 8.6.1 HotFix 11 and how to apply the hotfix.
Contents
Applying a HotFix.......................................................................................................................................... 3 Complete the Pre-Installation Tasks........................................................................................................... 4 Edit the Properties File (Silent Mode) ........................................................................................................ 4 Apply the PowerCenter Services HotFix.................................................................................................... 4 Complete the Post-Installation Tasks ......................................................................................................... 5 Apply the PowerCenter Client HotFix ....................................................................................................... 9 Complete the PowerCenter Client Post-Installation Tasks....................................................................... 10 Roll Back the HotFix.................................................................................................................................... 12 8.6.1 HotFix 11 Fixed Limitations ............................................................................................................... 12 PowerCenter 8.6.1 HotFix 11 Fixed Limitations...................................................................................... 12 Metadata Manager 8.6.1 HotFix 11 Fixed Limitations............................................................................. 14 Data Analyzer 8.6.1 HotFix 11 Fixed Limitations ................................................................................... 15 PowerExchange for Salesforce.com 8.6.1 HotFix 11 Fixed Limitations.................................................. 15 PowerExchange for SAP NetWeaver 8.6.1 HotFix 11 Fixed Limitations................................................ 16 8.6.1 HotFix 11 Documentation Updates ..................................................................................................... 16 PowerCenter Administrator Guide ........................................................................................................... 16 PowerCenter Advanced Workflow Guide ................................................................................................ 17 PowerCenter Command Reference .......................................................................................................... 17 Infacmd isp Command Reference ............................................................................................................ 18 PowerCenter Configuration Guide ........................................................................................................... 18 PowerCenter Release Guide ..................................................................................................................... 18 PowerCenter Transformation Language Reference.................................................................................. 19 PowerCenter XML Guide......................................................................................................................... 20 Metadata Manager Administrator Guide .................................................................................................. 20 Metadata Manager User Guide................................................................................................................. 21 8.6.1 HotFix 11 Known Limitations............................................................................................................. 21 PowerCenter 8.6.1 HotFix 11 Known Limitations ................................................................................... 22 Metadata Manager 8.6.1 HotFix 11 Known Limitations.......................................................................... 22 B2B 8.6.1 HotFix 11 Known Limitations ................................................................................................ 22 8.6.1 HotFix 10 Fixed Limitations ............................................................................................................... 23 PowerCenter 8.6.1 HotFix 10 Fixed Limitations...................................................................................... 23 Metadata Manager 8.6.1 HotFix 10 Fixed Limitations............................................................................. 24 PowerExchange for SAP NetWeaver 8.6.1 HotFix 10 Fixed Limitations................................................ 25 PowerExchange for WebSphere MQ 8.6.1 HotFix 10 Fixed Limitations ................................................ 25 8.6.1 HotFix 10 Documentation Updates ..................................................................................................... 25 PowerCenter Administrator Guide ........................................................................................................... 26 PowerCenter Command Reference .......................................................................................................... 26 PowerCenter Designer Guide ................................................................................................................... 27 Metadata Manager Administrator Guide .................................................................................................. 27
PC_RLN_861011_0002
-1-
Metadata Manager Business Glossary Guide ........................................................................................... 28 PowerCenter Release Guide ..................................................................................................................... 28 PowerExchange for WebSphere MQ User Guide .................................................................................... 29 8.6.1 HotFix 10 Known Limitations............................................................................................................. 29 PowerCenter 8.6.1 HotFix 10 Known Limitations ................................................................................... 30 8.6.1 HotFix 9 Fixed Limitations ................................................................................................................. 30 PowerCenter 8.6.1 HotFix 9 Fixed Limitations........................................................................................ 30 Metadata Manager 8.6.1 HotFix 9 Fixed Limitations............................................................................... 31 PowerExchange for SAP NetWeaver 8.6.1 HotFix 9 Fixed Limitations.................................................. 32 8.6.1 HotFix 9 Fixes Affecting Functionality............................................................................................... 32 Metadata Manager 8.6.1 HotFix 9 Fixes Affecting Functionality............................................................ 32 PowerExchange for SAP NetWeaver 8.6.1 HotFix 9 Fixes Affecting Functionality ............................... 33 8.6.1 HotFix 8 Fixed Limitations ................................................................................................................. 33 PowerCenter 8.6.1 HotFix 8 Fixed Limitations........................................................................................ 33 Metadata Manager 8.6.1 HotFix 8 Fixed Limitations............................................................................... 34 PowerExchange for JMS NetWeaver 8.6.1 HotFix 8 Fixed Limitations.................................................. 34 8.6.1 HotFix 8 Fixes Affecting Functionality............................................................................................... 34 Metadata Manager 8.6.1 HotFix 8 Fixes Affecting Functionality............................................................ 34 Reference Table Manager 8.6.1 HotFix 8 Fixes Affecting Functionality................................................. 35 8.6.1 HotFix 7 Fixed Limitations ................................................................................................................. 36 PowerCenter 8.6.1 HotFix 7 Fixed Limitations........................................................................................ 36 Metadata Manager 8.6.1 HotFix 7 Fixed Limitations............................................................................... 37 PowerExchange for SAP NetWeaver 8.6.1 HotFix 7 Fixed Limitations.................................................. 37 PowerExchange for Web Services 8.6.1 HotFix 7 Fixed Limitations ...................................................... 37 8.6.1 HotFix 7 Fixes Affecting Functionality............................................................................................... 38 Metadata Manager 8.6.1 HotFix 7 Fixes Affecting Functionality........................................................... 38 PowerExchange for Web Services 8.6.1 HotFix 7 Fixes Affecting Functionality ................................... 38 8.6.1 HotFix 6 Fixed Limitations ................................................................................................................. 38 PowerCenter 8.6.1 HotFix 6 Fixed Limitations........................................................................................ 38 Metadata Manager 8.6.1 HotFix 6 Fixed Limitations............................................................................... 39 PowerExchange for SAP NetWeaver 8.6.1 HotFix 6 Fixed Limitations.................................................. 40 8.6.1 HotFix 6 Fixes Affecting Functionality............................................................................................... 40 PowerExchange for SAP NetWeaver 8.6.1 HotFix 6 Fixes Affecting Functionality ............................... 40 8.6.1 HotFix 5 Fixed Limitations ................................................................................................................. 41 PowerCenter 8.6.1 HotFix 5 Fixed Limitations........................................................................................ 41 Metadata Manager 8.6.1 HotFix 5 Fixed Limitations............................................................................... 41 Data Analyzer 8.6.1 HotFix 5 Fixed Limitations ..................................................................................... 42 PowerExchange for Salesforce.com 8.6.1 HotFix 5 Fixed Limitations.................................................... 42 PowerExchange for Teradata Parallel Transporter 8.6.1 HotFix 5 Fixed Limitations ............................. 42 8.6.1 HotFix 5 Fixes Affecting Functionality............................................................................................... 42 Metadata Manager HotFix 5 Fixes Affecting Functionality..................................................................... 42 PowerExchange for Salesforce.com 8.6.1 HotFix 5 Fixes Affecting Functionality ................................. 43 8.6.1 HotFix 4 Fixed Limitations ................................................................................................................. 43 PowerCenter 8.6.1 HotFix 4 Fixed Limitations........................................................................................ 43 Metadata Manager 8.6.1 HotFix 4 Fixed Limitations............................................................................... 44 Data Analyzer 8.6.1 HotFix 4 Fixed Limitations ..................................................................................... 44 PowerExchange for SAP Netweaver 8.6.1 HotFix 4 Fixed Limitations .................................................. 44 8.6.1 HotFix 3 Fixed Limitations ................................................................................................................. 44 PowerCenter 8.6.1 HotFix 3 Fixed Limitations........................................................................................ 45 Metadata Manager 8.6.1 HotFix 3 Fixed Limitations............................................................................... 46 Data Analyzer 8.6.1 HotFix 3 Fixed Limitations ..................................................................................... 46 Reference Table Manager 8.6.1 HotFix 3 Fixed Limitations ................................................................... 46 PowerExchange for Salesforce.com 8.6.1 HotFix 3 Fixed Limitations................................................... 47 PowerExchange for SAP Netweaver 8.6.1 HotFix 3 Fixed Limitations .................................................. 47 PowerExchange for WebSphere MQ 8.6.1 HotFix 3 Fixed Limitations .................................................. 47 8.6.1 HotFix 3 Fixes Affecting Functionality............................................................................................... 47
-2-
PC_RLN_861011_0002
PowerCenter 8.6.1 HotFix 3 Fixes Affecting Functionality ..................................................................... 47 Metadata Manager 8.6.1 HotFix 3 Fixes Affecting Functionality............................................................ 54 PowerExchange for SAP Netweaver 8.6.1 HotFix 3 Fixes Affecting Functionality................................ 54 Reference Table Manager 8.6.1 HotFix 3 Fixes Affecting Functionality................................................. 54 8.6.1 HotFix 2 Fixed Limitations ................................................................................................................. 55 PowerCenter 8.6.1 HotFix 2 Fixed Limitations........................................................................................ 55 Metadata Manager 8.6.1 HotFix 2 Fixed Limitations............................................................................... 55 Data Analyzer 8.6.1 HotFix 2 Fixed Limitations ..................................................................................... 56 8.6.1 HotFix 2 Fixes Affecting Functionality............................................................................................... 56 PowerCenter 8.6.1 HotFix 2 Fixes Affecting Functionality ..................................................................... 56 8.6.1 HotFix 1 Fixed Limitations ................................................................................................................. 56 PowerCenter 8.6.1 HotFix 1 Fixed Limitations........................................................................................ 56 Metadata Manager 8.6.1 HotFix 1 Fixed Limitations............................................................................... 57 PowerExchange for SAP Netweaver 8.6.1 HotFix 1 Fixed Limitations .................................................. 58 PowerExchange for Web Services 8.6.1 HotFix 1 Fixed Limitations ...................................................... 58 8.6.1 HotFix 1 Fixes Affecting Functionality............................................................................................... 58 PowerExchange for Web Services 8.6.1 HotFix 1 Fixes Affecting Functionality ................................... 58 8.6.1 Fixed Limitations................................................................................................................................. 60 PowerCenter 8.6.1 Fixed Limitations....................................................................................................... 60 Metadata Manager 8.6.1 Fixed Limitations.............................................................................................. 62 Contact Information...................................................................................................................................... 62
Applying a HotFix
PowerCenter hotfixes contain updates to PowerCenter, Metadata Manager, and adapter for PowerExchange. 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.1 PowerCenter 8.6.1 HotFix 1 PowerCenter 8.6.1 HotFix 2 PowerCenter 8.6.1 HotFix 3 PowerCenter 8.6.1 HotFix 4 PowerCenter 8.6.1 HotFix 5 PowerCenter 8.6.1 HotFix 6 PowerCenter 8.6.1 HotFix 7 PowerCenter 8.6.1 HotFix 8 PowerCenter 8.6.1 HotFix 9 PowerCenter 8.6.1 HotFix 10 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. 2. 3. 4. 5. Complete the pre-installation tasks. Edit the properties file. Apply the PowerCenter Services hotfix. Complete the post-installation tasks. Apply the PowerCenter Client hotfix.
PC_RLN_861011_0002
-3-
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. 2. 3. Close the PowerCenter Client on all machines where you want to apply or roll back the hotfix. Close the PowerCenter installation directory and the subdirectories. 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. Download the hotfix package for your platform. Unzip or untar the contents of the hotfix package. For PowerExchange CDC sessions, save the restart tokens. Back up the Metadata Manager repository, PowerCenter repository, and any PowerCenter source repository. The backup files are required to roll back a hotfix.
4. 5. 6. 7.
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.1 # Installation type (install/rollback) INSTALL_TYPE=install ################################################################
To edit the installer.properties file: 1. 2. Find 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 interactive mode or silent mode.
-4-
PC_RLN_861011_0002
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. Warning: The installation fails when you run the installer and perform one of the following actions: Close the debug window that runs in the background. Create the server_8.6.1_HF$<rollback version> folder in the PowerCenter installation directory as a roll back prerequisite. Review the installation and debug log files in the PowerCenter installation directory.
2.
Complete the Post-Installation Tasks

After you apply the PowerCenter Services hotfix, complete the post-installation tasks.
Cold Start PowerExchange CDC Sessions

Effective in version 8.6.1 HotFix 3, PWXPC uses the value of the Application Name attribute for CDC restart processing. Due to this change, you must cold start CDC sessions. For more information about restarting CDC sessions, see the PowerExchange Migration Guide.
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 PowerCenter Administrator Guide.
Update PMRootDir
If you configured a location for $PMRootDir, update the location of the variable in the PowerCenter Administration Console. Restart any Integration Service in the domain.
Configure Metadata Manager

Before you begin to configure Metadata Manager, verify that the service is disabled. 1. Effective in version 8.6.1 HotFix 5, if the Metadata Manager Service runs in HTTPS mode, delete the Metadata Manager Service. Create the Metadata Manager Service again, using the previous Metadata Manager repository database and a keystore password. You can use the existing password or you can use a new password. To update the Metadata Manager repository with the latest changes, run the appropriate SQL scripts against the Metadata Manager repository depending on the Metadata Manager HotFix version that you are upgrading from. For example, if you are upgrading from HotFix 9 to HotFix 11, run the 861HotFix10.sql and 861HotFix11.sql scripts. Metadata Manager includes the following SQL scripts: 861HotFix1.sql 861HotFix2.sql 861HotFix3.sql 861HotFix4.sql 861HotFix5.sql 861HotFix7.sql 861HotFix9.sql
2.
PC_RLN_861011_0002
-5-
861HotFix9oracle10Plus.sql (if the Metadata Manager repository is on Oracle 10g or 11g) 861HotFix10.sql 861HotFix11.sql These scripts are located in the following directory:
<PowerCenter installation directory>\server\tomcat\mdrepo\scripts\HotFix\MM_Repo_Scripts\<database type>
Note: Use 861HotFix5_SQLSERVER2005.sql if the Metadata Manager repository is on Microsoft SQL Server 2005 or 2008. Or, use 861HotFix5_SQLSERVER2000.sql if the Metadata Manager repository is on Microsoft SQL Server 2000. 3. 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
For more information, see the Metadata Manager Administrator Guide. 4. 5. 6. Enable the Metadata Manager Service. Download and install the Metadata Manager Agent. For more information, see the Metadata Manager Administrator Guide. Effective in version 8.6.1 HotFix 10, import the Oracle Business Intelligence Enterprise Edition (OBIEE) model for OBIEE resources, the ERwin model for ERwin resources, and the Teradata model for Teradata resources. Use the upgradeMetamodel utility to import the model. To run the upgradeMetamodel utility, use the following syntax:
upgradeMetamodel.(bat | sh) <repository database type> <repository JDBC URL> <repository database user> <repository database password> <PowerCenter installation directory>\server\tomcat\md-repo\scripts\HotFix\Models\ obiee.metamodel.xml
The upgradeMetamodel utility is located in the following directory:

<PowerCenter installation directory>\server\MM_Utilities\mmBackupUtil
To import the OBIEE model use the model file named obiee.metamodel.xml. To import the ERwin model use the model file named ERwin.metamodel.xml. To import the Teradata model use the model file named teradata.xml. These files are located in the following directory:
<PowerCenter installation directory>\server\tomcat\md-repo\scripts\HotFix\ Models\
7.
Effective in version 8.6.1 HotFix 11, import the Oracle model for Oracle resources. Use the upgradeMetamodel utility to import the model file named oracle.xml. To run the upgradeMetamodel utility, use the following syntax:
upgradeMetamodel.(bat | sh) <repository database type> <repository JDBC URL> <repository database user> <repository database password> <PowerCenter installation directory>\server\tomcat\md-repo\scripts\HotFix\ Models\oracle.xml
The upgradeMetamodel utility is located in the following directory:

<PowerCenter installation directory>\server\MM_Utilities\mmBackupUtil
8.
9.
Effective in version 8.6.1 HotFix 5, if you previously encountered errors while browsing or performing lineage analysis on objects in a reloaded resource with deleted objects in the source, reload the resource and run data lineage again. Effective in version 8.6.1 HotFix 7, if a Metadata Manager business glossary contains related catalog objects from an ERwin or OBIEE resource, export the business glossary to an Excel file. Reload resource types depending on the Metadata Manager HotFix version that you are upgrading from. The following table lists the resource types that you must reload:
-6-
PC_RLN_861011_0002
If you are upgrading from
Reload all resources of these resource types
HotFix 8 or earlier HotFix 9 HotFix 10
Oracle, Teradata , OBIEE, ERwin, and PowerCenter Oracle, Teradata, and PowerCenter Oracle and PowerCenter
To view data lineage analysis between resources for relational databases and resources of other source types, you must load resources for relational databases first and then load the remaining resources. 10. Effective in version 8.6.1 HotFix 8, if you exported a business glossary in step 9, import the business glossaries that you exported. 11. Effective in version 8.6.1 HotFix 8, create a new search index for all resources to implement changes made to indexing and search functionality. For more information, see the Metadata Manager Administrator Guide. 12. Effective in version 8.6.1 HotFix 10, edit all Cognos ReportNet Content Manager resources to enter a valid value for the Dispatcher URL property. For more information, see the Metadata Manager Administrator Guide.
Configure Data Masking

Apply Kernel Patch Effective in version 8.6.1 HotFix 1, if you apply 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 Create Storage Table Effective in version 8.6.1 HotFix 3, you must run a script to create a storage table for repeatable Data Masking. Informatica provides scripts that you run to create the relational storage tables in the following directory:
<PowerCenter installation directory>\client\bin\Extensions\DataMasking
The directory contains scripts for Sybase, Microsoft SQL Server, IBM DB2, and Oracle databases. Each database type has two scripts, Substitution_<database type> and Expression_<database type>. Run both scripts for the database. You can create a table in a different database type if you configure the SQL statements and the primary key constraints.
Update the PowerCenter Repository for Data Masking

Effective in 8.6.1 HotFix 3, you must update the PowerCenter repository with the Data Masking registration file.
Upgrade Impact: Register plug-in Version implemented: 8.6.1 HotFix 3 Apply for any version prior to: 8.6.1 HotFix 3 Do not apply after version: 8.6.1 HotFix 3
Complete the following steps to update the repository: 1. 2. 3. Configure the Repository Service to run in exclusive mode. Connect to the Repository Service with the pmrep Connect command using a user account with Admin Repository privilege. Locate the pmdatamasking.xml registration file in the following directory:
PC_RLN_861011_0002
-7-
4.
<PowerCenter installation directory> \server\bin\native 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
Update the PowerCenter Repository for JMS

Effective in 8.6.1 HotFix 1, you must update the PowerCenter repository with the JMS registration file.
Complete the following steps to update the repository: 1. 2. 3. 4. Configure the Repository Service to run in exclusive mode. Connect to the Repository Service with the pmrep Connect command using a user account with Admin Repository privilege. Locate the pmjms.xml registration file in the following directory: <PowerCenter installation directory> \server\bin\native Use the pmrep RegisterPlugin command to update the repository. The RegisterPlugin command uses the following syntax:
Update the PowerCenter Repository for SAP NetWeaver

Effective in 8.6.1 HotFix 6, you must update the PowerCenter repository with the SAP NetWeaver registration file.
Complete the following steps to update the repository: 1. 2. 3. 4. Configure the Repository Service to run in exclusive mode. Connect to the Repository Service with the pmrep Connect command using a user account with Admin Repository privilege. Locate the pmsapplg.xml registration file in the following directory: <PowerCenter installation directory> \server\bin\native Use the pmrep RegisterPlugin command to update the repository. The RegisterPlugin command uses the following syntax:
Update the PowerCenter Repository for Web Services

Effective in 8.6.1 HotFix 7, you must update the PowerCenter repository with the PowerExchange for Web Services registration file.
-8-
PC_RLN_861011_0002
Complete the following steps to update the repository: 1. 2. 3. 4. Configure the Repository Service to run in exclusive mode. Connect to the Repository Service with the pmrep Connect command using a user account with Admin Repository privilege. Locate the pmwsconsumer.xml registration file in the following directory: <PowerCenter installation directory> \server\bin\native Use the pmrep RegisterPlugin command to update the repository. The RegisterPlugin command uses the following syntax:
Upgrade the Contents of the Reference Table Manager Repository

Effective in version 8.6.1 HotFix 8, you can assign users and groups permission on database connections. To assign permission on connections, you must upgrade the contents of the Reference Table Manager repository. When you access a Reference Table Manager Service in the Administration Console after applying the hotfix, the following message displays:
The repository version <version number> is incompatible with version <version number> of the product. An upgrade may be required.
You must upgrade the repositories of all Reference Table Manager Services in the domain. To upgrade the contents of the Reference Table Manager repository: 1. 2. 3. 4. In the Navigator of the Administration Console, select a Reference Table Manager Service. Disable the service. Click Actions > Upgrade Contents. Enter the user name and password to connect to the Reference Table Manager repository. The upgrade process can take a while to complete. You cannot interrupt or stop the upgrade process after you start it. Make sure that you provide enough time for the process to complete before you start any other process in the Administration Console. To start the repository upgrade process, click OK. When the upgrade process completes, the activity log displays the results. The upgrade is complete when the activity log displays the action status:
Action status for Upgrade Contents: Succeeded
5.
6.
Click Close.
Apply the PowerCenter Client HotFix

You can apply the PowerCenter Client hotfix in interactive mode or 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. -or-
PC_RLN_861011_0002
-9-
2.
If you are installing in silent mode, run silentInstall.bat from the root directory where you unzipped or untarred the hotfix package. Warning: The installation fails when you run the installer and perform one of the following actions: Close the debug window that runs in the background. Create the Client_8.6.1_HF$<rollback version> folder in the PowerCenter installation directory as a roll back prerequisite. Review the installation and debug log files in the PowerCenter installation directory.
Complete the PowerCenter Client Post-Installation Tasks

After you apply the PowerCenter Client hotfix, complete the post-installation tasks.
Authorization Check on SAP ABAP Programs

Effective in version 8.6.1 HotFix 9, you can require that SAP perform authorization checks on ABAP programs that are generated and installed from the Designer. To require that SAP perform authorization checks, reinstall the TBL_DESIGN transport program when you upgrade to the current version of PowerExchange for SAP NetWeaver. The transports are available at the following location on the installation DVD: 1. For Unicode SAP system: saptrans/mySAP/UC 2. For non-Unicode SAP system: saptarns/mySAP/NUC Note: Installing the HF9 TBL_DESIGN transport is optional. To overwrite the TBL_DESIGN transport program: 1. 2. Note the current configuration in the /INFATRAN/ZPRGSQ SAP R/3 custom tables. In the SAP Menu screen, enter STMS in the Transaction box. The Transport Management System appears. 3. Click Overview > Imports. The Import Overview page appears. 4. 5. Open the target system queue. Click Extras > Other Requests > Add. The Add Transport Request to Import Queue dialog box appears. 6. Add the transport request number. Transports for SAP Versions 4.6C and non-Unicode Versions 4.7 and Higher
Data and Cofile Names Required/ Optional Required Transport Request R46K900216 Function Group ZERP Functionality
TBL_DESIGN_R900216.R46 TBL_DESIGN_K900216.R46
For mySAP ECC (R/3) and mySAP add-on components, including CRM, and SAP BI: Supports table extraction for data integration using the ABAP program.
-10-
PC_RLN_861011_0002
Transports for SAP Unicode Versions 4.7 and Higher

Data and Cofile Names Required/ Optional Required Transport Request UC5K900019 Function Group ZERP Functionality
TBL_DESIGN_R900019.UC5 TBL_DESIGN_K900019.UC5
For mySAP ECC (R/3) and mySAP add-on components, including CRM, and SAP BI: Supports table extraction for data integration using the ABAP program.
7.
Press Enter. Request dialog box appears.
8. 9.
Select the transport request number you added and click Import. Select the Overwrite Originals option.
10. Compare the configuration information in /INFATRAN/ZPRGSQ SAP R/3 custom table with the configuration information you noted in step 1. Note: Some SAP systems refer to package as development class. For more information about reinstalling transport programs, see the PowerExchange SAP NetWeaver Transport Versions Installation Notice.
Cold Start PowerExchange CDC Sessions

Effective in version 8.6.1 HotFix 3, PWXPC uses the value of the Application Name attribute for CDC restart processing. Due to this change, you must cold start CDC sessions. For more information about restarting CDC sessions, see the PowerExchange Migration Guide.
Custom File Naming Conventions and Storage Location

Effective in version 8.6.1 HotFix 3, rename custom metamaps and create blank versions of custom mapping specification templates using the naming conventions. Copy the custom files to the following location:
<PowerCenter_Client_installation_directory>\bin\mimb\conf\MIRModelBridgeTempl ate\MIRMicrosoftExcel
Then, associate the custom metamap with the new name of the blank version of the mapping specification template to maintain the metamap links to the mapping specification template.
Matching Criteria for Custom Metamaps

Effective in version 8.6.1 HotFix 3, complete the following tasks to add the matching criteria to custom metamaps: 1. Open MappingTemplate-MetaMap.xls located in the following directory:
<PowerCenter_Client_installation_directory>\bin\mimb\conf\ MIRModelBridgeTemplate\MIRMicrosoftExcel
2. 3. 4. 5. 6.
Open the custom mapping specification template and custom metamap. On the Overview worksheet of MappingTemplate-MetaMap.xls, copy the Match Criteria section. On the Overview worksheet of the custom metamap, paste the Match Criteria section. Enter values for the parameters to uniquely identify the associated mapping specification template. Save the metamap as an XML spreadsheet to the following directory:
PC_RLN_861011_0002
-11-
<PowerCenter_Client_installation_directory>\bin\mimb\conf\ MIRModelBridgeTemplate\MIRMicrosoftExcel
Roll 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 8.6.1 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 roll back will stop. Review the installation and debug log files in the PowerCenter installation directory. For Metadata Manager, restore the Metadata Manager repository, PowerCenter repository, and any PowerCenter source repository from the backup files you created before you installed.
4. 5.
8.6.1 HotFix 11 Fixed Limitations

This section describes the fixed limitations for 8.6.1 HotFix 11.
PowerCenter 8.6.1 HotFix 11 Fixed Limitations

CR 231689 Description The parameter file is deleted after the workflow completes when you use the command line to run the workflow and the Workflow Manager to start the workflow. The Workflow Monitor displays an incorrect message in Japanese for scheduled workflows. The Integration Service within a grid continues to abort a session indefinitely after the Integration Service that is aborting the session on a node fails over to another node. The Integration Service fails the session after failing to generate the child process to read the parameter file for the operating system profile. The load balancer message for load statistics does not display the task name to correlate a load request for a session. The Integration Service shuts down unexpectedly when you change the scheduler for a workflow that is scheduled to run. The master gateway node shuts down unexpectedly with an out of memory error while fetching large log entries from the Administration Console.
231264 231249
231240
231239
231055
231031
-12-
PC_RLN_861011_0002
230134
The Integration Service that uses operating system profiles hangs a workflow that uses parameter files and is scheduled to run continuously. The Workflow Manager displays an error when you add a service level in the Administration Console in the Japanese locale. You cannot edit or delete the session after you open the session and the Workflow Manager displays an error message that states the object was modified since the last time it was opened. The Integration Service terminates sessions with multiple load order groups in a Lookup transformation. The Reference Table Manager displays an error when you manually enter date data into the reference tables. The Integration Service shuts down unexpectedly while aborting workflows with Event-Wait tasks. The Integration Service fails a session enabled for pushdown optimization. See 229124. Unicode session with the INSTR function returns incorrect binary comparison results. 861 HotFix 10 custom transformation sessions fail when the custom transformation has additional output ports. Sessions fail with an error message that states there is an unbound field error in the Source Qualifier while importing workflows into a new repository. Session incorrectly reads vargraphic datatype data from IBM DB2 on 64-bit Linux. Session takes a long time to initialize if the mapping contains many transformations and targets. An unexpected condition error occurs when you launch the Workflow Monitor in the Japanese locale. Database partition initialization fails for a range partitioned IBM DB2 target table. Single pipeline session with a Joiner transformation that uses sorted input returns inconsistent results when you switch the master/detail relationship. Metadata Manager cannot use the Reference Table Manager utilities to connect to the Reference Table Manager repository if the Reference Table Manager Service uses the service name parameter to connect to an Oracle database. Impacted objects appear in the target repository after you deploy a deployment group with valid objects from the source repository to the target repository. Dynamic partition sessions do not initialize and cause memory leaks. You cannot use the updateServiceProcess command to add or update custom environment variables for a service process. The operating system profile user cannot pick the LD_LIBRARY_PATH environment variable after specifying the variable in the operating system profile properties. See 227008. Session that uses the gunzip command as a pre-session command on Windows takes a long time to complete. The Integration Service incorrectly reads the message response from the FTP server if the FTP server has a
230065
230047
230009 229690
229124 228909 228824 228675 228637
228394
228046 227627 227410 227403 227239
227122
227098
227008 226543
226539
226493 226410
226400
PC_RLN_861011_0002
-13-
multi-line banner. 226368 The precision for the Varchar2 column multiplies after you import a table or synonym from an Oracle database with UTF-8 encoding into the Designer. After upgrade to 861 from 811, DECODE session performance. Session fails when an expression function invokes the REG_REPLACE function while deleting cache files for an Aggregator transformation. The Administration Console HTML code does not disable the Autocomplete tag that provides user name and password information. The Integration Service hangs and terminates workflows after a repository database deadlock on Microsoft SQL Server 2005 SP3. The Reference Table Manager displays an error when you enter decimal values into an IBM DB2 table. The Integration Service shuts down sessions with Custom transformations with more than 20 additional ports. You can view the stack trace for exceptions in the Administration Console browser. The XML Editor launches multiple Internet Explorer windows when you close the XML Editor without applying the changes. There is no pmrep command to list all the groups that a user belongs to. Custom transformation sessions with multiple output ports generate garbled output. The Integration Service creates recovery tables with update and insert errors if the connection retry period to reconnect to the database is set to greater than zero and the database connection times out. An 8.6.1 Web Services Hub does not display historical statistics. PowerCenter 8.6.1 HotFix 4 sessions on grid on Red Hat Linux 64-bit fail when reading data from an empty source flat file. The Workflow Manager does not replace the session when you change the name of a mapping after importing it and then export and import the mapping again. Session performance decreases when you create a partition point for the session that has an expression transformation with numerous variable and output ports.
226351 225620
225359
225357
225052 224721
223835 222917
220180 219612 218632
216137 207241
207217
205543
Metadata Manager 8.6.1 HotFix 11 Fixed Limitations

CR 231219, 227534 233077 Description Metadata Manager encounters unique constraint errors when you load an ERwin resource.
Data lineage does not display the link between a materialized view and a base table if the materialized view and base table exist in different schemas within the same database. You cannot select multiple schemas in the Schema Inclusion List for a relational database resource or the Folder Inclusion List for a PowerCenter resource. Metadata Manager does not list the schemas in the Schema Inclusion List in alphabetical order for a
232490
232489
-14-
PC_RLN_861011_0002
relational database resource. 232062 232061 Metadata Manager does not list the connections in the Connection Assignment tab in alphabetical order. You cannot select or clear Refresh for all schemas listed in the Schema Inclusion List for a relational database resource. When you load an IBM Rational Rose resource with an MDL file that contains a Data Model, Metadata Manager cannot find the local CAT file in the same directory as the MDL file. Metadata Manager encounters universe validation errors when you load a Business Objects resource. Data lineage does not display the link between a PowerCenter mapping and a source database table when the PowerCenter source definition uses a parameter for the Owner Name. Metadata Manager does not load the source creation date and source modified date for some Microstrategy classes. Data lineage does not display links between PowerCenter objects and relational database target tables when a connection name used in a parameter file uses lower case characters. A Cognos resource load fails with a null pointer exception when a Cognos report uses a semicolon as a delimiter. Metadata Manager Service fails to start when a loaded PowerCenter resource contains a large number of metadata extensions. When you search for a PowerCenter metadata object property, Metadata Manager does not return nonreusable sessions that match the search criteria. Metadata Manager 8.6.1 upgrade needs a performance improvement. When you delete a user from the PowerCenter domain, Metadata Manager does not delete the users personal folder. If the session mode is configured to ANSI in the Teradata ODBC driver, a Teradata resource load fails with a truncation error.
231231
230933 230908
227510
227289
227094
226942
225713
212428 183928
173543
Data Analyzer 8.6.1 HotFix 11 Fixed Limitations

CR 228101 Description You cannot access Data Analyzer version 861 HotFix 10 on Linux because the Data Analyzer Service and the PowerCenter domain are not in sync.
PowerExchange for Salesforce.com 8.6.1 HotFix 11 Fixed Limitations

CR 225524 Description The PowerCenter Integration Service only generated success and error files for only one target in a session with multiple targets. Now, the PowerCenter Integration Service generates success and error log files for each target in a session.
PC_RLN_861011_0002
-15-
215266
The PowerCenter Integration Service only generated success and error log files for the first partition in a session. Now, the PowerCenter Integration Service generates success and error log files for each partition in a session.
PowerExchange for SAP NetWeaver 8.6.1 HotFix 11 Fixed Limitations

CR 229751 Description A data record in the SAP/ALE IDoc Prepare transformation does not pick values if the MANDT field in the control record is a parameter. SAP sessions that run in file mode fail after an upgrade from 8.1.1 After requesting data from a DataSource in BCI, SAP NetWeaver does not pass any records to the target if one of the records contains a data error. BCI listener session that runs on Windows fails while extracting data from data sources that have a large number of records. Generated ABAP programs that contain "TYPE attr = UNIX" fail when run on a DB2/400 database and an AS400 platform. BAPI/RFC sessions fail with an error message that states the MATNR mapping parameter is blank or incorrectly transferred.
228514 227323
227169
226732
222572
8.6.1 HotFix 11 Documentation Updates

This section describes the documentation updates for 8.6.1 HotFix 11.
PowerCenter Administrator Guide

Chapter 11: Creating and Configuring the Metadata Manager Service
In Configuring the Metadata Manager Service > Advanced Properties, replace the description of the Max Concurrent Resource Load property with the following text: Maximum number of resources that Metadata Manager can load simultaneously. Maximum is 5. Metadata Manager adds resource loads to the load queue in the order that you request the loads. If you simultaneously load more than the maximum, Metadata Manager adds the resource loads to the load queue in a random order. For example, you set the property to 5 and schedule eight resource loads to run at the same time. Metadata Manager adds the eight loads to the load queue in a random order. Metadata Manager simultaneously processes the first five resource loads in the queue. The last three resource loads wait in the load queue. If a resource load succeeds or fails and cannot be resumed, Metadata Manager removes the resource load from the queue and starts processing the next load waiting in the queue. If a resource load fails when the PowerCenter Integration Service runs the workflows and the workflows can be resumed, the resource load is resumable. Metadata Manager keeps the resumable load in the load queue until the timeout interval is exceeded or until you resume the failed load. Metadata Manager includes a resumable load in the concurrent load count. Default is 3.
-16-
PC_RLN_861011_0002
PowerCenter Advanced Workflow Guide

Chapter 18: Partition Types
Database Partition Types Add the following sentence: Database partitioning can improve performance for IBM DB2 sources and targets that use range partitioning.
PowerCenter Command Reference

Chapter 3: infacmd Command Reference
The infacmd ListGroupsForUser replaces pmrep ListGroupsForUser command.
ListGroupsForUser
Lists all the groups that a user belongs to. The ListGroupsForUser command uses the following syntax:
<-DomainName|-dn> domain_name <-UserName|-un> user_name <-Password|-pd> password [<-SecurityDomain|-sdn> security_domain] [<-Gateway|-hp> gateway_host1:port gateway_host2:port...] [<-ResilienceTimeout|-re> timeout_period_in_seconds] <-ExistingUserName|-eu> existing_user_name [<-ExistingUserSecurityDomain|-esd> existing_user_security_domain] [<-fullHierarchy|-fh>]
The following table describes infacmd ListGroupsForUser options and arguments:

Option -DomainName -dn -UserName -un -Password -pd password Optional. Password for the user name. The password is case sensitive. You can set a password with the -pd option or the environment variable INFA_DEFAULT_DOMAIN_PASSWORD. If you set a password with both methods, the password set with the -pd option takes precedence. Required if you use LDAP authentication. Name of the security domain that the user belongs to. Default is Native. user_name Required. User name used to connect to the domain. Argument domain_name Description Required. Name of the domain.
-SecurityDomain -sdn -Gateway -hp -ResilienceTimeout -re
security_domain
gateway_host1:port gateway_host2:port
Required if the gateway connectivity information in the domains.infa file is out of date. The host names and port numbers for the gateway nodes in the domain. Optional. Amount of time in seconds that infacmd attempts to establish or reestablish a connection to the domain. If you omit this option, infacmd uses the timeout value specified in the INFA_CLIENT_RESILIENCE_TIMEOUT environment variable.
timeout_period_in_se conds
PC_RLN_861011_0002
-17-
If no value is specified in the environment variable, the default of 180 seconds is used. -ExistingUserName -eu ExistingUserSecurity Domain -esd -fullHierarchy -fh full_hierarchy Optional. List the full hierarchy of groups, including the parent groups. existing_user_security _domain Required if the requested user belongs to an LDAP security domain. Name of the security domain that the requested user belongs to. Default is Native. existing_user_name Required. Name of the user that you want to list groups for.
Infacmd isp Command Reference

updateServiceProcess
Effective in 8.6.1 HotFix11, you can use the updateServiceProcess command to add or update custom environment variables for a service process. You can provide multiple environment variables at a time. Previously, you could define custom environment variables using Informatica PowerCenter Administration Console.
PowerCenter Configuration Guide

Chapter 2: After You Install
Add the following information to Create Databases and User Accounts > IBM DB2 (Metadata Manager, Metadata Source): A Metadata Manager repository cannot be in a database for IBM DB2 that has the Database Partitioning Feature enabled.
PowerCenter Release Guide

Chapter 3: Version 8.x New Features and Enhancements
8.6.1 HotFix 11 New Features and Enhancements Add the following bullet to Integration Service > Partitioning: IBM DB2 range partitioning. You can configure database partitioning for IBM DB2 sources and targets that use range partitioning.
Chapter 5: PowerCenter Domains

Add a heading for Operating System Profiles Operating System Profiles Upgrade impact: Behavior Change Version Implemented: 8.6.1 HotFix 11 Versions Affected: 8.1.1/8.6.1/ 8.6.1 HotFix 1 to 8.6.1 HotFix 11 Effective in 8.6.1 HotFix 11, if you specify the LD_LIBRARY_PATH environment variable in the operating system profile properties, the Integration Service appends the value of this variable to its LD_LIBRARY_PATH environment variable. The Integration Service uses the value of its
-18-
PC_RLN_861011_0002
LD_LIBRARY_PATH environment variable to set the environment variables of the child processes generated for the operating system profile. If you do not specify the LD_LIBRARY_PATH environment variable in the operating system profile properties, the Integration Service uses its LD_LIBRARY_PATH environment variable. Previously, the operating system profile user could not pick the LD_LIBRARY_PATH environment variable after specifying the variable in the operating system profile properties.
Chapter 18: Metadata Manager

Add the following information to the Searches and Search Index section: Searching for PowerCenter Metadata Extensions Effective in version 8.6.1 HotFix 11, you cannot search for PowerCenter metadata extensions defined for PowerCenter metadata objects. When you upgrade, Metadata Manager modifies saved searches that search for a PowerCenter metadata extension property to search on Any Property. Previously, you could search for PowerCenter metadata extensions.
Chapter 19: PowerExchange (PowerCenter Connect)

Add the following information to the PowerExchange for SAP NetWeaver section: SAP/ALE IDoc Interpreter error output group Effective in 8.6.1 HotFix 10, the IDoc Interpreter in the processing mapping has an error output group. When you enable the row-level processing, the PowerCenter Integration Service writes all error rows to the error output group. When you upgrade, you must regenerate any processing map that you want to write error rows to the error output group. Previously, if one of the records was erroneous then no data was sent to the target.
PowerCenter Transformation Language Reference

Chapter 6: Functions
TRUNC (Numbers) Add the following text for CR 194129: A PowerCenter session enabled for high precision returns incorrect results when you use the TRUNC function. Example When the following expression is used to truncate the values in the QTY port: TRUNC ( QTY / 15 ) When the value for QTY = 15000000. The session returns the value 999999. The expected result is 1000000. At run time, the Integration Service evaluates the constant part of the expression and then the variable part. In the above expression, QTY is the variable value and (1/15) is the constant value. When QTY = 15000000, the expression is evaluated as follows:
PC_RLN_861011_0002
-19-
TRUNC ( 15000000 * (1/15) = TRUNC ( 15000000 * 0.0666666666666666) = TRUNC ( 999999.99999999) = 999999 To resolve this issue, use the ROUND function before truncating with the specified precision: TRUNC (ROUND (QTY/15, .99999999999999999999999999)).
PowerCenter XML Guide

Chapter 8: XML Datatype Reference
Add the following text to XML and Transformation Datatypes > XML Date Format: The XML parser converts the datetime value in the input xml to a value in the local time zone of the machine that hosts the PowerCenter server. If you enable the option to automatically adjust the clock for daylight savings on the Windows operation system, the XML parser adds an hour to the datetime value. For consistent datetime value conversions, do not enable the Automatically adjust clock for daylight saving changes in the Date and Time Properties on the Windows Operating System.
Metadata Manager Administrator Guide

Chapter 2: Configuring Metadata Manager and Metadata Sources
Add the following information to Step 2. Install the Metadata Manager Agent: The Metadata Manager Agent and a single version of the Business Objects client must be on the same machine. If multiple versions of the Business Objects client are on the same machine as the Metadata Manager Agent, the agent cannot extract the Business Objects metadata. Add the following information to Step 2. Install the Metadata Manager Agent > Rules and Guidelines for the Metadata Manager Agent: On Windows 32-bit, the Metadata Manager Agent runs as a service named Metadata Manager Agent <version>. The Metadata Manager Agent starts after you install it. You can stop or start the Metadata Manager Agent from the Windows Start menu or from the Windows Services panel. On Windows 64-bit, the Metadata Manager Agent does not run as a service. You must start the Metadata Manager Agent from the Windows Start menu or from a command prompt. To start the agent from a command prompt, run StartMetadataManagerAgent.bat in the Metadata Manager Agent installation directory. Add the following information to Step 3. Configure Metadata Sources > PowerCenter: Disable Extended Statistics on Oracle 11.1 When you load metadata from a PowerCenter repository that is on an Oracle 11.1 database, you must disable extended statistics on the database. Otherwise, the S_M_ELMNT_ATTR_FIRST_LOAD session fails with the following error:
ERROR at line 1: ORA-03113: end-of-file on communication channel
Extended statistics gathers object statistics and histograms on expressions or on a group of columns. To disable extended statistics, set the Oracle system parameter _optimizer_enable_extended_stats to FALSE. Run the following command on the Oracle database:
Alter system set "_optimizer_enable_extended_stats" = FALSE scope=spfile/both/memory;
For more information about this Oracle parameter, see the Oracle documentation.
-20-
PC_RLN_861011_0002
Chapter 3: Creating Resources

Add the following information to the description of the JDBC connection URL property in the Database Management section: For Teradata databases that contain multibyte data, add the CHARSET parameter to specify the Teradata character set. For example: jdbc:teradata://[database_server_name]/Database=[database_name],CHARSET=[character_set_name] For more information about the supported Teradata character sets, see the Teradata documentation.
Chapter 4: Managing Resources

Add the following information to the Configuring Resource Parameters > Schema Inclusion List section: Select Refresh for schemas that have changed since the last resource load or that you want to load for the first time. Metadata Manager loads the schemas selected for refresh. By default, all previously loaded schemas have Refresh selected. You can clear Refresh for a previously loaded schema that you do not want to reload. You can also clear or select Refresh for all schemas in the Selected Schemas list.
Appendix B: Resource Reference

Add the following information to the Microstrategy section: Creation and Modification Date of Classes Metadata Manager displays the source creation date and the source modified date for most Microstrategy classes. Metadata Manager does not display these dates for the following classes: MicrostrategyDataType MicrostrategyReportField MicrostrategyGraph MicrostrategySchemaJoin MicrostrategyGrid MicrostrategyReportObjectDetail MicrostrategyReportObject
Metadata Manager User Guide

Chapter 3: Searching Metadata
Add the following information to the Property description in the Performing an Advanced Search section: Note: You cannot search for PowerCenter metadata extensions defined for PowerCenter metadata objects.
8.6.1 HotFix 11 Known Limitations

The following section describes the known limitation for 8.6.1 HotFix 11.
PC_RLN_861011_0002
-21-
PowerCenter 8.6.1 HotFix 11 Known Limitations

234762: After you import an Oracle or Microsoft SQL table into the Designer, the precision of CLOB, NCLOB, and Long columns becomes 0 and the precision of the sysname column multiplies When you import an Oracle table into the Designer, the precision for CLOB, NCLOB, and Long columns becomes 0. When you import a Microsoft SQL table into the Designer, the precision for the sysname column multiplies by eight times. Workaround: After importing the tables edit the precision of the columns in the Designer. For Oracle database tables with UTF-8 encoding, enable the NChar datatype on the Data Source Name (DSN). Perform the following steps to enable the Oracle table to use the NChar datatype: 1. 2. 3. 4. In the Oracle database, click Control panel > Administrative tools > Data Source. Select the DSN that the Designer uses to import the table definition. Click Configure. The ODBC Oracle Wire Protocol Driver Setup window appears. On the Advanced tab, select the Enable N-CHAR support option.
215012: Cannot enable the Reporting Service on AIX 64 bit in the HTTPS mode when another Reporting Service runs in the HTTP mode When you enable the Reporting Service on an HTTP node that runs on AIX 64 bit on an HTTPS domain, the service fails with an error. Workaround: Perform one of the following tasks to enable the Reporting Service in the HTTP or HTTPS modes: 1.The Reporting Service is the only service that is being enabled in the domain. 2. There already is a Reporting Service running in the HTTPS mode in the domain. Or, a Reporting Service on an HTTP node in an HTTPS domain. 3. Disable any Reporting Services in the HTTP mode.
Metadata Manager 8.6.1 HotFix 11 Known Limitations

229863: Links, comments, and shortcuts are removed for some resource types after applying the HotFix. After you apply the HotFix and reload data modeling or business intelligence resources, links and comments are removed from metadata objects in these resource types. Shortcuts that refer to data modeling and business intelligence metadata objects are broken.
B2B 8.6.1 HotFix 11 Known Limitations

233647: Connecting to the B2B Data Exchange Repository Fails with PowerCenter 8.6.1 HF11 A connection error occurs when running B2B Data Exchange 8.6.1 or 8.6.2 with PowerCenter 8.6.1 HF11. PowerCenter displays the following error message: The connection to the Data Exchange repository failed. The values for the Event type selections are taken from the client plug-in configuration file. Workaround:
-22-
PC_RLN_861011_0002
To resolve this connection issue, perform the following tasks on each machine that has the B2B Data Exchange PowerCenter plug-in installed: 1. 2. 3. 4. Under the dx directory, back up powercenter/plugin/dxplugin.ini. Open dxplugin.ini with a text editor. Search for DataDirect 5.2 and replace it with DataDirect 6.0. Restart the PowerCenter Designer.


CR 225997 Description Sessions fail when multiple mappings use a reusable Lookup transformation configured to use a persistent cache. pmrep shuts down unexpectedly when a pmrep command uses a control file with a user-defined function that calls a Lookup transformation. The Workflow Manager shuts down when you open the Pushdown Optimization Viewer. A mapping is no longer valid after deployment from the source repository to the target repository. The Integration Service writes an error to the session logs instead of a warning when an incorrect expression is used in an Expression transformation. The Integration Service fails a session that reads from a file list source and writes to an IBM DB2 target in bulk mode. The XML writer, XML generator, and web services that use the MS Windows Latin1 (ANSI) superset of Latin1 [MS1252] code page generate output with the ISO-8859-1 codepage instead of the MS Windows 1252 codepage. The Designer does not recognize the period in ODBC sources. For more information, see the PowerCenter Designer Guide. A web service workflow randomly hangs when the workflow is hosted on the PowerCenter Web Services Hub. Session using an FTP connection for an SFTP server that requires public key authentication fails for a Pluggable Authentication Module enabled on the machine where the session runs. The Integration Service shuts down unexpectedly when a workflow enabled for recovery and configured to use an operating system profile has an exception error. Session fails when multiple FTP source partitions fail intermittently because of an FTP access error. Pushdowm optimization enabled session with a Netezza ODBC driver has a different SQL query in the session log and the ODBC trace file. Web Services Consumer session fails when no internet connectivity is available for the machine on which the Integration Service runs.
225851
225815 225567 224460
224293
222630
222260
221602
221053
220349
220033 219766
219670
PC_RLN_861011_0002
-23-
218857 218524 217826
The master gateway node hangs in the domain due to a deadlock that occurs during LDAP authentication. SQL transformation session returns a null value when the precision of the output port is greater than 65000. The repository agent fails unexpectedly if an LDAP user tries to log in to an application client during synchronization. The Repository Manager cannot import metadata from an ERwin 4.12 source because of a datatype mismatch. Duplicate sources appear in the Sources folder in the Designer and Repository Manager after deploying a deployment group to the target repository. The Designer shuts down unexpectedly when you preview data in the CSV file that contains special and non-English characters during import. A user needs to have the Administrator role to edit a service level assigned to the workflow. The Integration Service does not recover a recovery enabled session on grid if you stop the worker DTM. The Integration Service shuts down unexpectedly while scheduling workflows. A two second delay occurs between session runs when the Integration Service runs a workflow with sequential runs on Linux or zLinux. The DTM process shuts down unexpectedly while aborting a workflow configured to use an operating system profile and a FileWatch event task. When you compile a Java transformation, the Designer generates files within the default workspace directory instead of the user-defined directory. The Integration Service hangs intermittently while running a pre-session command on a Solaris machine. The domain shuts down while switching the repository from exclusive to normal mode. Session fails when there is a missing new line character in a workflow parameter file. Sessions on grid intermittently terminate while writing to a Netezza target. 8.6.1 HotFix 1 sessions take a long time to load data to a Sybase database. Sessions that use the FastExport utility to read data from Teradata sources read the Float datatype values as 0. Session terminates when there are multiple connected lookups and a restriction on the number of pipelines that the Integration Service can create concurrently set to Auto or a number greater than one.
217002
215841
214798
214301 214291 213133 211724
210244
210068
209743 207897 207384 203282 202854 202731
201241

CR 226478 224448 Description Metadata Manager incorrectly displays the lineage between a custom resource and its Business Term. Metadata Manager cannot load an IBM DB2 zOS resource that has view containing more than 4000 characters into the Metadata Manager warehouse in Oracle. Metadata Manager cannot load a MicroStrategy resource into the Metadata Manager warehouse using the
223985
-24-
PC_RLN_861011_0002
MicroStrategy 6.0.3 bridge. 222804 Metadata Manager cannot load an Oracle resource into the Metadata Manager warehouse due to an invalid datatype error. Metadata Manager cannot load a Teradata 13 resource into the Metadata Manager warehouse because Teradata 13 is not in the list of resources that Metadata Manager can load. Metadata Manager cannot display the lineage between a SAP and a PowerCenter resource. Metadata Manager cannot load a Cognos 8.4 resource into the Metadata Manager warehouse because Cognos 8.4 is not in the list of resources that Metadata Manager can load. Metadata Manager cannot load a Teradata 12 resource into the Metadata Manager warehouse because Teradata 12 is not in the list of resources that Metadata Manager can load. The Metadata Manager Agent does not have the Cognos patch required to run Cognos resources. Metadata Manager does not display the data lineage diagram between a Teradata view that contains comments and the original table. Metadata Manager cannot load an OBIEE resource into the Metadata Manager warehouse because of a memory allocation error. Metadata Manager cannot extract the source creation date and update date from any of the MicroStrategy classes in a MicroStrategy resource. Metadata Manager loads recycle tables named BIN$ for an Oracle 10g resource. Metadata Manager loads all the schemas from the Teradata source into the selected schema for the Teradata resource load.
222507
222496 222344
222343
221250 218669
218424
206258
203222 186146

CR 210303 Description After requesting data from a DataSource in BCI, SAP NetWeaver does not pass any records to the target if one of the records contains a data error.
PowerExchange for WebSphere MQ 8.6.1 HotFix 10 Fixed Limitations

CR 225484 Description WebSphere MQ sessions fail if target based commit is set for the file writer connection and the number of rows per message is greater than the maximum number of rows set for the queue manager.
8.6.1 HotFix 10 Documentation Updates

This section describes the documentation updates for 8.6.1 HotFix 10.
PC_RLN_861011_0002
-25-
PowerCenter Administrator Guide

Chapter 18: PowerCenter Integration Service
Using Operating System Profiles Add the following sentence: When you configure operating system profiles on UNIX, you must enable setuid for the file system that contains the Informatica installation. Using Operating System Profiles > Configuring Operating System Profiles Add the following step to the procedure: 1. On UNIX, verify that setuid is enabled on the file system that contains the Informatica installation. If necessary, remount the file system with setuid enabled.
PowerCenter Command Reference

Chapter 6: pmrep Command Reference
The following pmrep commands have the -e dbd_separator option: ApplyLabel ListObjectDependencies ObjectExport
Option -e
Argument dbd_separator
Description If an ODBC source has a period (.) in the name, define a different separator character when you define the source object. For example, instead of database_name.source_name, define the source object as database_name\source_name, and define the dbd_separator as backslash (\).
The following pmrep commands have the -s dbd_separator option: AddToDeploymentGroup Checkin DeleteObject ExecuteQuery FindCheckout ListObjects PurgeVersion UndoCheckout
-26-
PC_RLN_861011_0002
Option -s
Argument dbd_separator
Description If an ODBC source has a period (.) in the name, define a different separator character when you define the source object. For example, instead of database_name.source_name, define the source object as database_name\source_name, and define the dbd_separator as backslash (\).
PowerCenter Designer Guide

Chapter 2: Working with Sources
Working with Sources Overview > Special Character Handling in Source Definitions Add the following row to the table:
Special Character . Source Analyzer Behavior The Designer recognizes the period in ODBC sources. Mapping Designer Behavior The Designer recognizes the period in ODBC source instances.
Metadata Manager Administrator Guide

Chapter 2: Configuring Metadata Manager and Metadata Sources
In Step 3: Configure Metadata Sources > Relational Database Sources, remove the Teradata section.
Chapter 3: Creating Resources

Business Objects Rename the following resource properties: Repository User Name to User Name Repository User Password to Password Remove the Repository Name and JAVA API Path properties. Add the System property with the following description: Enter the name of the machine where Business Objects is installed and the Business Objects Central Management Server port number on that machine. Enter in the following format: <server_name>:<port_number> Cognos ReportNet Content Manager Rename the following resource properties: Login Namespace to Namespace Login User to User Login Password to Password Repository Subset to Content
Chapter 4: Managing Resources

In Configuring Connection Assignments, add the following property to the table in the Data Integration and Business Intelligence Resources section:
PC_RLN_861011_0002
-27-
Use Schema Prefix. Metadata Manager uses the schema name in the business intelligence model to link objects in connected relational database resources. If you disable this option, Metadata Manager does not use the business intelligence schema name to link objects. Metadata Manager can link objects to any relational database schema that contains all of the tables used by the business intelligence model. Disable this option if you did not extract the actual relational database schemas, but extracted other schemas that contain the same content.
Appendix B: Resource Reference

Oracle Add the following information to the Objects Extracted section: Metadata Manager does not extract dropped tables, constraints, triggers, or indexes from the Oracle schema. Teradata Remove the Browsing the Catalog section.
Appendix C: Source Privileges and Permissions

Remove the following information in the Teradata section: To browse a Teradata catalog, the user account must also have permission to view all schemas and users in the hierarchy between the DBC user and the metadata you want to browse.
Metadata Manager Business Glossary Guide

Chapter 4: Managing the Business Glossary
In Creating a Business Glossary in Microsoft Excel, replace the description of the Reference Table property in the Business Term Properties table with the following text: Reference Table Manager connection name and reference table name. Use the following syntax: <connection_name>@<schema_name>.<reference_table_name>
PowerCenter Release Guide

Chapter 18: Metadata Manager
Business Intelligence Resources Behavior Change Version Implemented: 8.6.1 HotFix 10 Versions Affected: 8.1 / 8.1.1 / 8.5 / 8.5.1 / 8.6 / 8.6.1 / 8.6.1 HotFix 1 through 9 Effective in 8.6.1 HotFix 10, the Connection Assignment tab for a business intelligence resource includes a Use Schema Prefix property. If you enable this option, Metadata Manager uses the schema name in the business intelligence model to link objects in connected relational database resources. If you disable this option, Metadata Manager does not use the business intelligence schema name to link objects. Metadata Manager can link objects to any relational database schema that contains all of the tables used by the business intelligence model. Disable this option if you did not extract the actual relational database schemas, but extracted other schemas that contain the same content. Previously, Metadata Manager could not use the business intelligence schema name to link objects in connected relational database resources.
-28-
PC_RLN_861011_0002
Business Objects Resource Behavior Change Version Implemented: 8.6.1 HotFix 10 Versions Affected: 8.1 / 8.1.1 / 8.5 / 8.5.1 / 8.6 / 8.6.1 / 8.6.1 HotFix 1 through 9 Effective in 8.6.1 HotFix 10, you do not need to configure the JAVA API Path configuration property. Metadata Manager automatically detects the path. Previously, you needed to enter the JAVA API Path for Business Objects resources. Effective in 8.6.1 HotFix 10, you use the System property to enter the name of the machine where Business Objects is installed and the Business Objects Central Management Server port number on that machine. Previously, you used the Repository Name property to enter the name of the Business Objects repository that you wanted to connect to. Oracle Resource Behavior Change Version Implemented: 8.6.1 HotFix 10 Versions Affected: 8.1 / 8.1.1 / 8.5 / 8.5.1 / 8.6 / 8.6.1 / 8.6.1 HotFix 1 through 9 Effective in 8.6.1 HotFix 10, Metadata Manager does not extract dropped tables, constraints, triggers, or indexes from an Oracle schema. Previously, Metadata Manager did extract dropped tables, constraints, triggers, and indexes. Teradata Resource Behavior Change, Updated Metadata Version Implemented: 8.6.1 HotFix 10 Versions Affected: 8.1 / 8.1.1 / 8.5 / 8.5.1 / 8.6 / 8.6.1 / 8.6.1 HotFix 1 through 9 Effective in 8.6.1 HotFix 10, Metadata Manager no longer extracts the Teradata hierarchy of databases and users. Teradata organizes databases and users under the DBC user. You do not need to export the entire hierarchy from the DBC user to the metadata that you want to view. Previously, to browse metadata in a Teradata database catalog, you had to export the entire hierarchy from the DBC user to the metadata that you wanted to view.
PowerExchange for WebSphere MQ User Guide

Chapter 5: Working with WebSphere MQ Targets
Working with a Static Websphere MQ Target Definition When you configure WebSphere MQ sessions for MQ targets with a file writer connection and Target Based Commit (TBC), the number of messages committed to MQ targets and number of rows per message might vary.
8.6.1 HotFix 10 Known Limitations

This section describes the known limitations for 8.6.1 HotFix 10.
PC_RLN_861011_0002
-29-
PowerCenter 8.6.1 HotFix 10 Known Limitations

191241: The DTM process shuts down unexpectedly when the Repeat Null Character fixedwidth flat file property is selected for multibyte null characters When you specify a multibyte null character and select the Repeat Null Character fixed-width flat file property, the field may contain extra trailing bytes if the field length is not evenly divisible by the number of bytes in the null character. In this case, the field is not null. Workaround: Specify a single-byte null character for the Repeat Null Character fixed-width flat file property.


CR 218337 217625 Description The Integration Service running on a grid with two nodes shuts down unexpectedly. After applying 8.6.1 HotFix 8, the workflow and session logs display Chinese characters if the locale on the machine is traditional Chinese. When the Load Balancer runs in adaptive mode, sessions go into wait mode and do not get dispatched to other nodes. Pushdown optimization session fails while connecting to an Oracle database with an error message that states the column names are too long. A user cannot create a shortcut or copy an object from a folder in a global repository to a local repository even when the user has read permission on the global repository folder and write permission on the local repository folder. Non-reusable objects are not checked in after you copy and check in a mapping shortcut to the target repository. Session hangs while running a workflow with the restart task recovery strategy enabled. Workflows in a static deployment group cannot be assigned to the Integration Service after you deploy the deployment group to the target repository. The Integration Service processes the SQL filter condition incorrectly when it runs a session with a Salesforce.com object. Session hangs intermittently when it contains the Sorter, Joiner, and Sequence Generator transformations. Recovery session terminates with the worklet status as terminating and the workflow status as running. An upgrade session fails when pushdown optimization is enabled for an unconnected Lookup transformation. The Integration Service fails a session configured for pushdown optimization. The Integration Service fails PowerCenter sessions configured for pushdown optimization that have many
217516
217273
216598
216221
215930 215907
215384
215100 214988 214857
214539 213904
-30-
PC_RLN_861011_0002
sources and targets. 213464 Session configured with pushdown optimization generates an invalid query for an Expression transformation that uses an IF ELSE expression and outputs date data to a Teradata database. The Integration Service fails sessions with pre- and post-session command that cannot open the standard output files. After sessions complete, connections for the Repository Service and the Integration Service process remain the close wait state. You cannot add multiple email addresses for the $PMSuccessEmailuser service variable when you configure the Integration Service. The Integration Service does not fail a session that encounters a user-defined error for the stored procedure in a Sybase database. Session fails when the XML source column has the string datatype of infinite precision. The pmrep ObjectImport command fails to import a workflow on AIX 5.3. The Repository Manager incorrectly deploys deployment group objects to the target repository. Real-time CDC session that is enabled for recovery takes a long time to load data.
211959
211348
211031
210880
210405 207419 206831 204688

CR 217770 217071 Description Metadata Manager takes a long time to edit an object if the catalog is large. Metadata Manager takes a long time to load a PowerCenter resource into the Metadata Manager warehouse on an Oracle database. Metadata Manager cannot update any custom property for a synonym. Metadata Manager cannot import the business glossary from an Excel file, if the business glossary name has Chinese characters. Metadata Manager extracts Oracle internal public synonyms if you include PUBLIC in the inclusion list of an Oracle resource. For more information, see Metadata Manager 8.6.1 HotFix 9 Fixes Affecting Functionality. Metadata Manager takes up to four minutes to display a business term with related catalog objects. Metadata Manager takes a long time to add a business term to the glossary. Metadata Manager displays an out of memory error when you import an XML file that is greater than 190 MB. Metadata Manager loads a PowerCenter resource but the PowerCenter sessions have unique constraint errors. The Metadata Manager Service fails to enable on a Sybase database and logs errors in the Domain log events. Metadata Manager cannot assign the relational connections for an OBIEE resource. Metadata Manager does not consider all the links between objects when performing data lineage analysis.
217054 216824
215816
215600 215402 215330
214008
213949
212610 210979
PC_RLN_861011_0002
-31-
205643
Lineage diagram does not display the links for a Powercenter target instance to a database object if the target table name has the SCHEMA_NAME.TABLE_NAME syntax. Metadata Manager displays an exception error while performing lineage analysis on a synonym created with a database link for an object in a different database.
203962

CR 217480 209431 Description See 206893. SAP does not perform authorization checks when you install an ABAP program. For more information, see PowerExchange for SAP NetWeaver 8.6.1 HotFix 9 Fixes Affecting Functionality. The SAP BI Monitor on the SAP system does not display the InfoPackage status as failed even when the Integration Service aborts the SAP BI session. For more information, seePowerExchange for SAP NetWeaver 8.6.1 HotFix 9 Fixes Affecting Functionality.
206893
8.6.1 HotFix 9 Fixes Affecting Functionality

This section describes the fixes affecting functionality for 8.6.1 HotFix 9.
Metadata Manager 8.6.1 HotFix 9 Fixes Affecting Functionality

217071: Metadata Manager takes a long time to load a PowerCenter resource into the Metadata Manager warehouse on an Oracle database Effective 8.6.1 HotFix 9, you can set the following property in imm.properties to improve Metadata Manager performance during a resource load:
Property Load.OracleOptimizerDynamicSampling Description Sets the Oracle session parameter OPTIMIZER_DYNAMIC_SAMPLING on the PowerCenter sessions that load to a Metadata Manager warehouse on Oracle. Default is 3. Valid values are 0-10. A value of 0 disables dynamic sampling. Contact your Oracle database administrator to get the appropriate value for your environment. Note: To use this option, Cost Based Optimization (CBO) must be enabled on the Oracle instance.
215816: Metadata Manager extracts Oracle internal public synonyms if you include PUBLIC in the inclusion list of an Oracle resource Effective 8.6.1 HotFix 9, Metadata Manager only extracts public synonyms for the schemas you selected to load. Previously, Metadata Manager extracted all public synonyms for an Oracle resource.
-32-
PC_RLN_861011_0002
PowerExchange for SAP NetWeaver 8.6.1 HotFix 9 Fixes Affecting Functionality

209431: SAP does not perform authorization checks when you install an ABAP program Effective in version 8.6.1 HotFix 9, you can require that SAP perform an authorization check on ABAP programs that are generated and installed from the Designer. To require that SAP perform an authorization check, upgrade the TBL_DESIGN transport program when you upgrade to the current version of PowerExchange for SAP NetWeaver. Previously, SAP did not perform an authorization check on ABAP programs that were generated and installed from the Designer. 206893: The SAP BI Monitor does not display the InfoPackage status as failed even when the Integration Service aborts or stops the SAP BI session Effective in version 8.6.1 HotFix 9, the SAP BI Monitor displays the InfoPackage status. The status in the SAP BI monitor is green, yellow, or red depending on the status of the PowerCenter session. Green indicates that the data loaded successfully. Yellow indicates that the data loaded with warnings. Red indicates that the failed to load. The SAP BI Monitor indicates status in the following cases: The Integration Service did not load any rows to SAP BI, because the source system contained no data. However, the PowerCenter session completed successfully. The SAP BI Monitor indicates a status of green, yellow, or red, depending on the Traffic Light Color for Empty Requests settings in the InfoPackage. Default is yellow. The Integration Service failed and did not load any rows to SAP BI. The SAP BI Monitor indicates a status of red. The Integration Service failed after loading some data into SAP BI. The SAP BI Monitor indicates a status of red. If a session enabled for recovery fails, the SAP BI Monitory indicates a status of yellow. The SAP BI Monitor status changes to green after data loads successfully during the recovery run.


CR 212732 Description Lookup transformation session enabled for pushdown optimization generates an invalid query when the Date datatype column is used in the lookup condition. Session rejects rows when writing Date datatype data from a Teradata database to the Timestamp datatype in an Oracle target definition. Session continues to read some rows from a Sybase database even when the database deadlocks. The Integration Service fails concurrent sessions with a broken pipe error when the sessions read from and write to an Operating System pipe.
212424
211330 211156
PC_RLN_861011_0002
-33-
210328 209221 206666
The Integration Service shuts down unexpectedly after workflows with Event-Wait tasks terminate. See 211330. Reference Table Manager does not provide security on connections. For more information, see Reference Table Manager 8.6.1 HotFix 8 Fixes Affecting Functionality. The Worklfow Manager duplicates concurrent workflow run instances after the workflow is deployed using the Repository Manager.
202080

CR 213002 Description A metadata catalog search that returns a large number of results can fail with an out of memory error. For more information, see Metadata Manager 8.6.1 HotFix 8 Fixes Affecting Functionality. See 211349. Metadata Manager cannot index large resources because of insufficient memory. Indexing large amounts of metadata during a resource load fails with an SQL exception. For more information, see .Metadata Manager 8.6.1 HotFix 8 Fixes Affecting Functionality. Metadata Manager returns incorrect search results if the search query contains a mixed case custom attribute for an object that was added or edited using the Metadata Manager interface.
211715 211349 211349
209713
PowerExchange for JMS NetWeaver 8.6.1 HotFix 8 Fixed Limitations

CR 211618 Description PowerExchange for JMS writes the value of the previous messages correlation ID to the queue if the value of the correlation ID for the current message is NULL.


211349: Indexing large amounts of metadata during a resource load fails with an SQL exception 213002: A metadata catalog search that returns a large number of results can fail with an out of memory error Effective 8.6.1 HotFix 8, you can set the following properties in imm.properties to improve Metadata Manager performance during indexing and searching:
-34-
PC_RLN_861011_0002
Property lucene.merge.factor
Description Controls the number of metadata objects to store in memory before merging them into the index. Use this option to improve indexing performance for Metadata Manager. Default is 1000. Note: Setting a value greater than the default value can result in a Java exception due to too many open files.
lucene.ram.buffer
Determines the amount of memory used to buffer metadata objects before they are merged into the index. Use this option to improve indexing performance for Metadata Manager. Default is 64 MB. Note: Setting a value greater than the default value can result in the following error:
java.lang.OutOfMemoryError
search.max.docs
Maximum number of search results that Metadata Manager displays for a catalog search. Default is 1000. Note: Setting a value greater than the default value can result in the following error:
java.lang.OutOfMemoryError
After you configure imm.properties, restart the Metadata Manager Service. imm.properties is located in the following directory:
<PowerCenter installation directory>\server\tomcat\shared\classes
Previously, indexing large amounts of metadata during a resource load catalog can fail with an SQL exception. In addition, a catalog search that returns a large number of results can fail with an out of memory errors.
Reference Table Manager 8.6.1 HotFix 8 Fixes Affecting Functionality

206666: Reference Table Manager does not provide security on connections Effective in version 8.6.1 HotFix 8, you can assign users and groups permission on database connections. A user must have permission on a connection to access the connection in Reference Table Manager. The fix includes the following changed functionality: Manage User privilege Permission assignment on connections Previously, all users had access to all connections. To assign permission on connections, you must upgrade the contents of the Reference Table Manager repository after applying the PowerCenter Services hotfix. For more information, see Upgrade the Contents of the Reference Table Manager Repository. Manage User Privilege
PC_RLN_861011_0002
-35-
The View User Information privilege for the Reference Table Manager Service is renamed the Manage User privilege. The Manage User privilege enables users to use Reference Table Manager to assign users and groups permission on connections. After you apply 8.6.1 HotFix 8, all users previously assigned the View User Information privilege are assigned the Manage User privilege. Use the PowerCenter Administration Console to review the Manage User privilege assignments so that only the appropriate users can assign permission on connections. Permission Assignment on Connections Permissions control whether a user can access an object. In Reference Table Manager, you assign permission on connections. When a user has permission on a connection, the user can access the connection in Reference Table Manager. You can assign users or groups permission on connections. When a group has permission on a connection, all subgroups and users belonging to the group inherit permission on the connection. When users are assigned the Administrator role for the Reference Table Manager Service, they inherit permission on all connections. To assign permission on connections: 3. 4. 5. 6. 7. In Reference Table Manager, click the Users tab. Select a user or group and click Edit. The User/Group Details dialog box appears. Select the connections to assign the user or group permission on. To revoke permission, clear the connections assigned to the user or group. Click OK.
After you apply 8.6.1 HotFix 8, users do not have permission on any connections. Use Reference Table Manager to assign users permission on connections.


CR 211102 Description Unexpected condition occurs when you re-import an XML source definition containing a CurrentlyProcessedFileName port. Rank and Aggregator session fails when loading data in the cache. Session fails to connect to an FTP server running on HPUX Tru64. After an Event-Wait task is dispatched for execution, the Integration Service that runs workflows for a worker service process on a grid shuts down unexpectedly. The Integration Service on Windows 64-bit Itanium shuts down unexpectedly. Session with multiple uncached lookups uses one relational database connection for each lookup in a partition instead of using the same relational database connection for all uncached lookups. See 210560.
210660 210560 210162
209519 209331
209025
-36-
PC_RLN_861011_0002
208730
Session hangs or takes a long time to complete if it is configured to use input source data or a file list generated by an operating system command. The Expression Editor for a Filter transformation does not display a message when the expression is parsed successfully. The deployment operation fails when you apply a label to a Timer task during the deployment process. The Repository Service on different operating systems can hang or shut down unexpectedly while processing a query. The pmcmd command getsessionstatistics and the Batch Web Services call getsessionstats do not execute the last run of the workflow for a recovery session. There are corrupt SQL script files in the PowerCenter 8.6.1 client installation directory. SQL transformation sessions return NULL values for string columns if the precision is greater than 65534.
208532
208279 206886
206067
204947 202398

CR 210341 210312 Description Metadata Manager Agent cannot extract metadata from a Business Objects resource. Metadata Manager fails to create a PowerCenter resource when the version of the PowerCenter source is less than version 8.5. Metadata Manager cannot parse the values of the parameter files associated with the PowerCenter workflow. Extracting metadata from a Microstrategy 8.1 fails if Safe Mode is set to False. For more information, see .Metadata Manager 8.6.1 HotFix 7 Fixes Affecting Functionality. The SQL scripts for Metadata Manager 8.6.1 HotFix 5 contain unnecessary ^M characters.
209508
210512
208718

CR 206874 Description The Designer shuts down unexpectedly while accessing the IDoc Display tab for an SAP/ALE IDoc Interpreter transformation.
PowerExchange for Web Services 8.6.1 HotFix 7 Fixed Limitations

CR 209466 Description Session containing Web Service sources or targets, or Web Service Consumer transformations terminates with an error in IIS web servers. For more information, seePowerExchange for Web Services 8.6.1 HotFix 7 Fixes Affecting Functionality.
PC_RLN_861011_0002
-37-


210512: Extracting metadata from a Microstrategy 8.1 fails if Safe Mode is set to False Effective 8.6.1 HotFix 7, Metadata Manager extracts all metadata from a Microstrategy 8.1 resource. Metadata Manager no longer displays the Safe Mode option. Previously, Metadata Manager could not extract metadata from a Microstrategy 8.1 resource if Safe Mode was set to False. 193077: Performance is slow when viewing Related Objects Catalog section Effective in 8.6.1 HotFix 7, the related catalog objects for a metadata object do not include parent or child objects. Use the metadata catalog to view the parent and child objects. Previously, the metadata object included all parent and child objects as related catalog objects.
PowerExchange for Web Services 8.6.1 HotFix 7 Fixes Affecting Functionality

209466: Session containing Web Service sources or targets, or Web Service Consumer transformations terminates with an error in IIS web servers Effective in version 8.6.1 HotFix 7, you can configure the SOAP Response Compression property on the Mapping tab in the session properties. You can configure SOAP response compression for web service sources and targets and Web Service Consumer transformations. Select one of the following values: All. The Integration Service enables HTTP response compression. None. The Integration Service uses no compression. If the Integration Service connects to an IIS web server, set SOAP Response Compression to None. Default is All. Previously, sessions running on an IIS web server failed because of incorrect compression in HTTP response headers.


CR 208544 208336 Description The Designer does not correctly create XML Views for an imported complex XSD file. Router transformation session duplicates rows when routing data from a source with more than 350,000 rows.
-38-
PC_RLN_861011_0002
208201
The Repository Agent shuts down unexpectedly when security audit trails log events are included in the Repository Service logs while copying workflows between repositories. Stored Procedure transformation session fails because the connection information for the stored procedure reverts to the default value after you import a workflow. An invalid scale error occurs when you import an XML file generated from an XSD source that does not have a datatype defined. The domain shuts down after you disable a Reporting Service. The Integration Service that uses operating system profiles shuts down unexpectedly while aborting a workflow with an Event-Wait task. The Integration Service rejects junk character rows when loading data to a fixed-width target flat file. When a domain with lower case letters in its name is restarted, the domain database table that stores lock information about the master gateway node is not updated causing multiple nodes to become master nodes. The Workflow Manager shuts down unexpectedly after a session is enabled for pushdown optimization. The SQL transformation prepares a dynamic SQL query for each record if the query entails string replacement. SQL transformation session fails when the mapping parameter uses a large SQL Override query. The DTM process aborts and terminates a session that has a VSAM source with a NULL character. With high precision enabled, the Integration Service writes duplicate rows to the target but writes correct number of rows to the session log. The pmcmd startworkflow command with the wait option enabled does not always wait till the worklflow completes before starting the workflow again. The Repository Manager shuts down unexpectedly while purging active objects from the repository. The Integration Service on UTF-8 encoding of Unicode truncates the mapping parameter value. pmrep on AIX shuts down unexpectedly when you run a script containing the pmrep deploydeploymentgroup command.
208091
207861
207802 207747
207632 207255
207014 206775
206711 205213 205022
204368
204050 203445 203278

CR 206451 Description Metadata Manager displays incorrect lineage for multiple related catalog objects that have the same business term after importing the business glossary as an Excel file. If the Metadata Manager Service does not run on the master gateway node, the Reference Table Manager link in the Metadata Manager Business Glossary does not work. Metadata Manager displays incorrect lineage for relationships that are added or updated after the business glossary was imported as an Excel file.
204546
201392
PC_RLN_861011_0002
-39-

CR 207953 Description Integration Service performs row-level processing for IDoc data with segments longer than 1,000 characters. For more information, see PowerExchange for SAP NetWeaver 8.6.1 HotFix 6 Fixes Affecting Functionality. After an upgrade from version 7.1.3 to any version up to 8.6.1 HotFix 5, SAP/ALE IDoc Interpreter transformation session run time increases. The SAP NetWeaver BCI Wizard cannot display data source fields that have the selection type M in the selection criteria. Business content integration processing workflows with long IDoc segments do not run as scheduled. For more information, see PowerExchange for SAP NetWeaver 8.6.1 HotFix 6 Fixes Affecting Functionality.
205511
196880
189863

PowerExchange for SAP NetWeaver 8.6.1 HotFix 6 Fixes Affecting Functionality

207953: Integration Service performs row-level processing for IDoc data with segments longer than 1,000 characters The Integration Service processes IDoc data with segments longer than 1,000 characters for sessions configured to perform row-level processing. Previously, when the Integration Service encountered IDoc data with segments longer than 1,000 characters in a session configured for row-level processing, it failed the session without logging the problem. 189863: Business content integration processing workflows with long IDoc segments do not run as scheduled The Integration Service does not start scheduled business content integration processing workflows that include segments longer than 1,000 characters. Configure the Connection Object Effective in PowerCenter 8.6.1 HotFix 6, PowerExchange for SAP NetWeaver provides an SAP_ALE_IDoc_Writer connection type, BCI Metadata Connection. Use this connection type to run business content integration processing workflows with segments longer than 1,000 characters. To use the application connection type, complete the following steps: 1. Upgrade and register the pmsapplg.xml plug-in. 2. Create a Type A DEST entry in saprfc.ini. 3. Configure an SAP_ALE_IDoc_Writer application connection that uses the DEST value in the saprfc.ini file. 4. In a business content integration source session, configure the BCI Listener to use the BCI Metadata Connection.
-40-
PC_RLN_861011_0002


CR 206950 206827 Description Informix sessions that run in parallel fail randomly. PowerCenter Client cannot connect to the repository after network connection is restored within resilience timeout. The Integration Service schedules unscheduled workflows after you deploy a deployment group to the target folder. The Integration Service shuts down unexpectedly after workflows with Event-Wait tasks terminate. The Integration Service fails sessions with multiple connected and unconnected lookups to the same source. The Integration Service cannot retry target writes on deadlock for Transaction Control transformation sessions with automatic memory settings enabled. The Integration Service does not write error messages to the session log for XML Parser sessions that drop records with incorrect Date/Time datatype values. Cannot log in to the Administration Console on a master gateway node that comes up after failover. After an upgrade, the Integration Service fails sessions enabled for pushdown optimization. The Data Transformation Manager process shuts down unexpectedly while processing the sort operation. Cannot open the query editor in the SQL Ports tab of the SQL transformation in the Japanese locale.
206147
206083 205495 205214
204997
201872 200305 197664 183106

CR 206896 Description You cannot use Metadata Manager in HTTPS mode with a keystore file password other than the default password, changeit. For more information, see Metadata Manager HotFix 5 Fixes Affecting Functionality. Metadata Manager cannot load an Oracle resource that contains a large number of stored procedures. Java processes for a Metadata Manager Service utilize almost 70 percent of the CPU. Metadata Manager does not map the source qualifier tables that have the owner name field specified in a mapplet to the database tables in the lineage diagram for a PowerCenter resource. After an upgrade to 8.6.1 HotFix 3, Metadata Manager cannot load a Business Objects resource into the Metadata Manager warehouse. Metadata Manager does not display the lineage diagram correctly for PowerCenter sources in a versioned repository that have a SQL Override in the source qualifier.
206604 205610 204953
204942
204507
PC_RLN_861011_0002
-41-
203396
Metadata Manager cannot extract all the models for a Cognos ReportNet resource because of a Java NULL Pointer error. Metadata Manager cannot load a Business Objects resource into the Metadata Manager warehouse because the Metadata Manager Agent extracts NULL values for the input model. The Metadata Manager application on an open browser times out after 12 hours.
202887
200743

CR 202127 Description The Reporting Service times out when it takes longer than four seconds to connect to the source database.

CR 205925 Description You cannot specify the ID field to use for an upsert operation on a Salesforce target object. For more information, see PowerExchange for Salesforce.com 8.6.1 HotFix 5 Fixes Affecting Functionality.
PowerExchange for Teradata Parallel Transporter 8.6.1 HotFix 5 Fixed Limitations

CR 205029 Description Teradata sessions fail if the Teradata decimal datatype has precision greater than 18.

Metadata Manager HotFix 5 Fixes Affecting Functionality

206834: You cannot use Metadata Manager in HTTPS mode with a keystore file password other than the default password, changeit. Previously, if you created the Metadata Manager Service in HTTPS mode with a keystore file password other than changeit, the Service Manager generated the following error:
java.io.IOException: Keystore was tampered with, or password was incorrect.
Effective in 8.6.1 HotFix 5, you can enter a password other than the default password when you create the Metadata Manager Service in HTTPS mode. You can also use the PowerCenter Administration Console to change the password after you create a Metadata Manager Service.
-42-
PC_RLN_861011_0002
PowerExchange for Salesforce.com 8.6.1 HotFix 5 Fixes Affecting Functionality

205925: You cannot specify the ID field to use for an upsert operation on a Salesforce target object A Salesforce target object may have multiple external ID or Idlookup fields. Previously, when you configured a session to upsert records into a Salesforce target, the Integration Service used the first external ID or Idlookup field to identify existing target records when performing an upsert operation. Effective 8.6.1 HotFix 5, you can specify the external ID or Idlookup field to use for the upsert operation. To use a particular ID field to upsert records into a Salesforce target object: 1. 2. 3. Double-click the session to open the session properties in the Edit Tasks window. Select the target. To use an external ID field, clear the Use Idlookup Field for Upserts option and enter the external ID field name in the Use this ExternalId/Idlookup Field for Upserts field. Note: If you do not enter the name of the external ID field, the Integration Service selects the first external ID field it encounters. If you specify a field that is not an external ID field or you misspell the field name, the session fails. 4. To use an Idlookup field, select the Use Idlookup Field for Upserts option and enter the ID lookup field name in the Use this ExternalId/Idlookup Field for Upserts field. Note: If you do not enter the name of the Idlookup field, the Integration Service selects the first Idlookup field it encounters. If you specify a field that is not an Idlookup field or you misspell the field name, the session fails. 5. 6. Click OK. Save the session.


CR 204756 Description The Integration Service runs previously completed workflows after its master service process fails over or restarts. The Integration Service shuts down unexpectedly when there is a broken connection to the Repository Service. The session fails when it is configured for full pushdown optimization to Teradata and the pushdown optimization casts strings to dates or dates to strings. The Integration Service truncates the long link condition between a session task and a worklet on a UTF-8 repository. The Data Transformation Manager process shuts down unexpectedly when processing data for a Lookup transformation.
204616
204551
204329
204299
PC_RLN_861011_0002
-43-
203956 203775
Library files packaged with PowerCenter conflict with other PowerCenter products. The Integration Service terminates a session enabled for recovery that ignores task resource requirements when distributing tasks across nodes of a grid. When the Web Services Hub calls a protected web service with an incorrect user name and password it does not return a meaningful error. See 203956. You cannot save an impacted non-reusable session from the Query Results window in the Repository Manager or with the pmrep Validate command. The XML Editor validates the large definition of the .xsd file but invalidates a simple mapping that contains the XML source definition. The pmcmd startworkflow command fails to start the workflow because the Integration Service truncates the value of the encrypted password stored in the environment variable. The powermart.dtd file is missing from Command Line Utilities installation directory. Cannot close socket connections between the gateway node and worker node. XML Parser session fails because it produces the same value for each run of a primary key column in an XML view.
202539
202225 201909
200848
200232
199436 198933 188851

CR 202181 Description Metadata Manager fails to load a Cognos ReportNet Content Manager resource.

CR 204516 Description The Administration Console displays an error message when you add a user to a group with Reporting Service privileges and data restrictions on operational tables.
PowerExchange for SAP Netweaver 8.6.1 HotFix 4 Fixed Limitations

CR 181111 Description SAP sessions configured to use key range partitioning extract data incorrectly from the SAP source.

-44-
PC_RLN_861011_0002

CR 203388 Description User authentication error occurs for the infacmd GetWorkflowLog command on 64-bit Linux because the read permissions set for a user in a group are not transferred to the user. The Integration Service shuts down unexpectedly when running sessions with Web Services Consumer transformations. The Repository Manager shuts down unexpectedly when you try to reconnect to the repository on 64-bit AIX. The Integration Service does not start the pre- and post-session command tasks on 32-bit HP UNIX. Real-time session that reads from a JMS source continues to run after encountering an error in a Stored Procedure transformation. The Integration Service shuts down unexpectedly on 64-bit Linux when the Performance Monitor checks CPU statistics. The Subsecond Precision property for a Lookup transformation changes when you export and import a mapping with the transformation into the Designer. The Integration Service cannot release an execution lock on a workflow while the Service Manager synchronizes the list of users and groups in the LDAP security domain. The Repository Manager imports the workflow but not the key range partition values. The Integration Service does not run workflows or does not complete workflow runs when it runs multiple concurrent tasks on AIX. When you select the Line Sequential File Format option for a fixed-width flat file, the Integration Service loads rows with multibyte characters that span two fields and does not write an error message to the session log. Multiple Integration Service processes shut down unexpectedly when you use the pmrep ObjectImport command. When there are multiple nodes in the domain, the Administrator Console displays an error message when you log in to a non-master gateway node and configure domain properties. PowerExchange ignores the values of the Application Name attribute in application connections for PowerExchange change data capture (CDC). A post-session command cannot read two environment variables that have the same names but different cases. Mapping Analyst for Excel does not detect the associated metamap when you import a mapping specification or export a mapping. For more information, see PowerCenter 8.6.1 HotFix 3 Fixes Affecting Functionality. 201506 201391 201098 The Integration Service shuts down unexpectedly when you run a debug session instance. The CONVERT_BASE function returns incorrect values for negative and zero values. If same name folders and objects are checked-out in two different repositories, checking in a folder and object in one repository causes the same name folder and object to be checked-in in the other repository. The Designer displays an error message when you use the Mapping Designer to check-out or check-in a
202978
202869 202816 202687
202521
202458
202366
202253 202113
202065
201937
201871
201863
201830
201697
201097
PC_RLN_861011_0002
-45-
mapping in a repository. 200964 200802 You cannot edit the sequence value for an XML Source Qualifier in the Designer. PowerCenter Services on Linux do not set the Xmx attribute for the INFA_JAVA_OPTS environment variable when you configure the variable from the command line. You cannot rename a shortcut that references a mapplet in a shared folder that is created by an administrator. Data Masking transformation does not allow substitution masking For more information, see PowerCenter Fixes Affecting Functionality. 188355 The Repository Manager shuts down unexpectedly when performing an advanced purge for active objects based on criteria. The Workflow Monitor shuts down unexpectedly and the pre- and post-session variable assignments are not removed when you convert a non-resuable session to a reusable session.
193951
192172
184746

CR 201558 Description Metadata Manager cannot extract all universes for a Business Objects resource and all models for a Cognos ReportNet Content Manager resource. For more information, see Metadata Manager 8.6.1 HotFix 3 Fixes Affecting Functionality. 201487 200979 Metadata Manager displays an error message when you assign an RTM Table to a Business Term. Metadata Manager displays an incorrect lineage diagram for a PowerCenter resource because the resource was loaded into the Metadata Manager warehouse with errors.

CR 189707 Description The Reporting Service is not enabled when HTTPS is configured on 64-bit AIX.
Reference Table Manager 8.6.1 HotFix 3 Fixed Limitations

CR 200930 Description Unable to use wildcard characters to search data in reference tables. For more information, see Reference Table Manager 8.6.1 HotFix 3 Fixes Affecting Functionality.
-46-
PC_RLN_861011_0002

CR 201715 Description The REQUIRED_FIELD_MISSING error appears when the task is configured for an upsert operation and the Integration Service tries to insert a record with master-detail relationship fields into a Salesforce target.

CR 199564 Description The Integration Service truncates high precision CURR, DEC, NUMC, and QUAN data in an SAP/ALE IDoc Interpreter transformation. For more information, see PowerExchange for SAP Netweaver 8.6.1 HotFix 3 Fixes Affecting Functionality.
PowerExchange for WebSphere MQ 8.6.1 HotFix 3 Fixed Limitations

CR 202574 Description When you set the Destructive Read option with a filter condition on a WebSphere MQ message header, the messages are filtered but not deleted from the source queue.

PowerCenter 8.6.1 HotFix 3 Fixes Affecting Functionality

201697: Mapping Analyst for Excel does not detect the associated metamap when you import a mapping specification or export a mapping Effective in version 8.6.1 HotFix 3, Mapping Analyst for Excel detects the associated metamap when you import a mapping specification or export a mapping. This fix includes the following changed functionality: Import options Export options Custom file naming conventions and storage location Matching criteria for custom metamaps Import Options When you import a mapping specification, you select the mapping specification file to import. Mapping Analyst for Excel detects the associated metamap for the mapping specification. Previously, when you imported a mapping specification, you selected the mapping specification file to import and the XML version of the associated metamap.
PC_RLN_861011_0002
-47-
Export Options The following options are new in the Microsoft Office Excel Options page of the Metadata Export Wizard:
Microsoft Excel Option Operation Description Type of export operation to perform. Select one of the following options: - Create. Exports all metadata to a new or an existing mapping specification. - Update Sources. Exports source metadata to an existing mapping specification. - Update Targets. Exports target metadata to an existing mapping specification. Default is Create. Format Format name of the metamap associated with the mapping specification template you want to use. Enter one of the following metamap values: - MappingTemplate - MappingTemplate_NoValidation - source-target-matrix - <custom-metamap-format-name>. For example, if the metamap is named MyCustom-MetaMap.xml, enter MyCustom. If you do not enter a format, Mapping Analyst for Excel uses the Default format that specifies Default-MetaMap.xml.
The Format export option replaces the following deprecated options in the Microsoft Office Excel Options page of the Metadata Export Wizard:
Microsoft Excel Option With metadata mapping spreadsheet Description Metamap associated with the mapping specification template you want to use. Valid values included: - MappingTemplate-MetaMap.xml - source-target-matrix-metamap.xml - <custom-metamap>.xml From base spreadsheet Mapping specification template. Valid values included: - MappingTemplate.xls - MappingTemplate_NoValidation.xls - source-target-matrix-mirrepeatingsheet.xls - <custom-template>.xls
Custom File Naming Conventions and Storage Location Custom Mapping Analyst for Excel files use the following naming conventions:
File Custom metamap 8.6.1 HotFix 3 Naming Convention <format-name>-MetaMap.xml For example, MyCustom-MetaMap.xml is a valid metamap name. <format-name> must match <format-name> of the associated blank version of the custom mapping Previous Naming Convention none
-48-
PC_RLN_861011_0002
specification template. Blank version of custom mapping specification template <format-name>-Blank.xls For example, MyCustom-Blank.xls is a valid name for the blank version of a custom mapping specification template. <formatname> must match <format-name> of the associated metamap. source-target-matrix-Blank.xls source-target-matrix-mirrepeatingsheet.xls none
Source-Target-Matrix repeating sheet file
These custom files are stored in the following location:

<PowerCenter installation directory>\client\bin\mimb\conf\ MIRModelBridgeTemplate\MIRMicrosoftExcel
Previously, these files were stored in the following location:

<PowerCenter installation directory>\client\bin\Sample Specifications
After you apply 8.6.1 HotFix 3, rename custom metamaps and create blank versions of custom mapping specification templates using the naming conventions. Copy the custom files to the following location:
<PowerCenter installation directory>\client\bin\mimb\conf\ MIRModelBridgeTemplate\MIRMicrosoftExcel
Then, associate the custom metamap with the new name of the blank version of the mapping specification template to maintain the metamap links to the mapping specification template. Matching Criteria for Custom Metamaps The Overview worksheet in a metamap contains a Match Criteria section. This section contains references to several cells in the associated mapping specification template. When you import a mapping specification or export a mapping, Mapping Analyst for Excel uses the Match Criteria section to detect the associated metamap for the mapping specification. When you create a custom metamap, you must edit the Match Criteria section to use matching criteria that uniquely identifies the associated mapping specification template. You can use up to five matching criteria. The Match Criteria section includes the following parameters:
Parameter Spreadsheet Match Criteria Description Name of the matching criteria. For example, you can enter the name of the worksheet and identifying cell in the mapping specification template. Contents of the identifying cell in the mapping specification template. Enter the name of the cell in the mapping specification template. Contains the location of the identifying cell in the mapping specification template. Copy and paste the cell location from the mapping specification template.
Contents
Link
Previously, a metamap Overview worksheet did not contain a Match Criteria section. When you imported a mapping specification or exported a mapping, you selected the correct mapping specification template and associated metamap. 192172: Data Masking transformation does not allow substitution masking Effective in version 8.6.1 HotFix 3, you can configure substitution masking in the Data Masking transformation. You can also configure repeatable expression masking.
PC_RLN_861011_0002
-49-
Substitution You can configure substitution masking in a Data Masking transformation. Substitution masking replaces a column of data with similar but unrelated data. You can use substitution masking instead of a Lookup transformation to retrieve substitute values. When you configure substitution masking, define the relational table or flat file dictionary that contains the substitute values. The Data Masking transformation performs a lookup on the dictionary that you configure. The Data Masking transformation replaces source data with data from the dictionary file. You can substitute data with repeatable or non-repeatable values. When you choose repeatable values, the Data Masking transformation produces deterministic unique results for the same source data and seed value. The Data Masking transformation requires a seed value to substitute data with deterministic results. Dictionary Files When you configure Data Masking substitution, define a dictionary file that contains the substitute data. A dictionary is a flat file or relational table that contains the substitute data and a serial number for each row in the dictionary. The Integration Service generates a number to retrieve a dictionary row by the serial number. The Integration Service generates a hash key for repeatable substitution masking or a random number for non-repeatable masking. You can configure an additional lookup condition if you configure repeatable substitution masking. You can configure a dictionary to mask more than one port in the Data Masking transformation. The following example shows a flat file dictionary that contains first name and gender:
SNO,GENDER,FIRSTNAME 1,M,Adam 2,M,Adeel 3,M,Adil 4,F,Alice 5,F,Alison
In this dictionary, the first field in the row is the serial number, and the second field is gender. The Integration Service always looks up a dictionary record by serial number. You can add gender as a lookup condition if you configure repeatable masking. The Integration Service retrieves a row from the dictionary using a hash key and it finds a row with a gender that matches the gender in the source data. Use the following rules and guidelines when you create a dictionary: Each record in the dictionary must have a serial number. The serial number does not have to be the key in a relational table. The serial numbers are sequential integers starting at one. The serial numbers cannot have a missing number in the sequence. The serial number column can be anywhere in a dictionary row. It can have any label. The first row of a flat file dictionary must have column labels to identify the fields in each record. The fields are separated by commas. If the first row does not contain column labels, the Integration Service takes the values of the fields in the first row as column names. A flat file dictionary must be in the following location: <PowerCenter_Installation_Directory>\server\infa_shared\LkpFiles If you create a flat file dictionary on Windows and copy it to a UNIX machine, verify that the file format is correct for UNIX. For example, Windows and UNIX mark end of line differently. If you configure substitution masking for more than one port, all dictionaries that are relational tables should be in the same database schema. You cannot change the dictionary type or the substitution dictionary file name in session properties. Storage Tables
-50-
PC_RLN_861011_0002
The Data Masking transformation maintains storage tables for repeatable substitution between sessions. A storage table row contains the source column and a masked value pair. Each time the Integration Service masks a value with a repeatable substitute value, it searches the storage table by dictionary name, locale, column name, input value, and seed. If it finds a row, it returns the masked value from the storage table to the Data Masking transformation. If the Integration Service does not find a row, it generates a hash key for repeatable masking or a random number for non-repeatable masking. It retrieves a row from the dictionary with the hash key or random number. The dictionary name for a flat file dictionary is the file name. The dictionary name for a relational table dictionary in the storage table has the following format: <PowerCenter connection object>_<dictionary table name>. You can create a table in a different database if you configure the SQL statements and the primary key constraints. If the storage table does not exist, and the Data Masking transformation is configured for repeatable substitution masking, the session fails. Substitution Masking Properties The following table describes the fields for substitution masking in the Data Masking Properties tab:
Masking Property Repeatable output Description Returns deterministic results between sessions. The Integration Service saves masked values in the storage table. - Seed. Apply a seed value to generate deterministic masked data for a column. - Value. Accept the default seed value or enter a number between 1 and 1,000. - Mapping Parameter. Use a mapping parameter to define the seed value. The Designer displays a list of the mapping parameters that you create for the mapping. Choose the mapping parameter from the list to use as the seed value. Flat File Relational Table Dictionary Name Lookup column Return value Lookup condition Indicates that the dictionary is a comma-delimited flat file. Indicates that the dictionary is relational. Displays the flat file or relational table name that you selected. Select the column in the dictionary file that contains the serial number. The dictionary column to return to the Data Masking transformation. Qualifies the dictionary row to use for substitution masking. The lookup condition is similar to the WHERE clause in an SQL query. When you configure a lookup condition you compare the value of a column in the source with a column in the dictionary file. For example, you want to mask the first name. The source data and the dictionary have a first name column and a gender column. You can add a condition that each female first name is replaced with a female name from the dictionary. The lookup condition compares gender in the source to gender in the dictionary. - Input column. Source data column to use in the lookup. - Dictionary column. Dictionary column to compare the input port to.
Relational Dictionary When you choose a relational table as a dictionary, configure the database table that contains the dictionary file. When you define the table, the Designer uses ODBC to connect to the table and display the columns in the file.
PC_RLN_861011_0002
-51-
To select a database, click Select Table on the Data Masking transformation Masking Properties tab. The Select Table dialog box appears. The following table describes the fields in the Select Table dialog box:
Field ODBC Data Source User Name Description ODBC data source that connects to the database that contains the dictionary. A database user name to connect to the database. The user name must have the database permissions to view the tables. Owner name for the database tables. The password for the database user name. Limits the number of tables that appear in the dialog box.
Owner Name Password Search for tables named
When you click Connect, the Designer connects to the database and displays the tables. Scroll through the list of tables and select a table you want to use for a dictionary. The table name appears in the Dictionary Name field of the Masking Properties tab. Connection Requirements You must configure a database connection for the storage table and the dictionary table if you use them with substitution masking. If you do not configure each connection, the session fails. Configure the database connections in the Workflow Manager. Configure the IDM_Dictionary connection and the IDM_Storage connection on the Mapping tab of the session properties. Rules and Guidelines Use the following rules and guidelines for substitution masking: If a storage table does not exist for a repeatable substitution mask, the session fails. If the dictionary contains no rows, the Integration Service returns default mask values. If you delete a connection object or modify the dictionary, truncate the storage table. When the Integration Service finds an input value with the locale, dictionary, and seed in the storage table, it retrieves the mask value, even if the row is no longer in the dictionary file. If the number of values in the dictionary file is less than the number of unique values in the source data, the Integration Service cannot mask the data with unique repeatable values. The Integration Service returns default mask values. Repeatable Expression Masking You can configure repeatable expression masking. Use repeatable expression mapping when a source column occurs in more than one table and you need to mask the column from each table with the same value. When you configure repeatable expression masking, the Integration Service saves the results of an expression in a storage table. If the same column value occurs in another source table, the Integration Service returns the mask value from the storage table instead of from the expression. Dictionary Name When you configure repeatable expression masking you must enter a dictionary name. The dictionary name is a key that allows multiple Data Masking transformations to generate the same mask values from the same source values. Define the same dictionary name in each Data Masking transformation. The dictionary name can be any text.
-52-
PC_RLN_861011_0002
Storage Table The Data Masking transformation maintains a storage table for repeatable expression masking between sessions. A storage table row contains the source column and a masked value pair. The storage table for expression masking is a separate table from the storage table for substitution masking. Each time the Integration Service masks a value with a repeatable expression, it searches the storage table by dictionary name, locale, column name and input value. If it finds a row in the storage table, it returns the masked value from the storage table to the Data Masking transformation. If the Integration Service does not find a row, it generates a mask value from the expression for the column. Example For example, you have an Employees table that contains the following columns:
FirstName LastName LoginID
In the Data Masking transformation, mask LoginID with an expression that combines FirstName and LastName. Configure the expression mask to be repeatable. Enter a dictionary name as a key for repeatable masking. The Computer_Users table contains a LoginID, but no FirstName or LastName columns:
Dept LoginID Password
To mask the LoginID in Computer_Users with the same LoginID as Employees, configure expression masking for the LoginID column. Enable repeatable masking and enter the same dictionary name that you defined for the LoginID Employees table. The Integration Service retrieves the LoginID values from the storage table. Create a default expression to use when the Integration Service cannot find a row in the storage table for LoginID. The Computer_Users table does not have the FirstName or LastName columns, so the expression creates less meaningful LoginID. Storage Table Scripts Informatica provides scripts that you can run to create the storage table. The scripts are located in the following directory:
<PowerCenter installation directory>\client\bin\Extensions\DataMasking
The DataMasking directory contains a script for Sybase, Microsoft SQL Server, IBM DB2, and Oracle databases. Each script is named Expression_<database type>. Rules and Guidelines You cannot use the output from one expression as input to another expression. If you manually add the output port name to the expression, you might get unexpected results. Use the point-and-click method to minimize errors when you build expressions. When you create an expression, verify that the expression returns a value that matches the port datatype. The Expression Editor does not validate that the return datatype is valid for the port. The Data Masking transformation returns zero if the datatype of the expression port is numeric and the datatype of the expression is not the same. The Data Masking transformation returns null values if the datatype of the expression port is a string and the data type of the expression is not the same. If the Data Masking transformation is configured for repeatable masking, and the storage table does not exist, the session fails.
PC_RLN_861011_0002
-53-

201558: Metadata Manager cannot extract all universes for a Business Objects resource and all models for a Cognos ReportNet Content Manager resource Metadata Manager cannot extract all universes for a Business Objects resource and all models for a Cognos ReportNet Content Manager resource after you load the resources into the Metadata Manager warehouse. New Options to Extract Metadata Effective in PowerCenter 8.6.1 HotFix 3, you can extract all universes from a Business Objects resource and all models from a Cognos ReportNet Content Manager resource when you load the resources into the Metadata Manager warehouse. In the Parameter tab for the Business Objects resource, select Extract metadata from all universes or Extract metadata from selected universes. Select Extract metadata from all universes to extract metadata from all Business Objects universes. Select Extract metadata from selected universes to extract metadata from select Business Objects universes. In the Parameter tab for the Cognos ReportNet Content Manager resource, select Extract metadata from all models or Extract metadata from selected models. Select Extract metadata from all models to extract metadata from all Cognos ReportNet Content Manager models. Select Extract metadata from selected models to extract metadata from select Cognos ReportNet Content Manager models.
PowerExchange for SAP Netweaver 8.6.1 HotFix 3 Fixes Affecting Functionality

198700: Integration Service truncates high precision CURR, DEC, NUMC, and QUAN data in an SAP/ALE IDoc Interpreter transformation In the SAP/ALE IDoc Interpreter transformation, CURR, DEC, NUMC, and QUAN datatypes display a precision of 15 but allow a precision up to 18. When a session containing CURR, DEC, NUMC or QUAN data in an SAP/ALE IDoc Interpreter transformation is configured for high-precision, the Integration Service allows a maximum precision of 18 and rounds data with a precision over 18. When a session is not configured for high precision, the Integration Service rounds data with a precision over 15. Regenerate Mappings and Transformations Effective in PowerCenter 8.6.1 HotFix 3, the SAP/ALE IDoc Interpreter transformation handles CURR, DEC, NUMC, and QUAN data up to the maximum precision of 28 and the SAP/ALE IDoc Interpreter transformation displays the correct precision. To display the correct precision and process high-precision data correctly, regenerate Business Content Integration processing mappings that include CURR, DEC, NUMC, or QUAN data with a precision greater than 15 in an SAP/ALE IDoc Interpreter transformation. For other mappings that round data because of an SAP/ALE IDoc Interpreter transformation, recreate the transformation.
Reference Table Manager 8.6.1 HotFix 3 Fixes Affecting Functionality

200930: Unable to use wildcard characters to search data in reference tables Reference Table Manager does not allow use of wildcard characters to search for patterns within data in the reference tables.
-54-
PC_RLN_861011_0002
Wildcard Search Functionality Effective in PowerCenter 8.6.1 HotFix 3, you can use the wildcard search functionality to search columns of string data in reference tables. You can specify the wildcard character % as the first, last, or first and last character in a search query. For example, use %ca% to search for following strings: Jamaica, Canada, and Madagascar. The updated search functionality affects the following features in the Reference Table Manager: Find, Highlight All, Replace, and Replace All.


CR 200931 200886 Description Reference Table Manager does not sort on table names. The Integration Service does not write error messages to the session log for lookups that are not resilient to database connections. Lookup is not resilient to IBM DB2 database errors in real-time change data capture workflows. Lookup is slow to reconnect to the IBM DB2 database. When you create a PowerCenter domain using a DNS alias, the Administration Console cannot generate node diagnostics. The Repository Manager displays an incorrect message when you apply a label to a shortcut object. Mapping Architect for Visio fails to import a mapping with a Teradata source or target that has a Date column. The Integration Service restarts a concurrent workflow with multiple sessions as a normal workflow when you restart a session from the Workflow Monitor. The Integration Service does not send or receive MSMQ messages to a remote private queue. For more information, see PowerCenter 8.6.1 HotFix 2 Fixes Affecting Functionality.
200884 200882 200829
200546 200485
198805
198698

CR 200995 200989 Description Metadata Manager sessions hang when extracting lineage information from a PowerCenter resource. Metadata Manager fails the profiling task for Teradata tables containing decimal columns.
PC_RLN_861011_0002
-55-

CR 198293 Description Enabling a Reporting Service that is configured with a Metadata Manager Service corrupts the Data Analyzer repository.

PowerCenter 8.6.1 HotFix 2 Fixes Affecting Functionality

198698: The Integration Service does not send or receive MSMQ messages to a remote private queue When a session writes to a remote private MSMQ queue, the Integration Service cannot determine whether the queue is transactional or not. New MSMQ Connection Object Attribute Effective in PowerCenter 8.6.1 HotFix 2, you can configure whether the MSMQ queue is transactional or not. Configure the Is Transactional connection attribute in the connection object. Select Yes, No, or Auto. When the queue is local or not private, you can choose Auto. The Integration Service determines if the queue is transactional or not. When the queue is a remote private queue, you must configure Is Transactional to match the queue configuration.


CR 199689 199481 Description The Integration Service on Linux shuts down unexpectedly. The reference fields in a Router transformation are incorrectly copied when you copy the transformation in the deployment group to the target repository. Memory peak on a gateway or worker node causes the PowerCenter domain, PowerCenter Services, and the Administration Console to hang. Cannot close socket connections between the gateway node and worker node. Session that has the Bigint datatype as the partition key for database partitioning does not load correct data to an IBM DB2 target. The INFA_OutputSessionLogMsg function in the Session Log Interface sometimes passes 0 for the curTime parameter instead of the current time.
199323
198933 198908
198904
-56-
PC_RLN_861011_0002
198861 198850
Real-time web service mappings are not resilient to IBM DB2 lookups. A warning message for an invalid connection object owner appears when copying a deployment group that has connection objects to a target repository. The Repository Manager cannot copy folders between a global repository and a local repository or between local repositories when the repositories are in different domains. The Integration Service fails sessions that use external loaders to load data to Sybase IQ targets and causes the external loader to create database table locks. Session fails when you restart a worklet in a concurrent workflow. Users cannot connect to the repository after a failover. The session does not commit the last transaction to the lookup source when you synchronize dynamic cache with the lookup source. Teradata and Teradata FastExport sessions generate different SQL statements for mappings with sorted ports and a source filter in the Source Qualifier. XML primary key values are not maintained when you deploy mappings that contain XML Parser transformations. A name conflict occurs when you copy a deployment group that has a global shortcut to a target repository. The Designer takes a long time to save a mapping that contains a user-defined function. The Administration Console displays two different error messages for an incorrect user name or password. The Service Manager cannot run the infacmd GetWorkflowLog command when the user is not an administrator. When the Integration Service loads multibyte source data with the EBCDIC Japanese or SJIS Japanese code pages, it writes inconsistent data to the target. Service Manager memory leak occurs when a Repository Service process shuts down unexpectedly on a domain that runs without the High Availability option. Session fails when loading data in bulk mode for IBM DB2.
198823
198815
198802 198645 198487
198365
198359
198355 198244 197993 197842
197133
197051
179069

CR 198343 Description Metadata Manager does not display the Body property for an Oracle Procedure if the user who configured the resource is not the owner of the Oracle Procedure. Metadata Manager cannot import a mapping generated by the Custom Metadata Configurator and cannot import the resource into the Metadata Manager warehouse. Sessions that profile IBM DB2 for z/OS source data fail when the pmrep CreateConnection command is used to create a connection for the IBM DB2 for z/OS source. Metadata Manager profiles all the tables in multiple Oracle schemas that are selected to create an Oracle resource.
198207
198160
195992
PC_RLN_861011_0002
-57-
194798 192741
Metadata Manager catalog displays logical groups that do not contain any objects. Session that deletes a Teradata resource from the Metadata Manager warehouse takes a long time.

CR 199084 198938 Description The Integration Service shuts down unexpectedly for IDoc Interpreter transformation sessions. Session with a SAP Source Qualifer, which uses a static filter to access a parameter file, does not pass any data from the SAP source. Japanese characters are not displayed in the description field of an IDoc source definition when you import it to create an IDoc Interpreter or an IDoc Prepare transformation. An IDoc Listener session that receives SAP source data keeps running past the value set for the Idle Time session property.
198712
196532
PowerExchange for Web Services 8.6.1 HotFix 1 Fixed Limitations

CR 198322 Description The Web Services Hub does not process SOAP fault messages for WSDL files with RPC encoding.

PowerExchange for Web Services 8.6.1 HotFix 1 Fixes Affecting Functionality

199160, 199553: You cannot set the keystore password when you create a Web Services Hub in HTTPS mode When you create a secure Web Services Hub, you cannot specify the password for the keystore file. The Web Services Hub uses the default password for the keystore file. If you use a keystore file with a different password, the Web Services Hub Console does not display correctly. New Web Services Hub Property Effective in version 8.6.1 HotFix 1, you can specify the password for the keystore file when you create a Web Services Hub running in HTTPS mode. When you create the Web Services Hub in the Administration Console, specify the password for the keystore file in the KeystorePass property. The value of the KeystorePass property must match the password of the keystore file. If you change the password of the keystore file, change the value of the KeystorePass property in the Administration Console.
-58-
PC_RLN_861011_0002
When you apply 8.6.1 HotFix 1, the value of the KeystorePass property of existing Web Services Hubs is null. In the Administration Console, the null password displays ***. The existing secure Web Services Hubs use the default password changeit for the keystore files. If you change the password of the keystore file associated with an existing secure Web Services Hub, change the value of the KeystorePass property to match the new password. Limitations This fix has the following limitations: The KeystorePass property is not available in the createWSHubService command of the infacmd command line program. When you use the createWSHubService command to create a Web Services Hub, you cannot specify the value for the keystore password. (199555) When you create the keystore file for a secure Web Services Hub, you must specify the same value for the public and private keys. If you use different public and private keys, you cannot connect to the Web Services Hub Console. (199801) PowerExchange for Web Services sessions can access PowerCenter web services running on a secure Web Services Hub with a default keystore password. The sessions fail if they access PowerCenter web services running on a secure Web Services Hub that uses a different keystore password. (199812) 199300: You cannot define a JMS target with a static destination name. You cannot run a JMS session in Transacted mode The Integration Service creates a JMS target with a null destination name. The Integration Service passes the destination name to the JMS target at run time. You cannot define a JMS target with a fixed destination name. JMS runs in Transacted or Non-transacted mode. When you run a JMS session in PowerCenter, you must use Non-Transacted mode. Static or Dynamic JMS Destination Name Effective in version 8.6.1 HotFix 1, you can configure a JMS target with a static or dynamic destination name. When you configure a JMS target with a static destination name, the Integration Service creates the JMS target with the destination name from the JMS application connection. The Integration Service sends all messages to that destination. If you configure a static destination name, do not project the JMSDestination name port in the JMS target. When you configure a JMS target with a dynamic destination name, the JMS target receives the destination name in the JMSDestination port at run time. The destination name is passed to the JMS target with other JMS header data. The destination name is dynamic by default. Configure IsDestinationNameDynamic on the Mapping tab for a JMS session. Click JMSWriter in the left panel. Updated JMS targets have IsDestinationNameDynamic enabled by default. Transacted Mode for JMS Sources Effective in version 8.6.1 HotFix 1, you can configure a JMS session to run in Transacted or NonTransacted mode. When you configure a JMS session to run in Transacted mode, the Integration Service receives and processes a group of messages as a transaction. The Integration Service acknowledges all the messages by committing the transaction. If a transaction rolls back, the JMS provider redelivers all the messages to the Integration Service. When you configure a JMS session to run in Non-Transacted mode, the Integration Service uses the CLIENT_ACKNOWLEDGE method to acknowledge messages. When the Integration Service acknowledges one message in the JMS session, then all the messages are acknowledged by default. PowerCenter JMS sessions run in Non-Transacted mode by default.
PC_RLN_861011_0002
-59-
Configure Transacted mode for JMS sessions on the Mapping tab for a JMS session. Click SQ_JMSReader in the left panel. Updated JMS sources have Transacted mode disabled by default. Limitations Data loss may occur if you enable Transacted mode for a SONIC JMS source in a multi-partitioned session.
8.6.1 Fixed Limitations

PowerCenter 8.6.1 Fixed Limitations

CR 195909 195540 Description The Repository Service logs invalid request errors when no errors occurred. The Asset Management Report PDF cannot display the Repository Service name that has Unicode characters. An administrator cannot send the Asset Management Report in an email from the Administration Console on LINUX 32-bit. infacmd AddGroupPrivilege command causes the domain to hang if certain services are running. 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. The XML Generator transformation returns restricted characters that result in an invalid XML document. User without read permission on a shared query can use the query to create a dynamic deployment group. A calendar does not appear in the Search options of the Administration Console Logs tab when the Administration Console runs on a node that uses a non-English version of Windows. Exporting a mapping to a mapping specification file can result in incorrect function definitions. Session terminates while running an Unstructured Data transformation on AIX. IBM DB2 EE external loader sessions fails on AIX 32-bit with error SQLCODE:-3016. Integration Service run-time file location, backup directory, and keystore file location not updated after you run the installer. Workflow log displays execution lock message when sessions fail. Incorrect ODBC library names in odbc.ini for DataDirect 5.2 ODBC drivers. Cannot upgrade a repository from PowerCenter 8.1.1 configured for LDAP authentication on Windows 64-bit. You can assign a license to multiple Repository Services when the license is valid for one Repository Service. The Integration Service does not correctly write data to Teradata targets.
194792
194286 193940
193450 193400
191701
190038 188726 188051 188020
187945 187899 187572
187473
187375
-60-
PC_RLN_861011_0002
187080
When you import an XML source definition, the Designer displays simple type elements as complex type. Mapping Architect for Visio launches but does not generate mappings if current version is not installed. A web services workflow becomes unresponsive after startup when it is configured to run on a single hub and the run count is one. Workflow Monitor displays incorrect session and workflow status. After you run the installer, an error appears the first time you launch Mapping Architect for Visio. See 186612. An unconnected Stored Procedure transformation is not returning output values in input/output ports. An exception occurs when you recalculate the CPU profile for a node that runs on a Windows EM64T (64-bit) or Windows IA (64-bit) operating system Session with an Unstructured Data transformation fails if the Data Transformation Service uses the LearnByExample function. Cannot view or run object query in Query Browser without read permission. Real-time session with partitioned JMS or WebSphere MQ source and relational target fails with database error. If you specify an Xpath query predicate and the output rows for the group span across multiple buffer blocks, the XML reader might not process the rows. Recovery session fails when processing incomplete or corrupted GMD storage cache files after Integration Service failover. DTM process shuts down unexpectedly when a session includes a flat file source with large row size. Importing a large WSDL file causes the Designer to shut down unexpectedly. See 187572. When you import a web service source or target definition from a WSDL in entity relationship mode and the input and output messages for the selected operation are the same, the XML views created in the source or target definition do not contain the correct ports. Unable to open Mapping Architect for Visio when you log in to PowerCenter Client with a different user name and password. Recovery session passes an incorrect variable port value in the first row of data on Linux 64-bit. The installer fails to connect to the domain configuration database when the password contains dollar sign ($) characters. Links to a port in a target definition fail to import when column name is changed in the target definition. Session with incremental aggregation fails with an unexpected condition. Log messages saved from the output window of PowerCenter client are not in a readable format. XML parser performance slows after upgrading from 8.1.1 and previous versions on Solaris 32 bit. DTM process generates a core file when line sequential buffer length is greater than 27,750,000 bytes.
187030 186924
186612 186405 186354 186277 186153
185500
185460 185250
184862
184841
183582 181614 180240 177382
176290
174760 172303
135022 131912 130901 108493 104029
PC_RLN_861011_0002
-61-
Metadata Manager 8.6.1 Fixed Limitations

CR 185933 184484 Description Scrolling through a large set of search results can cause timeout. Metadata Manager exports custom metadata objects where the name has an ampersand (&) to an XML file.
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 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 Spain and Portugal: +34 93 480 3760 United Kingdom: +44 1628 511 445
-62-
PC_RLN_861011_0002

PC 861 HotFix11

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

PC 861 HotFix11

Uploaded by

Copyright:

Available Formats

Informatica Corporation PowerCenter Version 8.6.

1 HotFix 11 Release Notes

Complete the Pre-Installation Tasks

Edit the Properties File (Silent Mode)

Save the properties file.

Apply the PowerCenter Services HotFix

Complete the Post-Installation Tasks

Cold Start PowerExchange CDC Sessions

Configure Operating System Profiles on UNIX

Configure Metadata Manager

The upgradeMetamodel utility is located in the following directory:

The upgradeMetamodel utility is located in the following directory:

If you are upgrading from

Reload all resources of these resource types

HotFix 8 or earlier HotFix 9 HotFix 10

Configure Data Masking

Update the PowerCenter Repository for Data Masking

Update the PowerCenter Repository for JMS

Update the PowerCenter Repository for SAP NetWeaver

Update the PowerCenter Repository for Web Services

Upgrade the Contents of the Reference Table Manager Repository

Apply the PowerCenter Client HotFix

Complete the PowerCenter Client Post-Installation Tasks

Authorization Check on SAP ABAP Programs

Transports for SAP Unicode Versions 4.7 and Higher

Press Enter. Request dialog box appears.

Cold Start PowerExchange CDC Sessions

Custom File Naming Conventions and Storage Location

Matching Criteria for Custom Metamaps

Roll Back the HotFix

8.6.1 HotFix 11 Fixed Limitations

PowerCenter 8.6.1 HotFix 11 Fixed Limitations

229124 228909 228824 228675 228637

228046 227627 227410 227403 227239

220180 219612 218632

Metadata Manager 8.6.1 HotFix 11 Fixed Limitations

Data Analyzer 8.6.1 HotFix 11 Fixed Limitations

PowerExchange for Salesforce.com 8.6.1 HotFix 11 Fixed Limitations

PowerExchange for SAP NetWeaver 8.6.1 HotFix 11 Fixed Limitations

8.6.1 HotFix 11 Documentation Updates

PowerCenter Administrator Guide

PowerCenter Advanced Workflow Guide

PowerCenter Command Reference

The following table describes infacmd ListGroupsForUser options and arguments:

-SecurityDomain -sdn -Gateway -hp -ResilienceTimeout -re

Infacmd isp Command Reference

PowerCenter Configuration Guide

PowerCenter Release Guide

Chapter 5: PowerCenter Domains

Chapter 18: Metadata Manager

Chapter 19: PowerExchange (PowerCenter Connect)

PowerCenter Transformation Language Reference

PowerCenter XML Guide

Metadata Manager Administrator Guide

Chapter 3: Creating Resources

Chapter 4: Managing Resources

Appendix B: Resource Reference

Metadata Manager User Guide

8.6.1 HotFix 11 Known Limitations

PowerCenter 8.6.1 HotFix 11 Known Limitations

Metadata Manager 8.6.1 HotFix 11 Known Limitations

B2B 8.6.1 HotFix 11 Known Limitations