Goldengate BEFORE Function Not Working For SQL Server BIT Data Type
(Doc ID 2632346.1)
Last updated on APRIL 17, 2023
Applies to:
Oracle GoldenGate - Version 12.3.0.1.4 to 12.3.0.1.4 [Release 12.3]Oracle Solaris on SPARC (64-bit)
Symptoms
The issue observed is with the use of @BEFORE function for data that is BIT datatype in SQL and number in oracle.
If @BEFORE(status) is removed from the map statement, the transaction is no longer discarded and the before image for the remaining 2 columns are populated on the target,
Also you've done a test where the same trailfile was used on another SQL db target, In this case, @BEFORE(status) is correctly mapped and target table gets populated with the before image or the BIT column.
This is leading us to assume that the issue lies when the @BEFORE function tries to replicat the BIT datatype from SQL to number datatype on Oracle.
converting BIT to number works fine as in colmap statement status=status works fine. The issue lies with the mapping bef_status=@before(status)
Cause
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
Symptoms |
Cause |
Solution |
References |