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

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:

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

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. Part 2: Immediate Diagnosis (Do Not Panic) When

After the replicat passes that RBA, remove the filter and restart normally. What is a GoldenGate Trail File

-- For Extract (writing trail) TRAILCHKSUMBLOCKCHECK YES TRAILCHKSUMCHECK YES -- For Replicat (reading trail) CHKPOINTCHKSYNC YES

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:

This error is not a simple configuration mismatch. It typically signals a serious structural problem in the trail file—the lifeblood of your GoldenGate replication. At its core, GoldenGate expected to read a 4-byte control field (usually a record length indicator or a checksum), but instead found an End-Of-File (EOF) marker or a null value (0 bytes).