Ogg-01184 Expected 4 Bytes But Got 0 Bytes In Trail ❲4K❳
logdump> pos 4820192 logdump> count 1 Look for TransInd and XID . Example output:
logdump> pos 4819000 logdump> n logdump> n logdump> n Observe the last good record before 4820192 . Is there a gigantic transaction? A LOB update? A BLOB ? Large transactions are often culprits because they span multiple trail blocks. Choose your path based on whether you can afford to lose some data and your ability to resync. Solution 1: Skip the Corrupt Transaction (Low Risk, Minimal Data Loss) If the corrupt RBA is at the beginning of a transaction (not in the middle of a multi-record operation), you can tell Replicat to skip that transaction. ogg-01184 expected 4 bytes but got 0 bytes in trail
#!/bin/bash for trail in /u01/gg/dirdat/rt*; do echo "checking $trail" echo "open $trail" > /tmp/logdump_cmd echo "n" >> /tmp/logdump_cmd echo "q" >> /tmp/logdump_cmd /u01/gg/logdump < /tmp/logdump_cmd | grep -i "error\|corrupt\|unexpected" done Scenario: A large financial firm replicates a 10TB Oracle database. One night, a backup job fills the /goldengate filesystem to 100%. The Extract continues writing but fails to complete the last record in rt000241 . logdump> pos 4820192 logdump> count 1 Look for
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: A LOB update
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: