Null Handling with CDC live audit setup

Problem Statement:

In our current CDC setup tables are mapped with Live audit where supplementary logging is enabled only on primary key columns and for other columns supplementary logging is not enabled. And hence we cannot differentiate between the actual updated NULL values and NULL which is inserted by CDC when source column is not updated.

CDC source instance created with read only access. Source Database minimal supplementary logging is enabled.

Solution:

Since we cannot apply supplementary logging for all columns on source database, we need solution that will differentiate the Actual Null values and NULL which is inserted by CDC when source column is not updated.

We understand that when there is no change in source column value which is not enabled for supplementary logging at source, CDC explicitly inserts NULL value for that column. we need CDC should not insert that explicit NULL value for that column where there is no change in source column.

Below example shows the difference between current and proposed solution where table has 2 columns named A and B where A is getting changed to value 1 and B column is unchanged.

Current CDC insert statement: insert into table (A,B) values ('1', NULL)

Proposed CDC insert statement: insert into table (A,) values (1)

So that we can handle that NULL for unchanged column with target table columns DDL with default criteria.

Needed By

Quarter

Post comment

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.

Please enter your email address

RELATED IDEAS

Null Handling with CDC live audit setup