Recover Database Fails with RMAN-06558 [ID 1185074.1]

rongshiyuan發表於2013-05-22
DatabaseAI
Recover Database Fails with RMAN-06558 [ID 1185074.1]

In this Document
Symptoms
Changes
Cause
Solution

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.

Applies to:

Oracle Server - Standard Edition - Version: 11.2.0.1 and later [Release: 11.2 and later ]
Information in this document applies to any platform.

Symptoms



Recover database fails with

RMAN-03002: failure of recover command at 08/23/2010 21:55:02
RMAN-06557: unable to restore archived log of thread 1 with sequence 200
RMAN-06558: archived log size of 15635 kb is bigger than available space of 10000 kb

Changes

Restore and recovery was been performed

Cause

The issue is caused due to lack of space in FRA(Flashback recovery area) if configured or the archive log destination.

Rman will try to restore the archive logs required for recovery to these destination . If the space is not adequate then Rman would error out.

Solution




Option 1
========


For database version >= 10.2

SQL>Show parameter db_recovery_file_dest_size


Increase the size to higher value

SQL>Alter system set db_recovery_file_dest_size=<>M ;



Retry the restore


Option 2
=======


Restore the archive log to an alternate location which has space

RMAN> run {
set ARCHIVELOG DESTINATION TO '';
recover database until time "to_date('2010-09-14 09:25:10', 'YYYY-MM-DD HH24:MI:SS')";
}



Option 3
=======

Set MAXSIZE limit



RMAN> run {
recover database until time "to_date('2010-09-14 09:25:10', 'YYYY-MM-DD HH24:MI:SS')" delete archivelog maxsize 50 K ; }


來自 “ ITPUB部落格 ” ，連結：http://blog.itpub.net/17252115/viewspace-761735/，如需轉載，請註明出處，否則將追究法律責任。

相關文章