Does Not Delete Archivelogs Even When They Already Backed Up To Tape_1607250.1

rongshiyuan發表於2014-05-22
deleteHive

In this Document

Symptoms
Cause
Solution
References


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 Database - Enterprise Edition - Version 11.2.0.3 and later
Information in this document applies to any platform.

Symptoms

RMAN is failing to delete the archivelog even when a  backup exist for the archivelog.

 

Recovery Manager: Release 11.2.0.3.0 - Production on Mon Nov 11 00:50:27 2013

Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.

RMAN>
connected to target database: SAMER (DBID=3224028897)

RMAN>
connected to recovery catalog database

RMAN>
echo set on

RMAN> show all;
RMAN configuration parameters for database with db_unique_name SAMER are:
CONFIGURE RETENTION POLICY TO NONE;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '%F';
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F';
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 1 BACKUP TYPE TO BACKUPSET;
CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE 'SBT_TAPE' TO 1;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE 'SBT_TAPE' TO 1;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE MAXSETSIZE TO 30 G;
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR
LOAD TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO
'/APP02/app/oracle/product/11.2/dbs/snapcf_SAMER.f'; # default
..

BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ -------------------
50756561300 68.75M SBT_TAPE 00:00:02 11/11/2013 00:50:17
  BP Key: 50756561303 Status: AVAILABLE Compressed: NO Tag: SEMANAL
  Handle: SAMER_20131111_5qoolae7_1_1.bkp Media: 131439
  Keep: BACKUP_LOGS Until: 09/02/2014 00:50:12

  List of Archived Logs in backup set 50756561300
  Thrd Seq Low SCN Low Time Next SCN Next Time
  ---- ------- ---------- ------------------- ---------- ---------
  1 580824 4744548387699 11/11/2013 00:45:02 4744548407643 11/11/2013
00:50:07


RMAN> run {
2> debug on;
3> delete noprompt archivelog until sequence 580824 backed up 1 times to
device type 'SBT_TAPE';
4> debug off;
5> }
RMAN-03036: Debugging set to level=9, types=ALL

RMAN-08030: allocated channel: ORA_DISK_1
RMAN-08500: channel ORA_DISK_1: SID=238 device type=DISK
RMAN-08138: WARNING: archived log not deleted - must create more backups
RMAN-08515: archived log file
name=/ARC01/ORAARC/huemul/respal_respal_LOG_580824_1_566155873.SAMER
thread=1 sequence=580824

 

Cause

This is expected behavior when using RMAN Keep option.

Solution

This is expected behavior when using RMAN Keep option.


 .
  delete noprompt archivelog until sequence 580824 backed up 1 times to
 device type 'SBT_TAPE';
 .
  -> RMAN-08138: WARNING: archived log not deleted - must create more backups
 .
 Because the backup of the archivelog has the KEEP
 attribute, it does not count towards the number of backups of this particular
 archivelog, and so the backup directive '...backed up 1 times...' is not
 satisfied, and the archivelog is not deleted.
 

References

BUG:17807533 - RMAN-08138 EVEN WHEN BACKUP EXIST FOR THE FILE

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

相關文章