Cause

Extract may have hit bug which can occur while processing a 0-length record while the extract is enabled for Bounded Recovery.

Solution

As a work around , please use the below extract parameter and start the extract which will turn off the Bounded recovery. When BR is off, the Extract will do a normal recovery, so it needs all the archive logs file starting from recovery checkpoint of the extract.

BR BROFF

The only time BR is used is upon restart of extract, and only if there were any long running transactions that were persisted. If all of the transactions in the workload are of short duration (less than the BR interval default of 4 hrs), then even upon restart, standard recovery is active instead of bounded recovery.

And regarding transactions we are only concerned with ones that modify data. There may, of course, be batch jobs which run and take a long time, so these could fall into the long duration category thats mentioned above, but even in this case, as long as the redo logs/archive logs are available for standard recovery, the restart time should not be much longer with SR (standard recovery) than BR.

Once the extract has passed by the problematic RBA, this parameter can be removed.The permanent fix is planned for OGG v11.2.1.