My Oracle Support Banner

RDBPROD: RMU/RECOVER Does Not Update Roll-foward Sequence Number (Doc ID 747862.1)

Last updated on OCTOBER 11, 2019

Applies to:

Oracle Rdb Server on OpenVMS - Version 7.1 and later
HP 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/DUMP/HEADER shows that next sequence is the sequence of the AIJ just recovered:

- Current roll-forward sequence number is 12658

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Symptoms
Cause
Solution
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.