Ogg-01184 Expected 4 Bytes But Got 0 Bytes In Trail 〈UPDATED〉

Find the transaction ID (XID) of the corrupt record. In logdump :

This article provides a complete, step-by-step guide to diagnosing, fixing, and preventing the OGG-01184 error. We will cover everything from basic concepts to advanced surgical recovery techniques. What is a GoldenGate Trail File? Before fixing the error, you must understand what GoldenGate is trying to read. A trail file (e.g., dirdat/rt000001 ) is a binary sequence of records. Each record represents a database operation (INSERT, UPDATE, DELETE, DDL). The structure is: ogg-01184 expected 4 bytes but got 0 bytes in trail

Checksums add about 3-5% overhead but prevent silent corruption. Do not use unlimited file sizes. Force rollover to reduce blast radius: Find the transaction ID (XID) of the corrupt record

When this happens, your target database stops synchronizing. Data latency begins to grow. And if not handled correctly, you risk data divergence between source and target. What is a GoldenGate Trail File

You lose exactly one transaction. You must manually reconcile that row(s) later. Solution 2: Use LOGDUMP to Skip to Next Good Record (Medium Risk) If the corrupt RBA is mid-transaction (TransInd = 2, 3, or 4), you cannot skip just one transaction without breaking referential integrity for that transaction’s group of operations.

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: