Is the error occurring on the or the target (Replicat) ? Have you checked the available disk space on both servers? What Oracle GoldenGate version are you running?
The GoldenGate process was reading a trail file and expected to find a 4-byte record trailer (a marker indicating the end of a record). Instead, it encountered 0 bytes (an empty space or end of file) at a specific Relative Byte Address (RBA).
In simple terms: GoldenGate reached a point in the trail file where a new record should begin, but there was no data left to read. The file is either incomplete or malformed. ogg-01184 expected 4 bytes but got 0 bytes in trail
From a safe RBA before the corruption (e.g., RBA 4819000), step forward record by record:
If the (source side) is corrupted, you may need to reposition the Extract process to a previous valid sequence number or RBA. Is the error occurring on the or the target (Replicat)
This article provides a complete, step-by-step guide to diagnosing, fixing, and preventing the OGG-01184 error. We will cover everything from basic concepts to advanced surgical recovery techniques.
If the error is paired with OGG-01705 (Input checkpoint position greater than the size of the file), the checkpoint is corrupt. The GoldenGate process was reading a trail file
:If the corruption is at the very end of the file, you can force the source process to start a new trail file: On the source, run: ALTER , ETROLLOVER . Note the new sequence number.
GGSCI> SEND REPLICAT <rep_name> STATS GGSCI> INFO REPLICAT <rep_name>, DETAIL GGSCI> SEND REPLICAT <rep_name> GETPOS
ggsci> ALTER REPLICAT rep01, EXTSEQNO 12, EXTRBA 4819000 ggsci> START REPLICAT rep01
stop extract ext1 alter extract ext1, extseqno 000003, extrba 0 start extract ext1