5.8.05 - 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 has column with TIMESTAMP(0) defined but not mapped, the Change Selector shuts down. Change Selector Only supported TIMESTAMP or TIMESTAMP(6) Will support any TIMESTAMP(<x>) definition on DB2 for IBMi as a source. For example,
DCL-S TS0 TIMESTAMP(0);    // YYYY-MM-DD-hh-mm-ss
DCL-S TS1 TIMESTAMP(1);    // YYYY-MM-DD-hh-mm-ss.f
DCL-S TS6A TIMESTAMP;      // YYYY-MM-DD-hh-mm-ss.ffffff
DCL-S TS6B TIMESTAMP(6);   // YYYY-MM-DD-hh-mm-ss.ffffff
DCL-S TS12 TIMESTAMP(12);  // YYYY-MM-DD-hh-mm-ss.ffffffffffff
Default definition is:
TIMESTAMP;      // YYYY-MM-DD-hh-mm-ss.ffffff
    or
DCL-S TS6B TIMESTAMP(6);   // YYYY-MM-DD-hh-mm-ss.ffffff
For other timestamp length, CS will either pad with 0 or truncate to 6 fractional seconds:
DCL-S TS0 TIMESTAMP(0);    // YYYY-MM-DD-hh-mm-ss              --> YYYY-MM-DD-hh-mm-ss.000000 (padding)
DCL-S TS1 TIMESTAMP(1);    // YYYY-MM-DD-hh-mm-ss.f            --> YYYY-MM-DD-hh-mm-ss.f00000 (padding)
DCL-S TS12 TIMESTAMP(12);  // YYYY-MM-DD-hh-mm-ss.ffffffffffff --> YYYY-MM-DD-hh-mm-ss.ffffff (truncate)
MXSHR-7180 5.8.05.02
Kafka messages not partitioned correctly Partitioning of Kafka messages when Partition by “Source Table Name” Kafka partition key if different from 5.8.04 when partitioned by Source table name.   MXSHR-7144 5.8.05.02
Postgres Loader does not handle special characters correctly Postgres copy loader for copy and sync requests Special characters such as æ, ø and å are not copied correctly to the target table.   MXSHR-7157 5.8.05.02
Unmonitored error message that generates JOBLOG entry which causes the requested heap space to be invalid. Change Selector A memory management issue while processing OMNIREP *JOBD on Change Selector start   MXSHR-7066 5.8.05.01
OMNIREP *JOBD usage for IBMi Change Selector Change Selector Created library list were added in reverse order

By default the install library will come first and then will come the additional libraries retrieved from OMNIREP JOBD. (Example A{*})

However if a customer needs to specify the position of the install library it can be added namely in the lilbrary list of OMNIREP JOBD and will consequently keep the same position. (Example B{*})

MXSHR-6930 5.8.05
Kafka messages not partitioned correctly Partitioning of Kafka messages when Partition by “Source Table Name” or “Round Robin” is specified.     MXSHR-6763 5.8.05