This document contains important information about PowerExchange HotFix 4.

Transcription

1 Informatica Corporation PowerExchange Version HotFix 4 Release Notes March 2012 Copyright (c) 2012 Informatica Corporation. All rights reserved. Contents Introduction... 1 Fixes... 1 PowerExchange HotFix Installation Overview... 3 First-Time and Upgrade Installation Files HotFix Installation Files Upgrade Considerations... 5 Rebind the DB2 for z/os Plans and Packages Upgrade Consideration for the IMS Synchronous ECCR EDP DB2 Apply Consideration Known Limitations... 6 Documentation Update... 7 Informatica Global Customer Support... 7 Introduction This document contains important information about PowerExchange HotFix 4. 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 Fixes CR If you select Resource Configuration Setting on the Options tab of a PowerExchange Navigator that is localized for Japanese, PowerExchange issues the message, "Attempted an unsupported operation." In addition, certain options, including Network Operation Timeout and Connection Pool Size/Retain, are not displayed While a mapping that contains lookups is running in a reusable DTM process, PowerExchange acquires and retains table intent locks on the database. PWX-RLN-910HF

2 CR With the fix, PowerExchange now releases table intent locks on the database by applying commits for every lookup request Type 1 fallback mappings of code pages are not enabled Starting the PowerExchange Listener from the PowerExchange Listener Service might result in a core dump When PowerExchange tries to initialize the DB2 capture catalog table during the installation process on Linux, UNIX, or Windows, PowerExchange issues an error message indicating that the function invoked is no longer supported If a PowerExchange CDC data source includes an Oracle or Microsoft SQL Server table that has a column name that contains a space, an attempt to import the source definition into the PowerCenter Designer fails Increase the maximum value for the primary space and secondary space parameters to tracks or the equivalent in cylinders on z/os If you enable alternative logging for a z/os data source with a variable-blocked record format, PowerExchange writes a life feed character (0x'15') to the end of each record. This extra character can cause problems with z/os utilities After you install a PowerExchange patch set that includes P513905, a cold or special start of the DB2 ECCR running under DB2 Version 9 new-function mode might abend when attempting to read the page header for the tablespaces containing the catalog and directory tables that the ECCR tracks If you use a third party ODBC or JDBC driver, such as iseries Navigator, to update a DB2 for i5/os table, a database row test for change data returns QUSER for the user name column instead of the user name that you provided to the ODBC or JDBC connection The IMS log-based ECCR might abend after trying to access the RECON data sets If a column in a PowerExchange z/os sequential or VSAM data source is not linked in a PowerCenter mapping, the data for the next linked column is moved to the unlinked column position, resulting in a shift of data when you run a workflow that includes the mapping A PowerCenter session that uses the DB2 LOAD utility to write to a PowerExchange target might fail if the target table contains columns with a BIGINT data type Because of an error in file switch processing, a workflow that includes a DB2 or Microsoft SQL Server CDC data source on Linux, UNIX, or Windows might fail with an error message indicating that the sequence information in the recreated file was greater than expected More efficient segment search arguments (SSA) are needed for PowerCenter mappings to IMS data sources for non-root segments When you extract data using a data map for a sequential data set with variable-length records that originated on a UNIX or Windows system, and the LRECL value for the data set is not greater than the length of the longest record in the UNIX or Windows file, PowerExchange issues an error message that indicates that the calculated field length exceeds the maximum field length If you run the DTLUCBRG utility to replace a capture registration that has version greater than 1 for a Microsoft SQL Server data source, the utility fails to make the replacement and issues a series of error messages In a PowerCenter session with an i5/os data source, PowerExchange uses the default EBCDIC sort sequence even if you specify an override. As a result, PowerCenter transformations such as the Joiner transformation might fail If a session is started with CURRENT_RESTART and processes exactly one UOW, the subsequent restart occurs at the point of the CURRENT_RESTART for the session. The restart token values are updated only after the second UOW is sent to the target. 2 PWX-RLN-910HF4-0001

3 CR Issuing the pwxcmd shutdown command to the PowerExchange Logger for Linux, UNIX, and Windows might result in a core dump or memory corruption When you perform a database row test on Windows, the results of the row test for columns of type CHAR or VARCHAR might be truncated under the following conditions: - A Hebrew code page is installed on the source system. - The source data contains accented European or multibyte Asian characters Setting the POLWAIT parameter in the MSQL CAPI_CONNECTION statement does not reduce the polling frequency on the Microsoft SQL Server source system If you open a sequential data map with the PowerExchange Navigator, open the Data Map Properties dialog box, click the browse button to select a different file name on the SEQ Access Method tab, and select a large Windows file, the Navigator might crash when you later try to re-open the data map In certain network configurations, PowerExchange returns error messages PWX-32700, which indicates that the PowerExchange Listener failed to launch, and PWX-00117, which indicates an IP mismatch Divide Oracapt.sql into functional subset members to enhance the installation process requirements If a PowerCenter session tries to write an overflow of numeric data into an unsigned packed column in a PowerExchange nonrelational target, the workflow completes successfully, but the output rows are not written to the target. The PowerCenter session log does not report error message PWX-00143, indicating that a conversion error occurred When the DB2 ECCR is refreshed after registration changes, it fails with a message indicating that the beginning unit of work occurred out of sequence. In addition, if the ECCR reprocesses DB2 log data for a DDL operation following a warm start, PowerExchange issues an error message indicating that the DB2 ECCR TCAP tables are invalid. PowerExchange HotFix Installation Overview To install a PowerExchange hotfix, you can complete a first-time installation, an upgrade installation, or a hotfix installation. Use the install files that are listed in these release notes by installation type and operating system. 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. 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. Note: If you perform a first-time or upgrade installation 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. PWX-RLN-910HF

4 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. 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 the latest hotfix: Operating System AIX (64-bit) HP-UX Itanium (64-bit) i5/os Linux x86 (32-bit) Linux x64 Opteron, EM64T (64-bit) Solaris SPARC (64-bit) Solaris Opteron, EM64T (64-bit) Windows x86 (32-bit) Windows x64 Opteron, EM64T (64-bit) z/linux z/os File Name pwx910_04_aix64.tar pwx910_04_hpux_ipf64.tar pwx910_04_i5os.exe pwx910_04_linux32_x86.tar pwx910_04_linux_em64t.tar pwx910_04_solaris_sp64.tar pwx910_04_solarisx86_64.tar pwx910_04_win32_x86.exe pwx910_04_win_x64.exe pwx910_04_zlinux.tar pwx910_04_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 4: Operating System AIX (64-bit) HP-UX Itanium (64-bit) i5/os Linux x86 (32-bit) Linux x64 Opteron, EM64T (64-bit) Solaris SPARC (64-bit) File Name pwx910_hotfix4_aix64.tar pwx910_hotfix4_hpux_ipf64.tar pwx910_hotfix4_i5os.exe pwx910_hotfix4_linux32_x86.tar pwx910_hotfix4_linux_em64t.tar pwx910_hotfix4_solaris_sp64.tar 4 PWX-RLN-910HF4-0001

5 Operating System Solaris Opteron, EM64T (64-bit) Windows (32-bit) Windows x64 Opteron, EM64T (64-bit) z/linux z/os File Name pwx910_hotfix4_solarisx86_64.tar pwx910_hotfix4_win32_x86.exe pwx910_hotfix4_win_x64.exe pwx910_hotfix4_zlinux.tar pwx910_hotfix4_zos.exe Upgrade Considerations Rebind the DB2 for z/os Plans and Packages If you perform an upgrade installation, rebind the DB2 plans and packages by submitting the SETUDB2U job. This job runs the XIDDB210 and XIDDB225 jobs. If you do not rebind packages, problems might occur. For example, if you do not rebind the X and X packages, whenever you drop a DB2 table that contains a FIELDPROC, the DB2 ECCR abends. If you do not rebind the X package, the DB2 ECCR commit/rollback processor might not work correctly. Normally, you rebind the DB2 plans and packages as part of the standard upgrade procedure. For more information, see the PowerExchange Installation Guide. If you perform a hotfix installation, you must rebind DB2 plans and packages as follows: Because changes were made to the DBRMXMIT member for PowerExchange HotFix 4, you must rebind the DB2 plan and packages for bulk data movement processing. No changes were made to the DBRM member for PowerExchange HotFix 4. You must rebind the plan used by your DB2 ECCR only if you are installing this hotfix on top of PowerExchange HotFix 1 or earlier. Before you perform the binds, use the PRESTLIB job to restore the members from the hotfix BINLIB library into the hotfix libraries, and copy the supplied replacement members into the DBRMLIB. After you perform a hotfix installation, use one of the following jobs to perform the binds: To rebind the bulk plan only, edit job XIDDB210 to add a job card and submit the job. To rebind the ECCR plan only, edit job XIDDB225 to add a job card and submit the job. To rebind both plans, run job SETUDB2U. This job submits jobs XIDDB210 and XIDDB225. Upgrade Consideration for the IMS Synchronous ECCR The PowerExchange CRG.LOAD library for IMS synchronous CDC contains a new version of the BMC Software CHANGE RECORDING FACILITY and DATABASE INTEGRITY PLUS components. If you use the CRG software, after you upgrade to this hotfix from an earlier release, you must run the CRGUMOD or CRGCLINK job in the hlq.samplib library again. If you performed this task for or an earlier hotfix, you must repeat the task for the current hotfix. Use the hlq.crg.load library as input. PWX-RLN-910HF

6 Otherwise, events such as abends might cause change capture to fail in the DLIODDCx module when the IMS synchronous ECCR tries to capture changes for a source segment. You do not need to perform this action 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. Make sure that the BMC Software product version matches or is later than the minimum supported version for your PowerExchange version. For more information about the CRGUMOD and CRGCLINK jobs and the minimum supported versions for the BMC Software products, see the PowerExchange CDC Guide for z/os. EDP DB2 Apply Consideration PowerExchange HotFix 1 and later includes a fix that also affects the EDP DB2 Apply processes. If you run PowerExchange and EDP from the same set of libraries on z/os and use the EDP DB2 Apply process, you must rebind the DB2 plan for the EDP DB2 Apply process after you upgrade to PowerExchange HF1 or later from PowerExchange To rebind the plan, use the commands in the APDxxxxP and APDxxxxB members of the EDP installation JCL library, where xxxx is the DB2 instance where the DB2 Apply process runs. Known Limitations CR If you include a TRACING statement in the DBMOVER configuration file to enable alternative logging for a PowerExchange data source, a PowerCenter workflow that includes the data source might fail and produce a core dump, if the data source is defined as local After a time change to Daylight Savings Time occurs and the fileswitch command is issued, the CDC Logger for Linux, UNIX, and Windows might shut down and issue a series of error messages 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 If you run a PowerCenter session that includes PWXPC connections, a VSAM KSDS data source, and a VSAM KSDS target, and if 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 A PowerCenter session might fail under the following conditions: - You use a PowerExchange ODBC connection with a VSAM source or VSAM target. - You override the source or target data set name by specifying {dtldsn=output.dsn} at Table Owner. - You run the PowerExcxhange Listener on the z/os system using code page 1026 (Turkısh EBCDIC) When you use the DTLURDMO utility to migrate an IMS capture registration and try to change the schema name, the migrated capture registration is not usable. 6 PWX-RLN-910HF4-0001

7 CR On i5/os systems, an APPBUFSIZE parameter value greater than 7.9 MB can result in a memory allocation failure during a read or write operation. Workaround: Specify a smaller APPBUFSIZE value in the DBMOVER configuration file or in the connection definition When you run a CDC session that has a password-protected Adabas data source and that 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 that 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 PowerExchange cannot process Adabas records larger than 32 KB on UNIX and Windows, because support for Adabas ACBX is not available on these operating systems 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 PowerExchange row test or PowerExchange utility tasks and the associated PowerExchange Listener task. Documentation Update The following clarification was added to the PowerExchange HotFix 4 CDC Guide for Linux, UNIX, and Windows: If you set the PowerExchange Logger for Linux, UNIX, and Windows COND_CDCT_RET_P parameter to a low value and do not extract change data from the PowerExchange Logger log files over a period that is longer than the retention period, the log files from which you need to capture data are likely to be deleted before extraction processing can run. In this case, you can lose change data without warning. For example, if you set the retention period to 5 and do not run extractions over a 10-day holiday, PowerExchange deletes the log files for which the retention period has expired and change data is lost. Before an extended quiet period, increase the COND_CDCT_RET_P parameter value to a number of days that is longer than the quiet period. 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 PWX-RLN-910HF

8 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: Toll Free France: Germany: Italy: Netherlands: Portugal: Spain: Switzerland: United Kingdom: Toll Free Australia: New Zealand: Standard Rate India: Standard Rate Belgium: France: Germany: Netherlands: United Kingdom: PWX-RLN-910HF4-0001