If the corrupt RBA is at the (not in the middle of a multi-record operation), you can tell Replicat to skip that transaction.
If the disk partition hosting the GoldenGate dirdat/ directory runs out of storage while the Extract is writing, the file terminates abruptly mid-record.
ERROR OGG-01184 Expected 4 bytes, but got 0 bytes, in trail ./dirdat/no000007, seqno 7, reading record trailer token at RBA 246849346. . 2. Verify File Integrity
If the error is constant and occurred after an upgrade, check your FORMAT RELEASE settings:
Expected 3,number,0 bytes, but got 4,number,0 bytes, in trail 0, seqno 1,number,0, reading record trailer token at RBA {2, Oracle Help Center Extract & Pump Abends - Oracle Communities ogg-01184 expected 4 bytes but got 0 bytes in trail
: Before proceeding, stop the affected Extract or Replicat process to prevent further complications. Use the command STOP EXTRACT <group_name> in GGSCI.
Depending on whether the issue occurs on your Source system (Extract / Pump) or Target system (Replicat), select one of the following systematic repair pathways.
| Field | Size | Description | |-------|------|-------------| | Record Length | 4 bytes | Indicates the total size of the following data | | Record Data | Variable | Actual change data in canonical format | | Checksum (optional) | 4 bytes | Integrity check |
Is this error happening on an , a Pump , or a Replicat process? What version of Oracle GoldenGate are you running? If the corrupt RBA is at the (not
The best fix is never encountering this error. Implement these hardened practices.
Find the transaction ID (XID) of the corrupt record. In logdump :
ggsci> START REPLICAT rep01
The error message OGG-01184: Expected 4 bytes but got 0 bytes in trail is the Oracle GoldenGate equivalent of a "sudden death" notification. It is a low-level I/O error that indicates the Extract process reached the end of a trail file expecting to find a complete record header (4 bytes) but found nothing but empty air. Use the command STOP EXTRACT <group_name> in GGSCI
If the steps above fail to resolve the issue, the problem may be more complex.
The OGG-01184 Expected 4 bytes, but got 0 bytes error is one of the more serious issues you can encounter, but it is almost always recoverable. In most cases, the solution is a straightforward ALTER EXTRACT, ETROLLOVER command. However, the true lesson of this error is the importance of building a resilient GoldenGate infrastructure. By focusing on stable storage, regular maintenance, and a solid backup plan, you can protect your replication pipelines from the disruption of trail file corruption.
To do this:
Never use hard terminal kills ( kill -9 ) on active Oracle GoldenGate processes unless absolutely necessary. Always use the internal STOP command via the GGSCI command line utility.
She scrolled up. The OGG file had played fine for eleven minutes and forty-three seconds. Then silence. Then the error.
EXTTRAIL /u01/gg/dirdat/rt, MEGABYTES 512, ROLLOVER AT 23:00