About OGG-01028 recovery record is missing error

Question

Hi! everybody,
My enviroment is :windows server 2008 64bit ,oracle 11GR2,goldengate 11.1.1.1.I often meet the error :ogg-01028 recorery record is missing .
In mos,I found the relative article((Doc ID 1094767.1)
In this Document
Symptoms
Cause
Solution
References
Applies to:
Oracle GoldenGate - Version: 10.4.0.19 to 11.1.1.1.0 - Release: 10.4.0 to 11.1.1
Information in this document applies to any platform.
Symptoms
Extract abended with:
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.
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, 12693291.
Solution
This bug is fixed in v11.1.1.1 with patches for bugs 12693183, 12693291.
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.
For reference the following lists the block size of major platforms:
AIX, Linux, Sun, Windows & VMS: 512 Bytes
HP-UX, Tru64: 1024 Bytes
S390, MVS: 4096 Bytes.
2. Backup the checkpoint file in directory dirchk
3. info <ext> showch
Get current and recovery checkpoints, example:
EXTRACT EIDLD Last Started 2010-05-04 16:39 Status ABENDED
Checkpoint Lag 01:14:54 (updated 01:14:41 ago)
Log Read Checkpoint Oracle Redo Logs
2010-05-04 15:24:21 Seqno 14496, RBA 149274704
Current Checkpoint Detail:
Read Checkpoint #1
Oracle Redo Log
Startup Checkpoint (starting position in the data source):
Sequence #: 14496
RBA: 149273104
Recovery Checkpoint (position of oldest unprocessed transaction in the data source):
Sequence #: 14496
RBA: 149273104
Current Checkpoint (position of last record read in the data source):
Sequence #: 14496
RBA: 149274704
4. Alter both recovery checkpoint and current checkpoint to the start point of next block number
alter <ext>, extseqno <seq#>, extrba <rba#>
In the above example:
SQL> select ceil (149274704/512) * 512 from dual;
CEIL(149274704/512)*512
149275136
seq# remains the same as in the showch display.
ggsci> alter extract <ext>, 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 <ext>, 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 <ext>, ioextseqno 14496, ioextrba 149273104
6. info <ext>, showch
Confirm the change.
7. start <ext>
Note: Above example is for extract without threads option. For extract with threads option, "thread <thread#>" is needed for "alter extract " command.
e.g., "ggsci> alter extract <ext>, extseqno 14497, extrba 0" will be "ggsci> alter extract <ext>, thread <n>, extseqno 14497, extrba 0" (here, <n> is the ogg thread number).
My question is :This bug is fixed in v11.1.1.1 with patches for bugs 12693183, 12693291.My goldengate version is 11.1.1.,is it need any patch to avoid the error?If the patch can not resolve the problem ,can I use some utilities ,such as logdump,logmnor to find the relative sql detail when the extract abends.

Answer 1

Well, you have the seqno and RBA (where extract abended, on a zero length record). You could assume that the record before was good to go, and that should give you an idea of the relative SQL. You could also get down and dirty with Logminer, using the SCN as a starting point to find the last good record shown in the trail.