Expected 3,number,0 bytes, but got 4,number,0 bytes, in trail 0, seqno 1,number,0, reading record trailer token at RBA {2, Oracle Help Center Extract & Pump Abends — oracle-mosc
Find the transaction ID (XID) of the corrupt record. In logdump :
Reposition the process: ALTER , RBA .
A typical error stack in the ggserr.log looks like:
Open the problematic trail file identified in the error log: Logdump 1 > open ./dirdat/et000001234 Use code with caution. Move to the exact offset where the error occurred: Logdump 2 > pos 104857600 Use code with caution. Try to read the next record: Logdump 3 > next Use code with caution. ogg-01184 expected 4 bytes but got 0 bytes in trail
Troubleshooting OGG-01184: Expected 4 Bytes But Got 0 Bytes in Trail
If the corruption is severe, the source Extract may need to be repositioned to recreate the trail files from a known good point in the archive logs. Contact Support:
Log into the server host operating system and look at the physical attributes of the trail file mentioned in the error. Compare the real size with the RBA listed in the error: ls -l ./dirdat/et000012 Use code with caution.
Monitor the process to ensure it passes the checkpoint smoothly. Expected 3,number,0 bytes, but got 4,number,0 bytes, in
(Note: Increment the extseqno by 1 from the broken file number). Restart the Replicat: GGSCI > start replicat REP1 Use code with caution. Option B: Regenerate the Trail File from the Source
If the file system hosting the GoldenGate trail files ( dirdat directory) runs out of space, GoldenGate cannot complete writing the current record block. It writes a partial record header but 0 bytes of the expected trailing data. 4. GoldenGate Version Mismatches
The trail was empty because the trail had been wiped. And whatever wiped it was still listening.
If the trail file on disk is physically corrupted or truncated, you cannot force GoldenGate to read past the missing bytes. You must signal the writing process to abandon the damaged trail block and create a completely fresh sequencer. Move to the exact offset where the error
Oracle GoldenGate provides a utility called logdump to inspect the internal structure of trail files. Use it to look at the exact position where the process failed. Launch logdump from your GoldenGate home directory: ./logdump Use code with caution. Open the offending trail file: Logdump 1 > open ./dirdat/et000000000 Use code with caution.
Expected 3,number,0 bytes, but got 4,number,0 bytes, in trail 0, seqno 1,number,0, reading record trailer token at RBA {2, Oracle Help Center Extract & Pump Abends — oracle-mosc
After rolling over, you may need to reposition the downstream process to the new sequence number.
Save the file and start the Replicat. Note: Remove temporary parameters once the process successfully moves past the broken file. Best Practices to Prevent OGG-01184
If the filesystem hosting the GoldenGate dirdat directory on the target server runs out of space, the writing process cannot commit the complete block. This leaves a partial record at the end of the trail file. 3. Abrupt Process or Server Shutdowns