rman delete Oracle archive log
rman target sys/corl
Recovery Manager: Release 12.2.0.1.0 – Production on Mon May 14 16:31:37 2018
Copyright (c) 1982, 2017, Oracle and/or its affiliates. All rights reserved.
connected to target database: ORCL001 (DBID=3872964947)
RMAN> show archivelog deletion policy;
using target database control file instead of recovery catalog
RMAN configuration parameters for database with db_unique_name ORCL001 are:
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
RMAN> configure archivelog deletion policy to backed up 2 times to sbt;
new RMAN configuration parameters:
CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 2 TIMES TO 'SBT_TAPE';
new RMAN configuration parameters are successfully stored
RMAN> configure archivelog deletion policy to backed up 2 times to disk;
old RMAN configuration parameters:
CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 2 TIMES TO 'SBT_TAPE';
new RMAN configuration parameters:
CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 2 TIMES TO DISK;
new RMAN configuration parameters are successfully stored
RMAN> backup archivelog all delete input;
Starting backup at 14-MAY-18
current log archived
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=17 device type=DISK
input archived log thread=1 sequence=1887 RECID=1887 STAMP=976120959
channel ORA_DISK_1: starting piece 1 at 14-MAY-18
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 05/14/2018 16:46:02
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 9963608576 bytes disk space from 10009706496 bytes limit
If the disk is fully
RMAN>delete force noprompt archivelog until time 'sysdate – 2';