Known issues

Known issues

The following table describes known issues:
Bug
Description
PWX-9535
During PowerExchange Express CDC for Oracle checkpoint processing of in-flight transactions, if a checkpoint SCN is less than the last commit SCN, the resource queue might become exhausted before a restart advance can be sent, which causes extraction processing to hang. PowerExchange 10.5 EBF01 will fix this problem.
Workaround: DO NOT USE THE CHECKPOINT FEATURE UNTIL YOU APPLY EBF01.
PWX-9473
When you run the DTLUCBRG utility to create an IDMS capture registration, DTLUCBRG does not create a correct capture registration even though the job ends with RC=00. (May 2020)
PWX-9404
If you try to run the PING command of the PWXUGSK utility from an IBM i V7r4 system and the target of the command is a Windows system, the command fails. PowerExchange does not support outward secure connections from IBM i systems. (January 2021)
PWX-9014
You cannot view paths for an IDMS capture registration in the PowerExchange Navigator. (May 2020)
PWX-8930
The IMS log-based ECCR REFRESH command causes the ECCR to end abnormally. (May 2020)
PWX-8733
PowerExchange Express CDC for Oracle processing of Oracle 19
c
indexed-organized tables (IOTs) in 4 KB tablespaces might result in change data loss or corruption.
Workaround: Do not try to capture change data from Oracle 19
c
tables that are IOTs in 4 KB tablespaces. (February 2020)
PWX-8563
In the PowerExchange Navigator, if you open a Microsoft SQL Server capture registration and click
Save
, the PowerExchange Navigator creates a new Microsoft 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. (November 2019)
PWX-8527
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. (November 2019)
PWX-8333
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:
PWX-36465 ORAD Info: DML sequence error: Subordinate DML sequence and active DML sequence is not only kdolkr/kdolmn/kdollb.
(September 2019)
PWX-8328
During PowerExchange Express CDC for Oracle, the following internal error might occur:
PWX-36000 Error Unexpected chain sequence: unchained into chained during large row chains for compressed tables
(September 2019)
PWX-8097
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. (June 2019)
PWX-7917
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. (March 2019)
PWX-7202
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. (May 2018)
PWX-7104
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. (April 2018)
PWX-7033
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. (March 2018)
PWX-6917
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. (January 2018)
PWX-2031
If you include hidden columns in capture registrations for Db2 for i tables, PowerExchange extraction processing ends abnormally with the following error message for each hidden column:
PWX-06714 Table
schema
.
table_name
Field
field_name
missing (DB2 for i5/OS CDC)
This error occurs because PowerExchange cannot detect the hidden columns.
Workaround: Register tables that contain hidden columns in the PowerExchange Navigator so that you can selectively omit the hidden columns from the capture registrations. (463305) (August 2016)
PWX-1971
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) (May 2016)
PWX-1922
PowerExchange Express CDC for Oracle ends abnormally when trying to capture direct-path load operations for tables that use Exadata Hybrid Columnar Compression (EHCC).
Workaround: If you have a source table that uses EHCC, do not enable the capture of direct-path load operations. Use the default setting of N for the SUPPORT_DIRECT_PATH_OPS parameter in the OPTIONS statement of the PowerExchange Express CDC for Oracle configuration file. (451128) (March 2016)
PWX-1827
PowerExchange Express CDC for Oracle capture processing ends with the following error message when a source index-organized table (IOT) is altered to add an overflow tablespace, a mapping table, or an INCLUDING
column_name
clause:
PWX-36000 ORAD: Internal error TableImpl::UpdateTAB unexpected condition: m_ObjId (
object_id
) !=rB.obj (
object_id
) in module PwxOrlDictImpl:10116.
In this situation, loss of column data in a row might occur.
Workaround: Re-materialize the target table. Then cold start the CDC session to recover the lost column data. (438982) (September 2015)
PWX-1752
PowerExchange Express CDC for Oracle does not properly process Quick Multi Insert (QMI) operations for IOTs. The PowerExchange Logger for Linux, UNIX, and Windows might end abnormally with a return code of 9980 if you perform the following types of actions that produce QMIs:
  • Use SQL*Loader to load a source IOT.
  • Run the Oracle Data Pump Import utility (impdp command) to load an IOT.
(June 2015)
PWX-1672
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) (January 2015)
PWX-1521
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) (July 2014)
PWX-1387
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) (December 2013)
PWX-1271
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) (July 2013)
PWX-1184
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) (January 2013)
PWX-1143
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. (October 2012)
PWX-825
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) (February 2011)
The current bug tracking system uses bug IDs that begin with the "PWX-" prefix. The previous tracking system used bug IDs that consist of six numbers. For known limitations that carried over from an earlier release and now have a PWX-
nnnn
bug ID, you can find the previous bug ID at the end of the description in parentheses.

0 COMMENTS

We’d like to hear from you!