Ogg-01184 Expected 4 Bytes But Got 0 Bytes In - Trail

Introduction: The Silent Corruption of Transaction Logs 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:

ADD EXTRACT ext01, TRANLOG, BEGIN SCN 123456789 Recreate Pump and Replicat, start fresh. Part 4: Preventing OGG-01184 Before It Happens The best fix is never encountering this error. Implement these hardened practices. 1. Enable Trail File Checksums Add this to both Extract and Replicat parameter files: ogg-01184 expected 4 bytes but got 0 bytes in trail

After the replicat passes that RBA, remove the filter and restart normally. Introduction: The Silent Corruption of Transaction Logs If

2025-01-15 10:23:45 ERROR OGG-01184 Oracle GoldenGate Delivery for Oracle, rep01.prm: Expected 4 bytes but got 0 bytes in trail file /u01/gg/dirdat/rt000012, at RBA 4820192. 2025-01-15 10:23:45 ERROR OGG-01668 PROCESS ABENDING. The 4820192 is critical—it tells you exactly where in the trail file the corruption begins. Part 2: Immediate Diagnosis (Do Not Panic) When you see this error, follow these diagnostic steps before attempting any fix. Step 1: Verify the Error is Consistent Restart the replicat once to confirm it’s not a transient I/O glitch: Implement these hardened practices

Manually locate the next valid record header after the corruption. In logdump , after hitting EOF at 4820192, try to “bump” forward:

| Field | Size | Description | |-------|------|-------------| | Record Length | 4 bytes | Indicates the total size of the following data | | Record Data | Variable | Actual change data in canonical format | | Checksum (optional) | 4 bytes | Integrity check |

ggsci> ALTER REPLICAT rep01, EXTSEQNO 12, EXTRBA 4819000 ggsci> START REPLICAT rep01 You lose all changes after RBA 4819000. Resync required for the missing window. Solution 3: Recover from Source Trail or Archive (Recommended for Production) If you have archive trails enabled ( EXTTRAIL with ROLLOVER at source) or a backup of the trail files before corruption: