Before Image Of Delete Operation In Trail Record Does Not Contain Non-PK Columns When GETUPDATEBEFORES Exists
(Doc ID 3034315.1)
Last updated on AUGUST 12, 2024
Applies to:
Oracle GoldenGate - Version 19.0.0.0.0 and laterOracle Cloud Infrastructure - Exadata Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Gen 2 Exadata Cloud at Customer - Version N/A and later
Information in this document applies to any platform.
Symptoms
When parameter GETUPDATEBEFORES is set, Before Image of Delete operation in Trail record does not contain non-PK columns even though enable supplemental logging for non-PK columns.
The result is not the expected behavior when target is filtering using non-PK columns with a FILTER clause.
This symptom can be reproduced regardless of mode (Classic/Integrated) of capture process.
Changes
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 |
| Changes |
| Cause |
| Solution |
| References |