: Any changes after the truncation point in the old trail are lost. You must reconcile them manually or reload the affected table(s).
Navigate to the dirdat directory and check the file size: ls -l ./dirdat/no000007 Use code with caution.
Open the problematic trail file specified in the error message: Logdump 1 > open ./dirdat/et000000123 Use code with caution.
This public link is valid for 7 days and shares a thread, including any personal information you added. This link or copies made by others cannot be deleted. If you share with third parties, their policies apply. Can’t copy the link right now. Try again later. ogg-01184 expected 4 bytes but got 0 bytes in trail
After the new trail is created, use ALTER [PROCESS_NAME], EXTSEQNO [new_seq_no], EXTRBA 0 to point the Pump or Replicat to the start of the new file. 2. Automatic Trail Recovery (OGG 12.2+)
When you see this error, follow these diagnostic steps before attempting any fix.
Understanding why this error occurs is essential for preventing its recurrence. The most common triggers include: 1. Disk Space Exhaustion : Any changes after the truncation point in
Look for TransInd and XID . Example output:
If skipping files causes data loss or the corruption is in the middle of a trail file, regenerate the trail from the source Pump process.
Can you share the exact physical file size compared to the RBA mentioned in your logs? Share public link Open the problematic trail file specified in the
If you need help resolving this issue in your environment, please let me know: OGG-01184 - Oracle GoldenGate Error Messages
The OGG-01184 error— expected 4 bytes but got 0 bytes in trail —is a clear indicator of trail file truncation or corruption. While the immediate fix involves rolling over the trail and possibly realigning Replicat, the long-term solution lies in robust monitoring, proper configuration, and disciplined file handling.
Then rename rt_clean to rt000012 (back up original first).