My Oracle Support Banner

How To Exclude NULL Values Written To Kafta Message When Trails Do Not Have Same Columns (Doc ID 2409414.1)

Last updated on NOVEMBER 25, 2019

Applies to:

Oracle GoldenGate Application Adapters - Version and later
Information in this document applies to any platform.


If you uses nocompress updates to log only keys and changed values to trail.
While using KAFTA handler to write messages, the on existing columns on trail gets populated to message file as NULL.

Is there any way to avoid getting NULL written to messages for non existent columns on trails?

++ Trail entry example ++

2018/06/02 13:31:36.023.086 FieldComp Len 18 RBA 1379
Name: <schema>.<table name>
After Image: Partition 4 G s
0000 0005 0000 0001 3100 0200 0500 0000 0132 | ........1........2
Column 0 (x0000), Len 5 (x0005)
0000 0001 31 | ....1
Column 2 (x0002), Len 5 (x0005)
0000 0001 32 | ....2

Current Kafta message : {"<col0>":1.0,"<col1>":null,"<col2>":2.0}

Expected result : {"<col0>":1.0,"<col2>":2.0}


To view full details, sign in with your My Oracle Support account.

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

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.