Welcome Guest! Log in


This article describes the principal changes of IBM DB2 Component.

If you need further information, please consult the full changelog.

Component download section can be found at this page.

Note:

Stambia DI is a flexible and agile solution. It can be quickly adapted to your needs.

If you have any question, any feature request or any issue, do not hesitate to contact us.

 

This article is dedicated to Stambia DI 2020 (S20.x.x) or higher.

 

Component.DB2.2.0.4

Minor improvements and fixed issues

This version contains some minor improvements and fixed issues, which can be found in the complete changelog.

 

Complete changelog

The complete changelog with the list of improvements and fixed issues can be found at the following location.

 

Component.DB2.2.0.3

Change Data Capture (CDC)

Multiple improvements have been performed to homogenize the usage of Change Data Capture (CDC) in the various Components.

Parameters have been homogenized, so that all Templates should now have the same CDC Parameters, with the same support of features.

Multiple fixes have also been performed to correct CDC issues. Refer to the changelog for the exact list of changes.

 

Minor improvements and fixed issues

This version also contains some other minor improvements and fixed issues, which can be found in the complete changelog.

 

Complete changelog

The complete changelog with the list of improvements and fixed issues can be found at the following location.

 

Component.DB2.2.0.2

Fix reverse of DB2 / 400 which could contain invalid characters

When doing a reverse on AS/400 the table and column comments sometimes contain some invisible characters incompatible with Unicode, which cause issues when saving the Metadata, raising exceptions such as "java.lang.RuntimeException: An invalid XML character (Unicode 0x0) was found in the element content.".

To avoid such issues, the reverse does not reverse comments anymore for DB2 / 400, as they can contain invalid characters.

 

Component.DB2.2.0.1

Fixed issue on truncate statement

With IBM DB2 UDB / IBM DB2 UDB for zos / IBM DB2 400, generated truncate table statements were missing the IMMEDIATE keyword, which were causing errors when executing them.

 

 

 

 

Articles

Suggest a new Article!