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

ggsci> START REPLICAT rep01 If it abends immediately with the same RBA, the corruption is real. From the error message:

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). ogg-01184 expected 4 bytes but got 0 bytes in trail

cd $OGG_HOME ./logdump logdump> open /u01/gg/dirdat/rt000012 logdump> ghdr on logdump> detail on logdump> pos 4820192 logdump> n ggsci&gt; START REPLICAT rep01 If it abends immediately

TransInd: 1 (First record of transaction) XID: 3.27.12345 Add a FILTER or MAP exception in the Replicat parameter file: If not, implement them immediately after recovery

This assumes you have file-level backups. If not, implement them immediately after recovery. Solution 4: Abort and Full Resync (Nuclear Option, Zero Data Loss but High Downtime) When corruption is widespread and no clean RBA exists, or if your replicat was far behind:

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: