My Oracle Support Banner

Resync / Recover Data ( Tables , Trails ) Trails Are Missing, Damaged, Incompatible, Corrupt or Suspect for Extract or Replicat (Doc ID 1614665.1)

Last updated on JULY 30, 2018

Applies to:

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

Goal

To reliably recover data from Oracle logs when such data may have been lost or damaged in the trails prior to application by replicat or processed by an extract pump.
Recovery depends on whether the local extract trail as created by the main transaction log extract or target remote trail as written by an extract pump.
Examples of these Error messages in the report file indicates a possible corrupt trail:
OGG-01028  Incompatible record (logical EOF) in
OGG-01179: Mismatched record version/bad data in {0} at {1}
OGG-01184: Expected {3,number,0} bytes, but got {4,number,0} bytes, in trail {0},seqno {1,number,0}, reading record trailer token at RBA {2,number,0}
....etc

Solution

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
Goal
Solution
 
Methods
 
1) For trails created by extract OGG versions 11.2+ and replicat running with a database checkpoint table (best practice).
 a) STOP groups
 b) FIND LOG_CSN
 
c) FIND LOCAL TRAIL WITH LOG_CSN
 

d) ALTER PUMP TO REBUILD TRAIL
 e) ALTER REPLICAT TO NEW TRAIL AND START
 
 
 
 
 
 
2) The OGG version is earlier than V11.1 and does not checkpoint the last source transaction done.

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