Release Notes for IDMC
- Release Notes for IDMC
- All Products
ASK INFAPreview
Please log in to access Ask INFA.
ASK INFAPreview
Issue
| Description
|
|---|---|
DBMI-26235 | Database ingestion and replication jobs that have an Oracle
source and SQL Server target incorrectly map source CLOB columns
to target VARCHAR columns by default. Because SQL Server VARCHAR
columns support only ASCII data, any non-ASCII characters from
the source are not stored correctly in the target. Change the
default mapping to a target data type such as NVARCHAR(MAX) that
would avoid the problem and achieve better data consistency. (October 2025) |
DBMI-26002 | Database ingestion and replication incremental load or combined
load jobs that have an Oracle source might fail with the
following error: PWX-36465 ORAD Info Mbr 1: DM sequence
error: Unsupported operation: multi-block (MBU) sequence in
process and not kDE_DML_MULTIBLK (October 2025) |
DBMI-25848 | Database ingestion and replication combined load jobs that have a
source table with a primary key and an Oracle target might not
write all change records to the target if DML operations occur
in the backlog of captured changes before change apply
processing starts. (October 2025) |
DBMI-25825 | Database ingestion and replication jobs that have an Oracle
source and SQL Server target incorrectly map source VARCHAR2
columns to target VARCHAR columns by default. Because SQL Server
VARCHAR columns support only ASCII data, any non-ASCII
characters from the source are not stored correctly in the
target. Change the default mapping to a target data type such as
NVARCHAR(MAX) that would avoid the problem and achieve better
data consistency. (October 2025) |
DBMI-25720 | Database ingestion and replication combined load jobs that have
an Oracle source and use the ARCHIVEONLY or ARCHIVECOPY reader
mode might fail with the following error:
When data is read only from Oracle archive logs, the next archive
log to consume might not be available before the default check
for backlog storage queue creation occurs. (October 2025) |
DBMI-25582 | Database ingestion and replication incremental load or combined load jobs that have an
Oracle source and connect to an Oracle Automatic Storage
Management (ASM) system to read redo logs might fail with the
following timeout error: 36558 ORAD Warn Mbr 2: ASM read
timed out after 6 seconds. (October 2025) |
DBMI-25489 | Database ingestion and replication incremental load and combined
load jobs that have an Oracle source and use BFILE access to the
redo logs might fail with the following error if the database
uses a softlink pointer to the archive log directory:
(October 2025) |
DBMI-25848 | Database ingestion and replication combined load jobs that have a source with a primary
key and an Oracle target might not write all change records to
the target if DML operations occur on a row during the backlog
phase of unload or initial load processing. (October 2025) |
DBMI-25482 | Database ingestion and replication jobs that have an Oracle
source and use the CDC_WITH_BACKLOG CDC transitioning method
might fail if the Oracle Flashback permissions are missing. (October 2025) |
DBMI-25391 | Database ingestion and replications jobs that have an Oracle source might fail if LOB
data is incompletely logged or cannot be interpreted and if the
data also cannot be fetched directly from the database because
the row has been deleted or removed. (October 2025) |
DBMI-25321 | For database ingestion and replication jobs that have an Oracle source and any target
type, a DML operation from an old cycle might be mistakenly
processed during job restart because its table's recovery data
wasn't fetched. This behavior might result in a duplicate key
error on the target. (October 2025) |
DBMI-25005 | Database ingestion and replication combined load jobs that have
an Oracle target might fail with the error ORA-00001:
unique constraint violated when processing an
Update operation if incorrect merge apply logic result in
attempts to insert duplicate records to the target:. (October 2025) |
DBMI-24965 | Database ingestion and replication jobs that have an Oracle source and use a connection
with the RAC Members property configured might fail if one of
the RAC members is down. (October 2025) |
DBMI-24820 | Database ingestion and replication combined load jobs that have an Oracle source and
Oracle target might fail with the error ORA-00001:
unique constraint violated when processing an
Update operation if incorrect merge apply logic result in
attempts to insert duplicate records to the target:(July 2025) |
DBMI-24786 | Database ingestion and replication incremental load jobs that
have an Oracle source and Oracle target might fail with the
following error because of incorrect merge apply processing:
(July 2025) |
DBMI-24710 | Database ingestion and replication jobs that have
an Oracle source with compressed SECUREFILE LOB columns can write
incorrect data to the target. (July 2025) |
DBMI-24588 | Database ingestion and replication jobs that have an Oracle source
might fail if the privilege for the GV$TRANSACTION view is
missing. (October 2025) |
DBMI-24562 | Database ingestion and replication incremental load jobs fail
with the following error when an Oracle database session that is
updating tables with LOB columns is killed and an unknown type
of backout operation occurs:
(July 2025) |
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:
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-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. (July 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:
(May 2025) |
DBMI-23704 | After a switch to Daylight Saving Time (DST), running database
ingestion and replication jobs that have an Oracle source do not
detect the time zone offset change on the database server and
consequently display capture progress messages that report an
incorrect capture time. (July 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-22984 | If database ingestion and replication combined load jobs that
have an Oracle source and use the ARCHIVEONLY reader mode
encounter a long-running open transaction with a begin SCN that
is older than the archive log start position, data loss might
occur. (July 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. (July 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) |
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-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:
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-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:
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-10794
| Oracle source columns with the TIMESTAMP WITH TIME ZONE data type are supported only for initial load jobs.
Workaround: To enable database ingestion and replication incremental load and combined
load jobs to process change data from TIMESTAMP WITH TIME ZONE
columns, set the source custom property
pwx.cdcreader.oracle.option.additional ENABLETIMSTAMPWITHTZ to
Y. (July 2022)
|
