PowerExchange HotFix Installation Overview

Transcription

1 Informatica Corporation PowerExchange Version and Hotfixes Cumulative Release Notes November 2010 Copyright (c) 2010 Informatica Corporation. All rights reserved. Contents PowerExchange HotFix Installation Overview... 1 PowerExchange HotFix Fixes First-Time and Upgrade Installation Files HotFix Installation Files Known Limitations PowerExchange HotFix PowerExchange Fixes First-Time and Upgrade Install Files HotFix Install Files PowerExchange Known Limitations PowerExchange Base Release... 7 PowerExchange Fixes PowerExchange Closed Enhancement Requests PowerExchange Known Limitations Informatica Global Customer Support This document compiles the release notes that Informatica has issued to date for PowerExchange and its hotfixes. The release notes are listed from latest to earliest with the base release notes last. PowerExchange HotFix Installation Overview To install a PowerExchange hotfix, you can complete a first-time installation, an upgrade installation, or a hotfix installation. To determine which type of installation to perform, use the following criteria: If PowerExchange is not currently installed, complete a first-time installation. Use the install files that are provided for a first-time or upgrade installation. PWX_RNC_901_0002 1

2 If a PowerExchange version earlier than is installed, complete an upgrade installation. Use the install files that are provided for a first-time or upgrade installation. If PowerExchange or a hotfix is currently installed, complete a hotfix installation. Use the hotfix install files. PowerExchange hotfixes are cumulative. The latest hotfix includes changes from all previous hotfixes on the current version. These release notes list the names of the install files to use by installation type and operating system. If you perform a first-time or upgrade installation of PowerExchange on a Linux, UNIX, or Windows system, you can use a localized version of the PowerExchange installer. When you run the installer, you get localized PowerExchange messages. On Windows, you also get a localized version of the PowerExchange Navigator. If you copy the localized help files to the helpdoc folder, you can get localized help through the PowerExchange Navigator. For more information about each installation procedure, see the latest PowerExchange Installation Guide. For upgrade and migration considerations and software requirements, see the PowerExchange Planning Guide for Installation and Migration. PowerExchange HotFix 2 Fixes When you run a database row test for an Adabas data map, PowerExchange might log error message PWX-00220, indicating that an error occurred in the dynamic allocation of an Adabas data set. First-Time and Upgrade Installation Files Use the following files from the software folder of the CD image to perform a first-time or upgrade installation of the PowerExchange software, including HotFix 2: Operating System AIX (64-bit) HP-UX Itanium (64-bit) i5/os Linux Itanium (64-bit) Linux x86 (32-bit) Linux x86 (64-bit) Solaris (64-bit) pwx901_02_aix64.tar pwx901_02_hpux_ipf64.tar pwx901_02_i5os.exe pwx901_02_linux_ipf64.tar pwx901_02_linux32_x86.tar pwx901_02_linux_em64t.tar pwx901_02_solaris_sp64.tar 2 PWX_RNC_901_0002

3 Operating System Windows (32-bit) Windows (64-bit) Windows Itanium (64-bit) z/os pwx901_02_win32_x86.exe pwx901_02_win_x64.exe pwx901_02_winipf64.exe pwx901_02_zos.exe HotFix Installation Files If you have PowerExchange currently installed, use the following files from the patches folder of the CD image to install HotFix 2: Operating System AIX (64-bit) HP-UX Itanium (64-bit) i5/os Linux Itanium (64-bit) Linux x86 (32-bit) Linux x86 (64-bit) Solaris (64-bit) Windows (32-bit) Windows (64-bit) Windows Itanium (64-bit) z/os pwx901_hotfix2_aix64.tar pwx901_hotfix2_hpux_ipf64.tar pwx901_hotfix2_i5os.exe pwx901_hotfix2_linux_ipf64.tar pwx901_hotfix2_linux32_x86.tar pwx901_hotfix2_linux_em64t.tar pwx901_hotfix2_solaris_sp64.tar pwx901_hotfix2_win32_x86.exe pwx901_hotfix2_win_x64.exe pwx901_hotfix2_winipf64.exe pwx901_hotfix2_zos.exe Known Limitations If you have multiple CAPI connection definitions in the dbmover.cfg file on the PowerCenter client and try to preview data in Designer for a remote source, the preview operation might fail. Workaround: In the dbmover.cfg file, remove or comment out all of the CAPI connection definitions except the one for the remote source. Then try to preview data again If you enable offload processing for a real-time extraction session for which you specify an i5/os library or file override, the sessions fails. PWX_RNC_901_0002 3

4 If you use the DTLURDMO utility REG_COPY statement to copy Microsoft SQL Server capture registrations on a 32-bit Windows machine, an unhandled win32 exception might occur in DTLURDMO.exe. This error occurs when the REG_COPY operation tries to use a MODIFY statement that includes the MSSOPTS parameter with the DBNAME option. You can successfully perform this type of REG_COPY operation on a 64-bit Windows system PowerExchange cannot use SSL when running with a Linux 64-bit operating system on an Itanium machine. PowerExchange issues the following error message: PWX Can't read certificate chain file. Key=key PowerExchange is not able to read DB2 for z/os image copies for partitioned table spaces. In this situation, PowerExchange issues the following message: PWX Dictionary Page found. Image copy reading not supported for compressed TS If the lowest level segment in an IMS database is not keyed, the Update all matching segments option on the IMS Options tab of the Table Properties dialog box in the PowerExchange Navigator does not work. Workaround: Do not select the Update all matching segments option if you have non-keyed segments When concatenated key (CCK) fields are passed from IMS to PowerExchange to create SSAs, PowerExchange does not use a lower-level CCK field unless you provide the CCK of the ROOT. The absence of the root key causes unqualified GN calls to scan IMS databases. Workaround: Always specify the key of the root When a DB2 for z/os bulk data movement operation fails, PowerExchange might not write an error message to the PowerExchange message log or PowerCenter session log to notify you of the situation. The PowerCenter session appears to complete successfully. PowerExchange HotFix 1 PowerExchange Fixes (9.0.1 HotFix 1) CDC sessions with DB2 for i5/os sources and PWX CDC Real-Time application connections might fail if you use offloading and override DB2 library or journal names. This failure can occur in continuous extraction mode with PowerExchange Condense or in real-time extraction mode The DB2 for z/os EC abends with message PWXEDM177588E when reading a table from a partitioned table space that is not EA-enabled The IMS log-based EC ends abnormally with the error message PWX when processing an IMS RECON data set that contains an entry for a SLDS data set with the name of "COMPRESSED DATA SET." The IMS log-based EC ends abnormally with the error message PWX when processing an IMS RECON data set that contains spanned records of type x'05' CDC sessions with Oracle sources might fail with error message PWX if the sources include small-sized FLOAT columns. The failure occurs because PowerExchange incorrectly registers the FLOAT columns as NUM32 columns and then detects too many decimal point characters for these columns Memory corruption occurs on the source system during CDC sessions that use an event table with a registration tag name longer than 18 bytes. 4 PWX_RNC_901_0002

5 PowerExchange Client for PowerCenter (PWXPC) workflows that include source definitions based on PowerExchange data maps with VARBIN columns fail to load VARBIN data to the targets. However, the workflows successfully load data for columns with other datatypes When Informatica Data Explorer sends a request for data to PowerExchange using a PowerExchange ODBC connection, PowerExchange returns message PWX-07015, which indicates a column fetch error. The error occurs because PowerExchange detects a column length error in the SQL call A CAPXRT database row test on an extraction map for a DB2 for i5/os table fails with message PWX when the table includes DATE, TIME, or TIMESTAMP columns that have long mixed-case column names that are enclosed in double quotation marks A bulk data movement session that uses group source processing and a PWX NRDB Batch application connection fails to read the last block of data for a VStream file that has multiple record types A bulk data movement session that uses a PWX NRDB Batch connection fails to load data to a VSAM RRDS data set when the Insert Only session property is selected. PowerExchange issues the following error message: PWX AMVSM UPDATEMODE not supported with RRDS access method A CAPXRT database row test of an Adabas source that includes MU and PE fields fails with a SOC4 abend code In the PowerExchange Navigator, when you open or create a personal metadata profile that includes metadata for an Oracle materialized view, the metadata request fails with multiple error messages in the PowerExchange message log and PowerExchange Navigator Bulk data movement workflows that load data to VSAM RRDS data sets fail when the Write Mode attribute on the PWX NRDB Batch application connection is set to Confirm Write Off On z/os, output from the PowerExchange Listener LISTTASK command in the JES job log might contain truncated PowerExchange messages. Truncation occurs at 125 characters in long messages such as PWX First-Time and Upgrade Installation Files (9.0.1 HotFix 1) Use the following files from the software folder of the CD image to perform a first-time or upgrade installation of the PowerExchange software, including HotFix 1: Operating System AIX (64-bit) HP-UX Itanium (64-bit) i5/os Linux Itanium (64-bit) Linux x86 (32-bit) Linux x86 (64-bit) Solaris (64-bit) Windows (32-bit) pwx901_01_aix64.tar pwx901_01_hpux_ipf64.tar pwx901_01_i5os.exe pwx901_01_linux_ipf64.tar pwx901_01_linux32_x86.tar pwx901_01_linux_em64t.tar pwx901_01_solaris_sp64.tar pwx901_01_win32_x86.exe PWX_RNC_901_0002 5

6 Operating System Windows (64-bit) Windows Itanium (64-bit) z/os pwx901_01_win_x64.exe pwx901_01_winipf64.exe pwx901_01_zos.exe HotFix Installation Files (9.0.1 HotFix 1) If you have PowerExchange currently installed, use the following files from the patches folder of the CD image to install HotFix 1: Operating System AIX (64-bit) HP-UX Itanium (64-bit) i5/os Linux Itanium (64-bit) Linux x86 (32-bit) Linux x86 (64-bit) Solaris (64-bit) Windows (32-bit) Windows (64-bit) Windows Itanium (64-bit) z/os pwx901_hotfix1_aix64.tar pwx901_hotfix1_hpux_ipf64.tar pwx901_hotfix1_i5os.exe pwx901_hotfix1_linux_ipf64.tar pwx901_hotfix1_linux32_x86.tar pwx901_hotfix1_linux_em64t.tar pwx901_hotfix1_solaris_sp64.tar pwx901_hotfix1_win32_x86.exe pwx901_hotfix1_win_x64.exe pwx901_hotfix1_winipf64.exe pwx901_hotfix1_zos.exe PowerExchange Known Limitations (9.0.1 HotFix 1) If you use the DTLURDMO utility REG_COPY statement to copy Microsoft SQL Server capture registrations on a 32-bit Windows machine, an unhandled win32 exception might occur in DTLURDMO.exe. This error occurs when the REG_COPY operation tries to use a MODIFY statement that includes the MSSOPTS parameter with the DBNAME option. You can successfully perform this type of REG_COPY operation on a 64-bit Windows system If you have multiple CAPI connection definitions in the dbmover.cfg file on the PowerCenter client and try to preview data in Designer for a remote source, the preview operation might fail. Workaround: In the dbmover.cfg file, remove or comment out all of the CAPI connection definitions except the one for the remote source. Then try to preview data again. 6 PWX_RNC_901_0002

7 PowerExchange cannot use SSL when running with a Linux 64-bit operating system on an Itanium machine. PowerExchange issues the following error message: PWX Can't read certificate chain file. Key=key PowerExchange is not able to read DB2 for z/os image copies for partitioned table spaces. In this situation, PowerExchange issues the following message: PWX Dictionary Page found. Image copy reading not supported for compressed TS If the lowest level segment in an IMS database is not keyed, the Update all matching segments option on the IMS Options tab of the Table Properties dialog box in the PowerExchange Navigator does not work. Workaround: Do not select the Update all matching segments option if you have non-keyed segments When concatenated key (CCK) fields are passed from IMS to PowerExchange to create SSAs, PowerExchange does not use a lower-level CCK field unless you provide the CCK of the ROOT. The absence of the root key causes unqualified GN calls to scan IMS databases. Workaround: Always specify the key of the root When a DB2 for z/os bulk data movement operation fails, PowerExchange might not write an error message to the PowerExchange message log or PowerCenter session log to notify you of the situation. The PowerCenter session appears to complete successfully. PowerExchange Base Release PowerExchange Fixes (9.0.1) If you import a COBOL copybook when creating a data map in the PowerExchange Navigator, PowerExchange incorrectly creates a dummy column named FILLER_REDEF_1 if it encounters a REDEFINES clause within an OCCURS clause. When you run a database row test on the data map, an error occurs A bulk data movement session that writes to a VSAM relative record data set might fail with message PWX-00784, indicating that update mode is not supported, even though the transaction type for the PWX NRDB Batch connection is defined as insert only During a cold start of the Datacom table-based EC, an inflight dummy UOW (FFFFFFFFFFFFFFFFF0000) causes the EC to fail For DB2 for i5/os CDC in real-time extraction mode, PowerExchange incorrectly sets the value of the DLT_CAPXRRN column in many change records to when offload processing is enabled PowerExchange issues error message PWX during an Oracle CDC session that extracts changes in continuous extraction mode from PowerExchange Logger for Linux, UNIX, and Windows log files If you try to register a DB2 for i5/os table that was created in the i5/os SQL interface and has a long file name in mixed case, the PowerExchange registration process fails. PowerExchange expects the long file name to be in uppercase When you run a PowerCenter session with a flat file target and a z/os source that uses a German code page for the source application connection, fields that are defined as ZONED and UNZONED are converted to zeros Oracle sends backout records for a failed update to the PowerExchange UOW Cleanser for CDC in an order that PowerExchange does not expect. As a result, extraction processing stops. PWX_RNC_901_0002 7

8 When a CDC session tries to extract changes from a PowerExchange Logger for Linux, UNIX, or Windows log file in continuous extraction mode, it might fail with error messages PWX and PWX because of unnecessary checking of sequence information In a PowerExchange Navigator database row test and in a PowerCenter session run, Hebrew characters are displayed in reverse order During a change from daylight savings time to standard time, PowerExchange Condense processing fails with the message PWX-10232, which indicates an internal error occurred The default DBTYPE for database row tests should be CAPXRT The IDMS EC abends with message PWX when processing a journal. The message indicates the following program logic error: "UOW Hash Table - Unexpected primary AREA duplicate for run unit id." The DB2 for z/os EC abends with message PWXEDM177588E when reading the catalog for a table space defined in a storage group that uses an extended-addressing-enabled SMS data class When a PowerCenter workflow includes a Lookup transformation for a PowerExchange source with a!= condition in a SQL WHERE clause, PowerExchange issues an error message indicating that the!= condition is not supported The IDMS EC abends with an EC6 error code, indicating a CPU usage timeout, when processing a journal During DB2 for z/os EC processing, share locks that the DB2 IFI306 interface obtains on the catalog, the work table space, and various customer table spaces are not released IMS synchronous CDC processing abends after patch P is applied When the security feature is enabled, that is, the first parameter in the SECURITY statement is set to 1 or 2 in the DBMOVER file for both the source and target PowerExchange Listeners, the DTLURDMO utility requires the same USER and PASSWORD values for both the source and target The PRESTLIB JCL that you run when installing a hotfix on z/os does not reflect changes to DB2 for z/os members in the DBRM library. As a result, a bind error occurs Some SQL Server registrations that are created with the DTLUCBRG utility do not appear in the PowerExchange Navigator After you restart a PowerExchange Logger for Linux, UNIX, and Windows process that ended abnormally, the process fails with message PWX-10232, which indicates a sequence error Workflows might fail to restart when RESTART1=CURRENT_RESTART and RESTART2=CURRENT_RESTART are specified in the restart token file Multiple CDC sessions that use the CAPXRT access method and have Oracle sources might write the Oracle catalogs to the log files at the same time, resulting in reduced performance and unnecessary write activity When an Oracle database uses a Japanese code page, Oracle messages that indicate a connection error and are issued during a PowerCenter session are not translated correctly A memory leak occurs during IMS synchronous CDC processing when units of work (UOWs) from an external subsystem are mixed with BMP processing in a DBCTL environment PowerExchange does not support IMS 7 for CDC processing If you use PowerExchange Condense or the PowerExchange Logger for Linux, UNIX, and Windows and set its NO_DATA_WAIT parameter to a time interval, in seconds, that is less than the FILE_SWITCH_VAL time interval, in minutes, condense processing might become erratic. 8 PWX_RNC_901_0002

9 The PowerExchange Condense task might end abnormally on i5/os if you receive the following message and enter a response other than Y or N: PWX: Error 1 on Delete of file PWX860CND2CHKPT(V0). Retry? (Y/N) If you use PWXPC with an extraction map source that contains BI or CI columns and attempt to extract change data from full condense files that contain before and after images, PowerExchange incorrectly issues message PWX PowerExchange Closed Enhancement Requests (9.0.1) Define the TIMEZONE statement in the DBMOVER configuration file to read or write Adabas date-time values in your local time for bulk data movement sessions. This statement applies only to Adabas data sources or targets that include datetime fields for which the Adabas TZ option is specified in the field definitions , For an Adabas source, a data map for which you import field metadata from an FDT can include mixed-case field names. Previously, the Adabas field names in data maps were in uppercase only If you configure a cache size, PowerExchange caches NRDB data maps on the system where they are used by a single PowerExchange Listener, or by multiple PowerExchange Listener, netport, and batch jobs If you use Oracle materialized views, PowerExchange can capture change data from the tables that underlie those views. PowerExchange CDC supports any type of materialized view For DB2 for i5/os CDC sources that include multiple data members, you can populate the DTL CAPXUSER column of each change record with the member name as well as the library and file names. To do so, set the LIBASUSER parameter to M on the AS4J CAPI_CONNECTION statement Bulk data movement sessions for z/os DB2 image copies support uncompressed table spaces in reordered row format The DTLURDMO utility writes the unmasked value of the encrypted password to the PowerExchange log file For a data map record defined for a nonrelational data source, the GetCurrentFileName function gets the name of the source data file. Use this function to determine from which data file the data for a record was read. PowerExchange Known Limitations (9.0.1) Bulk data movement workflows that load data to VSAM RRDS data sets fail when the Write Mode attribute on the PWX NRDB Batch application connection is set to Confirm Write Off. (fixed in HotFix 1) If you use the DTLURDMO utility REG_COPY statement to copy Microsoft SQL Server capture registrations on a 32-bit Windows machine, an unhandled win32 exception might occur in DTLURDMO.exe. This error occurs when the REG_COPY operation tries to use a MODIFY statement that includes the MSSOPTS parameter with the DBNAME option. You can successfully perform this type of REG_COPY operation on a 64-bit Windows system PowerExchange cannot use SSL when running with a Linux 64-bit operating system on an Itanium machine. PowerExchange issues the following error message: PWX Can't read certificate chain file. Key=key. PWX_RNC_901_0002 9

10 PowerExchange is not able to read DB2 for z/os image copies for partitioned table spaces. In this situation, PowerExchange issues the following message: PWX Dictionary Page found. Image copy reading not supported for compressed TS Oracle change data that PowerExchange extracts in conjunction with Oracle LogMiner might be incomplete if you run PowerExchange in an Oracle RAC environment. Oracle LogMiner might not extract all change data when performing continuous mining across log sequences that contain points in time where one or more instances have been stopped or started. As a result, the application of change data to target tables can either fail or be incomplete. Workaround: For information about the problem, refer to Oracle bug number or contact Oracle Support for assistance. Oracle supplies patches to fix this problem for Oracle Oracle has incorporated the fix into Oracle and If the lowest level segment in an IMS database is not keyed, the Update all matching segments option on the IMS Options tab of the Table Properties dialog box in the PowerExchange Navigator does not work. Workaround: Do not select the Update all matching segments option if you have non-keyed segments When concatenated key (CCK) fields are passed from IMS to PowerExchange to create SSAs, PowerExchange does not use a lower-level CCK field unless you provide the CCK of the ROOT. The absence of the root key causes unqualified GN calls to scan IMS databases. Workaround: Always specify the key of the root When a DB2 for z/os bulk data movement operation fails, PowerExchange might not write an error message to the PowerExchange message log or PowerCenter session log to notify you of the situation. The PowerCenter session appears to complete successfully. 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 Use the following telephone numbers to contact Informatica Global Customer Support: North America / South America Europe / Middle East / Africa Asia / Australia Toll Free Brazil: Mexico: North America: Standard Rate North America: Toll Free France: Germany: Israel: Italy: Netherlands: Portugal: Spain: Switzerland: or United Kingdom: or Toll Free Australia: New Zealand: Singapore: Standard Rate India: Standard Rate Belgium: France: Germany: Netherlands: PWX_RNC_901_0002