PowerExchange for CDC and Mainframe
- PowerExchange for CDC and Mainframe 10.5
- All Products
Bug
| Description
|
---|---|
PWX-9512
| The PowerExchange PostgreSQL CDC extraction process stalls when the connection to the database is lost in Linux.
|
PWX-9507
| When you run the PowerExchange Logger on Linux for Express CDC for Oracle, missing transactions occur if the source table is defined as ORGANIZATION INDEX (IOT).
|
PWX-9461
| PowerExchange Express CDC for Oracle processing on Linux terminates after reaching an open cursor limit. A BFILE query remains open after reaching the end of a log.
|
PWX-9451
| The PowerExchange Logger for Linux, UNIX, and Windows fails with the following error:
|
PWX-9442
| The DTLUCBRG utility output does not show the correct nullable value for columns when MSSQL_PROVIDER_TYPE=2 is specified in the dbmover.cfg file.
|
PWX-9414
| After PowerExchange is upgraded from an earlier release, CDC sessions that have a Db2 for z/OS target fail while checking for recovery tables on the target.
|
PWX-9413
| When you attempt to add a capture registration for an IMS data map that spans multiple 32 KB blocks in the z/OS data set, the PowerExchange Navigator displays incomplete metadata.
|
PWX-9346
| If you have Db2 for i source tables with more than 2,147,483,647 rows, PowerExchange propagates the same relative record number (RRN), instead of distinct values, for all of rows to the generated DTL__CAPXRRN column on the target.
|
PWX-9341
| For PowerExchange on IBM i, a Db2 for i table with a large number of referential constraints and trigger programs causes the CDC process to fail, reporting that the table was not journaled for before images.
|
PWX-9279
| During update operations where the row is migrated, Express CDC for Oracle encounters a row chaining issue with columns that contain LOBs.
|
PWX-9278
| The PowerExchange Logger for Linux, UNIX, and Windows does not start when the apply task is inactive.
|
PWX-9239
| A PowerExchange IMS Unload task fails with the following error:
|
PWX-9228
| An attempt to install PowerExchange on an IBM i system failed when using a permanent license key but succeeded with a temporary license key.
|
PWX-9200
| During PowerExchange Express CDC processing of an Oracle Exadata source database, the PowerExchange Logger might issue a warning about filling up log files.
|
PWX-9185
| PowerExchange on IBM i encounters an error while processing an SQL DELETE FROM request during pre-session processing.
|
PWX-9179
| During PowerExchange Express CDC for Oracle processing, the PowerExchange Logger might end abnormally with the invalid SetDPLParentPseudoTxn() DPL state.
|
PWX-9177
| PowerCenter bulk data movement sessions that use the Db2 LOAD utility to load data to PowerExchange
Db2 for z/OS targets might fail if the intermediate load files, including the input data, JCL, and control files, have generated file names that include a non-unique PID qualifier. On z/OS, PID values can be re-used, depending on the number of concurrent tasks.
|
PWX-9174
| In Developer Tool, the following logic error occurs when importing metadata for non-relational sources:
|
PWX-9148
| The PowerExchange Base Work Area size is reduced to improve memory usage. As part of this fix, the following parameters can no longer appear in the DBMOVER configuration file:
|
PWX-9143
| PowerExchange CDC on IBM i might exceed the maximum number of pointer handles for a table that includes LOB columns and then issue the following error message:
|
PWX-9125
| PowerExchange for Oracle displays BCE dates incorrectly.
|
PWX-9123
| PowerExchange Express CDC for Oracle might encounter a redo log assembly error:
This issue can occur when a table that contains one or more LOB columns contains an UPDATE TRIGGER that performs an UPDATE on another table that contains a LOB column.
|
PWX-9109
| If you try to create a registration for a Microsoft SQL Server table by using an Active Directory account user, the PowerExchange CCT file can become corrupted. This issue occurs with seven character domains.
|
PWX-9094
| During PowerExchange processing for an IMS source, the event marker message PWX-07850 displays the DBID instead of the DBDNAME.
|
PWX-9085
| During PowerExchange Express CDC for Oracle capture processing, rollbacks of DML changes to tables with inline LOBs might fail with the following error message:
In this case, the PowerExchange Logger ends.
|
PWX-9079
| ORA-01000: maximum open cursors exceeded error encountered during PowerExchange Express CDC for Oracle capture processing.
|
PWX-9052
| When PowerExchange IMS Synchronous CDC generates RBA values for data in IMS Fast Path databases, it uses a deprecated field to find the database area number that is used to create unique RBA values. This behavior causes the generated RBA values to be incorrect for data in areas that have area numbers greater than 255. This limitation applies under the following conditions:
|
PWX-8992
| PowerExchange Express CDC for Oracle might encounter a memory leak when allocating new pages.
|
PWX-8983
| PowerExchange Express for Oracle ends abnormally when processing a non-captured table that has the compression attributes on Oracle 18 c .
|
PWX-8966
| PowerExchange Express CDC for Oracle performance is degraded when repositioning within a log file.
|
PWX-8956
| If you create a Datacom capture registration by using the DTLUCBRG utility, the corresponding extraction map has a null
Tag value. When you run the CDC session, the session ends with multiple read errors.
|
PWX-8880
| On IBM i, PowerExchange accepts the selection of schemas that have long names. However, to specify journal names in PowerExchange, you must specify LIBRARY/JOURNAL.
|
PWX-8323
| To access MySQL 8.0 CDC sources, you cannot use passwords that are encrypted with the SHA256 algorithm because the currently installed DataDirect ODBC driver does not support this authentication type.
|
PWX-8186
| For PowerExchange for Adabas, when the mapping includes a spanned file with before-image or change indicator columns, an update can be mistakenly marked as a delete.
|
PWX-7993
| If you use the XM_COPY statement of the DTLURDMO utility to rename a Db2 data map that was merged with an extraction map, it does not rename the internal Db2 data map name. When you try to use the extraction map, it fails with the following message:
|
PWX-1877
|