5.8.07.00 - connect_cdc_mimix_share - Latest

Connect CDC Release Notes

Product type
Software
Portfolio
Integrate
Product family
Connect
Product
Connect > Connect CDC (MIMIX Share)
Version
Latest
Language
English
Product name
Connect CDC
Title
Connect CDC Release Notes
Copyright
2024
First publish date
2021
Last edition
2024-08-01
Last publish date
2024-08-01T21:24:12.809750
Symptom Area Affected Problem Solution Reference Number Release fixed in
IBMi Metabase upgrade scripts contain a misspelled column for rp_log Connect CDC Director Incorrect Metabase scripts to create a SQL Server trigger based capture Metabase The circumvention is to is to alter the rp_trans table to allow null values for rp_c_stamp column for trigger-based metabase for SQL Server.Reference number. MXSHR-7592 5.8.07.00
When the Oracle Change Selector encounters a begin of a transaction it captures this information. If this transaction does not contain any statements for tables marked for capture it is writing this information to the rp_log table after a period of time. Then this information does not get cleaned up. Change Selector, Oracle job   Updated model refresh to skip the start rows. MXSHR-4970 5.8.07.00
Unprintable characters are not replicating correctly to Kafka JSON targets Connect CDC application with Kafka JSON targets   Fixed JSON formatting. MXSHR-7498 5.8.07.00
Connect CDC Director The Azure SQL Metabase fails when testing the connection   The name of the metabase can contain special characters such as _ (underscore), and - (hyphen). MXSHR-7489 5.8.07.00
Connect CDC Director The Director blocks using an underscore for the Metabase database name   Removed the limitation and ensured it does not break anything MXSHR-42 5.8.07.00
In 5.8.05.02 the validation for a NULL ALLOWED source column when the target column is NOT NULL when Data Enhancement is used is now an ERROR. Earlier it was a WARNING. Validate a Connect-CDC Model with version 5.8.05   Changed back the message from error to a warning. MXSHR-7325 5.8.07.00, 5.8.06.02
When the rollback agent attempts to delete rows that are no longer in the queue, it repeatedly issued error messages to both the CSxLOG file and the joblog. This caused the job’s temporary storage to grow exceptionally fast. Scenarios where the rollback agent would attempt this behavior include: Manually clearing the queues (through CLRPFM or MonCon “Delete Queues”) or restarting a request before the rollback agent was able to successfully delete the records from the queues. Connect CDC   The rollback agent has been changed to seamlessly handle this scenario with minimal logging and no consequence to temporary storage. MXSHR-7585 5.8.07.00