Oracle RMAN archive deletion policy

Source: Internet
Author: User

Oracle RMAN archive deletion policy

RMAN> show all;

Configure archivelog deletion policy to none;

By default, the archive deletion policy is not configured in Oracle10g 11g;

In this case, how does one Delete archive logs that have not been applied:

RMAN> delete archivelog all;

Released channel: ORA_DISK_1
Allocated channel: ORA_DISK_1
Channel ORA_DISK_1: SID = 60 device type = DISK
RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process

Archived log file name =/u01/app/ora11/flash_recovery_area/1_2019_822927217.dbf thread = 1 sequence = 2019
RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process

Archived log file name =/u01/app/ora11/flash_recovery_area/4102023_822927217.dbf thread = 1 sequence = 2023
RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process

Oracle throws an alert; warning archived logs are not deleted, and archive logs must be used as standby or stream capture processes.

About the Configuration Policy in rman:

CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY

The archive is not automatically deleted. Instead, confirm that the archive has been applied by data guard and the stream environment during deletion. The purpose of this function is to avoid deleting the archive logs required by other functions.

If you configure an archive deletion policy:

Configure archivelog deletion policy to applied on standby;
Configure snapshot controlfile name to '/u01/app/oracle/product/11.2.0/db_home/dbs/snapcf_oradb1.f'; # default

Try to delete the archive log:
RMAN> delete archivelog all;


Released channel: ORA_DISK_1
Allocated channel: ORA_DISK_1
Channel ORA_DISK_1: SID = 27 instance = oradb1 device type = DISK
List of Archived Log Copies for database with db_unique_name ORADB
========================================================== ==================================

Key Thrd Seq S Low Time
---------------------------------------
2526 2 350 A 22-NOV-2014 02:01:04
Name: + FLASH/oradb/archivelog/2014_11_24/thread_2_seq_350.600.864470143
2527 2 351 A 23-NOV-2014 13:01:27
Name: + FLASH/oradb/archivelog/2014_11_24/thread_2_seq_351.6379864470173
2531 2 352 A 24-NOV-2014 10:29:04
Name: + FLASH/oradb/archivelog/2014_11_26/thread_2_seq_352.554.864634011

Do you really want to delete the above objects (enter YES or NO )? Yes
Deleted archived log
Archived log file name = + FLASH/oradb/archivelog/2014_11_24/thread_2_seq_350.600.864470143 RECID = 2526 STAMP = 864470171
Deleted archived log
Archived log file name = + FLASH/oradb/archivelog/2014_11_24/thread_2_seq_351.6379864470173 RECID = 2527 STAMP = 864470193
Deleted archived log
Archived log file name = + FLASH/oradb/archivelog/2014_11_26/thread_2_seq_352.554.864634011 reci= 2531 STAMP = 864634090
Deleted 3 objects

RMAN-08591: WARNING: invalid archived log deletion policy

[Oracle @ vmrac1 ~] $ Oerr rman 8591
8591, 3, "WARNING: invalid archived log deletion policy"
// * Cause: An invalid archivelog deletion policy was supplied. The archived
// Log deletion policy was APPLIED but there was no mandatory
// Archived log destinations.
// * Action: One of the following:
// 1) Change archived log deletion policy using CONFIGURE command
// 2) Make one or more of standby destination as MANDATORY.

-------------------------------------- Recommended reading --------------------------------------

RMAN: Configure an archive log deletion policy

Basic Oracle tutorial-copying a database through RMAN

Reference for RMAN backup policy formulation

RMAN backup learning notes

Oracle Database Backup encryption RMAN Encryption

-------------------------------------- Split line --------------------------------------

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.