Issue | Description |
|---|---|
DBMI-23004 | Database ingestion and replication combined load jobs that have an Amazon S3 target and use the Avro or Parquet format for output files might encounter the following error during backlog processing if the unload phase of the job runs on a Secure Agent different from the one that the job runs on: Internal logic error - CacheFactory for internal DBMI task is not expected. com.infa.rat.dbmi.reader.impl.BacklogTaskSetupException: BacklogTaskMainThread Failed to configure its BacklogTask Also, in the monitoring job details, the Stage value reported for some source tables might remain at Unloaded rather than progress. (April 2025) |
Issue | Description |
|---|---|
DBMI-11732 | If database ingestion and replication incremental load or combined initial and incremental load jobs replicate LOB source data to an Amazon S3 target and use the CSV format for the target output file, the LOB data appears as empty strings in the target file. (November 2022) |
DBMI-2297 | Although the Amazon S3 connection properties allow users to specify an IAM role, you cannot use temporary security credentials generated by the AssumeRole method of the AWS Security Token Service API to authorize user access to AWS Amazon S3 resources. (April 2020) |
Issue | Description |
|---|---|
DBMI-21764 | Database ingestion and replication jobs that have a Databricks target might replicate NULLs for columns that have LOB data types. (February 2025) |
Issue | Description |
|---|---|
DBMI-23703 | If database ingestion and replication jobs read data from a Db2 for i source physical file that’s defined in DDS with a unique index but no primary key, the unique index won’t be used when generating the corresponding target object. After this fix, if no primary key is available, unique indexes are fetched from the SYSPARTITIONINDEXES view and used to update the schema used for target generation. (May 2025) |
DBMI-23291 | For database ingestion and replication jobs that have a Db2 for i source, restart advance might not occur. (May 2025) |
DBMI-23209, DBMI-23014 | When a CDC Staging Task has multiple member jobs that process Db2 for i sources writing data to the same journal receiver and a job adds tables from a different schema, the CDC Staging Task stops collecting change data for the added tables with the following error message: [IBMiLogCollector failed creating SQL IBMiLogCollector createLogSQLStatement(), retry exception, Index 4 out of bounds for length 4 Condition is retryable.] (April 2025) |
DBMI-22959 | The ability to limit the journal receivers printed to the journal receivers list in the job log is needed when you do not want to print all entries every time the statistics are printed. Limiting the entries can reduce the log size and I/O. (April 2025) |
DBMI-22956 | The default settings of several internal custom parameters need to be optimized to enhance the performance of database ingestion and replication jobs with Db2 for i sources and reduce their CPU usage. (April 2025) |
DBMI-21956 | When you run a database ingestion and replication task with a Db2 for i source as part of the CDC Staging task, the trace messages for custom trace settings might not be found in the task log. (April 2025) |
DBMI-21990 | Database ingestion and replication combined initial and incremental load jobs that have a Db2 for i source might fail during merge apply processing of change data if the source has a large number of journal receivers with frequent log sequence resets. In this case, the job log volume increases and consumes too much space. (February 2025) |
DBMI-21957 | Database ingestion and replication incremental load and combined load jobs that have a Db2 for i source might encounter the following error if a log sequence reset occurs on every journal receiver switch and if the first log record timestamp on a reset journal receiver contains subseconds shorter than 23 bytes when timestamp- or position-based restart is used. [CDCPUB_10066] TRACE: [IBMiClient setErrorCondition() called. Error<IBMiUOWManager Log sequence reset/switch error, String index out of range: 23>]. (February 2025) |
DBMI-21838 | Database ingestion and replication incremental load and combined load jobs that have a Db2 for i source fail if you set the Initial Start Point for Incremental Load option to Position or Specific Date and Time. (February 2025) |
DBMI-21720 | Database ingestion and replication incremental load or combined load jobs that have a Db2 for i source fail with the following error if the source schema and journal are in different libraries: [DBMIP_23002] The process [CDC-CP1AZ PWX Reader] with the thread ID [31599] received an unexpected error from the PowerExchange Capture Service. Error: [IBMiMetadataManager getTableList(), Table Schema <schema_name> or Table System Schema <schema_name> does not match Journal Schema name <jrn_schema>]. (February 2025) |
DBMI-21531 | Database ingestion and replication incremental load or combined load jobs might hang during periods with no change activity of interest if a premature end-of-log (EOL) is detected and the journal receiver is in the SAVED or ONLINE state. The following message is issued: [logCollector] LEVEL_1 trace - IBMiLogCollector newEndOfLogChecks(), EOL check, ending log sequence returned <sequence> is less than current EOL sequence <current_sequence>, will continue log read at log sequence returned. (February 2025) |
DBMI-21436 | For database ingestion and replication jobs that have a Db2 for i source, the ability to read sequences backward up to a maximum number of records is needed in some situations. (April 2025) |
DBMI-19816 | Database ingestion and replication incremental load or combined load jobs that have a Db2 for i source might fail with the following error if the log collector misses a record in a cached journal receiver while reading to EOL and then tries to find the record by reading backwards in the log: [CDCPUB_10066] TRACE: [IBMiClient setErrorCondition() called. Error did not return a log record. Queue contains <0> rows after attempting to retry 11 times.>]. (February 2025) |
DBMI-19056 | If database ingestion and replication incremental load or combined load jobs that have a Db2 for i source request the End of Log (EOL) sequence when caching is enabled on the journal, the last record can’t be retrieved. Retries are attempted but are not successful. (April 2025) |
Issue | Description |
|---|---|
DBMI-23101 | If a database ingestion and replication job that has a Db2 for z/OS source tries to issue a request for source information such as the end of log when it’s not connected to Db2, the job fails. The job might become disconnected from Db2 during log collector slowdown processing, if enabled with the pwx.cdcreader.ZOS.LogCollectorSlowDown custom property. (April 2025) |
DBMI-20992 | If requests to Resync multiple Db2 for z/OS source objects in the same database ingestion and replication combined load task are made at the same time, the Resync might be ignored for some of the source objects. (April 2025) |
DBMI-20985 | Database ingestion and replication incremental load or combined initial and incremental load jobs that have a Db2 for z/OS source might fail with a log parser error like the following one because of incorrect sequence token checking: Caused by: com.infa.rat.pwxdbmi.pwxcdc.intf.CDCReaderException: zosLogParser run(), Error - zosLogParser processLogRecord(), Sequence number error for data sharing environment, 1536 Current Sequence VRS <002> HCSeq UOWSeq LogSeq <00DFB54159EB15B0A800> Last Sequence VRS <002> HCSeq UOWSeq LogSeq You can Resume the job successfully. (November 2024) |
DBMI-20084 | Database ingestion incremental load jobs that have a Db2 for z/OS source might fail with the following error during CDC reader processing, even after the jobs are stopped and then resumed: [CDCPUB_10066] TRACE: [PwxCDCReaderRunHandler encountered error :Previous sequence <sequence1> is not less than current sequence <sequence2>. (February 2025) |
DBMI-16129 | When you create a database ingestion and replication incremental load task that has a Db2 for z/OS source in the new task configuration wizard, if you add a table selection rule that excludes all tables, the associated job might fail with the a misleading message that reports DATA CAPTURE CHANGES is not enabled on the excluded tables. (Februrary 2025) |
Issue | Description |
|---|---|
DBMI-19760 | Database ingestion and replication initial load jobs that have an Oracle source and a Google BigQuery target might fail intermittently with the following error: uploadLocalFile has been failed because of error: Remote host terminated the handshake. (April 2025) |
Issue | Description |
|---|---|
DBMI-11732 | If database ingestion and replication incremental load or combined initial and incremental load jobs replicate LOB source data to a Google Cloud Storage target and use the CSV format for the target output file, the LOB data appears as empty strings in the target file. (November 2022) |
Issue | Description |
|---|---|
DBMI-11732 | If Database ingestion and replication incremental load or combined initial and incremental load jobs replicate LOB source data to a Microsoft Azure Data Lake Storage Gen2 target and use the CSV format for the target output file, the LOB data appears as empty strings in the target file. (November 2022) |
Issue | Description |
|---|---|
DBMI-24125 | Database ingestion and replication incremental load or combined load jobs that have a SQL Server source and use the Log-based CDC method might incorrectly process an update not involving the primary key as a pair of delete and insert operations that have the same sequence value. After restarting the job, the insert operation might have a different sequence value. This discrepancy occurs because the restart temporarily switches to CDC Tables mode, which doesn’t handle the update in the same manner as Log-based mode. (May 2025) |
DBMI-23957 | Database ingestion and replication jobs that have a Microsoft SQL Server source and process an update in a primary key and a non-primary key column in a single transaction might produce an incorrect timestamp in the DATETIME column on the Microsoft SQL Server target. (May 2025) |
DBMI-23610 | Database ingestion and replication jobs that have a Microsoft SQL Server source might fail to read the CDC capture instance tables because of a deadlock error. (May 2025) |
DBMI-23467 | A database ingestion and replication job that has a Microsoft SQL Server source and is configured to pause between reconnection attempts might retry the connection to the database without waiting for the requested delay. (May 2025) |
DBMI-23377 | For database ingestion and replication incremental load or combined load jobs that have a Microsoft SQL Server source, the SQL query that reads the CDC capture instance tables fails if a source table contains a column with the same name as a column found in the cdc.lsn_time_mapping table. (April 2025) |
DBMI-21747 | After the November 2024 upgrade, database ingestion and replication incremental load jobs that have a Microsoft SQL Server source and use the CDC Tables capture method might fail because of a memory leak in the pwxodbc library. In this case, Windows Event Viewer reports a low virtual memory condition. (February 2025) |
Issue | Description |
|---|---|
DBMI-21014 | Database ingestion and replication initial load jobs that have a MySQL source fail if the source contains invalid date, datetime, time, or timestamp data that the reader or target writer cannot process. For example, the following data is invalid: “0000-00-00 00:00:00”, “02-31-2024 00:00:00” (November 2024) |
DBMI-20874 | For database ingestion and replication jobs that have a MySQL source, two CDC records recorded at the same time but in different bin logs might cause the job to fail with the following error: "Previous sequence is not less than current sequence" (November 2024) |
Issue | Description |
|---|---|
DBMI-24183 | After the April 2025 release, database ingestion and replication initial load jobs with Oracle sources might fail with the following ODBC driver error: *Caused by: java.lang.ExceptionInInitializerError: Exception java.lang.SecurityException: sealing violation: package oracle.jdbc is sealed [in thread* "CDC-UNLOAD-CNS_CUST.CIS_OE_ORDER_HEADERS_DTLS Object Distributor (632)"] The problem occurs because the February 2025 release required the odbc8.jar file to be in the <Secure Agent >/apps/Database_Ingestion/ext directory. However, in the April 2025 release, the driver isn’t expected at that location. To prevent the error, the driver has been removed from the ext directory. (May 2025) |
DBMI-24177 | Database ingestion and replication jobs that have an Oracle source might produce single-digit values in some fields on the target, whereas the corresponding source fields contain multiple digits. This discrepancy is caused by an internal error, which results in random truncation of character strings. (May 2025) |
DBMI-24059 | After the April 2025 release, database ingestion and replication incremental load or combined load jobs that have an Oracle source without a primary key and a Snowflake target write duplicate rows to the target when processing an Update operation. (May 2025) |
DBMI-24113 | A database ingestion and replication job that has an Oracle source running on AIX, HP-UX, or Solaris platforms might fail to convert LOB data that was set as NULL on updates to Endian data formats. (May 2025) |
DBMI-23727 | A database ingestion and replication incremental load or combined load job that has an Oracle source might fail with the following message: PWX-36196 ORAD: No logs with Start SCN 5944410182514 and resetlogs Id 855675717 are available for THREAD# 1. (May 2025) |
DBMI-23611 | Database ingestion and replication incremental load or combined load jobs that have an Oracle source fail if they can’t parse redo log records that don’t have a transaction ID (XID) when processing DML changes. (May 2025) |
DBMI-23299 | Database ingestion and replication incremental load and combined load jobs with Oracle sources use the Oracle V$TRANSACTION view to check for open transactions. However, this view provides results for one active RAC node, not all RAC nodes in the cluster. The global GV$TRANSACTION view should be used instead. (May 2025) |
DBMI-23003 | Database ingestion and replication incremental load jobs that have an Oracle source with a NOT NULL LOB column might fail with the following error after a DML delete operation: PWX-36200 ORAD: Column conversion error: [36202] NULL value found for column that is not nullable for Table name=<table_name>, column[n] segment[n] DATA. Detail Type = CLOB, Oracle Type = CLOB. (April 2025) |
DBMI-22981 | Database ingestion and replication jobs that have an Oracle source in an Oracle Data Guard environment fail if the primary database is in an Oracle Real Application Cluster (RAC) and the RAC Members value set in the Oracle Database Ingestion connection properties is not valid. No error message describing the problem is issued. (April 2025) |
DBMI-22978 | Database ingestion and replication incremental load or combined load tasks that have an Oracle source might stop capturing change data with the following internal error message: PWX-36000 ORAD Mbr 1: Internal error SetDPLParentPseudoTxn() DPL invalid state. Expected PARENT:INITIAL Received PARENT:PARENT_PSEUDO_BEGINfor Object id 0 in module PwxOrlTMgrUow:529. (April 2025) |
DBMI-22385 | Database ingestion and replication incremental load jobs that have an Oracle source with CLOB columns replicate some special characters to the target, instead of CLOB data, when the NLS_CHARACTERSET parameter is set to a specific code page such as WE8MSWIN1252. (April 2025) |
DBMI-22213 | Database ingestion and replication jobs that have an Oracle source might end with the following error if an internal race condition exists between two threads, where one thread is trying to re-create a schema cache object while the main thread is stopping the task: [CDCPUB_10066] TRACE: [Internal logic error. schemaCache.schemaExists() threw unexpected checking for schema with ID <number>]. A schema cache isn't required when the task is shutting down. (April 2025) |
DBMI-22052 | If a database ingestion and replication job that has an Oracle source on Linux encounters a Log Write Number (LWN) for a group of redo blocks that is larger than the read buffer, the job might fail with an error such as: [CDCPUB_10066] TRACE: [Error message[1] PWX-36564 ORAD: LRdr for member n has been unresponsive for more than the timeout threshold of 600. Last response time was <date><time>. (April 2025) |
DBMI-21661 | A database ingestion and replication incremental or combined initial and incremental load job that has an Oracle source might fail if you use table selection rules and the number of rules defined is greater than 100. (February 2025) |
DBMI-20142 | When the source custom property transitionSchedulerType is set to CDC_WITH_BACKLOG, the EXECUTE ON DBMS_FLASHBACK privilege should not be required for combined load jobs with Oracle sources. Any change data that accumulates in the backlog queue is applied by using fuzzy logic instead of a FLASHBACK query that uses a SELECT AS OF scn statement. However, deployment of the task fails with an error stating the FLASHBACK privilege is required. (May 2025) |
DBMI-19760 | Database ingestion and replication initial load jobs that have an Oracle source and a Google BigQuery target might fail intermittently with the following error: uploadLocalFile has been failed because of error: Remote host terminated the handshake. (April 2025) |
Issue | Description |
|---|---|
DBMI-24444 | For database ingestion and replication tasks that have an Oracle source and use the Audit apply mode, LOB data might not be correctly replicated to the target. When a non-LOB data is updated, the remaining columns are replicated as NULLs. Workaround: None. (May 2025) |
DBMI-23758 | If database ingestion and replication initial load jobs that have an Oracle source with XMLTYPE columns use the Oracle JDBC Thin driver, as configured in the Oracle Database Ingestion connection, the jobs might write nulls to the target. Workaround: If you need to write data from Oracle source XMLTYPE columns to a target, use the DataDirect driver. (April 2025) |
DBMI-23360 | Database ingestion and replication incremental load or combined load jobs that have an Oracle source with XML columns and an Oracle target might fail with the following Oracle error when processing a DML operation: [Oracle JDBC Driver][Oracle]ORA-00932: inconsistent datatypes: expected - got CLOB. Error code: 932 Workaround: None. (April 2025) |
DBMI-23048 | If you configure an Oracle Database Ingestion connection to use both the Oracle JDBC Thin driver and SSL encription, when you try to test the connection, the test fails. Workaround: Do not use the JDBC Thin driver with SSL encryption. (April 2025) |
DBMI-22685 | A database ingestion combined load job that has an Oracle source and uses the query-based CDC method might fail if you do not have the EXECUTE ON DBMS_FLASHBACK permission. Workaround: Set the Runtime Environment metadata_manager.jvm.skipDbmsFlashbackPrivilegeCheck configuration property to true. To set the property, open a Secure Agent in your runtime environment and click Edit. Under Custom Configuration Details, add the custom property. Select Database Ingestion as the service and DBMI_AGENT_CONFIG as the type. (May 2025) |
DBMI-19145 | Database ingestion and replication jobs that use the Log-based CDC method and have an Oracle source with only LOB columns selected and no primary key do not create subtasks on the tables. As a result, the jobs cannot capture change data from the tables. Messages such as the following are written to the log: [DBMIP_23026] The process [CDC-LOBS] with the thread ID [9708] encountered new table [lob_table_name]. The new table is excluded from processing. [CDCPUB_10066] TRACE: [PwxCDCRequestProcessor.askSchema() returned: Don't capture.]. Workaround: In the task, select some non-LOB source columns, in addition to the LOB columns, for replication if you want to continue using the table without a primary key. (July 2024) |
DBMI-14767 | If a database ingestion and replication job uses an Oracle Database Ingetion source connection that's configured to use the Oracle JDBC Thin driver, the job can replicate up to 39 digits from source columns that have a numeric data type to the target. If a source numeric value has 40 or more digits, the fortieth digit and all additional digits are replaced by zeroes (0) on the target. Workaround: None. (September 2023) |
DBMI-13605 | The Oracle Database Ingestion connection properties page includes no property for entering JDBC connection properties, such as EncryptionLevel, when they're needed. Workaround: In the Service Name field, you can add JDBC connection properties after the Oracle SID value, using a semicolon (;) as the separator. (April 2023) |
DBMI-12331 | If you create custom data-type mappings for Oracle source binary_double and binary_float columns in a database ingestion task, the custom mappings are ignored. Instead, the target table is generated using the default mappings of binary_double > float and binary_float > real. When the database ingestion and replication job runs, nulls are written to the target float and real columns. Workaround: None. (February 2023) |
DBMI-10794 | Oracle source columns with the TIMESTAMP WITH TIME ZONE data type are supported only for initial load jobs. (July 2022) |
Issue | Description |
|---|---|
DBMI-23490 | An internal capture query to retrieve WAL information failed when called from a hot-standby replica. Capture processing that runs against a replica now uses pg_last_wal_replay_lsn() rather than pg_current_wal_lsn(). (April 2025) |
DBMI-21041 | Database ingestion and replication jobs that have a PostgreSQL source and use the source object as a view might list NUMERIC data type columns with precision and scale as unsupported. (November 2024) |
Issue | Description |
|---|---|
DBMI-21419 | For a database ingestion and replication job that has an SAP HANA source and uses the Superpipe option to stream data to a Snowflake target, the Snowflake stream might become stale and data might not be accessible if the source tables are updated very rarely, for example on a quarterly or yearly basis. (April 2025) |
Issue | Description |
|---|---|
DBMI-15247 | If database ingestion and replication jobs that have an SAP HANA source table with a multiple-column primary key use a custom data-type mapping that maps a source TIMESTAMP column to a Snowflake target VARCHAR column, data might be replicated to the target incorrectly, causing invalid data in the target column. Workaround: None. (November 2023) |
DBMI-14370 | Database ingestion and replication incremental load jobs that have an SAP HANA Cloud source with a DECIMAL column that has no precision fail with the following error message: Error executing query job. Message: Query error: Value of type BIGNUMERIC cannot be assigned to column, which has type INT64 at [number]. Error code: 100032 Workaround: None. (August 2023) |
DBMI-12571 | Database ingestion and replication jobs with a SAP HANA source might replicate data from REAL columns of 16 or more significant digits with a loss of precision on the target, causing data corruption. Workaround: None. (April 2023) |
Issue | Description |
|---|---|
DBMI-24059 | After the April 2025 release, database ingestion and replication incremental load or combined load jobs that have an Oracle source without a primary key and a Snowflake target write duplicate rows to the target when processing an Update operation. (May 2025) |
DBMI-21892 | For a database ingestion and replication combined load job that has a Snowflake target and uses the Superpipe option, the monitoring interface might report an Unload Count value under Object Detail that does not match the number of records read during the initial load phase, as reported in the unload log. This mismatch occurs if the transitionSchedulerType source custom property is set to CDC_WITH_BACKLOG, source partitioning is enabled, and the source tables contain over 2 billion records. (February 2025) |
Issue | Description |
|---|---|
DBMI-23323 | When configuring a database ingestion and replication job that has a Teradata source, if you attempt to fetch the entire schema either by applying rules or downloading include or exclude rules, an error might occur if any views have inaccessible definitions. (May 2025) |