My Oracle Support Banner

RMAN recover database fails RMAN-6025 - v$archived_log.next_change# is 281474976710655 (Doc ID 238422.1)

Last updated on DECEMBER 05, 2019

Applies to:

Oracle Database - Standard Edition - Version 9.0.1.0 to 11.2.0.2.0 [Release 9.0.1 to 11.2]
Oracle Database - Enterprise Edition - Version 9.0.1.0 to 11.2.0.2.0 [Release 9.0.1 to 11.2]
Information in this document applies to any platform.
RMAN recovery fails:


Symptoms

RMAN database recover failing with the following errors:

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 05/17/2010 10:22:51
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of log thread 1 seq 2668 lowscn 1079975830 found to restore


The archivelog being requested is very old compared to current log sequence.
Inspection of V$ARCHIVED_LOG shows:

CREATOR REGISTR  SEQ# FIRST_CHANGE# NEXT_CHANGE#        NAME
------- ------- -------------------- -------------------- -------------------- --------------------
RMAN     RMAN     2668     1079861514      281474976710655   /<path>/onlinelog/group_3.4508.718549667

To confirm if you have hit the same problem run this query against the controlfile :

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!


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