ls -l ./dirdat/rt* If the last trail file is suspiciously small or ends abruptly, it may be incomplete.
Alter the Pump/Replicat to start at the beginning of the next available sequence number. ALTER PUMP , EXTSEQNO , EXTRBA 0 4. Best Practices to Prevent OGG-01184
If you need help resolving this issue in your environment, please let me know: OGG-01184 - Oracle GoldenGate Error Messages ogg-01184 expected 4 bytes but got 0 bytes in trail
The hydrophone had been listening to a trench no one had mapped. And something down there, she realized with a cold wash of certainty, did not want to be known. It had reached up through the file system — not corrupting, not deleting, just un-writing the last four bytes of every copy.
#!/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 Best Practices to Prevent OGG-01184 If you need
: Any changes after the truncation point in the old trail are lost. You must reconcile them manually or reload the affected table(s).
Placing trail files on unstable or incorrectly tuned clustered file systems (e.g., poorly configured NFS or ACFS) can cause write delays, out-of-order writes, or cached IO drops. you have a gap.
Compare the current write position of Extract with the read position of Replicat. If Extract has passed the bad offset but Replicat cannot read it, you have a gap.