Changed behavior

In the monitoring job details for application ingestion and replication and database ingestion and replication combined initial and incremental load jobs, the Agent Name field in the Object Detail pane was renamed to Unload Agent Name field to specify the Secure Agent on which the initial unload phase of the job ran. This information is useful when unload phase runs on a different Secure Agent than the incremental CDC phase.

In the Overview section of the Task Summary pane, the Agent Name field still displays the name of the Secure Agent on which the combined load job ran.

If you define a connection for a Snowflake target using the KeyPair option as the authentication method, when you generate the private key with OpenSSL 3.x.x version, you can use the AES128, AES128-CBC, AES256, or AES-256-CBC cipher while generating the private key.

Previously, the supported ciphers were PBE-SHA1-2DES and PBE-SHA1-3DES.

When you define target properties for an application ingestion and replication task or database ingestion and replication task that has a Snowflake target and uses the Superpipe option, you can select the Enable Case Transformation option to control the case of letters in the generated target table and column names based on a strategy you select, instead of using the same case as the corresponding source names by default. Previously, this capability was not available for Snowflake targets that use the Superpipe option.

Application ingestion and replication jobs and database ingestion and replication jobs that have a Snowflake target and use the incremental load or combined load type use _LOG tables to internally stage change data temporarily on the Snowflake target during the merge apply cycle, provided that the Superpipe option is not selected. After the data is merged to the target table, the _LOG tables can now be truncated instead of dropped. By not dropping the _LOG tables, you can preserve any custom tags on the tables that were created by the Snowflake ingestion pipeline for purposes such as data governance or handling sensitive data. To implement this new behavior, you must set the target custom property writerTargetRetainLogTable to true. Previously, the _LOG tables were dropped after each apply cycle and then re-created for the next cycle.

Limitation: When a job can't apply a schema drift operation because of a target issue, the job might fail, causing the _LOG table to be dropped. If you manually fix the target issue and then Resume the job, the _LOG table is re-created based on the updated target schema. In this scenario, you might have to re-apply the custom tags in the _LOG table after the job is resumed.

The default settings of several internal parameters have been optimized to enhance the performance of database ingestion and replication jobs with Db2 for i sources and reduce their CPU usage.