Rman backup Failed "RMAN-03002, RMAN-06059" after optimizing backup

Environment:

CentOS 6.5 X64

Oracle 11g Enterprise Edition Release 11.2.0.2.0

Failure phenomena:

Rman Automatic backup script failed, error phenomenon:

Starting backup at 30-jul-15

Current log Archived

Released Channel:disk1

Released Channel:disk2

Released Channel:disk3

Released Channel:disk4

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE, STACK follows ===============

RMAN-00571: ===========================================================

Rman-03002:failure of Backup command at 07/30/2015 23:00:27

rman-06059:expected archived log not found, loss of archived log compromises recoverability

Ora-19625:error Identifying File/data0/oracle/database/archive/1_985092_843387931.arc

Ora-27037:unable to obtain file status

linux-x86_64 error:2: No such file or directory

Additional Information:3

Recovery Manager Complete

From the error phenomenon, it is because the archive log 985092 file was deleted.

The main reason for the analysis is that because this database is a Dataguard schema, colleagues do v$archived Max (sequence#)-500 Keep the archive and delete the archive log every hour. Since the start of the backup at 11 o'clock on the hour, it is said that when Rman starts executing run{} and allocates the channel after 23:04, the deletion script has already been executed at the hour 23:00. This time the Rman archive backup script executes the input archived log thread=1 sequence=985092 file when it discovers that the file does not exist. Causes Rman archive backup to fail.

View time:

Sql> SELECT Applied,to_char (first_time, ' Yyyy-mm-dd hh24:mi:ss ') as First_time,

2 To_char (Next_time, ' Yyyy-mm-dd hh24:mi:ss ') as Next_time

3 from V$archived_log

4 where sequence#= 985092;

Applied First_time Next_time

--------- ------------------- -------------------

YES 2015-07-30 16:03:06 2015-07-30 16:03:12

NO 2015-07-30 16:03:06 2015-07-30 16:03:12

Two methods are handled:

1, comprehensive consideration of server hard disk storage space "The implication is that the database to retain the archive log of the day," cancel the automatic deletion of the archive log script. Allow Rman to do an archive backup and automatically delete the archive log after completion.

2, modify the Rman archive backup time and backup script, such as: 23:10 start Backup.

Such as:

RUN {

Allocate channel Disk1 type disk maxpiecesize 4000M;

Allocate channel DISK2 type disk maxpiecesize 4000M;

SQL ' alter system archive log current ';

Backup Archivelog All Delete input format '/opt/oracle/backup/arch_backup/archbackup/%d_arch_%s_%p_%h.arh ' Filesperset = 50;

# Control File backup

Backup as compressed backupset format '/opt/oracle/backup/arch_backup/archbackup/cf_%t_%s_%p_d%t.ctl ' current Controlfile;

}

If you have enough space, the second one is recommended, so the data is available in a wide range.

This article is from the "Bug" blog, please be sure to keep this source http://worms.blog.51cto.com/969144/1681513

Rman backup Failed "RMAN-03002, RMAN-06059" after optimizing backup