Ogg-01184 Expected 4 Bytes But Got 0 Bytes In Trail 【99% QUICK】

start replicat <rep_name>

Before attempting a fix, verify the state of your trail files using the following steps.

Always stop GoldenGate processes gracefully before system shutdown:

GGSCI> STOP EXTRACT *
GGSCI> STOP REPLICAT *
GGSCI> STOP MANAGER

Subject: Production Extract Abend Error Code: OGG-01184 Status: Critical

Faulty storage, memory issues, or filesystem corruption can corrupt the trail file. In such cases, the error is a symptom rather than the root cause. ogg-01184 expected 4 bytes but got 0 bytes in trail

Add this to both Extract and Replicat parameter files:

TRAILCHKSUMCHECK NO
TRAILCHKSUMBLOCKCHECK NO

Wait—no, that disables checking. To enable checksum validation (ensuring corruption is caught early):

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

Checksums add about 3-5% overhead but prevent silent corruption.

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.

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

logdump> next
logdump> next

If the trail file is simply truncated, there is no next record. start replicat <rep_name>

Step 2: If the file is partially recoverable, use logdump to write a clean trail:

logdump> open /u01/gg/dirdat/rt000012
logdump> filter include rba < 4820192
logdump> write to /u01/gg/dirdat/rt_clean 0

Then rename rt_clean to rt000012 (back up original first).

Step 3: Alter Replicat to start at the last good RBA before corruption:

ggsci> ALTER REPLICAT rep01, EXTSEQNO 12, EXTRBA 4819000
ggsci> START REPLICAT rep01

Result: You lose all changes after RBA 4819000. Resync required for the missing window. Before attempting a fix, verify the state of