The Oracle GoldenGate error OGG-01184 occurs when a process (typically a Data Pump or Replicat) attempts to read a record from a trail file but encounters an unexpected end-of-file or a corrupted record trailer. Technical Review
The Cause: This error signifies that the process expected a 4-byte record trailer token but found 0 bytes instead. This usually indicates that the trail file was truncated or not fully written—often due to a disk space issue, a network interruption during file transfer, or a source process (Extract) crashing while writing.
The Checkpoint Conflict: You may also see a related error, OGG-01705, which occurs when the process's checkpoint position is actually beyond the physical size of the trail file. Recommended Action Plan ogg-01184 expected 4 bytes but got 0 bytes in trail
Validate Trail Integrity: Use the Logdump utility to inspect the specific Relative Byte Address (RBA) mentioned in the error. This helps determine if the file is truly empty at that point or just corrupted. Repump or Re-extract:
If the issue is in a remote trail (target side), try deleting the corrupted trail file and restarting the Pump process on the source to re-transmit the data. The Oracle GoldenGate error OGG-01184 occurs when a
If the local trail (source side) is corrupted, you may need to reposition the Extract process to a previous valid sequence number or RBA.
Check System Resources: Verify that the destination disk is not full and that there are no "file handle shortages" on the host system. 3. Primary Causes of OGG-01184
Reference Official Support: For detailed recovery steps, Oracle documentation frequently points to Doc ID 1138409.1 on My Oracle Support, which provides specific instructions for handling trail file mismatches. Extract & Pump Abends — oracle-mosc
start replicat <rep_name>
Set up alerts for the trail directory (e.g., 80% full). Use GGSCI info:
GGSCI> INFO EXTRACT *, TASKS
GGSCI> LAG EXTRACT *, REPLICAT *