When the filesystem hosting the trail directory runs out of space, GoldenGate cannot write the complete 4-byte header and subsequent data. The file is truncated at the point where the write failed. Replicat later reads this truncated file and encounters 0 bytes instead of the expected header.
Her colleague didn't look up. "CRC. Length. Sync flag. Depends on the codec."
If the file is not in the expected format or is not a valid Oracle data file/backup, you might encounter this error. ogg-01184 expected 4 bytes but got 0 bytes in trail
Identify the sequence number before the corrupt file:
Abrupt termination is the #1 cause of “expected 4 bytes but got 0”. When the filesystem hosting the trail directory runs
: Check the actual size of the trail file mentioned in the error at the OS level and compare it to the RBA reported in the error message. Inspect the Previous Process
If it abends immediately with the same RBA, the corruption is real. Her colleague didn't look up
Use the logdump utility to open the failing trail file and navigate to the RBA (Relative Byte Address) mentioned in the error log. This confirms if the record at that position is indeed truncated or invalid.