PowerCenter®
Version 8.6.1 HotFix 13
Release Notes
October 2010
Copyright 1998-2010 Informatica Corporation
This document contains important information about the fixed limitations included in 8.6.1 HotFix 13 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.................................................................................................... 5
Complete the Post-Installation Tasks ......................................................................................................... 5
Apply the PowerCenter Client HotFix ..................................................................................................... 11
Complete the PowerCenter Client Post-Installation Tasks....................................................................... 11
Roll Back the HotFix.................................................................................................................................... 13
8.6.1 HotFix 13 Fixed Limitations ............................................................................................................... 13
PowerCenter 8.6.1 HotFix 13 Fixed Limitations...................................................................................... 13
Metadata Manager 8.6.1 HotFix 13 Fixed Limitations............................................................................. 15
PowerChannel 8.6.1 HotFix 13 Fixed Limitations ................................................................................... 16
PowerExchange for Web Services 8.6.1 HotFix 13 Fixed Limitations .................................................... 16
PowerExchange for JMS 8.6.1 HotFix 13 Fixed Limitations................................................................... 16
PowerExchange for SAP NetWeaver 8.6.1 HotFix 13 Fixed Limitations................................................ 16
8.6.1 HotFix 12 Fixed Limitations ............................................................................................................... 16
PowerCenter 8.6.1 HotFix 12 Fixed Limitations...................................................................................... 17
Metadata Manager 8.6.1 HotFix 12 Fixed Limitations............................................................................. 17
Data Analyzer 8.6.1 HotFix 12 Fixed Limitations ................................................................................... 18
PowerExchange for SAP NetWeaver 8.6.1 HotFix 12 Fixed Limitations................................................ 18
8.6.1 HotFix 12 Known Limitations............................................................................................................. 18
PowerCenter 8.6.1 HotFix 12 Known Limitations ................................................................................... 18
PowerExchange for SAP NetWeaver 8.6.1 HotFix 12 Known Limitations ............................................. 19
8.6.1 HotFix 12 Documentation Updates ..................................................................................................... 19
PowerCenter Release Guide ..................................................................................................................... 19
8.6.1 HotFix 11 Fixed Limitations ............................................................................................................... 19
PowerCenter 8.6.1 HotFix 11 Fixed Limitations...................................................................................... 19
Metadata Manager 8.6.1 HotFix 11 Fixed Limitations............................................................................. 22
Data Analyzer 8.6.1 HotFix 11 Fixed Limitations ................................................................................... 23
PowerExchange for Salesforce.com 8.6.1 HotFix 11 Fixed Limitations.................................................. 23
PowerExchange for SAP NetWeaver 8.6.1 HotFix 11 Fixed Limitations................................................ 23
8.6.1 HotFix 11 Documentation Updates ..................................................................................................... 23
PowerCenter Administrator Guide ........................................................................................................... 23
PowerCenter Advanced Workflow Guide ................................................................................................ 24
PowerCenter Command Reference .......................................................................................................... 24
Infacmd isp Command Reference ............................................................................................................ 25
PowerCenter Configuration Guide ........................................................................................................... 25
PowerCenter Release Guide ..................................................................................................................... 25
PowerCenter Transformation Language Reference.................................................................................. 26
PC_RLN_861013_0001 -1-
PowerCenter XML Guide......................................................................................................................... 27
Metadata Manager Administrator Guide .................................................................................................. 27
Metadata Manager User Guide................................................................................................................. 28
8.6.1 HotFix 11 Known Limitations............................................................................................................. 29
PowerCenter 8.6.1 HotFix 11 Known Limitations ................................................................................... 29
Metadata Manager 8.6.1 HotFix 11 Known Limitations.......................................................................... 29
B2B 8.6.1 HotFix 11 Known Limitations ................................................................................................ 30
8.6.1 HotFix 10 Fixed Limitations ............................................................................................................... 30
PowerCenter 8.6.1 HotFix 10 Fixed Limitations...................................................................................... 30
Metadata Manager 8.6.1 HotFix 10 Fixed Limitations............................................................................. 32
PowerExchange for SAP NetWeaver 8.6.1 HotFix 10 Fixed Limitations................................................ 32
PowerExchange for WebSphere MQ 8.6.1 HotFix 10 Fixed Limitations ................................................ 33
8.6.1 HotFix 10 Documentation Updates ..................................................................................................... 33
PowerCenter Administrator Guide ........................................................................................................... 33
PowerCenter Command Reference .......................................................................................................... 33
PowerCenter Designer Guide ................................................................................................................... 34
Metadata Manager Administrator Guide .................................................................................................. 34
Metadata Manager Business Glossary Guide ........................................................................................... 35
PowerCenter Release Guide ..................................................................................................................... 35
PowerExchange for WebSphere MQ User Guide .................................................................................... 36
8.6.1 HotFix 10 Known Limitations............................................................................................................. 37
PowerCenter 8.6.1 HotFix 10 Known Limitations ................................................................................... 37
8.6.1 HotFix 9 Fixed Limitations ................................................................................................................. 37
PowerCenter 8.6.1 HotFix 9 Fixed Limitations........................................................................................ 37
Metadata Manager 8.6.1 HotFix 9 Fixed Limitations............................................................................... 38
PowerExchange for SAP NetWeaver 8.6.1 HotFix 9 Fixed Limitations.................................................. 39
8.6.1 HotFix 9 Fixes Affecting Functionality............................................................................................... 39
Metadata Manager 8.6.1 HotFix 9 Fixes Affecting Functionality............................................................ 39
PowerExchange for SAP NetWeaver 8.6.1 HotFix 9 Fixes Affecting Functionality ............................... 40
8.6.1 HotFix 8 Fixed Limitations ................................................................................................................. 40
PowerCenter 8.6.1 HotFix 8 Fixed Limitations........................................................................................ 40
Metadata Manager 8.6.1 HotFix 8 Fixed Limitations............................................................................... 41
PowerExchange for JMS NetWeaver 8.6.1 HotFix 8 Fixed Limitations.................................................. 41
8.6.1 HotFix 8 Fixes Affecting Functionality............................................................................................... 41
Metadata Manager 8.6.1 HotFix 8 Fixes Affecting Functionality............................................................ 42
Reference Table Manager 8.6.1 HotFix 8 Fixes Affecting Functionality................................................. 42
8.6.1 HotFix 7 Fixed Limitations ................................................................................................................. 43
PowerCenter 8.6.1 HotFix 7 Fixed Limitations........................................................................................ 44
Metadata Manager 8.6.1 HotFix 7 Fixed Limitations............................................................................... 44
PowerExchange for SAP NetWeaver 8.6.1 HotFix 7 Fixed Limitations.................................................. 45
PowerExchange for Web Services 8.6.1 HotFix 7 Fixed Limitations ...................................................... 45
8.6.1 HotFix 7 Fixes Affecting Functionality............................................................................................... 45
Metadata Manager 8.6.1 HotFix 7 Fixes Affecting Functionality........................................................... 45
PowerExchange for Web Services 8.6.1 HotFix 7 Fixes Affecting Functionality ................................... 45
8.6.1 HotFix 6 Fixed Limitations ................................................................................................................. 46
PowerCenter 8.6.1 HotFix 6 Fixed Limitations........................................................................................ 46
Metadata Manager 8.6.1 HotFix 6 Fixed Limitations............................................................................... 47
PowerExchange for SAP NetWeaver 8.6.1 HotFix 6 Fixed Limitations.................................................. 47
8.6.1 HotFix 6 Fixes Affecting Functionality............................................................................................... 47
PowerExchange for SAP NetWeaver 8.6.1 HotFix 6 Fixes Affecting Functionality ............................... 47
8.6.1 HotFix 5 Fixed Limitations ................................................................................................................. 48
PowerCenter 8.6.1 HotFix 5 Fixed Limitations........................................................................................ 48
Metadata Manager 8.6.1 HotFix 5 Fixed Limitations............................................................................... 49
Data Analyzer 8.6.1 HotFix 5 Fixed Limitations ..................................................................................... 49
PowerExchange for Salesforce.com 8.6.1 HotFix 5 Fixed Limitations.................................................... 49
PowerExchange for Teradata Parallel Transporter 8.6.1 HotFix 5 Fixed Limitations ............................. 49
-2- PC_RLN_861013_0001
8.6.1 HotFix 5 Fixes Affecting Functionality............................................................................................... 50
Metadata Manager HotFix 5 Fixes Affecting Functionality..................................................................... 50
PowerExchange for Salesforce.com 8.6.1 HotFix 5 Fixes Affecting Functionality ................................. 50
8.6.1 HotFix 4 Fixed Limitations ................................................................................................................. 50
PowerCenter 8.6.1 HotFix 4 Fixed Limitations........................................................................................ 51
Metadata Manager 8.6.1 HotFix 4 Fixed Limitations............................................................................... 51
Data Analyzer 8.6.1 HotFix 4 Fixed Limitations ..................................................................................... 52
PowerExchange for SAP Netweaver 8.6.1 HotFix 4 Fixed Limitations .................................................. 52
8.6.1 HotFix 3 Fixed Limitations ................................................................................................................. 52
PowerCenter 8.6.1 HotFix 3 Fixed Limitations........................................................................................ 52
Metadata Manager 8.6.1 HotFix 3 Fixed Limitations............................................................................... 53
Data Analyzer 8.6.1 HotFix 3 Fixed Limitations ..................................................................................... 54
Reference Table Manager 8.6.1 HotFix 3 Fixed Limitations ................................................................... 54
PowerExchange for Salesforce.com 8.6.1 HotFix 3 Fixed Limitations................................................... 54
PowerExchange for SAP Netweaver 8.6.1 HotFix 3 Fixed Limitations .................................................. 54
PowerExchange for WebSphere MQ 8.6.1 HotFix 3 Fixed Limitations .................................................. 54
8.6.1 HotFix 3 Fixes Affecting Functionality............................................................................................... 54
PowerCenter 8.6.1 HotFix 3 Fixes Affecting Functionality ..................................................................... 55
Metadata Manager 8.6.1 HotFix 3 Fixes Affecting Functionality............................................................ 61
PowerExchange for SAP Netweaver 8.6.1 HotFix 3 Fixes Affecting Functionality................................ 61
Reference Table Manager 8.6.1 HotFix 3 Fixes Affecting Functionality................................................. 62
8.6.1 HotFix 2 Fixed Limitations ................................................................................................................. 62
PowerCenter 8.6.1 HotFix 2 Fixed Limitations........................................................................................ 62
Metadata Manager 8.6.1 HotFix 2 Fixed Limitations............................................................................... 63
Data Analyzer 8.6.1 HotFix 2 Fixed Limitations ..................................................................................... 63
8.6.1 HotFix 2 Fixes Affecting Functionality............................................................................................... 63
PowerCenter 8.6.1 HotFix 2 Fixes Affecting Functionality ..................................................................... 63
8.6.1 HotFix 1 Fixed Limitations ................................................................................................................. 63
PowerCenter 8.6.1 HotFix 1 Fixed Limitations........................................................................................ 64
Metadata Manager 8.6.1 HotFix 1 Fixed Limitations............................................................................... 65
PowerExchange for SAP Netweaver 8.6.1 HotFix 1 Fixed Limitations .................................................. 65
PowerExchange for Web Services 8.6.1 HotFix 1 Fixed Limitations ...................................................... 65
8.6.1 HotFix 1 Fixes Affecting Functionality............................................................................................... 65
PowerExchange for Web Services 8.6.1 HotFix 1 Fixes Affecting Functionality ................................... 66
8.6.1 Fixed Limitations................................................................................................................................. 67
PowerCenter 8.6.1 Fixed Limitations....................................................................................................... 67
Metadata Manager 8.6.1 Fixed Limitations.............................................................................................. 69
Contact Information...................................................................................................................................... 69
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
PC_RLN_861013_0001 -3-
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
PowerCenter 8.6.1 HotFix 11
PowerCenter 8.6.1 HotFix 12
When you roll back the hotfix, the installer restores PowerCenter to the previously installed version.
To apply a PowerCenter hotfix, complete the following steps:
1. Complete the pre-installation tasks.
2. Edit the properties file.
3. Apply the PowerCenter Services hotfix.
4. Complete the post-installation tasks.
5. Apply the PowerCenter Client hotfix.
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.
Note: All updates from PowerExchange for Salesforce 8.6.1.0.1 to 8.6.1.0.4 have been included in
Informatica PowerCenter 8.6.1 HotFix 13.
-4- PC_RLN_861013_0001
To edit the installer.properties file:
1. Find the properties file at the root level of your extracted hotfix package.
2. Use a text editor to open and modify the values of the properties in the file.
The following table describes the installation properties to modify:
INSTALL_TYPE Use install to apply the hotfix. Use rollback to roll back the hotfix.
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.
PC_RLN_861013_0001 -5-
Configure Metadata Manager
Before you begin to configure Metadata Manager, verify that the Metadata Manager 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.
2. 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
861HotFix9oracle10Plus.sql (if the Metadata Manager repository is on Oracle 10g or 11g)
861HotFix10.sql
861HotFix11.sql
861HotFix12.sql
861HotFix13.sql
The SQL scripts are located in the following directory:
<PowerCenter installation directory>\server\tomcat\md-
repo\scripts\HotFix\MM_Repo_Scripts\<database type>
Notes:
If the Metadata Manager repository is on Microsoft SQL Server 2005 or 2008, use
861HotFix5_SQLSERVER2005.sql..
If the Metadata Manager repository is on Microsoft SQL Server 2000, use
861HotFix5_SQLSERVER2000.sql..
If the Metadata Manager repository is on DB2, specify @ as the delimiter when you run
861HotFix13.sql. From the DB2 command line client, run the following command:
db2 -td@ -vf 861HotFix13.sql
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
-6- PC_RLN_861013_0001
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
8. Effective in version 8.6.1 HotFix 13, import the PowerCenter model for PowerCenter resources and
reload PowerCenter resources. Use the upgradeMetamodel utility to import the powercenter.xml
model file.
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\powercenter.xml
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.
10. 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:
If you are upgrading from Reload all resources of these resource types
PC_RLN_861013_0001 -7-
12. 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.
13. 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.
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.
-8- PC_RLN_861013_0001
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.
PC_RLN_861013_0001 -9-
Complete the following steps to update the repository:
1. Configure the Repository Service to run in exclusive mode.
2. Connect to the Repository Service with the pmrep Connect command using a user account with Admin
Repository privilege.
3. Locate the pmsapplg.xml registration file in the following directory:
<PowerCenter installation directory> \server\bin\native
4. Use the pmrep RegisterPlugin command to update the repository.
The RegisterPlugin command uses the following syntax:
registerplugin -i <input_registration_file_name_or_path> -e -N
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. In the Navigator of the Administration Console, select a Reference Table Manager Service.
2. Disable the service.
3. Click Actions > Upgrade Contents.
-10- PC_RLN_861013_0001
4. 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.
5. 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
6. Click Close.
PC_RLN_861013_0001 -11-
5. 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
7. Press Enter.
Request dialog box appears.
8. Select the transport request number you added and click Import.
9. 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.
-12- PC_RLN_861013_0001
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.
CR Description
245454 Partitioned sessions shut down unexpectedly when connected and unconnected lookups share the same
cache.
PC_RLN_861013_0001 -13-
245348 The Integration Service fails to prepare a pushdown optimization session configured to create temporary
objects in the database if the session contains a Union or Sorter transformation followed by a Router
transformation.
245222 Importing a workflow multiple times causes the flat file lookup session attributes to revert to the session
attributes in the mapping properties instead of the attributes specified in a session override.
245087 The Integration Service writes errors to the session log if the source database has an nvarchar dataype and
the target database has the varchar datatype and a custom property is enabled to facilitate the nvarchar to
varchar datatype conversion.
245018 The PowerCenter Services user needs write permissions on the installation directory to attach a session log
to a post-session email.
245015 The Integration Service fails a session on grid that is configured to retry on deadlock.
244929 The Designer cannot import an exported XML target definition that has the Long datatype with a precision of
19.
244845 When you copy, export, or import a workflow from the Repository Manager, a hash auto-keys partition gets
added to the Joiner transformation.
244743 The Integration Service shuts down unexpectedly when Filewatch Event-Wait tasks are stopped or aborted
for multiple workflows.
244710 The Integration Service is not resilient to an MQ source queue and fails the session that is processing
messages from the MQ source queue if the connection to the queue manager is in the quiescing state.
244546 A mapplet in a deployment group is no longer valid after deploying the deployment group to the target
repository.
244291 The ADD_TO_DATE function does not work correctly for a Netezza session configured for pushdown
optimization.
244168 Workflow Manager shuts down unexpectedly when view a pushdown optimization session that contains a
Union transformation followed by a Router transformation.
243934 After upgrading to 8.6.1 HotFix 12 from 8.6.1 the log directory does not display correctly in the Administration
Console.
243860 The Repository Service shuts down unexpectedly while reconnecting to the repository when the locks for the
previous connection to the repository are being released.
243711 Cannot monitor workflows using the Workflow Monitor when multiple sessions are running continuously.
243093 The Repository Service shuts down unexpectedly while purging deleted objects from the Repository
Manager.
242850 The Repository Service shuts down unexpectedly while exporting objects in a deployment group to an XML
file.
242836 Some ports are missing from the XML views after you import an XML Schema file into the Designer using
the Hierarchy Normalized view.
242714 Deployment fails with a unique constraint error because of a naming conflict for a shortcut to an object in the
deployment group that matches a shortcut in the target folder, which points to an unrelated object.
242496 Pushdown optimization session does not generate the correct query when the schema name is used as part
of an attribute for the target table name.
242241 The Integration Service deadlocks after failing to connect to the repository.
-14- PC_RLN_861013_0001
242049 In a non-highly available domain, cannot connect to the repository from the Workflow Monitor or pmcmd
when the Repository Service restarts after resilience timeout.
241645 The Integration Service shuts down unexpectedly while writing a log file with a file name that exceeds 255
characters for a workflow that is enabled to run concurrently.
241639 The temporary text log file remains in the session logs if the process to send post-session email terminates.
240601 The Repository Service shuts down unexpectedly because the PowerCenter Services fail to authenticate the
user groups for the Repository Service.
239165 The Integration Service fails a Rank transformation session and writes a message to the session log that
states an error occurred while creating the buffer pool.
239118 An Integration Service custom property does not work correctly when the Integration Service runs on
Windows and uses an FTP connection with the Is Staged option enabled to write to an FTP target on a UNIX
machine.
237480 Attributes that are present one level below in the XML hierarchy are not included in the XML views created
using the hierarchy relationship.
234515 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.
232615 Groups are missing in the Router transformation after a PowerCenter repository upgrade from 8.1.1 SP4 to
8.6.1 and after the code page changes from UTF-8 to ISO.
226354 Mapping variable values are not retained when you use the pmrep deployDeploymentGroup command to
deploy a deployment group to the target repository.
CR Description
243188 If Metadata Manager repository is on DB2, post-installation, running the 861HotFix10.sql script makes a few
views invalid.
242328 Unique constraint violation occurs in the S_M_PC8X_SESS_DSQ_CNX_PAR_STAGE session when you
load a PowerCenter resource.
240360 When you configure a PowerCenter workflow, if you use absolute file name or the $PMFolderName and
$PMWorkflowName workflow variables to specify the parameter file name, Metadata Manager uses this
value to assign the parameter file to the workflow. If you use any other workflow variable for configuring the
parameter file name, you need to manually assign the parameter file to the workflow.
238050 Operation timeout occurs while assigning parameter files to all workflows during PowerCenter resource
configuration.
PC_RLN_861013_0001 -15-
PowerChannel 8.6.1 HotFix 13 Fixed Limitations
CR Description
225975 Cannot create PowerChannel services after installing PowerChannel 8.6.1 on Windows 64 bit.
CR Description
243388 Web Service Consumer transformation returns NULL for fields with xsi:type referring to an user defined
simpletype.
CR Description
245055 JMS message are lost when the JMS session is configured to read messages from an MQ JMS source for a
set period of time.
242739 JMS session terminates after a recovery task shuts down unexpectedly.
237488 The Integration Service does not write a batch of JMS messages to the target after aborting a session that
contains a JMS source and an Oracle target.
237485 The Integration Service occasionally does not write a JMS message to the target after aborting a session
that contains a JMS source and an Oracle target.
CR Description
240927 BAPI session fails when a returning string contains any non-English character part of the table type
parameter.
133401 The SAP BW Service needs to be restarted to clear the large number of Close_Wait tasks that the SAP BW
Service process creates.
-16- PC_RLN_861013_0001
PowerCenter 8.6.1 HotFix 12 Fixed Limitations
CR Description
238972 The master gateway node shuts unexpectedly while the Log Manager exports or saves the Administration
Console log events.
238533 The Profile Wizard cannot add some profile functions in a custom profile.
238423 Session hangs when it uses an SFTP connection to access a flat file source and a flat file target.
238049 The Integration Service deadlocks after it fails to connect to the repository.
236895 The Integration Service times out the request to terminate user connections to the repository when you abort
the workflow from the Workflow Monitor or use the pmrep killuserconnection command to terminate user
connections.
236843 The DTM process shuts down unexpectedly when an Expression transformation session uses the
REG_REPLACE function on a large set of data.
236224 Session performance degrades when the session is configured to use automatic memory settings and the
connection retry period is not set to zero.
236042 The Integration Service sometimes shuts down unexpectedly when running a session on a grid.
233870 Session fails when an expression function invokes the REG_REPLACE function while deleting cache files for
an Aggregator transformation.
233689 Performance degrades for Web Services Hub sessions when multiple concurrent requests are sent to the
Web Services Hub.
232381 Repository Service performance degrades when sessions that have a large number of connection variables
repeatedly access the database.
229411 Flat file properties get reset after you copy worklets with sessions that contain flat file lookup mapplets.
226814 The master gateway node shuts down unexpectedly when another node in the domain carries a high load.
226318 The master gateway node does not give up the master role even when it takes more than 32 seconds to
update the database while a worker node elects to become the master gateway node.
225331 After you import a mapping, the lookup decimal separator is set to period instead of comma.
223043 Session fails when it uses an SFTP connection with public key authentication to connect to the OpenSSH or
Tectia FTP server.
CR Description
238130 Metadata Manager authentication sessions timeout when you configure Single Sign-On for LDAP users.
236374 Metadata Manager does not display the lineage diagram between PowerCenter and SAP resources if the
SAP ABAP application connection name is defined in a parameter file.
PC_RLN_861013_0001 -17-
235293 Metadata Manager cannot display the lineage diagram between a versioned PowerCenter repository and the
target table.
234373 Metadata Manager cannot display the data lineage diagram for a mapping that contains multiple lookups
with a combination of direct connections and parameterized connections.
234137 Metadata Manager can fail to load a Teradata resource into the Metadata Manager warehouse because the
SQL queries that Metadata Manager uses to load the Teradata resource use a large amount of memory.
233570 Metadata Manager displays a null pointer exception message while launching data lineage between a
function definition that accesses an Oracle table and an Oracle materialized view.
232618 Metadata Manager takes a long time to access or save edit changes to business terms in the business
glossary.
226671 Metadata Manager cannot extract metadata from an ERStudio model if the Dimension model notation is
selected.
193804 When you create and enable the Metadata Manager Service, the metadata load folder that is created in the
versioned PowerCenter repository contains objects in the checked out state.
CR Description
231033 If a Reporting Service fails to enable because the port is in use, you cannot enable any other Reporting
Service.
CR Description
229963 SAP NetWeaver cannot import metadata for the SAP/ALE IDoc Interpreter and SAP/ALE IDoc Prepare
transformations that contain the RAWSTRING datatype.
201900 You cannot add the ABAP program namespace when you select the Enable Override and Customer
namespace in the Generate or Install ABAP window.
-18- PC_RLN_861013_0001
PowerExchange for SAP NetWeaver 8.6.1 HotFix 12 Known
Limitations
This section describes the known limitation for 8.6.1 HotFix 12.
240525: If there are no rows in the SAP BW OHS source, the OHS request status is set to R
If there are no rows in the data source for an OHD and when you extract the data using this OHD, the OHS
request status will be set to R.
Workaround: Before you run the same process chain, use the BAPI
RSB_API_OHS_REQUEST_SETSTATUS in the SAP system to set the status to G for the request ID.
Effective in 8.6.1 HotFix 12, you can edit web service sources and targets created in PowerCenter version
8.6.1 HF12. You cannot edit web service sources and targets upgraded from previous versions of
PowerCenter. To update a web service source or target from previous versions of PowerCenter, re-create
the source or target in PowerCenter 8.6.1 HotFix 12.
CR Description
231689 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.
231264 The Workflow Monitor displays an incorrect message in Japanese for scheduled workflows.
231249 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.
231240 The Integration Service fails the session after failing to generate the child process to read the parameter file
for the operating system profile.
PC_RLN_861013_0001 -19-
231239 The load balancer message for load statistics does not display the task name to correlate a load request for
a session.
231055 The Integration Service shuts down unexpectedly when you change the scheduler for a workflow that is
scheduled to run.
231031 The master gateway node shuts down unexpectedly with an out of memory error while fetching large log
entries from the Administration Console.
230134 The Integration Service that uses operating system profiles hangs a workflow that uses parameter files and
is scheduled to run continuously.
230065 The Workflow Manager displays an error when you add a service level in the Administration Console in the
Japanese locale.
230047 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.
230009 The Integration Service terminates sessions with multiple load order groups in a Lookup transformation.
229690 The Reference Table Manager displays an error when you manually enter date data into the reference
tables.
229124 The Integration Service shuts down unexpectedly while aborting workflows with Event-Wait tasks.
228909 The Integration Service fails a session enabled for pushdown optimization.
228675 Unicode session with the INSTR function returns incorrect binary comparison results.
228637 861 HotFix 10 custom transformation sessions fail when the custom transformation has additional output
ports.
228394 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.
228046 Session incorrectly reads vargraphic datatype data from IBM DB2 on 64-bit Linux.
227627 Session takes a long time to initialize if the mapping contains many transformations and targets.
227410 An unexpected condition error occurs when you launch the Workflow Monitor in the Japanese locale.
227403 Database partition initialization fails for a range partitioned IBM DB2 target table.
227239 Single pipeline session with a Joiner transformation that uses sorted input returns inconsistent results when
you switch the master/detail relationship.
227122 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.
227098 Impacted objects appear in the target repository after you deploy a deployment group with valid objects from
the source repository to the target repository.
227008 Dynamic partition sessions do not initialize and cause memory leaks.
226543 You cannot use the updateServiceProcess command to add or update custom environment variables for a
service process.
-20- PC_RLN_861013_0001
226539 The operating system profile user cannot pick the LD_LIBRARY_PATH environment variable after specifying
the variable in the operating system profile properties.
226410 Session that uses the gunzip command as a pre-session command on Windows takes a long time to
complete.
226400 The Integration Service incorrectly reads the message response from the FTP server if the FTP server has a
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.
225620 Session fails when an expression function invokes the REG_REPLACE function while deleting cache files for
an Aggregator transformation.
225359 The Administration Console HTML code does not disable the Autocomplete tag that provides user name and
password information.
225357 The Integration Service hangs and terminates workflows after a repository database deadlock on Microsoft
SQL Server 2005 SP3.
225052 The Reference Table Manager displays an error when you enter decimal values into an IBM DB2 table.
224721 The Integration Service shuts down sessions with Custom transformations with more than 20 additional
ports.
223835 You can view the stack trace for exceptions in the Administration Console browser.
222917 The XML Editor launches multiple Internet Explorer windows when you close the XML Editor without
applying the changes.
220180 There is no pmrep command to list all the groups that a user belongs to.
219612 Custom transformation sessions with multiple output ports generate garbled output.
218632 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.
216137 An 8.6.1 Web Services Hub does not display historical statistics.
207241 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.
207217 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.
205543 Session performance decreases when you create a partition point for the session that has an expression
transformation with numerous variable and output ports.
PC_RLN_861013_0001 -21-
Metadata Manager 8.6.1 HotFix 11 Fixed Limitations
CR Description
231219, Metadata Manager encounters unique constraint errors when you load an ERwin resource.
227534
233077 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.
232490 You cannot select multiple schemas in the Schema Inclusion List for a relational database resource or the
Folder Inclusion List for a PowerCenter resource.
232489 Metadata Manager does not list the schemas in the Schema Inclusion List in alphabetical order for a
relational database resource.
232062 Metadata Manager does not list the connections in the Connection Assignment tab in alphabetical order.
232061 You cannot select or clear Refresh for all schemas listed in the Schema Inclusion List for a relational
database resource.
231231 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.
230933 Metadata Manager encounters universe validation errors when you load a Business Objects resource.
230908 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.
227510 Metadata Manager does not load the source creation date and source modified date for some Microstrategy
classes.
227289 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.
227094 A Cognos resource load fails with a null pointer exception when a Cognos report uses a semicolon as a
delimiter.
226942 Metadata Manager Service fails to start when a loaded PowerCenter resource contains a large number of
metadata extensions.
225713 When you search for a PowerCenter metadata object property, Metadata Manager does not return non-
reusable sessions that match the search criteria.
183928 When you delete a user from the PowerCenter domain, Metadata Manager does not delete the user’s
personal folder.
173543 If the session mode is configured to ANSI in the Teradata ODBC driver, a Teradata resource load fails with a
truncation error.
-22- PC_RLN_861013_0001
Data Analyzer 8.6.1 HotFix 11 Fixed Limitations
CR Description
228101 You cannot access Data Analyzer version 861 HotFix 10 on Linux because the Data Analyzer Service and
the PowerCenter domain are not in sync.
CR Description
225524 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.
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.
CR Description
229751 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.
228514 SAP sessions that run in file mode fail after an upgrade from 8.1.1
227323 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.
227169 BCI listener session that runs on Windows fails while extracting data from data sources that have a large
number of records.
222572 BAPI/RFC sessions fail with an error message that states the MATNR mapping parameter is blank or
incorrectly transferred.
PC_RLN_861013_0001 -23-
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.
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>]
-24- PC_RLN_861013_0001
-un
-Password password Optional. Password for the user name. The password is case
sensitive. You can set a password with the -pd option or the
-pd environment variable INFA_DEFAULT_DOMAIN_PASSWORD.
If you set a password with both methods, the password set with
the -pd option takes precedence.
-SecurityDomain security_domain Required if you use LDAP authentication. Name of the security
domain that the user belongs to. Default is Native.
-sdn
-ExistingUserName existing_user_name Required. Name of the user that you want to list groups for.
-eu
-fullHierarchy full_hierarchy Optional. List the full hierarchy of groups, including the parent
groups.
-fh
PC_RLN_861013_0001 -25-
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
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.
-26- PC_RLN_861013_0001
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:
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)).
PC_RLN_861013_0001 -27-
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.
-28- PC_RLN_861013_0001
Note: You cannot search for PowerCenter metadata extensions defined for PowerCenter metadata objects.
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 in the HTTPS node on an AIX operating system while another
Reporting Service runs in the HTTP mode, the Reporting Service being enabled fails.
Workaround:
Perform the following tasks to enable the Reporting Service in the HTTPS mode on an AIX operating
system while another Reporting Service runs in the HTTP mode:
1. Disable the Reporting Service that runs in the HTTP mode.
2. Enable the Reporting Service that you want to enable in the HTTPS mode.
3. Enable the Reporting Service that previously ran in the HTTP mode.
PC_RLN_861013_0001 -29-
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:
To resolve this connection issue, perform the following tasks on each machine that has the B2B Data
Exchange PowerCenter plug-in installed:
1. Under the dx directory, back up powercenter/plugin/dxplugin.ini.
2. Open dxplugin.ini with a text editor.
3. Search for DataDirect 5.2 and replace it with DataDirect 6.0.
4. Restart the PowerCenter Designer.
CR Description
225997 Sessions fail when multiple mappings use a reusable Lookup transformation configured to use a persistent
cache.
225851 pmrep shuts down unexpectedly when a pmrep command uses a control file with a user-defined function that
calls a Lookup transformation.
225815 The Workflow Manager shuts down when you open the Pushdown Optimization Viewer.
225567 A mapping is no longer valid after deployment from the source repository to the target repository.
224460 The Integration Service writes an error to the session logs instead of a warning when an incorrect expression
is used in an Expression transformation.
224293 The Integration Service fails a session that reads from a file list source and writes to an IBM DB2 target in
bulk mode.
222630 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.
222260 The Designer does not recognize the period in ODBC sources. For more information, see the PowerCenter
Designer Guide.
221602 A web service workflow randomly hangs when the workflow is hosted on the PowerCenter Web Services
Hub.
221053 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.
-30- PC_RLN_861013_0001
220349 The Integration Service shuts down unexpectedly when a workflow enabled for recovery and configured to
use an operating system profile has an exception error.
220033 Session fails when multiple FTP source partitions fail intermittently because of an FTP access error.
219766 Pushdowm optimization enabled session with a Netezza ODBC driver has a different SQL query in the
session log and the ODBC trace file.
219670 Web Services Consumer session fails when no internet connectivity is available for the machine on which
the Integration Service runs.
218857 The master gateway node hangs in the domain due to a deadlock that occurs during LDAP authentication.
218524 SQL transformation session returns a null value when the precision of the output port is greater than 65000.
217826 The repository agent fails unexpectedly if an LDAP user tries to log in to an application client during
synchronization.
217002 The Repository Manager cannot import metadata from an ERwin 4.12 source because of a datatype
mismatch.
215841 Duplicate sources appear in the Sources folder in the Designer and Repository Manager after deploying a
deployment group to the target repository.
214798 The Designer shuts down unexpectedly when you preview data in the CSV file that contains special and
non-English characters during import.
214301 A user needs to have the Administrator role to edit a service level assigned to the workflow.
214291 The Integration Service does not recover a recovery enabled session on grid if you stop the worker DTM.
213133 The Integration Service shuts down unexpectedly while scheduling workflows.
211724 A two second delay occurs between session runs when the Integration Service runs a workflow with
sequential runs on Linux or zLinux.
210244 The DTM process shuts down unexpectedly while aborting a workflow configured to use an operating system
profile and a FileWatch event task.
210068 When you compile a Java transformation, the Designer generates files within the default workspace directory
instead of the user-defined directory.
209743 The Integration Service hangs intermittently while running a pre-session command on a Solaris machine.
207897 The domain shuts down while switching the repository from exclusive to normal mode.
207384 Session fails when there is a missing new line character in a workflow parameter file.
202854 8.6.1 HotFix 1 sessions take a long time to load data to a Sybase database.
202731 Sessions that use the FastExport utility to read data from Teradata sources read the Float datatype values
as 0.
201241 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.
PC_RLN_861013_0001 -31-
Metadata Manager 8.6.1 HotFix 10 Fixed Limitations
CR Description
226478 Metadata Manager incorrectly displays the lineage between a custom resource and its Business Term.
224448 Metadata Manager cannot load an IBM DB2 zOS resource that has view containing more than 4000
characters into the Metadata Manager warehouse in Oracle.
223985 Metadata Manager cannot load a MicroStrategy resource into the Metadata Manager warehouse using the
MicroStrategy 6.0.3 bridge.
222804 Metadata Manager cannot load an Oracle resource into the Metadata Manager warehouse due to an invalid
datatype error.
222507 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.
222496 Metadata Manager cannot display the lineage between a SAP and a PowerCenter resource.
222344 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.
222343 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.
221250 The Metadata Manager Agent does not have the Cognos patch required to run Cognos resources.
218669 Metadata Manager does not display the data lineage diagram between a Teradata view that contains
comments and the original table.
218424 Metadata Manager cannot load an OBIEE resource into the Metadata Manager warehouse because of a
memory allocation error.
206258 Metadata Manager cannot extract the source creation date and update date from any of the MicroStrategy
classes in a MicroStrategy resource.
203222 Metadata Manager loads recycle tables named BIN$ for an Oracle 10g resource.
186146 Metadata Manager loads all the schemas from the Teradata source into the selected schema for the
Teradata resource load.
CR Description
210303 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.
-32- PC_RLN_861013_0001
PowerExchange for WebSphere MQ 8.6.1 HotFix 10 Fixed
Limitations
CR Description
225484 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.
-e dbd_separator 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 (\).
PC_RLN_861013_0001 -33-
Checkin
DeleteObject
ExecuteQuery
FindCheckout
ListObjects
PurgeVersion
UndoCheckout
-s dbd_separator 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 (\).
-34- PC_RLN_861013_0001
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
PC_RLN_861013_0001 -35-
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.
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.
-36- PC_RLN_861013_0001
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.
CR Description
218337 The Integration Service running on a grid with two nodes shuts down unexpectedly.
217625 After applying 8.6.1 HotFix 8, the workflow and session logs display Chinese characters if the locale on the
machine is traditional Chinese.
217516 When the Load Balancer runs in adaptive mode, sessions go into wait mode and do not get dispatched to
other nodes.
217273 Pushdown optimization session fails while connecting to an Oracle database with an error message that
states the column names are too long.
216598 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.
216221 Non-reusable objects are not checked in after you copy and check in a mapping shortcut to the target
repository.
215930 Session hangs while running a workflow with the restart task recovery strategy enabled.
215907 Workflows in a static deployment group cannot be assigned to the Integration Service after you deploy the
deployment group to the target repository.
215384 The Integration Service processes the SQL filter condition incorrectly when it runs a session with a
Salesforce.com object.
PC_RLN_861013_0001 -37-
215100 Session hangs intermittently when it contains the Sorter, Joiner, and Sequence Generator transformations.
214988 Recovery session terminates with the worklet status as terminating and the workflow status as running.
214857 An upgrade session fails when pushdown optimization is enabled for an unconnected Lookup
transformation.
214539 The Integration Service fails a session configured for pushdown optimization.
213904 The Integration Service fails PowerCenter sessions configured for pushdown optimization that have many
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.
211959 The Integration Service fails sessions with pre- and post-session command that cannot open the standard
output files.
211348 After sessions complete, connections for the Repository Service and the Integration Service process remain
the close wait state.
211031 You cannot add multiple email addresses for the $PMSuccessEmailuser service variable when you configure
the Integration Service.
210880 The Integration Service does not fail a session that encounters a user-defined error for the stored procedure
in a Sybase database.
210405 Session fails when the XML source column has the string datatype of infinite precision.
207419 The pmrep ObjectImport command fails to import a workflow on AIX 5.3.
206831 The Repository Manager incorrectly deploys deployment group objects to the target repository.
204688 Real-time CDC session that is enabled for recovery takes a long time to load data.
CR Description
217770 Metadata Manager takes a long time to edit an object if the catalog is large.
217071 Metadata Manager takes a long time to load a PowerCenter resource into the Metadata Manager warehouse
on an Oracle database.
217054 Metadata Manager cannot update any custom property for a synonym.
216824 Metadata Manager cannot import the business glossary from an Excel file, if the business glossary name
has Chinese characters.
215816 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.
215600 Metadata Manager takes up to four minutes to display a business term with related catalog objects.
215402 Metadata Manager takes a long time to add a business term to the glossary.
215330 Metadata Manager displays an out of memory error when you import an XML file that is greater than 190
-38- PC_RLN_861013_0001
MB.
214008 Metadata Manager loads a PowerCenter resource but the PowerCenter sessions have unique constraint
errors.
213949 The Metadata Manager Service fails to enable on a Sybase database and logs errors in the Domain log
events.
212610 Metadata Manager cannot assign the relational connections for an OBIEE resource.
210979 Metadata Manager does not consider all the links between objects when performing data lineage analysis.
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.
203962 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.
CR Description
209431 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.
206893 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.
Property Description
PC_RLN_861013_0001 -39-
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.
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 Description
212732 Lookup transformation session enabled for pushdown optimization generates an invalid query when the Date
datatype column is used in the lookup condition.
-40- PC_RLN_861013_0001
212424 Session rejects rows when writing Date datatype data from a Teradata database to the Timestamp datatype
in an Oracle target definition.
211330 Session continues to read some rows from a Sybase database even when the database deadlocks.
211156 The Integration Service fails concurrent sessions with a broken pipe error when the sessions read from and
write to an Operating System pipe.
210328 The Integration Service shuts down unexpectedly after workflows with Event-Wait tasks terminate.
206666 Reference Table Manager does not provide security on connections. For more information, see Reference
Table Manager 8.6.1 HotFix 8 Fixes Affecting Functionality.
202080 The Worklfow Manager duplicates concurrent workflow run instances after the workflow is deployed using
the Repository Manager.
CR Description
213002 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.
211349 Metadata Manager cannot index large resources because of insufficient memory.
211349 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.
209713 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.
CR Description
211618 PowerExchange for JMS writes the value of the previous message’s correlation ID to the queue if the value
of the correlation ID for the current message is NULL.
PC_RLN_861013_0001 -41-
Metadata Manager 8.6.1 HotFix 8 Fixes Affecting Functionality
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:
Property Description
lucene.merge.factor 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.
-42- PC_RLN_861013_0001
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 Update the SAP BW
System
Effective in 8.6.1 HotFix 12, to run data extraction systems using SAP BI Open Hub Destination, update
the SAP BI systems with the following patch:
Install Patch level 24 (SAPKW70024) on SAP BI 7.0
Upgrade the Contents of the Reference Table Manager Repository.
Manage User Privilege
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. In Reference Table Manager, click the Users tab.
4. Select a user or group and click Edit.
The User/Group Details dialog box appears.
5. Select the connections to assign the user or group permission on.
6. To revoke permission, clear the connections assigned to the user or group.
7. 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.
PC_RLN_861013_0001 -43-
PowerCenter 8.6.1 HotFix 7 Fixed Limitations
CR Description
211102 Unexpected condition occurs when you re-import an XML source definition containing a
CurrentlyProcessedFileName port.
210660 Rank and Aggregator session fails when loading data in the cache.
210162 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.
209519 The Integration Service on Windows 64-bit Itanium shuts down unexpectedly.
209331 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.
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.
208532 The Expression Editor for a Filter transformation does not display a message when the expression is parsed
successfully.
208279 The deployment operation fails when you apply a label to a Timer task during the deployment process.
206886 The Repository Service on different operating systems can hang or shut down unexpectedly while
processing a query.
206067 The pmcmd command getsessionstatistics and the Batch Web Services call getsessionstats do not execute
the last run of the workflow for a recovery session.
204947 There are corrupt SQL script files in the PowerCenter 8.6.1 client installation directory.
202398 SQL transformation sessions return NULL values for string columns if the precision is greater than 65534.
CR Description
210341 Metadata Manager Agent cannot extract metadata from a Business Objects resource.
210312 Metadata Manager fails to create a PowerCenter resource when the version of the PowerCenter source is
less than version 8.5.
209508 Metadata Manager cannot parse the values of the parameter files associated with the PowerCenter
workflow.
210512 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.
208718 The SQL scripts for Metadata Manager 8.6.1 HotFix 5 contain unnecessary ^M characters.
-44- PC_RLN_861013_0001
PowerExchange for SAP NetWeaver 8.6.1 HotFix 7 Fixed
Limitations
CR Description
206874 The Designer shuts down unexpectedly while accessing the IDoc Display tab for an SAP/ALE IDoc
Interpreter transformation.
CR Description
209466 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_861013_0001 -45-
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 Description
208544 The Designer does not correctly create XML Views for an imported complex XSD file.
208336 Router transformation session duplicates rows when routing data from a source with more than 350,000
rows.
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.
208091 Stored Procedure transformation session fails because the connection information for the stored procedure
reverts to the default value after you import a workflow.
207861 An invalid scale error occurs when you import an XML file generated from an XSD source that does not have
a datatype defined.
207802 The domain shuts down after you disable a Reporting Service.
207747 The Integration Service that uses operating system profiles shuts down unexpectedly while aborting a
workflow with an Event-Wait task.
207632 The Integration Service rejects junk character rows when loading data to a fixed-width target flat file.
207255 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.
207014 The Workflow Manager shuts down unexpectedly after a session is enabled for pushdown optimization.
206775 The SQL transformation prepares a dynamic SQL query for each record if the query entails string
replacement.
206711 SQL transformation session fails when the mapping parameter uses a large SQL Override query.
205213 The DTM process aborts and terminates a session that has a VSAM source with a NULL character.
205022 With high precision enabled, the Integration Service writes duplicate rows to the target but writes correct
number of rows to the session log.
204368 The pmcmd startworkflow command with the wait option enabled does not always wait till the worklflow
completes before starting the workflow again.
204050 The Repository Manager shuts down unexpectedly while purging active objects from the repository.
-46- PC_RLN_861013_0001
203445 The Integration Service on UTF-8 encoding of Unicode truncates the mapping parameter value.
203278 pmrep on AIX shuts down unexpectedly when you run a script containing the pmrep deploydeploymentgroup
command.
CR Description
206451 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.
204546 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.
201392 Metadata Manager displays incorrect lineage for relationships that are added or updated after the business
glossary was imported as an Excel file.
CR Description
207953 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.
205511 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.
196880 The SAP NetWeaver BCI Wizard cannot display data source fields that have the selection type ‘M’ in the
selection criteria.
189863 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.
PC_RLN_861013_0001 -47-
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.
CR Description
206827 PowerCenter Client cannot connect to the repository after network connection is restored within resilience
timeout.
206147 The Integration Service schedules unscheduled workflows after you deploy a deployment group to the target
folder.
206083 The Integration Service shuts down unexpectedly after workflows with Event-Wait tasks terminate.
205495 The Integration Service fails sessions with multiple connected and unconnected lookups to the same source.
205214 The Integration Service cannot retry target writes on deadlock for Transaction Control transformation
sessions with automatic memory settings enabled.
204997 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.
201872 Cannot log in to the Administration Console on a master gateway node that comes up after failover.
200305 After an upgrade, the Integration Service fails sessions enabled for pushdown optimization.
197664 The Data Transformation Manager process shuts down unexpectedly while processing the sort operation.
183106 Cannot open the query editor in the SQL Ports tab of the SQL transformation in the Japanese locale.
-48- PC_RLN_861013_0001
Metadata Manager 8.6.1 HotFix 5 Fixed Limitations
CR Description
206896 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.
206604 Metadata Manager cannot load an Oracle resource that contains a large number of stored procedures.
205610 Java processes for a Metadata Manager Service utilize almost 70 percent of the CPU.
204953 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.
204942 After an upgrade to 8.6.1 HotFix 3, Metadata Manager cannot load a Business Objects resource into the
Metadata Manager warehouse.
204507 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.
203396 Metadata Manager cannot extract all the models for a Cognos ReportNet resource because of a Java NULL
Pointer error.
202887 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.
200743 The Metadata Manager application on an open browser times out after 12 hours.
CR Description
202127 The Reporting Service times out when it takes longer than four seconds to connect to the source database.
CR Description
205925 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.
CR Description
205029 Teradata sessions fail if the Teradata decimal datatype has precision greater than 18.
PC_RLN_861013_0001 -49-
8.6.1 HotFix 5 Fixes Affecting Functionality
This section describes the fixes affecting functionality for 8.6.1 HotFix 5.
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.
-50- PC_RLN_861013_0001
PowerCenter 8.6.1 HotFix 4 Fixed Limitations
CR Description
204756 The Integration Service runs previously completed workflows after its master service process fails over or
restarts.
204616 The Integration Service shuts down unexpectedly when there is a broken connection to the Repository
Service.
204551 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.
204329 The Integration Service truncates the long link condition between a session task and a worklet on a UTF-8
repository.
204299 The Data Transformation Manager process shuts down unexpectedly when processing data for a Lookup
transformation.
203956 Library files packaged with PowerCenter conflict with other PowerCenter products.
203775 The Integration Service terminates a session enabled for recovery that ignores task resource requirements
when distributing tasks across nodes of a grid.
202539 When the Web Services Hub calls a protected web service with an incorrect user name and password it
does not return a meaningful error.
201909 You cannot save an impacted non-reusable session from the Query Results window in the Repository
Manager or with the pmrep Validate command.
200848 The XML Editor validates the large definition of the .xsd file but invalidates a simple mapping that contains
the XML source definition.
200232 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.
199436 The powermart.dtd file is missing from Command Line Utilities installation directory.
198933 Cannot close socket connections between the gateway node and worker node.
188851 XML Parser session fails because it produces the same value for each run of a primary key column in an
XML view.
CR Description
202181 Metadata Manager fails to load a Cognos ReportNet Content Manager resource.
PC_RLN_861013_0001 -51-
Data Analyzer 8.6.1 HotFix 4 Fixed Limitations
CR Description
204516 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.
CR Description
181111 SAP sessions configured to use key range partitioning extract data incorrectly from the SAP source.
CR Description
203388 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.
202978 The Integration Service shuts down unexpectedly when running sessions with Web Services Consumer
transformations.
202869 The Repository Manager shuts down unexpectedly when you try to reconnect to the repository on 64-bit AIX.
202816 The Integration Service does not start the pre- and post-session command tasks on 32-bit HP UNIX.
202687 Real-time session that reads from a JMS source continues to run after encountering an error in a Stored
Procedure transformation.
202521 The Integration Service shuts down unexpectedly on 64-bit Linux when the Performance Monitor checks
CPU statistics.
202458 The Subsecond Precision property for a Lookup transformation changes when you export and import a
mapping with the transformation into the Designer.
202366 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.
202253 The Repository Manager imports the workflow but not the key range partition values.
202113 The Integration Service does not run workflows or does not complete workflow runs when it runs multiple
concurrent tasks on AIX.
202065 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
-52- PC_RLN_861013_0001
log.
201937 Multiple Integration Service processes shut down unexpectedly when you use the pmrep ObjectImport
command.
201871 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.
201863 PowerExchange ignores the values of the Application Name attribute in application connections for
PowerExchange change data capture (CDC).
201830 A post-session command cannot read two environment variables that have the same names but different
cases.
201697 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 The Integration Service shuts down unexpectedly when you run a debug session instance.
201391 The CONVERT_BASE function returns incorrect values for negative and zero values.
201098 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.
201097 The Designer displays an error message when you use the Mapping Designer to check-out or check-in a
mapping in a repository.
200964 You cannot edit the sequence value for an XML Source Qualifier in the Designer.
200802 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.
193951 You cannot rename a shortcut that references a mapplet in a shared folder that is created by an
administrator.
188355 The Repository Manager shuts down unexpectedly when performing an advanced purge for active objects
based on criteria.
184746 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.
CR Description
201558 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 Metadata Manager displays an error message when you assign an RTM Table to a Business Term.
200979 Metadata Manager displays an incorrect lineage diagram for a PowerCenter resource because the resource
was loaded into the Metadata Manager warehouse with errors.
PC_RLN_861013_0001 -53-
Data Analyzer 8.6.1 HotFix 3 Fixed Limitations
CR Description
189707 The Reporting Service is not enabled when HTTPS is configured on 64-bit AIX.
CR Description
CR Description
201715 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 Description
199564 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.
CR Description
202574 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.
-54- PC_RLN_861013_0001
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.
Export Options
The following options are new in the Microsoft Office Excel Options page of the Metadata Export Wizard:
Operation 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:
With metadata mapping Metamap associated with the mapping specification template you want to use.
spreadsheet Valid values included:
- MappingTemplate-MetaMap.xml
- source-target-matrix-metamap.xml
- <custom-metamap>.xml
PC_RLN_861013_0001 -55-
From base spreadsheet Mapping specification template. Valid values included:
- MappingTemplate.xls
- MappingTemplate_NoValidation.xls
- source-target-matrix-mirrepeatingsheet.xls
- <custom-template>.xls
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:
-56- PC_RLN_861013_0001
Parameter Description
Spreadsheet Match Criteria Name of the matching criteria. For example, you can enter the name of the
worksheet and identifying cell in the mapping specification template.
Contents Contents of the identifying cell in the mapping specification template. Enter the name
of the cell in the mapping specification template.
Link Contains the location of the identifying cell in the mapping specification template.
Copy and paste the cell location from the mapping specification template.
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.
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:
PC_RLN_861013_0001 -57-
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
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:
Repeatable output 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.
-58- PC_RLN_861013_0001
Dictionary Name Displays the flat file or relational table name that you selected.
Lookup column Select the column in the dictionary file that contains the serial number.
Return value The dictionary column to return to the Data Masking transformation.
Lookup condition 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.
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 Description
ODBC Data Source ODBC data source that connects to the database that contains the dictionary.
User Name A database user name to connect to the database. The user name must have the
database permissions to view the tables.
Search for tables named Limits the number of tables that appear in the dialog box.
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.
PC_RLN_861013_0001 -59-
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.
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
-60- PC_RLN_861013_0001
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_861013_0001 -61-
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.
CR Description
200886 The Integration Service does not write error messages to the session log for lookups that are not resilient to
database connections.
200884 Lookup is not resilient to IBM DB2 database errors in real-time change data capture workflows.
200829 When you create a PowerCenter domain using a DNS alias, the Administration Console cannot generate
node diagnostics.
200546 The Repository Manager displays an incorrect message when you apply a label to a shortcut object.
200485 Mapping Architect for Visio fails to import a mapping with a Teradata source or target that has a Date
column.
198805 The Integration Service restarts a concurrent workflow with multiple sessions as a normal workflow when you
restart a session from the Workflow Monitor.
-62- PC_RLN_861013_0001
198698 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.
CR Description
200995 Metadata Manager sessions hang when extracting lineage information from a PowerCenter resource.
200989 Metadata Manager fails the profiling task for Teradata tables containing decimal columns.
CR Description
198293 Enabling a Reporting Service that is configured with a Metadata Manager Service corrupts the Data Analyzer
repository.
PC_RLN_861013_0001 -63-
PowerCenter 8.6.1 HotFix 1 Fixed Limitations
CR Description
199481 The reference fields in a Router transformation are incorrectly copied when you copy the transformation in
the deployment group to the target repository.
199323 Memory peak on a gateway or worker node causes the PowerCenter domain, PowerCenter Services, and
the Administration Console to hang.
198933 Cannot close socket connections between the gateway node and worker node.
198908 Session that has the Bigint datatype as the partition key for database partitioning does not load correct data
to an IBM DB2 target.
198904 The INFA_OutputSessionLogMsg function in the Session Log Interface sometimes passes 0 for the curTime
parameter instead of the current time.
198861 Real-time web service mappings are not resilient to IBM DB2 lookups.
198850 A warning message for an invalid connection object owner appears when copying a deployment group that
has connection objects to a target repository.
198823 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.
198815 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.
198487 The session does not commit the last transaction to the lookup source when you synchronize dynamic cache
with the lookup source.
198365 Teradata and Teradata FastExport sessions generate different SQL statements for mappings with sorted
ports and a source filter in the Source Qualifier.
198359 XML primary key values are not maintained when you deploy mappings that contain XML Parser
transformations.
198355 A name conflict occurs when you copy a deployment group that has a global shortcut to a target repository.
198244 The Designer takes a long time to save a mapping that contains a user-defined function.
197993 The Administration Console displays two different error messages for an incorrect user name or password.
197842 The Service Manager cannot run the infacmd GetWorkflowLog command when the user is not an
administrator.
197133 When the Integration Service loads multibyte source data with the EBCDIC Japanese or SJIS Japanese
code pages, it writes inconsistent data to the target.
197051 Service Manager memory leak occurs when a Repository Service process shuts down unexpectedly on a
domain that runs without the High Availability option.
-64- PC_RLN_861013_0001
179069 Session fails when loading data in bulk mode for IBM DB2.
CR Description
198343 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.
198207 Metadata Manager cannot import a mapping generated by the Custom Metadata Configurator and cannot
import the resource into the Metadata Manager warehouse.
198160 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.
195992 Metadata Manager profiles all the tables in multiple Oracle schemas that are selected to create an Oracle
resource.
194798 Metadata Manager catalog displays logical groups that do not contain any objects.
192741 Session that deletes a Teradata resource from the Metadata Manager warehouse takes a long time.
CR Description
199084 The Integration Service shuts down unexpectedly for IDoc Interpreter transformation sessions.
198938 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.
198712 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.
196532 An IDoc Listener session that receives SAP source data keeps running past the value set for the Idle Time
session property.
CR Description
198322 The Web Services Hub does not process SOAP fault messages for WSDL files with RPC encoding.
PC_RLN_861013_0001 -65-
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.
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.
-66- PC_RLN_861013_0001
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 Non-
Transacted 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.
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.
CR Description
195909 The Repository Service logs invalid request errors when no errors occurred.
195540 The Asset Management Report PDF cannot display the Repository Service name that has Unicode
characters.
194792 An administrator cannot send the Asset Management Report in an email from the Administration
Console on LINUX 32-bit.
194286 infacmd AddGroupPrivilege command causes the domain to hang if certain services are running.
193940 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.
193450 The XML Generator transformation returns restricted characters that result in an invalid XML document.
193400 User without read permission on a shared query can use the query to create a dynamic deployment
group.
191701 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.
PC_RLN_861013_0001 -67-
190038 Exporting a mapping to a mapping specification file can result in incorrect function definitions.
188051 IBM DB2 EE external loader sessions fails on AIX 32-bit with error “SQLCODE:-3016.”
188020 Integration Service run-time file location, backup directory, and keystore file location not updated after
you run the installer.
187945 Workflow log displays execution lock message when sessions fail.
187899 Incorrect ODBC library names in odbc.ini for DataDirect 5.2 ODBC drivers.
187572 Cannot upgrade a repository from PowerCenter 8.1.1 configured for LDAP authentication on Windows
64-bit.
187473 You can assign a license to multiple Repository Services when the license is valid for one Repository
Service.
187375 The Integration Service does not correctly write data to Teradata targets.
187080 When you import an XML source definition, the Designer displays simple type elements as complex
type.
187030 Mapping Architect for Visio launches but does not generate mappings if current version is not installed.
186924 A web services workflow becomes unresponsive after startup when it is configured to run on a single
hub and the run count is one.
186405 After you run the installer, an error appears the first time you launch Mapping Architect for Visio.
186277 An unconnected Stored Procedure transformation is not returning output values in input/output ports.
186153 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
185500 Session with an Unstructured Data transformation fails if the Data Transformation Service uses the
LearnByExample function.
185460 Cannot view or run object query in Query Browser without read permission.
185250 Real-time session with partitioned JMS or WebSphere MQ source and relational target fails with
database error.
184862 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.
184841 Recovery session fails when processing incomplete or corrupted GMD storage cache files after
Integration Service failover.
183582 DTM process shuts down unexpectedly when a session includes a flat file source with large row size.
181614 Importing a large WSDL file causes the Designer to shut down unexpectedly.
-68- PC_RLN_861013_0001
177382 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.
176290 Unable to open Mapping Architect for Visio when you log in to PowerCenter Client with a different user
name and password.
174760 Recovery session passes an incorrect variable port value in the first row of data on Linux 64-bit.
172303 The installer fails to connect to the domain configuration database when the password contains dollar
sign ($) characters.
135022 Links to a port in a target definition fail to import when column name is changed in the target definition.
130901 Log messages saved from the output window of PowerCenter client are not in a readable format.
108493 XML parser performance slows after upgrading from 8.1.1 and previous versions on Solaris 32 bit.
104029 DTM process generates a core file when line sequential buffer length is greater than 27,750,000 bytes.
CR Description
185933 Scrolling through a large set of search results can cause timeout.
184484 Metadata Manager exports custom metadata objects where the name has an ampersand (&) to an XML
file.
Contact Information
North America / South America Europe / Middle East / Africa Asia / Australia
PC_RLN_861013_0001 -69-
-70- PC_RLN_861013_0001