Release Notes for IDMC
- Release Notes for IDMC
- All Products
ASK INFAPreview
Please log in to access Ask INFA.
ASK INFAPreview
Issue
| Description
|
|---|---|
DBMI-19568
| If you perform a
Resync (retain) operation on a source table in a database ingestion and replication combined load job that has an Oracle source after a column is dropped, the target table is re-created, instead of retaining the table's current schema and resynchronizing the column data as expected. This behavior occurs even though the job's Drop Column schema drift option is set to Ignore.
(August 2024)
|
DBMI-19315
| In a database ingestion and replication combined load job that includes an Oracle source, a subtask on a source table that includes a TIMESTAMP WITH LOCAL TIME ZONE column fails after you rename that column and perform a the Resync (refresh) operation on the table subtask. This problem occurs even though the RENAME COLUMN schema drift option is set to Ignore and the Database Ingestion agent service's DBMI_ORACLE_SOURCE_ENABLE_TIMESTAMP_WITH_LOCAL_TZ environment variable is set to true.
(August 2024)
|
DBMI-19297
| Database ingestion and replication jobs that have a highly encrypted Oracle source in a Real Application Clusters (RAC) Oracle Cloud Infrastructure (OCI) environment might fail with the following error:
(August 2024)
|
DBMI-19126
| Database ingestion and replication tasks that are configured to not include LOBs in capture processing but have source tables with unsupported Oracle BFILE or LOB columns, incorrectly add table-level Exclude rules that specify conditions with the unsupported column names on the
Source page of the task wizard.
(August 2024)
|
DBMI-19124
| Database ingestion and replication incremental load or combined load jobs that have an Oracle source might fail intermittently with the following error if the source database uses Create Table As Select (CTAS) statements or direct-path loads with a dblink:
The CTAS or direct load operations can cause a different pattern of redo logs to be produced.
(October 2024)
|
DBMI-19022
| When you configure database ingestion and replication initial load jobs that have an Oracle source and Microsoft Azure Data Lake Storage target, if you select
Add Operation Type on the
Target page, that setting is cleared when the task is saved. As a result, the infa_operation_type metadata column is not added to the target.
(August 2024)
|
DBMI-18629
| In a
database ingestion and replication task that has an Oracle source and Google BigQuery target, if you add a custom data type mapping that maps the Oracle DATE type to the Google BigQuery TIMESTAMP type, the custom mapping is ignored when you run the job. Instead, the default mapping of Oracle DATE to Google BigQuery DATETIME is used.
(July 2024)
|
DBMI-18230
| In
database ingestion and replication tasks that have an Oracle source, selected tables might be automatically deselected in the following situation:
(July 2024)
|
DBMI-18096
| Database ingestion and replication incremental load jobs that have Oracle sources might fail if the TDE master key is changed.
(May 2024)
|
DBMI-17805
| Database ingestion and replication incremental load jobs that have Oracle sources and run in ARCHIVECOPY reader mode end abnormally after a failover from the primary database to a standby database.
(May 2024)
|
DBMI-17552
| During
database ingestion and replication CDC processing of an Oracle source, a capture progress marker might be sent out of sequence after processing catches up to the current end of log.
(May 2024)
|
DBMI-17547
| In
database ingestion and replication jobs that have an Oracle source and a Snowflake target with schema drift enabled, the target column size might be inconsistent with the source column size.
(May 2024)
|
DBMI-16384
| Database ingestion and replication jobs that have an Oracle source might ignore transactions with no DML activity of interest after 60 minutes. Data loss might occur after a job restarts if an ignored transaction that's no longer being tracked later contains DML changes.
(May 2024)
|
DBMI-16138
| Database ingestion and replication combined initial and incremental load jobs that have an Oracle source might incorrectly report the suspension time in the suspension duration trace message.
(May 2024)
|
DBMI-15421
| When
database ingestion and replication jobs read Oracle logs using BFILE trailing directory separators in the Oracle directory object, the read operation might fail.
(May 2024)
|
Issue
| Description
|
|---|---|
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-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)
|
