Option B: Reposition the Replicat Process (If applying to Target)
If the source trail itself is corrupted, you must force the source Extract to start a new file. www.oracle-scn.com ALTER EXTRACT , ETROLLOVER
Check the process report or ggserr.log to find the exact sequence number and RBA.
If the error occurs on a Target Replicat or a Data Pump Extract, and the primary source Extract is healthy, the easiest fix is to alter the pump to re-read from a known good position on the source and overwrite the corrupted target trail file. ogg-01184 expected 4 bytes but got 0 bytes in trail
If you are reading this, you have likely just encountered a nightmare scenario for any data replication engineer. Your Oracle GoldenGate (OGG) Replicat process has aborted with the cryptic message:
: Ensure the filesystem is not full, as this often prevents GoldenGate from completing record writes. Oracle Communities Potential Resolutions Repositioning
What is the and RBA reported in the error? Option B: Reposition the Replicat Process (If applying
Always verify that your destination disk isn't full. If it is, clear up space before attempting to alter your GoldenGate processes. df -h /path/to/goldengate Use code with caution. Step 4: The Recovery Options
Protocol 3: Re-generating the Trail (The Purge & Regen Method)
Carefully terminate the specific orphaned process that was holding onto the trail file lock: kill -9 Use code with caution. If you are reading this, you have likely
Use the PURGEOLDEXTRACTS parameter in the Manager configuration to automatically delete old trail files and prevent disk space exhaustion.
Before doing anything, review your GoldenGate error logs and the process report file. Look for the exact trail filename, the sequence number (e.g., seqno 7 ), and the exact Relative Byte Address (RBA) reported in the OGG-01184 message. Step 2: Check OS-Level File Health
This is the most common culprit. GoldenGate writes to trail files in buffered blocks. Usually, the OS handles the syncing of data to disk. However, if the server experienced a sudden power loss, a kernel panic, or a hard reset exactly while the Extract was writing a record, the file system might have closed the file handle without flushing the final buffer. The file system metadata says the file is size X, but the actual data blocks on the disk only contain data up to size X minus a few bytes. When GoldenGate restarts and re-reads the file, it sees the file size, assumes the data is there, tries to read the header, and hits a void.