Ogg-01184 Expected 4 Bytes But Got 0 Bytes In Trail

If you have identified that the problematic trail file has a size of 0 bytes, the solution is straightforward. GoldenGate cannot process an empty file.

Restart the replicat once to confirm it’s not a transient I/O glitch:

ggsci> START REPLICAT rep01

If it abends immediately with the same RBA, the corruption is real. ogg-01184 expected 4 bytes but got 0 bytes in trail

The error ogg-01184 expected 4 bytes but got 0 bytes in trail is a distress signal from your GoldenGate trail file. It indicates an incomplete or truncated write operation. While intimidating, it is recoverable through careful use of logdump, transaction skipping, or file recovery.

start replicat <rep_name>

If the Extract process that generated the trail is gone (e.g., source system down):

Solution: Bypass the Corrupted Record Use logdump to skip the bad header: If you have identified that the problematic trail

logdump> open /ggs/dirdat/mt000001
logdump> pos 0
logdump> SCAN 4 N
logdump> NEXT 1
logdump> COUNT 10

But more directly, in Replicat parameter file: Replace the damaged trail with the next good one:

GGSCI> ALTER REPLICAT <rep_name>, EXTSEQNO <next_seq>, EXTRBA 0

Then re-sync missing data from source using initial load or GoldenGate’s REPLICAT SPECIALRUN. If it abends immediately with the same RBA,

Check the ggserr.log for the exact error line. Note:

Example:

Trail file /ggs/dirdat/mt000001 at offset 626222