Informatica Corporation PowerExchange Version Release Notes August Contents. Introduction

Transcription

1 Informatica Corporation PowerExchange Version Release Notes August 2014 Copyright (c) 2014 Informatica Corporation. All rights reserved. Contents Introduction... 1 Enhancements... 2 Fixes... 3 EDP Patches in PowerExchange Installation and Upgrades... 7 Upgrade Considerations... 7 Updated Components in the IMS Synchronous ECCR CRG.LOAD Library Expanded PowerExchange Agent Buffer Size for DB2 for z/os ECCR Processing Known Limitations... 8 Additional Information for Known Limitation Informatica Global Customer Support Introduction This document contains important information about PowerExchange For more information about the product, see the PowerExchange PDFs and online help. Informatica updates the PowerExchange PDFs, as needed. To get the latest documentation, navigate to PowerExchange Product Documentation from PWX-RLN

2 Enhancements The following table describes closed enhancement requests: CR In the PowerExchange Navigator, you can use the File > Refresh Configuration command to refresh all locally held resources, including data maps, browser profiles, application groups, extraction groups, and registration groups. If the PowerExchange Navigator is open when you import a data map by using the createdatamaps utility, you can use the Refresh Configuration command to refresh the list of data maps You can enter the new ENDRBA parameter in the -SEL statement of EDMLUCTR utility. This parameter specifies an RBA in the log data sets to use as the ending point for the utility PowerExchange can now perform dynamic application buffer sizing for connections to all data sources that contain fixed-length or variable-length records and for both bulk data movement and CDC processing. In PowerExchange 9.6.0, dynamic application buffer sizing applies only to connections to Microsoft SQL Server, Oracle, or sequential data sources that contain variable-length records and only to bulk data movement. Dynamic application buffer sizing is enabled by default. You can use the APPBUFSIZEDYN statement in the DBMOVER configuration file to explicitly enable or disable dynamic application buffer sizing Enhanced monitoring statistics are now available for PowerExchange Listeners on Windows and z/os. The statistics include summary information on PowerExchange Listener resource usage and client requests and more detailed information for each active client task and access method. Use the new displaystats or pwxcmd displaystats command to print any of the statistics reports on demand. If you run a PowerExchange Listener Service in the Informatica domain, use the infacmd pwx displaystatslistener command to print the summary statistics. You can also configure the STATS statement in the DBMOVER configuration file to print the summary statistics at a specified interval In the PowerExchange Navigator Database Row Test dialog box, you can enter a number of initial rows of data to skip in the new Skip First n Rows field. This field is available only if you select CAPX, CAPXRT, NRDB, or NRDB2 in the DB Type list and select Data in the Fetch list. When the row test fetches data, it skips the specified number of rows before displaying data To control the impact of long outstanding transactions that have no change records of CDC interest on the restart of PowerExchange Express CDC for Oracle processing, you can specify the new AGEOUTPERIOD parameter in the OPTIONS statement of the pwxorad.cfg configuration file. This parameter specifies the number of minutes after which an outstanding transaction with no change records of CDC interest is removed from the calculation of the CDC restart point. This feature can reduce the length of time archive logs must be kept available for restart purposes When you import IDMS subschema records into an IDMS data map, you can automatically generate fields that applications can use to preserve IDMS set relationships among tables. These fields include expressions that call PowerExchange functions that are used to maintain data relationships You can control whether the generated DTL CAPXUSER column in change records contains the SQL Server publication database name or a null. Use the new UIDFMT parameter in the MSQL CAPI_CONNECTION statement of the DBMOVER configuration file. 2 PWX-RLN

3 When the DB2 for z/os ECCR ends abnormally, PowerExchange requires an IBM SYSUDUMP to find the last processed LSRN value to use for a subsequent ECCR special start. However, if you have the Compuware Abend-AID tool or IBM Fault Analyzer tool, that tool might be used instead of IBM SYSUDUMP to generate diagnostic information. In PowerExchange 9.6.1, the z/os Installation Assistant customizes the sample DB2 ECCR JCL in the ECCRDB2 member of the RUNLIB library with the following statements that cause these tools to be bypassed: //ABNLIGNR DD DUMMY //IDIOFF DD DUMMY Do not delete or comment out these statements. Otherwise, you might not get the correct LSRN for a special start of the ECCR after an abend In Oracle 11g and later environments, PowerExchange Express CDC for Oracle can capture change data from Oracle Data Guard physical standby databases. If the standby database is not open for read-only access, you must define the new STANDBY statement in the PowerExchange Express CDC for Oracle configuration file, pwxorad.cfg PowerExchange now supports IMS 13 for synchronous CDC For DB2zOS target connections, when the PowerCenter Integration Service requests a TRUNCATE statement, PowerExchange now issues a TRUNCATE statement instead of a DELETE statement by default PowerExchange now supports DB2 for Linux, UNIX, and Windows 10.1 with Fix Pack 3 for CDC. However, PowerExchange does not support DB on Linux on IBM System z (zlinux) for CDC. Fixes The following table describes fixed limitations: CR During PowerExchange Express CDC for Oracle processing in a RAC on an Oracle SuperCluster system, the PowerExchange Logger for Linux, UNIX, and Windows ends abnormally with the following error message: PWX ORAD: Enabled thread count does not match instance count. Enabled threads = threads : Cluster Instances = number The PowerExchange installation program requires a specific minor version of Java to be installed on UNIX If a data map for a PowerExchange target defines field delimiters, a PowerCenter session that writes to the target places an extra field separator and field delimiter at the end of the file During PowerExchange Oracle CDC with LogMiner, the PowerExchange Logger for Linux, UNIX, and Windows and PowerCenter real-time CDC sessions fail with error message PWX This problem occurs if a SQL application uses the Oracle OLAP unstri function to convert text data to the national character set for a source table. PWX-RLN

4 During PowerExchange Express CDC for Oracle processing, the PowerExchange Logger for Linux, UNIX, and Windows fails with the following message: PWX ORAD Info: DML sequence error: KDO_FLAG_F not on and no DML sequence in process This failure occurs after you add a column to a source table by using an ALTER TABLE table ADD column NOT NULL WITH DEFAULT statement. This problem is related to Oracle Bug The IDMS log-based ECCR ends with the following program logic error message when reading IDMS journal files: PWX Program logic error. Prog="DTLAMCSP". Line=6988. P1="UOW Database key unexpected mismatch". P2=-1. An sr4 chain that belongs to a nonregistered, bypassed record was incorrectly associated with a subsequent registered record. This fix removes that sr4 chain before processing subsequent records During DB2 for z/os CDC processing, the PowerExchange Logger for MVS might end abnormally with the following error message PWXEDM172507W PWX LOGGER XCF Inte subtask abended with S0C4 This error occurs because the storage queue definition does not account for the longer record lengths After a DB2 for z/os ECCR special start, if the ECCR processes a log record for an update or delete of a table space that did not exist when the ECCR was started, the ECCR abends with message PWXEDM177430E, abend code U3680, and reason code B The PowerExchange Agent might issue the following error message when it uses connection pooling and tries to reactivate a PowerExchange Listener connection after the connection pool times out: PWX Program logic error. Prog="DTLNETAT". Line=985. P1="Error Text: Takesocket failed!, cruntime errno: EDC5121I Invalid argum ent.". P2= When a high volume of changes occur on a DB2 for z/os database within a short period of time, the DB2 for z/os ECCR might end with a SOC9 abend because of an internal error in active module PX During PowerExchange Express CDC for Oracle processing, the PowerExchange Logger for Linux, UNIX, and Windows ends abnormally because of a problem with processing a backout of a DML trigger sequence When a PowerCenter PWXPC session name includes a Turkish character, the session fails with a series of error messages that indicate a conversion error The DTLURDMO utility fails to copy Microsoft SQL Server capture registrations when the REG_COPY control statement includes the SELECT DBTYPE=MSS parameter When you use a PowerExchange connection to import metadata for an IBM DB2 for z/os table into Metadata Manager, Metadata Manager generates invalid SQL. 4 PWX-RLN

5 The IDMS log-based ECCR ends with the following program logic error message: PWX Program logic error. Prog="DTLAMCSP". Line= P1="The start of chain pointer is NULL". P2=-1. This internal error occurs because the ECCR encountered an unexpected sequence of journal records During PowerExchange Express CDC for Oracle processing, the PowerExchange Logger for Linux, UNIX, and Windows fails with the following error message: PWX ORAD: PowerExchange encountered a redo log assembly error in a committed transaction During PowerExchange Express CDC for Oracle processing, the PowerExchange Logger for Linux, UNIX, and Windows fails with one of the following error messages: PWX ORAD: Internal error NULL pointer encountered in module PwxOrlCmnCV:3723. PWX ORAD: Column conversion error: [error_code] error_text for Table name=table_name, column[column_number] segment[column_segment] column_name. Detail Type = pwx_datatype, Oracle Type = oracle_datatype. This problem occurs when the source table is defined with the ROWDEPENDENCIES property and is loaded with either SQL*Loader or an INSERT INTO SELECT FROM operation, also called an arrayed insert During PowerExchange Express CDC for Oracle processing, the PowerExchange Logger for Linux, UNIX, and Windows fails with the following error message: PWX ORAD Mbr rac_members: Log parser found unexpected error. Changed Vector Array error The PowerExchange Listener fails with TCP/IP BIND error messages. The messages indicate that the IP address is already in use, even though the Listener port is available When you create a PowerExchange environment on i5/os, if you specify a value other than *LOCAL for the Remote DB Directory Entry (RMTRDBDIRE) parameter, the command fails to create the SQL package that is used to access the remote database and the environment is not created During PowerExchange Express CDC for Oracle processing, the PowerExchange Logger for Linux, UNIX, and Windows fails with the following message: PWX ORAD: Column conversion error NULL value found for column that is not nullable. This problem might occur if you use Oracle or with the COMPATIBLE parameter set to the current version. This problem is related to Oracle Bug , which is fixed in the Oracle patch set If you delete multiple i5/os libraries that contain DB2 for i5/os table instances that use the same structure and journal and then add back these same libraries, the SNDPWXJRNE request for the add-library operation fails to update the CDC interest list. No warning message is issued The SNAPSHOT command of the DTLUCUDB utility fails with an internal error when processing DB2 for Linux, UNIX, and Windows source tables that were created with both the VALUE COMPRESSION clause for value compression and the COMPRESS YES clause for row compression. In the SYSIBM.SYSTABLES table, the COMPRESSION column has a value of B for these tables. PWX-RLN

6 During DB2 for Linux, UNIX, and Windows CDC processing, the PowerExchange Logger for Linux, UNIX, and Windows might fail with error message PWX when processing a ROLLBACK on an update operation When you view DB2 for z/os data in Informatica Developer with a DB2 for z/os connection that specifies a valid PowerExchange passphrase, the following error message is issued: PWX Value specified for parameter "ARRAY_SIZE" is out of range. Position 285. Value "0" If a PowerExchange netport job fails and you close the PowerExchange Navigator, PowerCenter, or another Informatica client application that uses the netport, the PowerExchange Listener stops accepting new connections. However, if the client times out, the Listener responds properly If you use the Microsoft SQL Server 2012 Native Client and import PowerExchange extraction maps into PowerCenter to define a SQL Server source that includes columns with the date datatype, CDC sessions that include the source fail with multiple database errors. The error messages indicate a datatype conversion error The resources folder for the createdatamaps utility, which contains the DatamapGeneration.xsd schema file and examples, is missing from the installation You can execute a stored procedure that is not qualified with a schema name in a Stored Procedure transformation in a bulk data movement mapping by using the Library List attribute of the PowerCenter DB2i5OS relational connection. However, if that stored procedure is used with multiple schemas, the workflow fails In a PowerCenter workflow that performs multiple-record writes, if you select Filter Before for the Offload Processing attribute for a source NRDB application connection, PowerExchange disables offload processing instead of changing the setting to Filter After. PowerExchange performs the processing that failed to be offloaded on the z/os source system. Also, if you select Filter After for the Offload Processing attribute for a source NRDB application connection in a PowerCenter workflow that performs multiple-record writes to an IMS unload file, core dump errors might occur on HP-UX 64-bit Itanium and Solaris 64-bit SPARC systems If a DB2 for Linux, UNIX, and Windows source table is altered by an ALTER TABLE statement that contains both ADD COLUMN and DROP COLUMN operations during CDC processing, the CDC session fails with the following message: PWX API call CAPDM_ColumnCreate returned An internal PowerExchange Agent buffer was expanded to make DB2 for z/os change data capture processing more efficient. Review the Release Notes of previous releases for information about previous fixed limitations. EDP Patches in The PowerExchange and Enterprise Data Propagation (EDP) products have some code in common. Although the EDP product is no longer sold, Informatica occasionally issues maintenance patches for 6 PWX-RLN

7 existing customers. The EDP patches that affect the common code are incorporated into PowerExchange releases and hotfixes. The following table lists the EDP patches that are included in PowerExchange 9.6.1: EDP Patch Number P P P P Patch Title LOGGER: BLANK UOWID IN DB2 MSG / ADD -SEL ENDRBA CCD: DB2 ECCR MSG PROBLEMS PWXEDM CCD: DIAGNOSTICS FOR IFI READS RC 00E60863 CCD: ENHANCE ECCR DIAGNOSTICS P CCD: PWXEDM177430E IN SPECIAL START W/ USEDIR P P P P P CCD: ABEND S0C9 AT OFFSET 0X2F8 IN PX CCD: MULTIPLE PWXEDM177413/414 DURING WARM START LOGGER: INSTRUMENT EXPANDED ECCR INFO CCI: IMS V13 SUPPORT AGENT: INCREASE INTERNAL AGENT- COMMUNICATION BUFFER SIZE PowerExchange Installation and Upgrades Follow the procedures in the PowerExchange Installation and Upgrade Guide for a full or upgrade installation. Before you begin, verify that PowerExchange supports your operating system and database versions. For more information about PowerExchange software requirements, also see the PowerExchange Installation and Upgrade Guide. Upgrade Considerations Updated Components in the IMS Synchronous ECCR CRG.LOAD Library If you upgrade to from an earlier release that does not include patch P638444, the PowerExchange CRG.LOAD library for IMS synchronous CDC does not contain the latest available version of the BMC Software CHANGE RECORDING FACILITY and DATABASE INTEGRITY PLUS components. If you use the CRG software, after you upgrade to 9.6.1, run the CRGUMOD or CRGCLINK job in the hlq.samplib library again to install DBRC modifications. Otherwise, events such as abends might cause change capture to fail in the DLIODDCx module when the IMS synchronous ECCR tries to capture PWX-RLN

8 changes for a source segment. After you run the CRGUMOD or CRGCLINK job, restart the IMS control region. Important: If you have a supported version of the BMC Software CHANGE RECORDING FACILITY or DATABASE INTEGRITY PLUS product, use the BMC Software product instead of the CRG software. In this case, you do not need to run the CRGUMOD or CRGCLINK job. Ensure that the BMC Software product version matches or is later than the minimum BMC version that PowerExchange supports for your IMS version. Expanded PowerExchange Agent Buffer Size for DB2 for z/os ECCR Processing PowerExchange expanded the size of a PowerExchange Agent internal buffer to make DB2 for z/os ECCR processing more efficient. To use the expanded buffer size, you must perform the following steps when you upgrade to PowerExchange from an earlier release: 1. After you upgrade PowerExchange, issue the PowerExchange Agent DRAIN command to ensure that all PowerExchange Agent tasks have completed processing before you shut down the Agent address space. Use the following syntax: cmd_prefix DRAIN The cmd_prefix variable is the command prefix that is specified in the AGENTCTL member of the RUNLIB library or the AGENTID parameter value in the AGENTCTL member. 2. Issue the PowerExchange Agent SHUTDOWN COMPLETELY command to shut down the Agent address space and delete the data space that contains the buffer. Use the following syntax: cmd_prefix SHUTDOWN COMPLETELY Known Limitations Attention Oracle and SQL Server Users: If you use PowerExchange with Oracle or Microsoft SQL Server sources, make sure that you read known limitations and for workarounds to application buffer size issues that can cause data loss. 8 PWX-RLN

9 The following table describes known limitations: CR A PowerCenter workflow might fail with a core dump under the following circumstances: - You selected Confirm Write On for the Write Mode attribute of a target PowerExchange connection. - You specified a value greater than 0 for the Stop on errors property on the Config Object tab for the session. - The number of errors reaches the Stop on errors limit. If a core dump occurs, contact Informatica Global Customer Support to request an EBF for this problem. Note: This problem does not affect workflows with DB2 targets that use connection sharing In a PowerCenter workflow, if a PowerExchange Microsoft SQL Server or Oracle source on Linux, UNIX, or Windows contains a single row that has a length greater than the application buffer size (APPBUFSIZE), the workflow fails. Existing workflows are not affected unless either the data length changes or you modify the workflow, such as to add another source that contains a row with a length greater than APPBUFSIZE. When you add a source table to a new or existing workflow, use one of the following workarounds to avoid this error: - In the DBMOVER configuration file, specify an APPBUFSIZE value that is greater than the length of the row. - In the PWX Override connection attribute, specify a value for the APPBUFSIZE option that is greater than the row size In a PowerCenter workflow that writes variable-length rows to a PowerExchange Microsoft SQL Server or Oracle target on Linux, UNIX, or Windows with a Write Mode connection attribute of Asynchronous with Fault Tolerance, if PowerExchange dynamically resizes the application buffer on the target platform, you might experience data loss. When PowerExchange dynamically resizes the application buffer, it issues message PWX Existing workflows are not affected unless the data row length increases or you modify the workflow, such as to add another target that contains a row with a length greater than APPBUFSIZE. When you add a target table to a new or existing workflow, use one of the following workarounds to avoid this error: - In the DBMOVER configuration file, specify an APPBUFSIZE value that is greater than the maximum row length. - In the PWX Override connection attribute, specify a value for the APPBUFSIZE option that is greater than the maximum row length A PowerCenter or earlier workflow that uses a PowerExchange ODBC connection to connect to a source or target fails on an AIX or zlinux system. Workaround: Use a PWXPC connection instead of a PowerExchange ODBC connection If you run a workflow that writes to a PowerExchange NRDB target using high-precision processing in Unicode mode and the character size of the Integration Service code page is greater than that of the target connection code page, an internal memory overflow can occur. The error occurs during the processing of high-precision numeric fields. For example, this situation can occur when the Integration Service uses a multibyte code page such as UTF-8 and the target connection uses a single-byte code page such as MS1252. To avoid this error, use one of the following workarounds: - Run the workflow in ASCII mode. - Use an Integration Server code page with a character size that is not greater than that of the target connection code page. - Disable high-precision processing in the workflow. Note: An EBF that corrects this issue will be available shortly after the PowerExchange release.contact Informatica Global Customer Support for more information about the EBF. PWX-RLN

10 If a PowerCenter bulk data movement session processes an SEQ data map with a variable-length data file of type VS, you must specify at least bytes (144 KB) for the GSBUFSIZE value in the DBMOVER configuration file. A data file of type VS is a variable-length stream data file without record boundaries On an IBM AIX machine, you cannot run the PowerExchange Listener or PowerExchange Logger as a service in the Informatica domain if the domain is enabled for TLS network authentication. The PowerExchange Listener and PowerExchange Logger must run as standalone tasks. Therefore, in the DBMOVER configuration file, specify a node_name instead of a service_name in the NODE statement for the AIX machine PowerExchange changes that support enhancements to DB2 uncached lookup performance might require a larger initial APPBUFSIZE value. When the application buffer size is too small, workflows fail with message PWX-01277, which recommends a larger APPBUFSIZE value. Workarounds: - If the Write Mode connection attribute is set to Confirm Write On, include the APPBUFSIZE option in the PWX Override connection attribute for the DB2 lookup or target connection. The required application buffer size depends on the number of columns in a DB2 target table or DB2 lookup table. For suggested values, see Additional Information for Known Limitation on page To revert to pre behavior for DB2 uncached lookups, include the CONNSHARE=N option in the PWX Override connection attribute A PowerCenter bulk data movement session receives Adabas response code 9 subcode 15 errors when inserting records into an Adabas target. However, the PowerCenter Workflow Monitor reports that the session succeeded If you run a PowerCenter session that performs a multiple-record write to a GDG target file, the CREATEFILE command that you specify in the Pre SQL session property creates three GDG versions instead of one In PowerCenter Designer, if you use the Import from PowerExchange option to import a DB2 for Linux, UNIX, and Windows extraction map for a source that has long table and column names, some column names might not be displayed or long column names might be truncated to 74 characters without any warning or error message. Alternatively, if you use the Import from PowerExchange option to import table definitions from the DB2 catalog for a source or target table that has table or column names longer than 80 characters, Designer displays a message that indicates the table name or column name is too long and the import fails When you try to import a very large data map for a nonrelational data source into PowerCenter Designer, the import might fail. Workaround: Instead of creating a multiple-record data map, create a separate data map for each source record When you import a COBOL copybook that contains REDEFINES clauses into the PowerExchange Navigator, the field named FILLER_REDEF_1 might be created in certain cases if the calculation of subgroup lengths is not performed correctly If a distribution key that has multiple columns was used to partition a source table that is included in a PowerCenter session, the session log shows an incorrect number of requested and applied update operations A PowerCenter session that uses a PWX DB2LUW connection to write data to a target fails if the target table metadata contains non-ascii characters. 10 PWX-RLN

11 After a PowerCenter upgrade from version to or later, some workflows for PowerExchange CDC sessions fail with an error that indicates a source connection for the PowerExchange CDC reader was not found. The session reads connection information for the first source in the mapping instead of the intended source because the upgrade changed the order in which sessions read connection definitions. Workaround: Define a connection for each source in the mapping When you specify a SQL override that includes complex SQL such as the IN keyword for an i5/os source or target in a PowerCenter session, the session fails If you import source or target tables that contain columns with the datatype of graphic, vargraphic, or long vargraphic from PowerExchange into PowerCenter Designer, the columns are imported with character datatypes. Workaround: After you import the table definition, edit the datatypes in PowerCenter Designer. However, if you import a CDC extraction map, you cannot edit the datatypes If you import a table for which the metadata contains non-ascii characters into the PowerExchange Navigator and specify UTF-8 for the code page, the Navigator does not identify the primary key In Informatica Developer or Informatica Analyst, enterprise discovery fails to list an IBM DB2 for z/os or DB2 for i5/os connection after you perform the following steps: 1. Define the DB2 for z/os or DB2 for i5/os connection in the Developer tool. 2. Create an enterprise discovery profile with Informatica Data Explorer. 3. Select the tables to use with the DB2 connection. 4. Run the enterprise discovery profile. Workaround: Import the tables into the Model repository. You can then use the tables in enterprise discovery In the PowerExchange Navigator, some attempts to create an Oracle registration group or personal metadata profile might fail with a core file and no PowerExchange error message. Workaround: To prevent the failure, enable query access on the Oracle V$INSTANCE view. Use the following GRANT statement: GRANT SELECT ON "PUBLIC"."V$INSTANCE" TO "navigator_user"; If you run the LISTTASK command of the DTLUTSK utility, tasks that use pooled connections do not display the correct access method or mode When a PowerCenter workflow runs an IDMS netport job in Central Version (CV) mode, such as when performing a lookup on an IDMS data source, and delays occur in processing the source data or performing other lookups, the netport job might return IDMS error code This error occurs when no activity has occurred in the netport job for the length of the CV internal timeout and the bind run unit has expired. Workaround: To disable IDMS timeouts, specify the following IDMS System Generation parameters: - CHKUSER TASK IS number_of_tasks - EXTERNAL WAIT IS FOREVER If you use the createdatamaps utility to create a data map that imports metadata from a COBOL copybook that contains dollar, decimal, or exponential values in a PICTURE clause, the utility reports an error and fails to create the data map. Workaround: Use the PowerExchange Navigator to create the data map. PWX-RLN

12 If you use PowerCenter to write updates to a PowerExchange target and an update fails, the PowerCenter session log displays an incorrect count of rows rejected in the Load Summary. An update might fail, for example, because the target record does not exist If you synchronize a nonrelational data object in Informatica Developer after you rename a column in the associated PowerExchange data map, the renamed column is not in the same sequence in the Developer tool as it is in the PowerExchange Navigator If you run the DTLUCBRG utility to create a capture registration for a data map that does not exist in the DATAMAPS member on z/os, the utility fails to report the error and does not create a registration. Workaround: Ensure that the required data maps exist in the DATAMAPS member before running the DTLUCBRG command When you import a copybook that contains certain German-language characters, such as ' ß' or vowels with umlauts, into a PowerExchange data map, the lines that contain these characters are not imported. Workaround: If these German-language characters appear within comments, edit the comments to remove or replace the characters If you use an Informatica Data Services SQL query to view DB2 for z/os fields that have the TIME datatype, the Data Viewer displays the result as a time stamp. The date portion of the time stamp is incorrectly populated with the current date instead of the default date of When you create a data map in the PowerExchange Navigator, if you import a PL/I copybook and enter Start and End values that define a column range that includes line sequence numbers, the PowerExchange Navigator might add an extraneous "NEW_RECORD " record and then either fail or produce unpredictable results. Workaround: When importing a PL/I copybook, do not define a column range or accept a default column range that includes line sequence numbers In Informatica Developer, if you specify the Library List property for a DB2 for i5/os connection and the table name in the SQL that is submitted on the connection is enclosed in quotation marks to escape special characters, PowerExchange does not find the i5/os files to process. The quotation marks might have been generated as a result of the SQL Identifier Character and Support Mixed-case Identifiers connection properties or manually specified in the SQL. Workaround: For table names that do not contain special characters, set the SQL Identifier Character connection property to None and do not select the Support Mixed-case Identifiers connection property If you set the Location connection attribute to Local when importing metadata for PowerExchange sources into PowerCenter, the import operation might fail. This problem occurs for DB2 for Linux, UNIX, and Windows, Microsoft SQL Server, Oracle, Sybase, and PowerExchange ODBC sources. Workaround: In the Location connection attribute, enter the node name that is defined in the NODE statement for the PowerExchange Listener on the source system If you create an alias for an i5/os physical file and import the object into Informatica Developer, the Developer tool does not successfully import the metadata for the object. Workaround: Import the physical file and then rename it to match the alias. 12 PWX-RLN

13 When you try to add a capture registration for a Microsoft SQL Server data source, the PowerExchange Navigator fails with a license key error. This failure occurs even if the PowerExchange Listener is running with a license.key file that includes Microsoft SQL Server CDC as a data source. Workaround: Open a Service Request of Type=Shipping, and ask for a PowerExchange Navigator license key that includes SQL Server CDC If you run a PowerCenter session that includes PWXPC connections and a VSAM KSDS data source and target and the source file contains packed decimal fields with spaces, the session fails. Workaround: Enable data checking for packed decimal fields, and select the option to skip bad records To create a source or target definition in PowerCenter, you can import a VSAM source or target from PowerExchange. If you select more than one source or target object and do not select Multi-Record Datamaps, the resulting source or target objects have no columns. Workaround: Import multiple-record sources or targets one at a time When you run a CDC session that includes a password-protected Adabas data source and uses the CAPXRT access method and offload processing, the session fails When you run a Data Services mapping that writes data to an Adabas file, the mapping might fail with a series of error messages that indicate an SQL insert failure. This problem occurs when the number of records that are being written exceeds the number or records that the Adabas buffer can hold. You cannot specify a commit interval to control it. Workarounds: Consider increasing the NISNHQ and NH nucleus parameter values. Also, adjust the size of the protection area of the Work data set to accommodate the possibility that one transaction adds 10,000 records When you run a Data Services mapping that includes an Update Strategy transformation and writes data to a nonrelational target, the mapping might fail with an error message. The message indicates that the target table has no keys, even though the data map for the target has keys defined The PowerExchange Listener CLOSE FORCE command does not cancel active Listener subtasks on i5/os and z/os. After a CLOSE FORCE command is issued, PowerCenter workflow tasks shut down after they read the next record. However, PowerExchange utility tasks and PowerExchange row test tasks remain active. The PowerExchange Listener task remains active until the utility and row test subtasks are shut down. Workaround: Use operating system commands to cancel the PowerExchange row test or PowerExchange utility tasks and the associated PowerExchange Listener task. Additional Information for Known Limitation If you set the Write Mode connection attribute to Confirm Write On for a DB2 bulk data movement session and get error message PWX-01277, increase the APPBUFSIZE value based on the number of columns in the DB2 target table. PWX-RLN

14 The following table shows the recommended APPBUFSIZE settings, depending on the maximum number of columns in the DB2 target table, to ensure that the workflow does not generate message PWX-01277: Maximum Number of Columns Recommended APPBUFSIZE Value Informatica Global Customer Support You can contact a Customer Support Center by telephone or through the Online Support. Online Support requires a user name and password. You can request a user name and password at The telephone numbers for Informatica Global Customer Support are available from the Informatica web site at 14 PWX-RLN