Last updated on JULY 05, 2017
Applies to:
Oracle Rdb Server on OpenVMS - Version 7.1 and laterHP OpenVMS Itanium
HP OpenVMS Alpha
Symptoms
After recovering an AIJ file, the roll-forward sequence number is not updated and no transaction is applied, despite the sequence of the AIJ file being correct.
For instance:
$ RMU/RECOVER/ROOT=DATABASE.RDB AIJ_FILE_SEQ_12658
The following warnings are shown:
%RMU-W-NOTRANAPP, no transactions in this journal were applied
%RMU-I-AIJALLDONE, after-image journal roll-forward operations completed
%RMU-I-AIJFNLSEQ, to start another AIJ file recovery, the sequence number needed will be 12658
%RMU-I-AIJALLDONE, after-image journal roll-forward operations completed
%RMU-I-AIJFNLSEQ, to start another AIJ file recovery, the sequence number needed will be 12658
RMU/DUMP/HEADER shows that next sequence is the sequence of the AIJ just recovered:
- Current roll-forward sequence number is 12658
Cause
Sign In with your My Oracle Support account |
|
Don't have a My Oracle Support account? Click to get started |
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms