Home » RDBMS Server » Backup & Recovery » Database hang due to ArchiveLog full (Oracle 10, Solaris 10)
Database hang due to ArchiveLog full [message #586184] Tue, 04 June 2013 06:04 Go to next message
wegadnie
Messages: 2
Registered: June 2013
Location: Ho Chi Minh
Junior Member
Hi all,

I am new to forum so please bear with me.

Just now my database is hang due to the archivelog full. I try to use RMAN to delete the expired one and free space but encounter the error:

RMAN>crosscheck archivelog all;
archive log filename=/geodata/oraclelog/archive_log/ORAGF45/archivelog/2013_06_04/o1_mf_1_1444_8tsxvwc2_.arc recid=1350 stamp=817182450
validation succeeded for archived log
archive log filename=/geodata/oraclelog/archive_log/ORAGF45/archivelog/2013_06_04/o1_mf_1_1445_8ttx2q6j_.arc recid=1351 stamp=817214416
Crosschecked 1351 objects
RMAN> delete expired archivelog all;
released channel: ORA_DISK_1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=244 devtype=DISK
specification does not match any archive log in the recovery catalog
RMAN>


So I try to back it up first by using the below command:

RMAN> backup archivelog all;

Starting backup at 04-JUN-13
using channel ORA_DISK_1
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=592 recid=498 stamp=757252810
channel ORA_DISK_1: starting piece 1 at 04-JUN-13
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 06/04/2013 16:02:29
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 5797403648 bytes disk space from 107374182400 limit
continuing other job steps, job failed will not be re-run
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set


I know that I have to extend the db_recovery_file_dest directory for "limit exceed" error but would anyone here show me how can I safely delete the archivelog in order to bring up the database?
Re: Database hang due to ArchiveLog full [message #586185 is a reply to message #586184] Tue, 04 June 2013 06:07 Go to previous messageGo to next message
John Watson
Messages: 4522
Registered: January 2010
Location: Global Village
Senior Member
delete archivelog all;
Re: Database hang due to ArchiveLog full [message #586188 is a reply to message #586185] Tue, 04 June 2013 06:14 Go to previous messageGo to next message
wegadnie
Messages: 2
Registered: June 2013
Location: Ho Chi Minh
Junior Member
I wonder do i need to backup the archivelog first

RMAN>backup archivelog all;

and then

RMAN>delete archivelog all;

Thanks.
Re: Database hang due to ArchiveLog full [message #586189 is a reply to message #586188] Tue, 04 June 2013 06:15 Go to previous message
John Watson
Messages: 4522
Registered: January 2010
Location: Global Village
Senior Member
If you want to. But you'll have to specify a destination that is outside your fast recovery area, eg,
backup archivelog all format '/somewhere_or_other/$U.bset';

--update: Typo! $U should read %U.

[Updated on: Tue, 04 June 2013 06:19]

Report message to a moderator

Previous Topic: RMAN-0621-List of Mismatched objects
Next Topic: Disable RedoLog for a single user?
Goto Forum:
  


Current Time: Mon Sep 01 16:04:24 CDT 2014

Total time taken to generate the page: 0.12564 seconds