Base24 Refresh Rename Process Can Result In Records Replicated To Wrong Target File
(Doc ID 1310060.1)
Last updated on DECEMBER 07, 2019
Applies to:
Oracle GoldenGate - Version 4.0.0 and laterHP NonStop Itanium (Guardian)
HP NonStop S-series (Guardian)
Purpose
During a Base24 Full File Refresh, when the file is renamed, we have observed the following can occur:
1) During the CAF* rename to OLDCAF, for records to be replicated on the target system to the old CAF, and not the new CAF.
2) It is possible for the I/Os that occur in the correct order on the source to be placed into the trail files out of order because multiple Logger processes are in use.
How can we address these issues?
*CAF - applies to all refresh, PBF etc.
Troubleshooting Steps
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
| Purpose |
| Troubleshooting Steps |
| References |