If you selected the

Full Audit

option in a capture registration for a SAP HANA CDC source, the shadow _CDC table and SAP HANA triggers are generated when the PowerExchange Logger for LUW starts. However, if a shadow_CDC table was dropped and one or more of the corresponding triggers still exist, the table is not created. If the PowerExchange Logger then tries to restart from an earlier restart point without a shadow _CDC table, it ends abnormally.

Workaround: Before starting the PowerExchange Logger, either manually re-create the shadow _CDC table or drop the triggers.

Workaround: Do not specify a passphrase that includes an apostrophe.

If your PostgreSQL installation is configured to use the scram-sha-256 password encryption method, PowerExchange database connections will fail.

Workaround: Disable scram-sha-256 encryption by setting password_encryption=md5 in the postgresql.conf configuration.

During PowerExchange CDC for Db2 for i processing, the PowerExchange Listener on IBM i intermittently hangs if alternate logging is enabled. A connection error is issued.

Workaround: Disable alternate logging and try running the job again

If you select

View Paths

for an IDMS capture registration in the PowerExchange Navigator, the parent hierarchy for the IDMS base record is not displayed.

In the PowerExchange Navigator, if you open a Microsoft SQL Server capture registration and click

Save

, the PowerExchange Navigator creates a new SQL Server article and deletes the previous one even if no changes were made to the registration. The data associated with the previous SQL Server article is deleted.

Workaround: Do not click

Save

unless you are making changes to the capture registration.

After a PowerExchange IMS ECCR REFRESH operation, CDC processing might fail with an SVC99 error because of an IMS log deletion.

Workaround: Stop and restart the IMS ECCR and the PowerExchange Listener on the system where change capture occurs.

During PowerExchange Express CDC for Oracle, a transaction assembler error might occur for indexed-organized tables (IOTs) that contain OVERFLOW tables with chained rows. The following error message is issued:

The PWXUCDCT utility fails with a segmentation fault when running a derive_cdct_backup command and trying to process corrupted PowerExchange Logger log records. The messages that the utility issues do not contain useful diagnostic information.

Workaround: Ensure that the EXT_CAPT_MASK parameter value in the PowerExchange Logger configuration file is correct and that the Logger log files exist.

If you select the

Pre SQL run once per Connection

check box in a PWXPC connection definition for a nonrelational target, any SQL statements that you specify in the

Pre SQL

connection attribute will not be executed.

Workaround: Clear the

Pre SQL run once per Connection

check box to allow the SQL to run one or more times for the connection.

If you define a PowerCenter session that uses a PWX NRDB Lookup relational connection and set the TCPIP_OP_TIMEOUT and TCPIP_CON_TIMEOUT overrides in the

PWX Override

connection attribute, the session fails.

Workaround: Use the connection string to specify the overrides.

If you issue a pwxcmd command such as displaystats to an ECCR on a z/OS system, the pwxcmd command handler might hang. This problem occurs when the amount of command output is greater than 4 KB.

If the PowerExchange Agent encounters an error in the DBMOVER configuration file, it does not end processing as expected. As a result, the Agent cannot successfully connect to the PowerExchange Listener for change data capture.

Workaround: Shut down the PowerExchange Agent by using the SHUTDOWN COMPLETELY command. Edit the DBMOVER configuration file to correct the error and then restart the PowerExchange Agent.

For PowerExchange on z/OS, if you use the IPV6 protocol for a TCP/IP connection, the IP address is truncated in SMF reports. The connection is not affected, but the IP address is not complete in SMF.

If the file permissions on the directory path that is defined in the LOGPATH statement in the DBMOVER configuration file on the Linux Data Integration Service machine are not set correctly, a core dump occurs and a Java Runtime Environment fatal error is reported.

Workaround: Ensure that the file permissions are not too restrictive. Permissions of 755 are sufficient. (459102)

A CAPXRT database row test in the PowerExchange Navigator for an IMS complex table source returns no changes even though the PowerExchange Logger for z/OS contains data for the source. This problem occurs when a capture registration is re-created for the source with the same tag name as the previous registration and the new registration includes an additional IMS segment. As a result, PowerExchange cannot map the new registration to the data in the PowerExchange Logger log files.

Workaround: None available. Contact Informatica Global Customer Support. (409991)

If you capture change data from a Db2 for Linux, UNIX, and Windows source table that uses range partitioning and a DDL operation that adds, attaches, or detaches a partition is performed on the table, data loss might occur and cause data corruption on the target.

Workaround: Do not issue DDL statements that add, attach, or detach a partition for a source table. Alternatively, if you must perform these DDL operations on a source, before you start CDC processing, synchronize the source and target tables by using PowerExchange bulk data movement or another tool. (395055)

If you use PowerCenter to write Updates to a PowerExchange target and an Update fails, the PowerCenter session log displays an incorrect counts of Update rows in the Load Summary. An Update might fail, for example, because the target record does not exist. (375568)

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. (350646)

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. (331003)

When you import a PL/1 copybook for a z/OS source into a data map from the PowerExchange Navigator, the import succeeds, but the import record is not created.

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. (257540)