Shulou(Shulou.com)06/03 Report--

Environment:

Centos 6.5 X64

Oracle 11g Enterprise Edition Release 11.2.0.2.0

Failure phenomenon:

Rman automatic backup script failed with an error:

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 point of view of the error phenomenon, it is because the archive log 985092 file was deleted.

The main reason for the analysis is that because the database is dataguard architecture, colleagues do v$archived max (SEQUENCE#)-500 retention archives and delete archive logs every hour. Because the backup starts at 11:00 in the evening, that is to say, it is after 23:04 when rman starts to execute run {} and allocates channels at exactly one o'clock, but the delete script has already been executed at 23:00 sharp. At this point, when the rman archive backup script executes the input archived log thread=1 sequence=985092 file, it finds that the file does not exist. Causes the rman archive backup to fail.

View time:

SQL > SELECT APPLIED,to_char (FIRST_TIME, 'yyyy-mm-dd hh34:mi:ss') as FIRST_TIME

2 to_char (NEXT_TIME, 'yyyy-mm-dd hh34: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

There are two ways to deal with it:

1. Considering the storage space of the server's hard disk (the implication is that the database should keep the archive log for a day), cancel the script to delete the archive log automatically. Let rman do the archive backup and delete the archive log automatically after completion.

2. Modify the rman archive backup time and backup script, for example, start backup at 23:10.

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 there is enough space, the second is recommended, so that the data can be used in a wide range.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.