Ogg-01184 Expected 4 Bytes But Got 0 Bytes In Trail !!exclusive!! File
In the ggsci console, alter the process to skip the bad trail block or roll over to a fresh trail file: ALTER EXTRACT , ETROLLOVER Use code with caution.
To ensure you never face an unexpected production outage from OGG-01184 again, implement these infrastructure safeguards:
: The process reached the end of the trail file earlier than expected, often because a previous write operation (by an Extract or Pump) was interrupted before the record trailer could be written. Checkpoint Mismatch
: Finding "0 bytes" means the file terminated prematurely. The metadata promised more data, but the filesystem returned an EOF (End of File). Root Causes of Trail File Truncation
Anti-virus software, backup agents, or third-party monitoring tools scanning the GoldenGate directory can temporarily lock trail files. This interferes with write operations and causes file corruption. Step-by-Step Troubleshooting and Resolution ogg-01184 expected 4 bytes but got 0 bytes in trail
If the error is on a Data Pump ( EXTRACT process), replace REPLICAT with EXTRACT in the command.
Look directly inside the GoldenGate report file ( .rpt ) or the overall alert log ( ggserr.log ). The error message provides essential tracking fields:
The error is a critical Oracle GoldenGate replicat failure that halts data synchronization. It occurs when a reading process encounters an unexpected end-of-file (EOF) or corrupted marker within a trail file.
Physical media errors can also cause this issue, especially if you are reading from or writing to removable media. In the ggsci console, alter the process to
GGSCI> alter replicat rep_name, extseqno , extrba 0 Use code with caution. : GGSCI> start replicat rep_name Use code with caution. Method 3: Use the TRAILBYTEORDER Parameter
If the corruption occurs at the very end of the trail file, you can force the Replicat to skip the corrupted fragment and move to the next sequential trail file. Open the GoldenGate Software Command Interface: ./ggsci Use code with caution.
2026-05-22T14:32:10.123-0500 ERROR OGG-01184 Oracle GoldenGate Delivery for Oracle, rep_prod.prm: Expected 4 bytes but got 0 bytes in trail file ./dirdat/et000001234, at offset 104857600. Use code with caution. What It Means
Always stop GoldenGate processes before rebooting or unmounting filesystems: The metadata promised more data, but the filesystem
Add a FILTER or MAP exception in the Replicat parameter file:
To fix OGG-01184, you must identify the exact location of the corruption and position the affected GoldenGate process past the damaged record. Step 1: Identify the Affected File and Position
View the information for your Extract to see the new trail sequence context: INFO EXTRACT extract_name Use code with caution.
Killing a primary Extract or Data Pump with hard system commands ( kill -9 ) during heavy transaction volumes can permanently prevent the process from writing its closing internal record trailers safely. Step-by-Step Diagnostics
Initialize the target from scratch using:
