To understand the error, you need to understand how GoldenGate writes data. GoldenGate stores captured database operations in intermediate files known as "trail files." These files are broken down into logical records, which include transaction headers, data, and record trailers.
Note the sequence number ( seqno 15 ) and the Relative Byte Address ( RBA 45612398 ). 2. Compare File Size vs. Expected Position
Since the primary Extract reads from the database transaction logs (Oracle Redo/Archive logs), you can alter the Extract to regenerate the clean trail data. :
From a safe RBA before the corruption (e.g., RBA 4819000), step forward record by record: ogg-01184 expected 4 bytes but got 0 bytes in trail
You lose exactly one transaction. You must manually reconcile that row(s) later.
She ran a differential against the source recording — the one from the deep-sea hydrophone array, pulled up last week. The original had the four bytes: 0x4B 0x4E 0x4F 0x57 . ASCII: .
Ensure that NFS mounts or SAN connections are stable and that you do not have hidden network timeouts causing interrupted writes. To understand the error, you need to understand
If the corruption is severe, you may need to delete the corrupt trail file and allow the Extract/Pump to re-extract data from the transaction logs. Stop the Extract/Pump process. Move/Rename the corrupted trail file (e.g., no000007 ).
If you cannot regenerate the data and the missing payload represents a negligible transaction that you are willing to manually reconcile later, you can force the Replicat to skip to the next sequence file.
If the Extract process that generated the trail is gone (e.g., source system down): : From a safe RBA before the corruption (e
$ cd /ggs $ ./logdump logdump> open /ggs/dirdat/mt000001 logdump> ghostlib on logdump> gcount on logdump> detail on logdump> next
Troubleshooting OGG-01184: Expected 4 Bytes, But Got 0 Bytes in Trail
Alter the Data Pump to roll over to a new sequence number or reposition to the last valid RBA of the source trail: GGSCI> alter pump_name, extseqno 123, extrba 1234567 Use code with caution. Restart the Data Pump: GGSCI> start pump_name Use code with caution. Scenario B: The Error Occurs in the Replicat
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.