Update appears to be ignored when Column is Updated To Null a 2nd time

(Doc ID 1265822.1)

Last updated on JANUARY 13, 2017

Applies to:

Oracle GoldenGate - Version: 10.4.0.19 and later   [Release: 10.4.0 and later ]
Information in this document applies to any platform.

Symptoms

Here is an example,

When a 2nd null update is done on a number field, it appears that the 2nd null update only puts the KEY values in the trail, not the KEY plus the Nulls

Table TEST.S1  (col1 number primary key, col2 number)

SQL> select * from s1 where a=1;

A              B
---------- ----------
1               1

First update :
SQL> update s1 set b=null where a=1;
SQL> commit;

1 row updated.

What appears in the trail

logdump :
 2010/09/01 11:12:57.000.000 FieldComp Len 17 RBA 1578
Name: TEST.S1
After Image: Partition 4 G s
0000 0005 0000 0001 3100 0100 04ff ff00 00 | ........1........
Column 0 (x0000), Len 5 (x0005)
0000 0001 31 | ....1
Column 1 (x0001), Len 4 (x0004)
ffff 0000 | ....


SQL> select * from s1 where a=1;

A             B
---------- ----------
1              NULL

If you do it a 2nd time

SQL>  update s1 set b=null where a=1; 
SQL > commit;

1 row updated.

This is what appears in the trail

Logdump :

2010/09/01 11:13:11.000.000 FieldComp Len 9 RBA 1712
Name: TEST.S1
After Image: Partition 4 G s
0000 0005 0000 0001 31 | ........1
Column 0 (x0000), Len 5 (x0005)
0000 0001 31 | ....1
-----------------------

SQL> select * from s1 where a=1;

A             B
---------- ----------
1               NULL

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms