Fixed issues

If you select the advanced Add Last Replicated Time property on the Target page of the task wizard and save task and then later clear the check box and save the task again, when you return to the task wizard, the check box is still selected. However, if you open the task in view mode, the property is disabled. In this case, the database ingestion and replication job does not add the last replicated time metadata column on the target, which appears to conflict with the wizard setting.

Database ingestion and replication jobs that have a Snowflake target and use the Superpipe feature to stream change data to target tables might fail with the following error if mixed-case and lowercase column identifiers are quoted and if the QUOTED_IDENTIFIERS_IGNORE_CASE=true parameter is set in the Additional JDBC URL Parameters field of the connection properties:

In the Data Ingestion and Replication Command-Line Interface (CLI), if you issue the job status command without the optional -f option, the command fails with the following error:

The failure occurs because of date-time format discrepancies that are encountered when fetching the job's start time.

Database ingestion and replication jobs that have an Amazon Redshift target might fail when creating target tables that have names in mixed case or uppercase. The failure occurs if the Amazon Redshift enable_case_sensitive_identifier cluster configuration parameter is set to false and the Enable Case Transformation target property is not selected for the job.

Database ingestion and replication incremental load jobs that have a Db2 for i source fail repeatedly before issuing the following error message:

A database ingestion and replication job that has a Kafka target configured with one-way SSL connection mode does not start because of a missing SSL KeyStore Password connection property which is not required for this mode.

A database ingestion and replication initial load job that has a Microsoft Azure Data Lake Storage Gen2 target does not attempt a retry if the upload to target fails.

Database ingestion and replication jobs that have a SQL Server source and SQL Server target might fail with the following error when processing large queries to the database:

The problem persists even after the job is undeployed, the tables on the target are dropped, and the job is deployed again.

Redeployed database ingestion and replication combined load jobs that have an Oracle 11g source might fail with the following error when querying redo logs for start information:

Database ingestion and replication incremental load or combined initial and incremental load jobs that have Db2 for i sources might fail if the query for source journal receivers encounters an empty journal receiver name.

Database ingestion and replication incremental load jobs that have Oracle sources might fail if the TDE master key is changed.

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.

The Resync option is available for a database ingestion and replication job even though the user does not have the required privileges to perform a resync.

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.

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.

When running a database ingestion and replication initial load job that has a MySQL source, the retrieval of the first record might be delayed by hours, reducing the overall throughput of the database ingestion job. In this case, an out-of-memory issue might occur if the source table result set is large enough to exceed the available heap memory of the database ingestion and replication task container process. In combined initial and incremental load jobs, the switch to incremental load processing might also be delayed by hours.

Database ingestion and replication incremental load or combined load jobs that use the Soft Deletes apply mode might not apply all change records to the Snowflake target if you delete a source record and then add the same record shortly afterwards again. In this case, only the Delete record is captured.

Database ingestion and replication combined initial and incremental load jobs that have a MySQL source might fail with the following error:

When running a database ingestion and replication initial and incremental load job, the switch from initial load processing to incremental load processing might be delayed by hours.

Database ingestion and replication incremental load jobs that have a Db2 for z/OS source fail repeatedly with the following error message:

Database ingestion and replication jobs might corrupt multi-byte character data in SAP HANA source tables when replicating the data to Snowflake targets. The problem occurs with encodings other than UTF-8.

Database ingestion and replication incremental load or combined initial and incremental load jobs that use a Microsoft Azure Synapse Analytics Database Ingestion connection to the target might fail with a target connection reset error during the execution of merge apply statements at the target database.

Database ingestion and replication jobs that have a Snowflake target and the Persistent Storage and Superpipe options enabled might fail when a new internal StreamObjectID is assigned to the source object schema.

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.

Database ingestion and replication incremental load jobs now detect non-responsive connections and fail if a connection is non-responsive for 5 minutes. This situation is usually caused by a network failure that leaves dead sockets.

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.

When database ingestion and replication jobs read Oracle logs using BFILE trailing directory separators in the Oracle directory object, the read operation might fail.

If you Abort a running database ingestion and replication initial load job for which partitioning is enabled, the job does not end immediately. Abort execution is delayed.

Database ingestion and replication incremental load jobs that have a Db2 for z/OS source and Snowflake target might fail repeatedly with the following error:

During periods of no DML activity, database ingestion and replication combined initial and incremental load jobs that have a Db2 for i source might hang with subtasks in the Queued state during the initial load phase. The job log contains the following types of messages:

Database ingestion and replication combined initial and incremental load jobs that have an Oracle source and Snowflake target and schema drift enabled might fail it you increase the precision of a column, for example, from VARCHAR(16) to VARCHAR(20). The problem occurs if you use code page CP1252 at task deployment time, but this character set is unavailable at runtime. At runtime, the job will use the UTF-8 code page, which causes the precision to be reduced and the following exception:

A means to override the code page used with a coded character set identifier (CCSID) encoding is not available. With this fix, you can use the pwx.cdcreader.iseries.option.CCSID2CodePageOverrides (ccsid,code_page) custom property to specify an override code page for a given CCSID at the Db2 for i table level. For more information, contact Informatica Global Customer Support.

Database ingestion and replication jobs that have Db2 for i sources cannot retry queries for getting the journal receiver list from Db2 for certain SQL error codes, such as:

With this fix, you can use the pwx.cdcreader.iseries.option.useNewLogCollector=true and pwx.cdcreader.iseries.option.useJournalReceiverQueries= true custom properties with the pwx.cdcreader.iseries.option.ConnectionRetryCodes, pwx.cdcreader.iseries.option.journalReceiverRetries, and pwx.cdcreader.iseries.option.journalReceiverInterval custom properties to enable retry attempts when encountering SQL errors during journal receiver queries. For more information, contact Informatica Global Customer Support.

The pwx.cdcreader.ZOS.ConnectionRetryCodes custom property should accept negative error codes such as -443.

Database ingestion and replication incremental load jobs that replicate data from an Oracle 19c source with LOB columns and with non-LOB columns defined with the NOT NULL DEFAULT constraint might fail with following message when processing some Insert operations:

Database ingestion and replication incremental load jobs that have an Oracle source with some LOB columns might fail with the following message when trying to process some Update operations:

The problem occurs if Oracle generates a bad redo record for the Update.

After you save a database ingestion and replication task that has Oracle or SQL Server source tables that are selected based on rules, some with a subset of selected columns, if you then add or remove selected columns for some tables and click the Refresh icon, the Table View count of source tables and the column selection for some tables are incorrect.

Database ingestion and replication incremental load jobs that have an on-premises SQL Server source and an Azure SQL Database target incorrectly replicate Update operations to the target when multiple Updates occur in a transaction for the same column using the same primary key.

Database ingestion and replication jobs that have a Kafka target might log sensitive information, such as a password, in clear text in the job log if it was entered in the Additional Connection Properties field of the connection properties.

Database ingestion and replication jobs that have source columns with the FLOAT data type and precision greater than 32 and that use the Parquet output format do not convert the source FLOAT columns to target data types consistently across all load types. Initial load jobs generate target FLOAT columns, whereas incremental load and combined load jobs generate target DOUBLE columns. Now, jobs of all load types generate target DOUBLE columns.

A database ingestion and replication job that has a SQL Server source and uses the query-based CDC method might incorrectly replicate INTEGER data with the value of NULL to the target as 0 and replicate BIT data with the value of NULL as FALSE.

A database ingestion and replication job that has a Db2 for i source might not capture any change data after a journal reset in new log collection mode.

When you create a new database ingestion and replication task that has an Oracle source or update an existing task, the following error might be issued when you click Apply Rules:

A database ingestion and replication job that has a SQL Server source and partitioning enabled might fail if you use Windows authentication to connect to SQL Server.

A database ingestion and replication incremental load or combined load job that has an Oracle or SQL Server source and schema drift enabled might fail with one of the following errors, instead of issuing a schema drift alert, if you select additional source columns and redeploy the job after the job has run:

Database ingestion and replication incremental load jobs that have a SAP HANA source might hang while waiting for incoming change data, although the data is present in the source tables. The job continues to run without reporting any errors.

On the Source page of the database ingestion and replication task wizard, the Table View shows only previously selected columns for a table, instead of all selected and unselected columns, if you filtered for that table in the table view after the task was in the Deployed, Completed, or Up and Running state.

If you select the Superpipe option for a database ingestion and replication job that has a SQL Server source and a Snowflake Data Cloud target and if a source column has the DATETIMEOFFSET data type, the job fails with the following error when trying to write data for that source column to a TIMESTAMP column on the target:

A database ingestion and replication job that a SQL Server source and uses the query-based CDC method might fail to load the source tables if you select Windows Authentication v2 as the Authentication Mode in the SQL Server connection properties.

A database ingestion and replication task might fail with a SQL compilation error if Database Ingestion and Replication detects a Drop Column request for a column that was previously removed.

Database ingestion and replication combined initial and incremental load jobs that have an Oracle source with a VARCHAR2 column and an Oracle target fail when incremental change data processing starts. The failure occurs because of the following unique constraint error: