in later OGG version, the error code is like following:
OGG-01028 Recovery record is missing from log with seqno 1934 when extract has reached log with seqno 1935, block size 512, and next_checkpoint RBA at 83962348.

Archive logs 14497 & 14498 exist, and restarting extract failed with same error.
Cause
The extract was manually stopped and current/next checkpoint is set to a zero length record in redo. This is a very rare condition, and the chance of hitting it is also low. When this extract was restarted, the error occurred. Extract’s Current/Next checkpoint is set to a zero length record at the end of a log and on restart this zero length record is skipped as it has no useful data. Since this record is skipped the recovery code thinks this record was missed and generates an error.

This is bug 12693183.
Solution
This bug is fixed in v11.1.1.1 with patches for bugs 12693183.

The following workaround may also be used with no data loss.
Workaround: change the current checkpoint RBA to next block boundary, keep the recovery checkpoint the same

1. Get block size of your platform.
The block size is shown in the error message.
2010-05-04 15:42:23 GGS ERROR 190 Recovery record is missing from log with seqno 14496 when extract has reached log with seqno 14497, block size 512, and next_checkpoint RBA at 149274704.

ggsci> alter extract , extseqno 14496, extrba 149275136
If the new rba number is bigger than the current file size of the archivelog file, you have to alter both checkpoint to start from RBA 0 in next seqno file.
For example, if the size of archived log that has seqno 14496 is only 149275000, which is smaller than the new RBA calculated, 149275136, you have to issue the following command
ggsci> alter extract , extseqno 14497, extrba 0

5. Alter the extseqno and extrba of recovery checkpoint back to its original recovery checkpoint position
In this example,
ggsci> alter extract , ioextseqno 14496, ioextrba 149273104