RAC RECOVERY fails with RMAN-06054 / ORA-308 with wrong Archived Log : Bug 12625205 (Doc ID 1420172.1)

Last updated on APRIL 21, 2017

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.1 to 11.2.0.3 [Release 10.2 to 11.2]
Information in this document applies to any platform.

Symptoms

In RAC Database having more than one active thread, RMAN fails with RMAN-06054. SQL based RECOVER command fails with ORA-308 asking wrong Archived log sequence:

RMAN:

RMAN> run {
2> set until scn 2382318 ;
3> recover database ;
4> }
......
......
archived log for thread 2 with sequence 9 is already on disk as file
/tmp/stage/rman/arc/arc_arch_D-H112_id-2028969338_S-9_T-2_A-757458941_0cmibubr.arc
archived log file
name=/tmp/stage/rman/arc/arc_arch_D-H112_id-2028969338_S-7_T-2_A-757458941_07mibubl.arc thread=2 sequence=7
unable to find archived log
archived log thread=1 sequence=8
RMAN-571: ===========================================================
RMAN-569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-571: ===========================================================
RMAN-3002: failure of recover command at 07/25/2011 23:03:13
RMAN-6054: media recovery requesting unknown archived log for thread 1 with sequence 8 and starting SCN of 2381659


SQL:

SQL> recover database using backup controlfile until change 2382318 ;
ORA-279: change 2381659 generated at 07/25/2011 21:56:48 needed for thread 2
ORA-289: suggestion : /tmp/stage/rman/arc/arc_arch_D-H112_id-2028969338_S-7_T-2_A-757458941_07mibubl.arc
ORA-280: change 2381659 for thread 2 is in sequence #7

Specify log: {<RET>=suggested | filename | AUTO | CANCEL}

ORA-279: change 2381659 generated at 07/25/2011 21:31:52 needed for thread 1
ORA-289: suggestion : /tmp/stage/fra/HDUP/archivelog/2011_07_25/o1_mf_1_8_%u_.arc
ORA-280: change 2381659 for thread 1 is in sequence #8                      *)1 <<<<-------- v$archived_log  shows this SCN 2381659 is in Thread #1 SEQ#10 !!

Specify log: {<RET>=suggested | filename | AUTO | CANCEL}

ORA-308: cannot open archived log '/tmp/stage/fra/HDUP/archivelog/2011_07_25/o1_mf_1_8_%u_.arc'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3


We can verify from V$ARCHIVED_LOG that there is mismatch in Seq/SCN prompted by above Recovery for failing archived logs:

SQL> select thread#, sequence#, first_change#, next_change# from v$archived_log a, v$database b
where a.resetlogs_change#=b.resetlogs_change#
order by next_change# ;

THREAD#  SEQUENCE# FIRST_CHANGE# NEXT_CHANGE#
------- ---------- ------------- ------------
.....
.....
      1          3       2238655      2258925
      1          4       2258925      2279498
      1          5       2279498      2299747
      1          6       2299747      2320043
      1          7       2320043      2340264
      1          8       2340264      2365100
      1          9       2365100      2371200
      2          5       2367712      2371274
      2          6       2371274      2381659
      1         10       2371200      2381774 *)1
      1         11       2381774      2381800
      2          7       2381659      2381916
      1         12       2381800      2381951
      2          8       2381916      2382205
      1         13       2381951      2382311
      1         14       2382311      2382318
      2          9       2382205      2382346

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