Retention Policy in 8i

You can configure a retention policy in later versions of rman but how is it done in 8i? We have inherited two 8i databases but I can't even tell what the backup retention is. The backups go to tape. Is retention controlled by the media manager? Thanks for any help. John

Retention policy was a new rman feature in 9iR1, so you won't be able to set this parameter in 8i.
Regards.

Similar Messages

Can i use the retention policy without using the Flash Recovery area?

Yes ,lets see here
RMAN>list backup summary
C:\>dir *.bus
Volume in drive C is khurram
Volume Serial Number is F49D-FF2B
Directory of C:\
File Not Found
C:\>dir *.arc
Volume in drive C is khurram
Volume Serial Number is F49D-FF2B
Directory of C:\
File Not Found
RMAN> crosscheck backup
2> ;
using channel ORA_DISK_1
RMAN> list backup summary
2> ;
RMAN> show retention policy
2> ;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
RMAN> run {
2>   allocate channel ch0 type disk;
3>   backup as compressed backupset database format
4>   'c:\rman_%s_%d_%T.bus'
5>   plus archivelog format 'c:\arch_%s_%d_%T.arc';
6>   release channel ch0;
7>   allocate channel ch1 device type disk format 'c:\arch_%s_%d_%T.arc';
8>   release channel ch1;
9>   delete force noprompt obsolete;
10>   allocate channel ch2 device type disk format 'c:\rman_%s_%d_%T.bus';
11>   release channel ch2;
12>   delete force noprompt obsolete;
13> }
released channel: ORA_DISK_1
allocated channel: ch0
channel ch0: sid=146 devtype=DISK
Starting backup at 15-APR-08
current log archived
channel ch0: starting compressed archive log backupset
channel ch0: specifying archive log(s) in backup set
input archive log thread=1 sequence=24 recid=79 stamp=652108461
input archive log thread=1 sequence=25 recid=80 stamp=652112650
channel ch0: starting piece 1 at 15-APR-08
channel ch0: finished piece 1 at 15-APR-08
piece handle=C:\ARCH_130_ORCL1_20080415.ARC comment=NONE
channel ch0: backup set complete, elapsed time: 00:00:05
Finished backup at 15-APR-08
Starting backup at 15-APR-08
channel ch0: starting compressed full datafile backupset
channel ch0: specifying datafile(s) in backupset
input datafile fno=00001 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL1\SYSTEM01.DB
F
input datafile fno=00003 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL1\SYSAUX01.DB
F
input datafile fno=00004 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL1\USERS01.DBF
input datafile fno=00002 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL1\UNDOTBS01.D
BF
channel ch0: starting piece 1 at 15-APR-08
channel ch0: finished piece 1 at 15-APR-08
piece handle=C:\RMAN_131_ORCL1_20080415.BUS comment=NONE
channel ch0: backup set complete, elapsed time: 00:00:45
Finished backup at 15-APR-08
Starting backup at 15-APR-08
current log archived
channel ch0: starting compressed archive log backupset
channel ch0: specifying archive log(s) in backup set
input archive log thread=1 sequence=26 recid=81 stamp=652112703
channel ch0: starting piece 1 at 15-APR-08
channel ch0: finished piece 1 at 15-APR-08
piece handle=C:\ARCH_132_ORCL1_20080415.ARC comment=NONE
channel ch0: backup set complete, elapsed time: 00:00:02
Finished backup at 15-APR-08
Starting Control File and SPFILE Autobackup at 15-APR-08
piece handle=C:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ORCL1\AUTOBACKUP\2008_
04_15\O1_MF_S_652112718_408X3ZVJ_.BKP comment=NONE
Finished Control File and SPFILE Autobackup at 15-APR-08
released channel: ch0
allocated channel: ch1
channel ch1: sid=146 devtype=DISK
released channel: ch1
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=146 devtype=DISK
Deleting the following obsolete backups and copies:
Type                 Key    Completion Time    Filename/Handle
Backup Set           128    15-APR-08
Backup Piece       128    15-APR-08          C:\ARCH_130_ORCL1_20080415.ARC
Archive Log          79     15-APR-08          C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
COVERY_AREA\ORCL1\ARCHIVELOG\2008_04_15\O1_MF_1_24_408RYXDF_.ARC
Archive Log          80     15-APR-08          C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
COVERY_AREA\ORCL1\ARCHIVELOG\2008_04_15\O1_MF_1_25_408X1SCR_.ARC
deleted backup piece
backup piece handle=C:\ARCH_130_ORCL1_20080415.ARC recid=128 stamp=652112652
deleted archive log
archive log filename=C:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ORCL1\ARCHIVEL
OG\2008_04_15\O1_MF_1_24_408RYXDF_.ARC recid=79 stamp=652108461
deleted archive log
archive log filename=C:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ORCL1\ARCHIVEL
OG\2008_04_15\O1_MF_1_25_408X1SCR_.ARC recid=80 stamp=652112650
Deleted 3 objects
released channel: ORA_DISK_1
allocated channel: ch2
channel ch2: sid=146 devtype=DISK
released channel: ch2
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=146 devtype=DISK
no obsolete backups found
RMAN>
C:\>dir *.bus
Volume in drive C is khurram
Volume Serial Number is F49D-FF2B
Directory of C:\
04/15/2008 02:24 PM        96,813,056 RMAN_131_ORCL1_20080415.BUS
               1 File(s)     96,813,056 bytes
               0 Dir(s) 61,960,724,480 bytes free
C:\>dir *.arc
Volume in drive C is khurram
Volume Serial Number is F49D-FF2B
Directory of C:\
04/15/2008 02:25 PM            56,832 ARCH_132_ORCL1_20080415.ARC
               1 File(s)         56,832 bytes
               0 Dir(s) 61,960,724,480 bytes free
C:\>
RMAN> run {
2>   allocate channel ch0 type disk;
3>   backup as compressed backupset database format
4>   'c:\rman_%s_%d_%T.bus'
5>   plus archivelog format 'c:\arch_%s_%d_%T.arc';
6>   release channel ch0;
7> }
released channel: ORA_DISK_1
allocated channel: ch0
channel ch0: sid=146 devtype=DISK
Starting backup at 15-APR-08
current log archived
channel ch0: starting compressed archive log backupset
channel ch0: specifying archive log(s) in backup set
input archive log thread=1 sequence=26 recid=81 stamp=652112703
input archive log thread=1 sequence=27 recid=82 stamp=652112873
channel ch0: starting piece 1 at 15-APR-08
channel ch0: finished piece 1 at 15-APR-08
piece handle=C:\ARCH_134_ORCL1_20080415.ARC comment=NONE
channel ch0: backup set complete, elapsed time: 00:00:02
Finished backup at 15-APR-08
Starting backup at 15-APR-08
channel ch0: starting compressed full datafile backupset
channel ch0: specifying datafile(s) in backupset
input datafile fno=00001 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL1\SYSTEM01.DB
F
input datafile fno=00003 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL1\SYSAUX01.DB
F
input datafile fno=00004 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL1\USERS01.DBF
input datafile fno=00002 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL1\UNDOTBS01.D
BF
channel ch0: starting piece 1 at 15-APR-08
channel ch0: finished piece 1 at 15-APR-08
piece handle=C:\RMAN_135_ORCL1_20080415.BUS comment=NONE
channel ch0: backup set complete, elapsed time: 00:00:45
Finished backup at 15-APR-08
Starting backup at 15-APR-08
current log archived
channel ch0: starting compressed archive log backupset
channel ch0: specifying archive log(s) in backup set
input archive log thread=1 sequence=28 recid=83 stamp=652112925
channel ch0: starting piece 1 at 15-APR-08
channel ch0: finished piece 1 at 15-APR-08
piece handle=C:\ARCH_136_ORCL1_20080415.ARC comment=NONE
channel ch0: backup set complete, elapsed time: 00:00:02
Finished backup at 15-APR-08
Starting Control File and SPFILE Autobackup at 15-APR-08
piece handle=C:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ORCL1\AUTOBACKUP\2008_
04_15\O1_MF_S_652112928_408XBKCZ_.BKP comment=NONE
Finished Control File and SPFILE Autobackup at 15-APR-08
released channel: ch0
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
Report of obsolete backups and copies
Type                 Key    Completion Time    Filename/Handle
Backup Set           129    15-APR-08
Backup Piece       129    15-APR-08          C:\RMAN_131_ORCL1_20080415.BUS
Backup Set           130    15-APR-08
Backup Piece       130    15-APR-08          C:\ARCH_132_ORCL1_20080415.ARC
Backup Set           131    15-APR-08
Backup Piece       131    15-APR-08          C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
COVERY_AREA\ORCL1\AUTOBACKUP\2008_04_15\O1_MF_S_652112718_408X3ZVJ_.BKP
Backup Set           132    15-APR-08
Backup Piece       132    15-APR-08          C:\ARCH_134_ORCL1_20080415.ARC
Archive Log          81     15-APR-08          C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
COVERY_AREA\ORCL1\ARCHIVELOG\2008_04_15\O1_MF_1_26_408X3HRP_.ARC
Archive Log          82     15-APR-08          C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
COVERY_AREA\ORCL1\ARCHIVELOG\2008_04_15\O1_MF_1_27_408X8RXN_.ARC
RMAN>Note: i have archivelog which is at FRA ,it also apply there and as well yours own defined backupsets path.
Yours comments are wellcome.
http://oraware.blogspot.com/2008/04/can-i-use-retention-policy-without.htmlKhurram

Hmmm, I can't see where the confusion originates. The table near the bottom of www.apple.com/timecapsule/specs.html has one row labelled "For backup using Time Machine" and another row labelled "For AirPort Disk with a USB hard drive".
The requirement for backup via Time Machine is OS 10.5.1 or better. Time Machine is not supported in pre-Leopard (OS 10.5) nor in Windows.
The requirement for using Time Capsule as a remote disk is identified as "Mac with Mac OS X v10.4.8 or later" or "PC with Windows XP (SP2) or Windows Vista; Bonjour for Windows (included on Time Capsule CD)".
Doesn't that pretty much spell out that Time Capsule works as a network drive without the need for Time Machine?
Also Joe (the OP) never indicated any desire to use it with Windows so I'm not sure why all the discussion about Windows compatibility. ??
Also the quote posted by Henry seems pretty clear:
"Time Capsule with Time Machine in Leopard is the ideal backup solution. But that doesn’t mean Tiger, Windows XP, and Windows Vista users can’t enjoy the benefits of Time Capsule, too. Because it mounts as a wireless hard drive, Tiger and Windows users simply access Time Capsule directly from the wireless network for exchanging and storing files quickly and easily."

Performance Issue when turning on Retention Policy

Hello,
I am currently in the process of enabling retention policy for my organization. We have 18,000+ mailboxes. How much of a performance impact (if any) will it be to the end users if we were to enable retention polices for so many mailboxes at once?
We have not had retentions enabled for about 3 years and the goals to basically delete/purge anything over 15 months. I tried doing some research on this and can't seem to find any topics pertaining to this particular question.
Thanks,
Emmanuel
Emmanuel Fumero Exchange Administrator

The user impact of enabling retention on this many mailboxes at once is not your primary issue - your primary issue will be how long it will take to complete the process on all of your mailboxes so it can "just keep up" from that point onward.
I'll give you some information about our own results and let you decide how you wish to implement retention for your users.
We have 14,000+ mailboxes running on Exchange 2010, fully updated. We migrated three years ago from "another messaging platform" well known for allowing users to have huge mailboxes with little or no capability to restrict how large the
mailboxes grew - and they grew. When I started here, our average mailbox size had just popped over 2GB, and our corporate target mailbox size limit was 2GB. We had mailboxes over 30GB, and messages older than 10 years (our corporate retention policy
states no emails older than 7 years is allowed). We were tasked with implementing retention across the board, with the following settings:
Daily emails will be kept only for 60 days, and can be recovered (if necessary) for another 60 days
Working emails (things needed for projects, etc) can be kept for 2 years, and can be recovered (if necessary) for another 60 days
Messages required for legal reasons can be kept for up to 7 years, and can't be recovered if they are deleted
Messages saved for legal reasons do not count against the 2 GB mailbox size limit
Due to my previous experience implementing retention (when I was a consultant focused on Microsoft Exchange), I knew that deploying to all users at once would cause a hit on our servers (your current fear, and well founded), but I had only deployed to smaller
organizations, and never in so radical a manner - previously, size limits had been in effect, so retention was just to "maintain the status quo", rather than to hack huge amounts of stale data from the system. However, we did have huge servers
(72 GB RAM and 24CPUs, but multirole) that, early on, were not highly taxed (under 15% CPU average during the peak timeframe, and we are in only two time-zones, so all 13,000 users will connect during the 7:00-10:30 Eastern timeframe). So we determined
that we would ramp retention across the organization in the same manner that we migrated - each 1000 users would get retention enabled weekly in a phased manner.
When we started our first group, the IT group (naturally), most users kept their mailboxes relatively small - only 1.8 GB average - so retention ran from Thursday (the day we kicked off the implementation) through the weekend. However, as each subsequent
group was placed into retention, we found that the retention task was taking longer and longer. Toward the end, we had to slip some of our retention groups a day or so because retention for the previous mailboxes hadn't completed. We attribute
this to two factors - 1) the mailboxes were larger on average, and B) there were also more and more mailboxes in retention already that also had to be handled.
In the end, we took 22 weeks to fully implement retention across the organization, and the process took another two weeks to get to the point that is was "running the status quo", rather than yanking huge volumes of stale email out of mailboxes.
During implementation, our servers' performance numbers were good - still under 30% CPU - and users weren't complaining about poor performance due to that (cached mode is a godsend), but getting the process to complete was our sticking point. If
you turn on retention for all 18,000 of your mailboxes at once, you will see some server performance degradation (especially if your servers aren't as beefy as ours), but the process may never have a chance to complete across the board. Our 22 weeks
may well take over a year for your mailboxes.
HTH - you are going to need all the help you can get. (-;

Control_file_record_keep_time vs retention policy

Its not thread nor question just read from documents and tried to imply the fact of documents and i think its written correct what i tried to do proof it practically ,neither i am trying to be smart just share with you guys is my observation correct or not.i am using FRA area for backup.
<quote>
Relation between RMAN retention period and control_file_record_keep_time
RMAN backup keeps the backup metadata information in the reusable section of the controlfile.Its depends on the parameter CONTROL_FILE_RECORD_KEEP_TIME. CONTROL_FILE_RECORD_KEEP_TIME specifies the minimum number of days before a reusable record in the control file can be reused.
In the event a new record needs to be added to a reusable section and there is not enough space then it will delete the oldest record, which are aged enough.
Backup retention policy is the rule to set regarding which backups must be retained (whether on disk or other backup media) to meet the recovery and other requirements.
If the CONTROL_FILE_RECORD_KEEP_TIME is less than the retention policy then it may overwrite reusable records prior to obsoleting them in the RMAN metadata. Therfor it is recommended that the CONTROL_FILE_RECORD_KEEP_TIME should set to a higher value than the retention policy.
Formula
CONTROL_FILE_RECORD_KEEP_TIME = retention period + level 0 backup interval + 1
For e.g.
e.q. level 0 backup once a week with retention policy of a recovery windows of 14 days then in this
case the CONTROL_FILE_RECORD_KEEP_TIME should be 14+7+1=22
<quote>
RMAN> show retention policy
2> ;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
SQL> show parameter control_file_record_keep_time
NAME                                 TYPE        VALUE
control_file_record_keep_time        integer     7
SQL>
SQL> alter system set control_file_record_keep_time=1
2 /
System altered.
SQL> show parameter control_file_record_keep_time
NAME                                 TYPE        VALUE
control_file_record_keep_time        integer     1
RMAN> configure retention policy to redundancy 3
2> ;
new RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO REDUNDANCY 3;
new RMAN configuration parameters are successfully stored
RMAN> show retention policy
2> ;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 3;
RMAN> backup database
2> ;
Starting backup at 20-NOV-07
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=126 devtype=DISK
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSTEM01.DBF
input datafile fno=00003 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSAUX01.DBF
input datafile fno=00002 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\UNDOTBS01.DBF
input datafile fno=00004 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\USERS01.DBF
channel ORA_DISK_1: starting piece 1 at 20-NOV-07
channel ORA_DISK_1: finished piece 1 at 20-NOV-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\BACKUPSET\2007_11_20\O1_MF_NN
NDF_TAG20071120T185951_3N5T2RTX_.BKP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:01:17
Finished backup at 20-NOV-07
Starting Control File and SPFILE Autobackup at 20-NOV-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\AUTOBACKUP\2007_11_20\O1_MF_S
_639169270_3N5T598C_.BKP comment=NONE
Finished Control File and SPFILE Autobackup at 20-NOV-07
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 3
no obsolete backups found
RMAN> backup database
2> ;
Starting backup at 20-NOV-07
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSTEM01.DBF
input datafile fno=00003 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSAUX01.DBF
input datafile fno=00002 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\UNDOTBS01.DBF
input datafile fno=00004 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\USERS01.DBF
channel ORA_DISK_1: starting piece 1 at 20-NOV-07
channel ORA_DISK_1: finished piece 1 at 20-NOV-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\BACKUPSET\2007_11_20\O1_MF_NN
NDF_TAG20071120T190313_3N5T94SG_.BKP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:01:22
Finished backup at 20-NOV-07
Starting Control File and SPFILE Autobackup at 20-NOV-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\AUTOBACKUP\2007_11_20\O1_MF_S
_639169477_3N5TCPVW_.BKP comment=NONE
Finished Control File and SPFILE Autobackup at 20-NOV-07
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 3
no obsolete backups found
RMAN> backup database
2> ;
Starting backup at 20-NOV-07
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSTEM01.DBF
input datafile fno=00003 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSAUX01.DBF
input datafile fno=00002 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\UNDOTBS01.DBF
input datafile fno=00004 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\USERS01.DBF
channel ORA_DISK_1: starting piece 1 at 20-NOV-07
channel ORA_DISK_1: finished piece 1 at 20-NOV-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\BACKUPSET\2007_11_20\O1_MF_NN
NDF_TAG20071120T190500_3N5TDGC9_.BKP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:55
Finished backup at 20-NOV-07
Starting Control File and SPFILE Autobackup at 20-NOV-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\AUTOBACKUP\2007_11_20\O1_MF_S
_639169556_3N5TG65X_.BKP comment=NONE
Finished Control File and SPFILE Autobackup at 20-NOV-07
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 3
Report of obsolete backups and copies
Type                 Key    Completion Time    Filename/Handle
Archive Log          30     19-NOV-07          C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_19\O1_MF_1_1_3N35QQX7_.ARC
Archive Log          31     19-NOV-07          C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_19\O1_MF_1_2_3N39LR86_.ARC
Archive Log          32     20-NOV-07          C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_20\O1_MF_1_3_3N4RZBXV_.ARC
Archive Log          33     20-NOV-07          C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_20\O1_MF_1_4_3N4W8SLF_.ARC
Archive Log          34     20-NOV-07          C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_20\O1_MF_1_5_3N4Y1CN7_.ARC
Archive Log          35     20-NOV-07          C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_20\O1_MF_1_6_3N4Z6LGF_.ARC
Archive Log          36     20-NOV-07          C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_20\O1_MF_1_7_3N53S4XK_.ARC
Archive Log          37     20-NOV-07          C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_20\O1_MF_1_8_3N57XHYB_.ARC
Archive Log          38     20-NOV-07          C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_20\O1_MF_1_9_3N5C52D8_.ARC
Archive Log          39     20-NOV-07          C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_20\O1_MF_1_10_3N5C83YB_.ARC
Archive Log          40     20-NOV-07          C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_20\O1_MF_1_11_3N5K9J2Z_.ARC
Archive Log          41     20-NOV-07          C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_20\O1_MF_1_12_3N5MMXHO_.ARC
Archive Log          42     20-NOV-07          C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_20\O1_MF_1_13_3N5N566W_.ARC
Archive Log          43     20-NOV-07          C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_20\O1_MF_1_14_3N5RVB4G_.ARC
RMAN>
Now i just delete alls backup and increase the control_file_record_keep_time 7 which will be more then retention policy redundancy 3
RMAN> list backup
2> ;
List of Backup Sets
===================
BS Key Type LV Size       Device Type Elapsed Time Completion Time
6       Full    512M       DISK        00:01:10     20-NOV-07
        BP Key: 6   Status: AVAILABLE Compressed: NO Tag: TAG20071120T185951
        Piece Name: C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\BACKUPSET\2007_11_20\O
1_MF_NNNDF_TAG20071120T185951_3N5T2RTX_.BKP
List of Datafiles in backup set 6
File LV Type Ckp SCN    Ckp Time Name
1       Full 478504     20-NOV-07 C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSTEM01
.DBF
2       Full 478504     20-NOV-07 C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\UNDOTBS0
1.DBF
3       Full 478504     20-NOV-07 C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSAUX01
.DBF
4       Full 478504     20-NOV-07 C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\USERS01.
DBF
BS Key Type LV Size       Device Type Elapsed Time Completion Time
7       Full    2M         DISK        00:00:04     20-NOV-07
        BP Key: 7   Status: AVAILABLE Compressed: NO Tag: TAG20071120T190110
        Piece Name: C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\AUTOBACKUP\2007_11_20\
O1_MF_S_639169270_3N5T598C_.BKP
Controlfile Included: Ckp SCN: 478975       Ckp time: 20-NOV-07
SPFILE Included: Modification time: 20-NOV-07
BS Key Type LV Size       Device Type Elapsed Time Completion Time
8       Full    513M       DISK        00:01:15     20-NOV-07
        BP Key: 8   Status: AVAILABLE Compressed: NO Tag: TAG20071120T190313
        Piece Name: C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\BACKUPSET\2007_11_20\O
1_MF_NNNDF_TAG20071120T190313_3N5T94SG_.BKP
List of Datafiles in backup set 8
File LV Type Ckp SCN    Ckp Time Name
1       Full 480265     20-NOV-07 C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSTEM01
.DBF
2       Full 480265     20-NOV-07 C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\UNDOTBS0
1.DBF
3       Full 480265     20-NOV-07 C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSAUX01
.DBF
4       Full 480265     20-NOV-07 C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\USERS01.
DBF
BS Key Type LV Size       Device Type Elapsed Time Completion Time
9       Full    2M         DISK        00:00:02     20-NOV-07
        BP Key: 9   Status: AVAILABLE Compressed: NO Tag: TAG20071120T190437
        Piece Name: C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\AUTOBACKUP\2007_11_20\
O1_MF_S_639169477_3N5TCPVW_.BKP
Controlfile Included: Ckp SCN: 480346       Ckp time: 20-NOV-07
SPFILE Included: Modification time: 20-NOV-07
BS Key Type LV Size       Device Type Elapsed Time Completion Time
10      Full    513M       DISK        00:00:52     20-NOV-07
        BP Key: 10   Status: AVAILABLE Compressed: NO Tag: TAG20071120T190500
        Piece Name: C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\BACKUPSET\2007_11_20\O
1_MF_NNNDF_TAG20071120T190500_3N5TDGC9_.BKP
List of Datafiles in backup set 10
File LV Type Ckp SCN    Ckp Time Name
1       Full 480415     20-NOV-07 C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSTEM01
.DBF
2       Full 480415     20-NOV-07 C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\UNDOTBS0
1.DBF
3       Full 480415     20-NOV-07 C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSAUX01
.DBF
4       Full 480415     20-NOV-07 C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\USERS01.
DBF
BS Key Type LV Size       Device Type Elapsed Time Completion Time
11      Full    2M         DISK        00:00:02     20-NOV-07
        BP Key: 11   Status: AVAILABLE Compressed: NO Tag: TAG20071120T190556
        Piece Name: C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\AUTOBACKUP\2007_11_20\
O1_MF_S_639169556_3N5TG65X_.BKP
Controlfile Included: Ckp SCN: 480449       Ckp time: 20-NOV-07
SPFILE Included: Modification time: 20-NOV-07
RMAN> delete backup
2> ;
using channel ORA_DISK_1
List of Backup Pieces
BP Key BS Key Pc# Cp# Status      Device Type Piece Name
6       6       1   1   AVAILABLE   DISK        C:\ORACLE\FLASH_RECOVERY_AREA\OR
C\ORC\BACKUPSET\2007_11_20\O1_MF_NNNDF_TAG20071120T185951_3N5T2RTX_.BKP
7       7       1   1   AVAILABLE   DISK        C:\ORACLE\FLASH_RECOVERY_AREA\OR
C\ORC\AUTOBACKUP\2007_11_20\O1_MF_S_639169270_3N5T598C_.BKP
8       8       1   1   AVAILABLE   DISK        C:\ORACLE\FLASH_RECOVERY_AREA\OR
C\ORC\BACKUPSET\2007_11_20\O1_MF_NNNDF_TAG20071120T190313_3N5T94SG_.BKP
9       9       1   1   AVAILABLE   DISK        C:\ORACLE\FLASH_RECOVERY_AREA\OR
C\ORC\AUTOBACKUP\2007_11_20\O1_MF_S_639169477_3N5TCPVW_.BKP
10      10      1   1   AVAILABLE   DISK        C:\ORACLE\FLASH_RECOVERY_AREA\OR
C\ORC\BACKUPSET\2007_11_20\O1_MF_NNNDF_TAG20071120T190500_3N5TDGC9_.BKP
11      11      1   1   AVAILABLE   DISK        C:\ORACLE\FLASH_RECOVERY_AREA\OR
C\ORC\AUTOBACKUP\2007_11_20\O1_MF_S_639169556_3N5TG65X_.BKP
Do you really want to delete the above objects (enter YES or NO)? yes
deleted backup piece
backup piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\BACKUPSET\2007_11_20\O
1_MF_NNNDF_TAG20071120T185951_3N5T2RTX_.BKP recid=6 stamp=639169192
deleted backup piece
backup piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\AUTOBACKUP\2007_11_20\
O1_MF_S_639169270_3N5T598C_.BKP recid=7 stamp=639169273
deleted backup piece
backup piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\BACKUPSET\2007_11_20\O
1_MF_NNNDF_TAG20071120T190313_3N5T94SG_.BKP recid=8 stamp=639169396
deleted backup piece
backup piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\AUTOBACKUP\2007_11_20\
O1_MF_S_639169477_3N5TCPVW_.BKP recid=9 stamp=639169478
deleted backup piece
backup piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\BACKUPSET\2007_11_20\O
1_MF_NNNDF_TAG20071120T190500_3N5TDGC9_.BKP recid=10 stamp=639169502
deleted backup piece
backup piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\AUTOBACKUP\2007_11_20\
O1_MF_S_639169556_3N5TG65X_.BKP recid=11 stamp=639169558
Deleted 6 objects
RMAN> delete archivelog all
2> ;
released channel: ORA_DISK_1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=126 devtype=DISK
specification does not match any archive log in the recovery catalog
RMAN> list backup
2> ;
RMAN> show retention policy
2> ;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 3;
SQL> show parameter control_file_record_keep_time
NAME                                 TYPE        VALUE
control_file_record_keep_time        integer     1
SQL> alter system set control_file_record_keep_time=7
2 /
System altered.
SQL> show parameter control_file_record_keep_time
NAME                                 TYPE        VALUE
control_file_record_keep_time        integer     7
SQL>
RMAN> backup database
2> ;
Starting backup at 20-NOV-07
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSTEM01.DBF
input datafile fno=00003 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSAUX01.DBF
input datafile fno=00002 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\UNDOTBS01.DBF
input datafile fno=00004 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\USERS01.DBF
channel ORA_DISK_1: starting piece 1 at 20-NOV-07
channel ORA_DISK_1: finished piece 1 at 20-NOV-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\BACKUPSET\2007_11_20\O1_MF_NN
NDF_TAG20071120T191412_3N5TXRSG_.BKP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:01:15
Finished backup at 20-NOV-07
Starting Control File and SPFILE Autobackup at 20-NOV-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\AUTOBACKUP\2007_11_20\O1_MF_S
_639170131_3N5V03YT_.BKP comment=NONE
Finished Control File and SPFILE Autobackup at 20-NOV-07
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 3
no obsolete backups found
RMAN> backup database
2> ;
Starting backup at 20-NOV-07
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSTEM01.DBF
input datafile fno=00003 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSAUX01.DBF
input datafile fno=00002 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\UNDOTBS01.DBF
input datafile fno=00004 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\USERS01.DBF
channel ORA_DISK_1: starting piece 1 at 20-NOV-07
channel ORA_DISK_1: finished piece 1 at 20-NOV-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\BACKUPSET\2007_11_20\O1_MF_NN
NDF_TAG20071120T191655_3N5V2S20_.BKP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:45
Finished backup at 20-NOV-07
Starting Control File and SPFILE Autobackup at 20-NOV-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\AUTOBACKUP\2007_11_20\O1_MF_S
_639170261_3N5V462Z_.BKP comment=NONE
Finished Control File and SPFILE Autobackup at 20-NOV-07
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 3
no obsolete backups found
RMAN> backup database
2> ;
Starting backup at 20-NOV-07
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSTEM01.DBF
input datafile fno=00003 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSAUX01.DBF
input datafile fno=00002 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\UNDOTBS01.DBF
input datafile fno=00004 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\USERS01.DBF
channel ORA_DISK_1: starting piece 1 at 20-NOV-07
channel ORA_DISK_1: finished piece 1 at 20-NOV-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\BACKUPSET\2007_11_20\O1_MF_NN
NDF_TAG20071120T191836_3N5V5X20_.BKP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:45
Finished backup at 20-NOV-07
Starting Control File and SPFILE Autobackup at 20-NOV-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\AUTOBACKUP\2007_11_20\O1_MF_S
_639170362_3N5V7C1K_.BKP comment=NONE
Finished Control File and SPFILE Autobackup at 20-NOV-07
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 3
no obsolete backups foundnothing obsolete it means control_file_record_keep_time will not affect backups unless it will be less then or equal
to retention policy.
Note : Please agree or disagree with me may be i would be wrong
Khurram

Sorry for alls readers after a long practical observation at my own database server i came across that my observation was wrong and absurd in this first post, the above observation is not due to control_file_record_keep_time ,its due to something obvious which i am going to share you guys here.
RMAN> show retention policy
2> ;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
no obsolete backups found
RMAN> list backup
2> ;
RMAN>AS documentation says
"Besides affecting datafile and control file backups, the retention policy affects archived logs and archived log backups.
First, RMAN decides which datafile and control file backups are obsolete. Then, RMAN considers as obsolete all archived
log backups that are older than the oldest datafile or control file backup that must be retained."
Now i connect to SQL and create two big table for filling the redo log file and then get it archived.Please
consider it here that i am getting archived before any taking backup i.e backup database in order to make
archive older then the oldest datafile.
SQL> show parameter control_file_record_keep_time
NAME                                 TYPE        VALUE
control_file_record_keep_time        integer     7
SQL> create table a1 as select * from all_objects
2 /
Table created.
SQL> create table a2 as select * from all_objects
2 /
Table created.
C:\>dir C:\oracle\product\10.1.0\flash_recovery_area\ORCL\ARCHIVELOG\2008_03_17
Volume in drive C is khurram
Volume Serial Number is F49D-FF2B
Directory of C:\oracle\product\10.1.0\flash_recovery_area\ORCL\ARCHIVELOG\2008_03_17
03/17/2008 03:44 PM    <DIR>          .
03/17/2008 03:44 PM    <DIR>          ..
03/17/2008 03:44 PM         9,750,528 O1_MF_1_15_3XWLVK6T_.ARC
               1 File(s)      9,750,528 bytes
               2 Dir(s) 62,714,875,904 bytes free
Now i take backup
RMAN> backup database
2> ;
Starting backup at 17-MAR-08
using channel ORA_DISK_1
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
no obsolete backups found
RMAN> backup database
2> ;
Starting backup at 17-MAR-08
using channel ORA_DISK_1
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
Report of obsolete backups and copies
Type                 Key    Completion Time    Filename/Handle
Archive Log          402    17-MAR-08          C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
COVERY_AREA\ORCL\ARCHIVELOG\2008_03_17\O1_MF_1_15_3XWLVK6T_.ARCYou can see the obsolete archived files which is the older then the oldest file which has been obsolete.It also
does'nt make sense to keep the archived log files which is older then the oldest file cause it will no longer
be useful for recovery process.
now back to pavillion
RMAN> delete obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
using channel ORA_DISK_1
Deleting the following obsolete backups and copies:
Type                 Key    Completion Time    Filename/Handle
Archive Log          402    17-MAR-08          C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
COVERY_AREA\ORCL\ARCHIVELOG\2008_03_17\O1_MF_1_15_3XWLVK6T_.ARC
Do you really want to delete the above objects (enter YES or NO)? yes
deleted archive log
archive log filename=C:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ORCL\ARCHIVELO
G\2008_03_17\O1_MF_1_15_3XWLVK6T_.ARC recid=402 stamp=649611842
Deleted 1 objects
RMAN> delete backup
2> ;
using channel ORA_DISK_1
RMAN> list backup
2> ;
C:\>dir C:\oracle\product\10.1.0\flash_recovery_area\ORCL\ARCHIVELOG\2008_03_17
Volume in drive C is khurram
Volume Serial Number is F49D-FF2B
Directory of C:\oracle\product\10.1.0\flash_recovery_area\ORCL\ARCHIVELOG\2008_
03_17
03/17/2008 03:59 PM    <DIR>          .
03/17/2008 03:59 PM    <DIR>          ..
               0 File(s)              0 bytes
               2 Dir(s) 62,724,440,064 bytes freenow this time what i did i created the archived log files after first backup in order to not to make it older
then the oldest datafile backup.
RMAN> backup database
2> ;
Starting backup at 17-MAR-08
using channel ORA_DISK_1
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
no obsolete backups foundnow i come to at SQL and make redo log file filled by creating 2 big tables in order to get it archived
SQL> create table a3 as select * from all_objects
2 /
Table created.
SQL> create table a4 as select * from all_objects
2 /
Table created.
C:\>dir C:\oracle\product\10.1.0\flash_recovery_area\ORCL\ARCHIVELOG\2008_03_17
Volume in drive C is khurram
Volume Serial Number is F49D-FF2B
Directory of C:\oracle\product\10.1.0\flash_recovery_area\ORCL\ARCHIVELOG\2008_
03_17
03/17/2008 04:09 PM    <DIR>          .
03/17/2008 04:09 PM    <DIR>          ..
03/17/2008 04:09 PM         9,751,552 O1_MF_1_16_3XWNCGRS_.ARC
               1 File(s)      9,751,552 bytes
               2 Dir(s) 62,563,205,120 bytes free
RMAN> backup database
2> ;
Starting backup at 17-MAR-08
using channel ORA_DISK_1
channel ORA_DISK_1: starting compressed full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
no obsolete backups foundYou can see no archived logs get obsolete yet cause the archivelog O1_MF_1_16_3XWNCGRS_.ARC
is not older then oldest datafile backup.
But this archivelog file will get obsolete if its beyond the retention policy,lest see how ,just take one more
backup ,as i have already taken two time backup and the moment i go to take third backup it will cross ours
retetnion policy from the period of 2.
RMAN> backup database
2> ;
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
Report of obsolete backups and copies
Type                 Key    Completion Time    Filename/Handle
Backup Set           240    17-MAR-08
Backup Piece       231    17-MAR-08          C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
COVERY_AREA\ORCL\BACKUPSET\2008_03_17\O1_MF_NNNDF_TAG20080317T160604_3XWN4WTB_.B
KP
Backup Set           241    17-MAR-08
Backup Piece       232    17-MAR-08          C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
COVERY_AREA\ORCL\BACKUPSET\2008_03_17\O1_MF_NCSNF_TAG20080317T160604_3XWN6Z95_.B
KP
Archive Log          403    17-MAR-08          C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
COVERY_AREA\ORCL\ARCHIVELOG\2008_03_17\O1_MF_1_16_3XWNCGRS_.ARCKhurram

RMAN retention policy - backup spfile and then redundancy = 5 removes it.

I have a database that is Oracle Standard Edition and it is version 9.2.0.6.
The spfile has not changed since November, 2005. A list backup does not show an spfile backup with a tag of "hot_database_spfile_backup_full". I took a close look at the RMAN script log and was shocked to discover that the spfile backup from the current day is being deleted. Is that because of the redundancy = 5? I'm trying to figure out why a backup piece from the current day is being deleted?
Examples follow.
The script deletes obsolete with redundancy = 5, however, I believe the intent was to keep 25 days because one of the configure clauses is set to a recovery window of 25 days. I realize that the redundancy overrides the configure retention policy command. I can fix the script and remove the redundancy = 5.
In the RMAN run statement, I first resync the catalog, backup the spfile, a full backup of the database including current controlfile plus archive log (delete input), resync catalog, switch logfile, and backup any additional archive logs. The backup looks fine.
Then, I allocate a channel for maintenance type sbt. The script then has a "delete noprompt expired backup;" a "delete noprompt obsolete redundancy = 5;" and finally, a crosscheck;
example of backup piece that is later deleted:
Starting backup at 07/18/2006 20:00:14
channel t1: starting full datafile backupset
channel t1: specifying datafile(s) in backupset
including current SPFILE in backupset
channel t1: starting piece 1 at 07/18/2006 20:00:14
channel t1: finished piece 1 at 07/18/2006 20:00:15
piece handle=P*****_2338_1_596145614_FULL comment=API Version 2.0,MMS Version 5.2.0.0
channel t1: backup set complete, elapsed time: 00:00:01
Finished backup at 07/18/2006 20:00:15
deletion:
Deleting the following obsolete backups and copies:
Type Key Completion Time Filename/Handle
<other lines deleted>
Backup Set 27453 07/18/2006 20:00:14
Backup Piece 27454 07/18/2006 20:00:14
P*****_2338_1_596145614_FULL
deleted backup piece
backup piece handle=P*****_2338_1_596145614_FULL recid=2039 stamp=596145614
Deleted 12 objects
Why is a backup piece created on 7/18 being deleted in the maintenance step?
Thanks in advance!

In the next step in the script, the controlfile and spfile are backed up:
backup
full
skip inaccessible
tag hot_database_backup_full
format '%d_%s_%p_%t_FULL'
(Database
include current controlfile)
Plus Archivelog delete input;
Even though my backup script is redundant by backing up the spfile twice, when I list the backup of the spfile, I would have expected to find 5 backups with a tag of hot_database_spfile_backup_full and 5 with a tag of hot_database_backup_full. That is not the case. I only find spfiles with a tag of hot_database_backup_full. i am still perplexed by RMAN.
I will modify my script - remove the backup of the spfile, and crosscheck before the delete commands. I will also remove the redundancy = 5. The intent is to keep 25 days of backups.
Thanks for your comments

When Retention policy is set as REDUNDANCY

DB version: 10.2.0.4
Just trying to understand the concept of Redundancy.
If i set my Retention Policy set to REDUNDANCY like
CONFIGURE RETENTION POLICY TO REDUNDANCY 4;and all the backup files are stored in one location like '/u04/rmanbkp/' then multiple copies (4 of them) of the same datafile with different names (unique names generated using U% setting) will be created here. Right?
The next day all these datafile copies will be obsolete. Right?
Recovery Window retention policy is more widely used than Redundancy . Right?

on the 5th day,the first (out of 4 copies) copy of backup becomes obseleteprovided that you do exactly one backup every day. If you do 6 backups a day -- e.g. every 4 hours -- you'd be obsoleting a backup less than 24 hours old !
So, if you are DBA new to a site, ask first "how many backups we do, what is the RETENTION Policy" ?
Hemant K Chitale

Sharepoint List Retention Policy based on Modified Date

How do I implement a Sharepoint List Retention Policy that deletes list items that haven't been modified in X days?
I've tried to create a retention policy in Sharepoint, but I only get the option to base the policy on:
Created Date
Declared Record
I need the policy to be based on Modified Date, a standard date field that appears against all lists & document libraries. Is there a configuration change I can make to cause Modified Date to appear in the list of available fields on the Retention Policy
dialog window?
Thanks.

Veda, thanks but I'm not really a hardcore C# coder.
We found more elegant solution was to create a List View which returns all records that should be deleted, based on our own custom deletion criteria, and then create an very simple SSIS Package in Visual Studio using the
Sharepoint Connectors for SSIS to delete all Sharepoint List Items returned from that List View. The Sharepoint Destination Connector has a delete operation.
This worked for us and didn't require any coding.

Retention Policy and report/delete obsolete

The database is Oracle 9i on Solaris 8 Platform.
The backup of datafiles and archivelog files use tape and run every night.
The backups should be held for two weeks therefore using RMAN retention policy with REPORT / DELETE OBSOLETE will be the apropiate method. Unfortunatelly somehow none of the two methods of retention policy RECOVERY WINDOW or REDUNDANCY don't seem to work. The big question is WHY?
I configured the retention policy using:
CONFIGURE RETENTION POLICY TO REDUNDANCY 7
Then ALLOCATE CHANNEL FOR MAINTENANCE DEVICE TYPE sbt;
I ran CROSSCHECK BACKUP with a correct output and then REPORT OBSOLETE. The report displays all existing backups - (SYSDATE-2)!
If using RECOVERY WINDOW OF 7 DAYS then the obsolete report displays the list of backups - (SYSDATE-1).
Somehow whatever number I use (7/9/5)in any of the retention policy the result is identical with the one above!

Really I do not know if there is a limitation regarding that aspect if you take the backups in tapes directly. I have implanted and I have seen it function well when backups are store directly in disk.
Find out here if that is a limitation.
Recovery Manager Quick Reference Contents / Search / / PDF
Recovery Manager Reference Contents / Search / Index / PDF
Recovery Manager User's Guide Contents / Search / Index / PDF
http://otn.oracle.com/pls/db92/db92.docindex?remark=homepage
Joel P�rez

Retention policy configuration

Hi, I need some clarification regarding the two configuration parameter of retention policy, so please help me regarding this , I am giving my view about both the configuration
1 . CONFIGURE RETENTION POLICY TO REDUNDANCY 3;
Explanation => This configuration ensure that there can be the maximum of three backup of copies of a data file and control file, we we take the backup for our database/ datafile/ control file for the 4th times, then our previous backup which was taken for the first time will be not be in used, it become obsolete...
suppose on the above configuration , the first backup will be obsolete after taking the database/datafile/controlfile
backup for fourth time...when we take the backup for 5th time, the process will goes as previous , the second backup that was taken earlier will become obsolete..
2.CONFIGURE RETENTION POLICY TO RECOVER WINDOW OF 5 DAYS;
Explanation = > This configuration deals basically with the time based..here the main concept is that the backup will be there of period basis. The recovery window is a period of time that begins with the current time and extend backward in time to the period of recoverability is the earliest time.
Here, the backup that was taken early will remain there unless and until the specified days does not met..
on the above configuration the backup will remain and can be in use that was taken from last five days
suppose. today is 08/11/2010, and the back up is taken then the backup can be recovered form 04th of nov..
Please show me the right path regarding my view and clear up my concept if I am wrong....
Thanks in advance

Hi,
Welcome to forums.. !!
1 . CONFIGURE RETENTION POLICY TO REDUNDANCY 3;
Explanation => This configuration ensure that there can be the maximum of three backup of copies of a data file and control file, we we take the backup for our database/ datafile/ control file for the 4th times, then our previous backup which was taken for the first time will be not be in used, it become obsolete...
suppose on the above configuration , the first backup will be obsolete after taking the database/datafile/controlfile
backup for fourth time...when we take the backup for 5th time, the process will goes as previous , the second backup that was taken earlier will become obsolete..
2.CONFIGURE RETENTION POLICY TO RECOVER WINDOW OF 5 DAYS;
Explanation = > This configuration deals basically with the time based..here the main concept is that the backup will be there of period basis. The recovery window is a period of time that begins with the current time and extend backward in time to the period of recoverability is the earliest time.
Here, the backup that was taken early will remain there unless and until the specified days does not met..
on the above configuration the backup will remain and can be in use that was taken from last five days
suppose. today is 08/11/2010, and the back up is taken then the backup can be recovered form 04th of nov..Your understanding is correct. some times if the backups will not become obsolete, under the recovery window, when it needs for recovery.
- Pavan Kumar N

Retention Policy to delete both backup sets and archivelogs automatically

I configured the Recovery Window-Based Retention Policy for my database for the window=14 days. I also set up a crontab to do a full backup every Monday. So say in a month, there will be 30 archive logs and 4 full DB backup sets.
Now that I understand if the FRA gets filled up, older archive logs that are not needed for the 14 days recoverable window will be automatically deleted. My questions is what happen to the old backup sets? Will they get deleted automatically too if there is no space left in FRA? Or I need to use "DELETE OBSOLETE" to delete them?
Thanks.

One of the advantages of the FRA is, in case of space pressure obsolete objects (obsolete due to the defined retention policy) are deleted automatically. That's true for backups and archivelogs. The objects are NOT deleted automatically after the retention policy expires, but only when additional space is needed. That does not mean you don't have to care about FRA space consumption. You may have unusual amounts of archivelogs, additional backups and flashback logs (if flashback database is configured), which fill up the FRA.
Werner

Retention policy vs. Archivelog deletion policy

Environment:
Oracle EE 11.2.0.3 on Solaris 10.5
Which policy takes precedence?
My Retention Policy is set to 'Recovery window of 8 days' and my Archivelog deletion policy is set to 'backed up 2 times to disk'.
My DAILY full backup happens at 03:00am and uses the following commands:
backup incremental level 0 cumulative database tag 'full_daily' plus archivelog tag 'full_daily';
DELETE NOPROMPT OBSOLETE;I also have an archivelog backup that runs every 4 hours at 02:00, 06:00, 10:00, 14:00, 18:00 and 22:00 and looks like this:
backup archivelog all tag '&1';
delete noprompt ARCHIVELOG UNTIL TIME 'SYSDATE-8';With the archivelog backup running every 4 hours the logs are getting backed up to disk the required 2 times very quickly. Much sooner than 8 days! :-)
I have a problem where the archivelog backup that runs immediately AFTER the full database backup fails due to not being able to find some older archivelog files.
In looking at V$ARCHIVED_LOG the files were dated (COMPLETION_DATE) just outside the 8 day retention window but they had a status of 'A' (Archived) instead of the 'D' (Deleted) I was expecting. When I ran a 'Crosscheck archivelog all' it changed the statuses to 'D' and the next archivelog backup ran successfully.
What am I missing?
Should I change the archivelog deletion policy to something else? If so, what and why (just trying to understand!) ?
I am not using an FRA and have controlfile autobackup turned on.
Please let me know if you need more information. I have been scouring the docs and the 11g RMAN Oracle Press book but haven't found the trick yet!
Thanks for any assistance!
-gary

Hemant K Chitale wrote:
The Retention Policy applies to Backups. It does not apply to ArchiveLogs.
The ArchiveLog Deletion Policy applies to ArchiveLogs. It does not apply to Backups.
Since you have 2 copies of ArchiveLogs in the backups and these are retained for 8 days, a "delete noprompt ARCHIVELOG UNTIL TIME 'SYSDATE-8';" is overkill. Why retain 8 days of archivelogs on disk if there are 2 copies already backed up ?
Does your full backup that begins at 3am complete before 6am ? If it goes beyond 6am, it will be deleting some files after 6am but the "backup archivelog all" at 6am will expect some archivelogs (8 days old) to be present.
Hemant K Chitale
RMAN> CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/oracle/oracle/.Autobackup_CTRL/%F.ctl_bkp';
Starting backup at 22-MAY-12
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile copy
input datafile file number=00001 name=/oracle/oracle/oradata/orcl/system01.dbf
output file name=/oracle/oracle/flash_recovery_area/ORCL/datafile/o1_mf_system_7vpg432v_.dbf tag=TAG20120522T122602 RECID=1 STAMP=783951999
channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:46
channel ORA_DISK_1: starting datafile copy
input datafile file number=00002 name=/oracle/oracle/oradata/orcl/sysaux01.dbf
output file name=/oracle/oracle/flash_recovery_area/ORCL/datafile/o1_mf_sysaux_7vpg5l1n_.dbf tag=TAG20120522T122602 RECID=2 STAMP=783952038
channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:35
channel ORA_DISK_1: starting datafile copy
input datafile file number=00003 name=/oracle/oracle/oradata/orcl/undotbs01.dbf
output file name=/oracle/oracle/flash_recovery_area/ORCL/datafile/o1_mf_undotbs1_7vpg6ms0_.dbf tag=TAG20120522T122602 RECID=3 STAMP=783952046
channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:03
channel ORA_DISK_1: starting datafile copy
input datafile file number=00004 name=/oracle/oracle/oradata/orcl/users01.dbf
output file name=/oracle/oracle/flash_recovery_area/ORCL/datafile/o1_mf_users_7vpg6ptn_.dbf tag=TAG20120522T122602 RECID=4 STAMP=783952047
channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:03
Finished backup at 22-MAY-12
Starting Control File and SPFILE Autobackup at 22-MAY-12
piece handle=/oracle/oracle/product/11.2.0/dbhome_1/dbs/controlfile_c-1309370544-20120522-02 comment=NONE
Finished Control File and SPFILE Autobackup at 22-MAY-12
ORA-00604: error occurred at recursive SQL level 1
ORA-06502: PL/SQL: numeric or value error: character string buffer too small
RMAN-08132: WARNING: cannot update recovery area reclaimable file list
old RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F';
new RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/oracle/oracle/.Autobackup_CTRL/%F.ctl_bkp';
new RMAN configuration parameters are successfully stored
RMAN> delete noprompt ARCHIVELOG UNTIL TIME 'SYSDATE-8';
released channel: ORA_DISK_1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=196 device type=DISK
RMAN-08138: WARNING: archived log not deleted - must create more backups
archived log file name=/oracle/oracle/flash_recovery_area/ORCL/archivelog/2012_04_28/o1_mf_1_2_7sq8tf5p_.arc thread=1 sequence=2
RMAN-08138: WARNING: archived log not deleted - must create more backups
archived log file name=/oracle/oracle/flash_recovery_area/ORCL/archivelog/2012_05_22/o1_mf_1_3_7vpdcjjm_.arc thread=1 sequence=3
ORA-00604: error occurred at recursive SQL level 1
ORA-06502: PL/SQL: numeric or value error: character string buffer too small
RMAN-08132: WARNING: cannot update recovery area reclaimable file list
RMAN> having problem with Archivelog backup.

Not set configure retention policy to recovery window of 7 days

HI all,
if parameter "" configure retention policy to recovery window of 7 days "" is not set
then i am taking weekly and inreamental cumulative backup any effect of backup
i think in this case delete obsolete is not working.
currently parameter set is CONFIGURE RETENTION POLICY TO REDUNDANCY 1;

HI all,
if parameter "" configure retention policy to recovery window of 7 days "" is not set
then i am taking weekly and inreamental cumulative backup any effect of backup
i think in this case delete obsolete is not working.
currently parameter set is CONFIGURE RETENTION POLICY TO REDUNDANCY 1;

Purpose of Retention Policy Recovery Window and Redundancy

Hi,
Good Evening,
I have some queries regarding the RMAN Retention Policy Recovery Window and Redundancy.
1. Any condition is there to set the Retention Policy Recovery Window and Redundancy and control_file_record_keep_time?What is the relationship between these 3 parameters?
2. Explain the scenario if i set the control_file_record_keep_time=4 Redundancy=3 and Recovery Window=7?
3. If i set the Redundancy=3 and Recovery Window=7 means my backup place only have 3 copies of backup based on the redundancy then what is the purpose of Recovery Window=7 please give some example.
4. If i change the values for Recovery Window=3 and Redundancy=7 what will happened, how many days backup will be available in my FRA location?Explain with one scenario?
Thanks in advance.
Vijay.

Hi,
Take a look of the above doc contents:
Configuring the Backup Retention Policy
As explained in "Backup Retention Policies", the backup retention policy specifies which backups must be retained to meet your data recovery requirements. This policy can be based on a recovery window or redundancy. Use the CONFIGURE RETENTION POLICY command to specify the retention policy.
so you have option to choose either recovery windows or redundancy based you can set the configuration like
read in the Doc What it said for both:
Recovery Window-Based Retention Policy ==>RMAN does not consider any full or level 0 incremental backup as obsolete if it falls within the recovery window. Additionally, RMAN retains all archived logs and level 1 incremental backups that are needed to recover to a random point within the window.
Redundancy-Based Retention Policy==>The REDUNDANCY parameter of the CONFIGURE RETENTION POLICY command specifies how many full or level 0 backups of each datafile and control file that RMAN should keep. If the number of full or level 0 backups for a specific datafile or control file exceeds the REDUNDANCY setting, then RMAN considers the extra backups as obsolete. The default retention policy is REDUNDANCY 1.
RMAN> show RETENTION POLICY;
using target database control file instead of recovery catalog
RMAN configuration parameters for database with db_unique_name DDTEST are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
RMAN> CONFIGURE RETENTION POLICY TO REDUNDANCY 3;
old RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
new RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO REDUNDANCY 3;
new RMAN configuration parameters are successfully stored
RMAN> show RETENTION POLICY;
RMAN configuration parameters for database with db_unique_name DDTEST are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 3;
RMAN> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
old RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO REDUNDANCY 3;
new RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
new RMAN configuration parameters are successfully stored
RMAN> show RETENTION POLICY;
RMAN configuration parameters for database with db_unique_name DDTEST are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
CONTROL_FILE_RECORD_KEEP_TIME:This parameter applies only to records in the control file that are circularly reusable (such as archive log records and various backup records) ref Doc:CONTROL_FILE_RECORD_KEEP_TIME
1. Any condition is there to set the Retention Policy Recovery Window and Redundancy and control_file_record_keep_time?What is the relationship between these 3 parameters?
2. Explain the scenario if i set the control_file_record_keep_time=4 Redundancy=3 and Recovery Window=7?
3. If i set the Redundancy=3 and Recovery Window=7 means my backup place only have 3 copies of backup based on the redundancy then what is the purpose of Recovery Window=7 please give some example.
4. If i change the values for Recovery Window=3 and Redundancy=7 what will happened, how many days backup will be available in my FRA location?Explain with one scenario?
so i believe you can get the Answer from Your Question from Above details.
HTH

Retention Policy and Managed folder based retention

What is difference between "Retention Policy/ Policy Tags" and " Managed Content Settings"?
In my setup , my managed folder folder become general folder after following steps
1. Created Managed folder
2. Created managed content settings for IPM.post and IPM.Appointment with retention action "Delete and Allow recovery".
3. Created managed policy and applied to 1 mailbox, and this is working properly
But After that,
1. Created 3 retention tags(1 for inbox, 1 for sent, 1 personal).
2. Created retention policy combining these 3 tags.
3. Applied to SAME mailbox
4. Ran 'ManagedFolderAssitant'
**After this, Managed folder become general outlook folder.
So, cant I have "Managed folder based retention for managed folders" and General retention for "Inbox,Sent"

Exchange 2010 RTM introduced Retention Policies as the successor to the Message Records Management (MRM) technology introduced in Exchange 2007. MRM was the successor to Mailbox Manager Policies in Exchange 2003. Message Records Management is called MRM
1.0 and Retention Policies is being called MRM 2.0 for short. MRM 1.0 as well as MRM 2.0 are both available in Exchange 2010. Only difference is we can manage Retention Policies from the EMC and EMS, but the Managed Folder Mailbox Policy is only Managed from
the EMS through cmdlets in Exchange 2010 SP1.
It completely depends on your requirements when to use MRM 1.0 and when to Use MRM 2.0.
Certain new features are added in MRM 2.0 (Retention Policy) which allow us to manage our mailbox email items at very granular level. But if we are still happy with earlier version MRM 1.0 then we can continue using Managed folder mailbox
Policy in Exchange 2010.
[ Note: If we are Using the Retention Policy (MRM 2.0) then we can view the expiry of each and every email items of the folders on which the retention Policy is tagged and this can be only view from OWA and Outlook 2010, But this feature
is not available for Managed Folder Mailbox Policy (MRM 1.0) ]
We cannot use the Base Folder only switch in MRM 2.0 because it is TAG specific (DPT, RPT, and PPT) not Managed Folder specific.
Managed folder Mailbox Policy is folder specific this would be the major difference.
Refer to this link :
Retention policies vs Managed folders

RMAN Retention Policy - redundancy vs recovery window

Hi All,
I'm wondering what the most commonly used rman retention policy is, to provide point-in-time recovery. We have 2 oracle servers, one using redundancy policy (3) and the other using recovery window (2 days). I would like to standardize them but am not confident in which direction I should go in.
I'm tempted to lean towards redundancy but wanted to pose the question to a wider, experienced audience for any things to think about/watch out for. Also, I assume the restore process would the same for either.
Thanks in advance.

Redundancy based retention policy means how many backups of each datafile must be retained and Recovery windows based retention policy is a period of time which starts with current time and goes backward in time upto the point of recoverability.
Oracle suggests and its Best practice is "Recovery Window" .( I don't know the reason though)
Two things you need to consider:
1) You might need more space in case of "recovery window" because it depends upon the schedule of the backup. In "redundancy" , your space consumption will be same.
2) You need to keep "recovery window" time less than the value of "control_file_Record_keep_time" so your backup records won't be overwritten in controlfile.
We use "Recovery Window"

Recovery window retention policy deletes archive logs before a backup?

Hi All,
Oracle 11G on Windows 2008 R2
This afternoon, I changed my RMAN retention policy from 'RETENTION POLICY REDUNDANCY 3' to RETENTION POLICY RECOVERY WINDOW OF 3 DAYS'
However, i checked tonight and after my daily backup ran, all the archive logs prior to the backup had been deleted! Thus meaning i dont think i can restore to any point in time, prior to my daily backup. All the .arc logs were there after the backup. So i tried another test and kicked off the daily backup again. During the backup process, the archive logs got deleted again! Now i don't have any archive logs..
Is this proper behaviour of RETENTION POLICY RECOVERY WINDOW?? I thought it would keep all the files needed for me to restore to any point in time for the previous 3 days. When i used REDUNDANCY, with my daily backups, it kept 3 days worth of backups+ archive logs so i could restore point-in-time to any point. How can i use RECOVERY WINDOW so that i can actually restore to any point-in-time for the 3 days??
I wanted to change to RECOVERY WINDOW since i read that by using REDUNDANCY it only keeps X copies of a backup (so if i ran the backup 3 times in a day, i would only have those 3).
Thanks in advance.

Hi All,
Here is the SHOW ALL output:
RMAN> show all;
RMAN configuration parameters for database with db_unique_name MMSPRD7 are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 3 DAYS;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOA
D TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'D:\ORACLE\DATABASE\ORA11G\DATABASE\SNCFM
MSPRD7.ORA'; # default
Here is the RMAN script:
Recovery Manager: Release 11.2.0.3.0 - Production on Mon Jan 20 23:03:12 2014
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to target database: XXX (DBID=)
RMAN> CROSSCHECK ARCHIVELOG ALL;
2> CROSSCHECK BACKUPSET;
3> CROSSCHECK BACKUP;
4> CROSSCHECK COPY;
5> DELETE NOPROMPT EXPIRED ARCHIVELOG ALL;
6> DELETE NOPROMPT EXPIRED BACKUPSET;
7> DELETE NOPROMPT OBSOLETE;
8> BACKUP CURRENT CONTROLFILE;
9> BACKUP AS COMPRESSED BACKUPSET DATABASE PLUS ARCHIVELOG DELETE INPUT;
Also, not sure if you needed the whole RMAN output, but here is the deletion part:
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 3 days
using channel ORA_DISK_1
Deleting the following obsolete backups and copies:
Type                 Key    Completion Time    Filename/Handle
Backup Set           1392   15-JAN-14
Backup Piece       1392   15-JAN-14          F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_15\O1_MF_NNNDF_TAG20140115T190054_9FG89R8N_.BKP
Backup Set           1393   15-JAN-14
Backup Piece       1393   15-JAN-14          F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_15\O1_MF_ANNNN_TAG20140115T192204_9FG9KDHX_.BKP
Backup Set           1397   16-JAN-14
Backup Piece       1397   16-JAN-14          F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_16\O1_MF_ANNNN_TAG20140116T190027_9FJWNW6L_.BKP
Backup Set           1400   17-JAN-14
Backup Piece       1400   17-JAN-14          F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_17\O1_MF_ANNNN_TAG20140117T190138_9FMK349M_.BKP
deleted backup piece
backup piece handle=F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_15\O1_MF_NNNDF_TAG20140115T190054_9FG89R8N_.BKP RECID=1392 STAMP=836938856
deleted backup piece
backup piece handle=F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_15\O1_MF_ANNNN_TAG20140115T192204_9FG9KDHX_.BKP RECID=1393 STAMP=836940124
deleted backup piece
backup piece handle=F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_16\O1_MF_ANNNN_TAG20140116T190027_9FJWNW6L_.BKP RECID=1397 STAMP=837025228
deleted backup piece
backup piece handle=F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_17\O1_MF_ANNNN_TAG20140117T190138_9FMK349M_.BKP RECID=1400 STAMP=837111700
Deleted 4 objects

Retention Policy in 8i

Similar Messages

Maybe you are looking for