This documentation is for an older version of HVR.
How to Skip and Recover Record that Continually Causes Capture to Fail
Question
How can I skip and recover a record that continually causes Capture to fail?
Environment
HVR 5
Answer
There are many reasons a record could cause Capture to fail. Often the issue is revealed in the error message itself, along with recovery options. Sometimes further root cause analysis is needed. In order to resume capture, the hvrcontrol command can be used.
Example
hvrcontrol -c -l src -s -tfvalue -whvr_tx_id=0x29000100000000 -x0 <hub> <chn>
F_JT1456: Log parsing error F_JZ1201. Supplemental logging information is missing for change type 5.1 within record with SCN 0x0000.04A707D8. Supplemental logging should have been enabled automatically. The previous error occurred during parsing an operation for table id 95123 (udfvalue [admuserpsp.udfvalue]). …. To skip this transaction's changes to this table, use command {hvrcontrol -c -l <loc> -s -tudfvalue -whvr_tx_id=0x29000100000000 -x0 <hub> <chn>}. If this fails, skip all log records for this log address with command {hvrcontrol -c -l <loc> -s "-whvr_rba='t2.0x00019c.0002bdec.0050'" -x0 <hub> <chn>}. If this fails too, skip all log records for this timestamp with command {hvrcontrol -c -l <loc> -s "-whvr_rec_tstamp=2016-07-27 05:05:11" -x0 <hub> <chn>}. Afterwards, restart the capture job. The skipped change(s) can be recovered later with on-line refresh; {hvrrefresh -r <loc> -tudfvalue -qwo <hub> <chn>}.
F_JT1410: The previous error occurred after scanning record 307167, which has RBA t2.0x00019c.0002bdec.0050 and timestamp 2016-07-27 05:05:11.
Skipped changes can be fixed with online refresh after capture has resumed:
hvrrefresh -r <loc> -tudfvalue -qwo <hub> <chn>
To find the format of the <hub> argument, see the tip in Calling HVR on the Command Line.