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
Similar Messages
-
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 -
Query on RMAN Retention Policy
Hi, I have my Retention policy set to Redundancy 2
I have taken 3 backups so far ( 2 Backup Sets, 1 Image Copy )
When I check report obsolete I get the following
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 1 05-SEP-13
Backup Piece 1 05-SEP-13 /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_05/o1_mf_annnn_TAG20130905T100934_92jllgn1_.bkp
Backup Set 2 05-SEP-13
Backup Piece 2 05-SEP-13 /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_05/o1_mf_nnndf_TAG20130905T100949_92jllycp_.bkp
Backup Set 3 05-SEP-13
Backup Piece 3 05-SEP-13 /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_05/o1_mf_ncsnf_TAG20130905T100949_92jln4d5_.bkp
Backup Set 4 05-SEP-13
Backup Piece 4 05-SEP-13 /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_05/o1_mf_annnn_TAG20130905T101030_92jln6cx_.bkp
Backup Set 5 27-SEP-13
Backup Piece 5 27-SEP-13 /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_27/o1_mf_annnn_TAG20130927T120734_94bsqrj6_.bkp
Backup Set 7 27-SEP-13
Backup Piece 7 27-SEP-13 /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_27/o1_mf_ncsnf_TAG20130927T120751_94bssf0j_.bkp
Archive Log 305 10-OCT-13 /home/app/oracle/fast_recovery_area/PRIMARYP/archivelog/2013_10_10/o1_mf_1_138_95dv9okt_.arc
Archive Log 306 10-OCT-13 /home/app/oracle/fast_recovery_area/PRIMARYP/archivelog/2013_10_10/o1_mf_1_139_95dv9px0_.arc
Archive Log 307 10-OCT-13 /home/app/oracle/fast_recovery_area/PRIMARYP/archivelog/2013_10_10/o1_mf_1_140_95dv9r8f_.arc
Archive Log 308 10-OCT-13 /home/app/oracle/fast_recovery_area/PRIMARYP/archivelog/2013_10_10/o1_mf_1_141_95dv9sk9_.arc
Backup Set pieces 1,2,3,4 basically equate to my oldest backup - hence under redundancy of 2, I can see why that is obsolete
5 and 7 were simply Control File/SPFILE backups from Auto Backup and the 2 newer backups of these have been taken since ( i.e. backupset pieces 9 and 10 )
Q. What happens if I wanted to restore the database to the 27/09 ? What SPFILE and Control would it use ( presuming the OBSOLETE files had been removed out of the FRA ) ?
Would I have to restore the removed backup set into the FRA, Cross Check and then restore the database via RMAN to the 27/09 ?
Q. Why are some of today's ( 10/10/13 ) archive logs marked as OBSOLETE ?
Q. If I wanted to have the ability to restore the database to 2 days ago, is perhaps a Rentention Policy of a 2 day Recovery Window perhaps better than my current Redundancy=2 policy ( combined with taking a daily backup ) ?
any advice appreciated,
JimQ. What happens if I wanted to restore the database to the 27/09 ? What SPFILE and Control would it use ( presuming the OBSOLETE files had been removed out of the FRA ) ?
Would I have to restore the removed backup set into the FRA, Cross Check and then restore the database via RMAN to the 27/09 ?
- Yes you can get the database to the date which ever you want , using recover database until time.
Q. Why are some of today's ( 10/10/13 ) archive logs marked as OBSOLETE ?
- can you please provide the output of below command
RMAN> show all;
Q. If I wanted to have the ability to restore the database to 2 days ago, is perhaps a Rentention Policy of a 2 day Recovery Window perhaps better than my current Redundancy=2 policy ( combined with taking a daily backup ) ?
- You can restore the database back to two days or 5 days based on your requirement. You nee to recover the database using until time option.
Thanks,
http://gssdba.wordpress.com -
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.htmlKhurramHmmm, 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." -
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
KhurramSorry 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 -
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 0 DAYS;
Hi Guys
Can you please put some light on the 0 days. what is the meaning on 0 days and how does this work.
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 0 DAYS; If I take full backup every night how many backup will it contain and how will it obsolete the backup.
RMan 9i R2
Soalris 5.9
I understand the concept if recover window is 1 or more days but confuse with 0 days.
Thank you in advance.RECOVERY WINDOW OF 0 DAYS is effective like REDUNDANCY 1.
RMAN> configure retention policy to recovery window of 0 days;
old RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
new RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 0 DAYS;
new RMAN configuration parameters are successfully stored
RMAN> backup datafile 4;
Starting backup at 09-SEP-07
using target database controlfile instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=15 devtype=DISK
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00004 name=E:\ORACLE\ORADATA\WIN9I\DRSYS01.DBF
channel ORA_DISK_1: starting piece 1 at 09-SEP-07
channel ORA_DISK_1: finished piece 1 at 09-SEP-07
piece handle=E:\ORACLE\ORA92\DATABASE\0BIRHB2F_1_1 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
Finished backup at 09-SEP-07
RMAN> report obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 0 days
no obsolete backups found
RMAN> backup datafile 4;
Starting backup at 09-SEP-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=00004 name=E:\ORACLE\ORADATA\WIN9I\DRSYS01.DBF
channel ORA_DISK_1: starting piece 1 at 09-SEP-07
channel ORA_DISK_1: finished piece 1 at 09-SEP-07
piece handle=E:\ORACLE\ORA92\DATABASE\0CIRHB4Q_1_1 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
Finished backup at 09-SEP-07
RMAN> report obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 0 days
Report of obsolete backups and copies
Type Key Completion Time Filename/Handle
Backup Set 10 09-SEP-07
Backup Piece 10 09-SEP-07 E:\ORACLE\ORA92\DATABASE\0BIRHB2F_1_1
RMAN> delete backup;
using channel ORA_DISK_1
List of Backup Pieces
BP Key BS Key Pc# Cp# Status Device Type Piece Name
10 10 1 1 AVAILABLE DISK E:\ORACLE\ORA92\DATABASE\0BIRHB2F_1_1
11 11 1 1 AVAILABLE DISK E:\ORACLE\ORA92\DATABASE\0CIRHB4Q_1_1
Do you really want to delete the above objects (enter YES or NO)? yes
deleted backup piece
backup piece handle=E:\ORACLE\ORA92\DATABASE\0BIRHB2F_1_1 recid=10 stamp=632859727
deleted backup piece
backup piece handle=E:\ORACLE\ORA92\DATABASE\0CIRHB4Q_1_1 recid=11 stamp=632859802
Deleted 2 objects
RMAN> configure retention policy to redundancy 1;
old RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 0 DAYS;
new RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
new RMAN configuration parameters are successfully stored
RMAN> backup datafile 4;
Starting backup at 09-SEP-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=00004 name=E:\ORACLE\ORADATA\WIN9I\DRSYS01.DBF
channel ORA_DISK_1: starting piece 1 at 09-SEP-07
channel ORA_DISK_1: finished piece 1 at 09-SEP-07
piece handle=E:\ORACLE\ORA92\DATABASE\0DIRHB90_1_1 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
Finished backup at 09-SEP-07
RMAN> report obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
no obsolete backups found
RMAN> backup datafile 4;
Starting backup at 09-SEP-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=00004 name=E:\ORACLE\ORADATA\WIN9I\DRSYS01.DBF
channel ORA_DISK_1: starting piece 1 at 09-SEP-07
channel ORA_DISK_1: finished piece 1 at 09-SEP-07
piece handle=E:\ORACLE\ORA92\DATABASE\0EIRHB9H_1_1 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
Finished backup at 09-SEP-07
RMAN> report obsolete;
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 12 09-SEP-07
Backup Piece 12 09-SEP-07 E:\ORACLE\ORA92\DATABASE\0DIRHB90_1_1
RMAN> -
Retention policy for archivelogs in the flash recovery area
I am using the flash recovery area for all my backup files (archive logs, data and control files). I want to use the redundancy retention policy because it is easy to calculate the space requirement. However, I am not clear how the retention policy applies to archive logs.
Say I set the retention policy to be "keeping 3 backups". How does it affect the archive logs? Will archive logs in the flash recovery area be deleted automatically or I need to do it manually. If they are deleted automatically just like dataset files, what is the "retention policy" for them? I do not have a tape device so all archive logs are going to be stay in disk.
Thanks.I am using the flash recovery area for all my backup
files (archive logs, data and control files). I want
to use the redundancy retention policy because it is
easy to calculate the space requirement. However, I
am not clear how the retention policy applies to
archive logs.
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 -
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 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 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!
-garyHemant 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. -
Backup with retention policy to recovery window of N days
Hello,
I've issued command to create database incremental backup with configuration:
run
configure retention policy to recovery window of 14 days;
backup incremental level 1 cumulative
tag daily_incr_14_days
database
plus archivelog delete all input;
All parameters are set to their default values and database backups goes to FRA. I've got recovery catalog connected and all RC_ views at my disposal.
1) Is there any way to find out, what recovery window was used for backup from any command in rman or query from RC_ views or local database views (information from control file)?
2) If I use other recovery window setting with configure command what would rman crosscheck or report commands do?
BR
Patrycjusz.TenakaKhan wrote:
Mahir,
thanks for answer - this means that recovery window should be used mainly for maintenance purposes (crosscheck, delete obsolete, report need backup etc.) and it's not related to actual retention period with backup pieces like 'keep until' clause for backup ... database command (this information are saved with backup as I could check in rc_backup_set view from recovery catalog)?
Yes it is.
Maintaining RMAN Backups and Repository&nbsp;Records
keepOption
backup retention policy
A user-defined policy for determining how long backups and archived logs must be retained for media recovery. You can define a retention policy in terms of backup redundancy or a recovery window.
RMAN retains the data file backups required to satisfy the current retention policy, and any archived redo logs required for complete recovery of those data file backups.
recovery window
A recovery window is one type of RMAN backup retention policy, in which the DBA specifies a period of time and RMAN ensures retention of backups and archived redo logs required for point-in-time recovery to any time during the recovery window.
The interval always ends with the current time and extends back in time for the number of days specified by the user. For example, if the retention policy is set for a recovery window of seven days, and the current time is 11:00 AM on Tuesday,
RMAN retains the backups required to allow point-in-time recovery back to 11:00 AM on the previous Tuesday.
Regards
Mahir M. Quluzade -
Retention policy and deletion of archived files
hello, I 'am a novice DBA having a backup question.
Our retention policy is set to 14 days; weekly we have full database backup; daily we have an incremental backup.
See scripts below.
The drive "\\is003s012\rhea\rman" where the backup files reside has files older than 2 months.
I expected these files to be deleted already by rman.
I can't find the cause why these files are not removed.
The database backup jobs are running fine ; logs file do not contain any errors and once and a while you see that rman removes obsolete files.
list expired / report obsolete do not return any files.
thanks for the assistance
chris
================= full db
c$rman_script="backup incremental level 0 cumulative device type disk tag '%TAG' database;
backup device type disk tag '%TAG' archivelog all not backed up delete all input;
allocate channel for maintenance type disk;
delete noprompt obsolete device type disk;
release channel;
&br_save_agent_env();
&br_prebackup($l_db_connect_string, $l_is_cold_backup, $l_use_rcvcat, $l_db_10_or_higher, $l_backup_strategy, "TRUE");
my $result = &br_backup();
exit($result);
================ incr db
$rman_script="backup incremental level 1 cumulative device type disk tag '%TAG' database;
recover copy of database;
backup device type disk tag '%TAG' archivelog all not backed up delete all input;
allocate channel for maintenance type disk;
delete noprompt obsolete device type disk;
release channel;
&br_save_agent_env();
&br_prebackup($l_db_connect_string, $l_is_cold_backup, $l_use_rcvcat, $l_db_10_or_higher, $l_backup_strategy, "TRUE");
my $result = &br_backup();
exit($result);
================== rman setting
RMAN> show all;
RMAN configuration parameters for database with db_unique_name RHEA are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 14 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 '\\is003s012\rhea\rman\%F';
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 CHANNEL DEVICE TYPE DISK FORMAT '\\is003s012\rhea\rman\%U';
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 LOAD TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 1 TIMES TO 'SBT_TAPE';
CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'D:\ORACLE\PRODUCT\11.2.0\DBHOME_1\DATABASE\SNCFRHEA.ORA'; # defaultChris,
Thanks for the info; my current setting for this parameter:
SQL> show parameter CONTROL_FILE_RECORD_KEEP_TIME;
NAME TYPE VALUE
control_file_record_keep_time integer 7
I found another thread that elaborated on this: Re: CONTROL_FILE_RECORD_KEEP_TIME vs Retention Policy in RMAN
a) RMAN Retention Policy set to recovery window of 30 days means backups and archivelogs that you need to do a Point in Time Recovery to before 30 days do not get obsolete.
b) CONTROLFILE_RECORD_KEEP_TIME=7 will keep (potentially, if space pressure in the controlfile) the records of these files for only 7 days
Effect: Your old backups and archivelogs (+7 days) are no longer known by the system and will not get deleted (automatically or by delete obsolete) and your recovery area/backup location/archive destination will get filled up with old files.
Therefore set b) > a)
Based on this I changed the parameter:
alter system set CONTROL_FILE_RECORD_KEEP_TIME=35 scope=both;
Even tho the 'stale' backupsets are still invisible (still getting 'no obsolete backups found' when doing REPORT OBSOLETE), I guess that's because it will take a while (23 days?) for the CONTROL_FILE_RECORD_KEEP to catch up to the RMAN Retention Policy of 30 days)....
Barry -
RMAN backups does not match its retention policy
Hello,
I have couple of PROD instances on Windows environment with 11.2.0.3 DB version. RMAN retention policy is set to 14 days but I have noticed that backup is showing longer than that.
For example: LIST BACKUP OF DATABASE whows backups since 13th October. I also checked backup pieces at netapp share and they are present.
DELETE NOPROMPT OBSOLETE do not remove anything as expired backup.
I have clear retention policy and set to 14 days again but does not seem to work.
I would appreciate suggestion(s) regarding the strange issue.
Thanks a lot.
Best RegardsJohn-MK wrote:
Hello,
I have couple of PROD instances on Windows environment with 11.2.0.3 DB version. RMAN retention policy is set to 14 days but I have noticed that backup is showing longer than that.
For example: LIST BACKUP OF DATABASE whows backups since 13th October. I also checked backup pieces at netapp share and they are present.
DELETE NOPROMPT OBSOLETE do not remove anything as expired backup.
I have clear retention policy and set to 14 days again but does not seem to work.
I would appreciate suggestion(s) regarding the strange issue.
Thanks a lot.
Best Regards
We would need to know what kind of backups and when they were taken. Consider this scenario:
retention policy of 7 days.
Incremental level 0 backup taken on Sundays
Incremental level 1 backups taken Mon through Sat.
Let's say Oct 1 is a Sunday, so we take an inc-0 backup on Oct 1, and again on Oct 8.
Now let's say we are at Oct 10. Our 7 day retention policy dicatates that we be able to recover to any day back to Oct 3.
The only way we can recover to Oct 3 is to begin with that inc-0 backup from Oct 1.
All recovery begins with the last inc-0 backup prior to the point in time to be recovered. In a normal, regularly cycling schedule of backups, you will actually end up with backups 1 day short of being twice as old as your retention period.
Let's take a more extreme example. Same 7-day retention period, but after a single inc-0 backup, you don't take any more backups for 3 months. That one single backup is still needed to enforce your recovery window, and so is not obsolete, despite the fact it is 3 months old and your recovery window is only 7 days.
Also, you mention 'expired'. In terms of oracle backups, 'expired' is not the same as 'obsolete'.
"Obsolete" means 'no longer needed to enforce recovery policy'.
"Expired" is a bit more complex.
when a backup is taken, or an archivelog is written, a record of that is written to the repository. when you do an rman 'crosscheck', those repository records are compared to reality -- to see if the recorded backup file or archivelog file actually exists. Maybe someone used an OS command to delete them. Any file found to have 'gone walkabout' have their repository records marked as 'expired'. An rman 'delete expired' then removes those records from the repository. -
Hi,
on 10g R2 on AIX6.1 , I have the followings :
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 14 DAYS;My backup script :
RMAN> run
allocate channel t1 type disk;
backup as compressed backupset format '$dir/df_%d_%T_%s_%p' database;
sql 'alter system switch logfile';
backup as compressed backupset format '$dir/al_%d_%T_%s_%p' archivelog all delete input;
backup as compressed backupset format '$dir/ctl_%d_%T_%s_%p' current controlfile;
crosscheck backup;
delete noprompt obsolete;
delete noprompt expired backup of database;But I have the backup files of 3th of March yet :
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=/appli/oracle/BACKUP/RMAN/FULL/MYDB/df_MYDB_20110303_179_1 recid=171 stamp=744800219And the only file it deletes is :
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 14 days
using channel ORA_DISK_1
Deleting the following obsolete backups and copies:
Type Key Completion Time Filename/Handle
Backup Set 13404 18-MAR-11
Backup Piece 13408 18-MAR-11 /appli/oracle/BACKUP/RMAN/INCR/MYDB/ctl_MYDB_20110318_339_1
deleted backup piece
backup piece handle=/appli/oracle/BACKUP/RMAN/INCR/MYDB/ctl_MYDB_20110318_339_1 recid=331 stamp=746072971
Deleted 1 objectsShould not RMAN delete the backup files of before 15 of March ? Why it does not ?
Thank for explanation ? Or more.Thank to all.
We backup it every night (FULL at WE and incremental in week).
list backup of database;
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
7145 Full 571.86M DISK 00:01:55 03-MAR-11
BP Key: 7151 Status: AVAILABLE Compressed: YES Tag: TAG20110303T085658
Piece Name: /appli/oracle/BACKUP/RMAN/FULL/MYDB/df_MYDB_20110303_179_1
List of Datafiles in backup set 7145
File LV Type Ckp SCN Ckp Time Name
1 Full 75445711 03-MAR-11 /data01/bases/MYDB/system01.dbf
2 Full 75445711 03-MAR-11 /data01/bases/MYDB/psundots01.dbf
4 Full 75445711 03-MAR-11 /data01/bases/MYDB/psdefault.dbf
BS Key Type LV Size Device Type Elapsed Time Completion Time
19112 Full 772.42M DISK 00:03:05 01-APR-11
BP Key: 19118 Status: AVAILABLE Compressed: YES Tag: TAG20110401T121403
Piece Name: /appli/oracle/BACKUP/RMAN/FULL/MYDB/df_MYDB_20110401_60_1
List of Datafiles in backup set 19112
File LV Type Ckp SCN Ckp Time Name
8 Full 152751106 01-APR-11 /data01/bases/MYDB/ptprc.dbf
10 Full 152751106 01-APR-11 /index01/bases/MYDB/pttbl.dbf
15 Full 152751106 01-APR-11 /data01/bases/MYDB/pttlrg.dbf
19 Full 152751106 01-APR-11 /data01/bases/MYDB/ptprjwk.dbf
20 Full 152751106 01-APR-11 /data01/bases/MYDB/ptaudit.dbf
24 Full 152751106 01-APR-11 /data01/bases/MYDB/amlarge.dbf
26 Full 152751106 01-APR-11 /data01/bases/MYDB/apapp.dbf
27 Full 152751106 01-APR-11 /data01/bases/MYDB/aparch.dbf
34 Full 152751106 01-APR-11 /data01/bases/MYDB/aucapp.dbf
35 Full 152751106 01-APR-11 /data01/bases/MYDB/auclrge.dbf
37 Full 152751106 01-APR-11 /data01/bases/MYDB/bdapp.dbf
38 Full 152751106 01-APR-11 /data01/bases/MYDB/bdlarge.dbf
40 Full 152751106 01-APR-11 /data01/bases/MYDB/bilarge.dbf
42 Full 152751106 01-APR-11 /data01/bases/MYDB/caapp.dbf
50 Full 152751106 01-APR-11 /data01/bases/MYDB/cuaudit.dbf
54 Full 152751106 01-APR-11 /data01/bases/MYDB/cularge.dbf
58 Full 152751106 01-APR-11 /data01/bases/MYDB/dpwork.dbf
60 Full 152751106 01-APR-11 /data01/bases/MYDB/eobfapp.dbf
64 Full 152751106 01-APR-11 /data01/bases/MYDB/eocmwrk.dbf
71 Full 152751106 01-APR-11 /data01/bases/MYDB/eoecwrk.dbf
74 Full 152751106 01-APR-11 /data01/bases/MYDB/eoepapp.dbf
75 Full 152751106 01-APR-11 /data01/bases/MYDB/eoeplrg.dbf
77 Full 152751106 01-APR-11 /data01/bases/MYDB/eoewapp.dbf
81 Full 152751106 01-APR-11 /data01/bases/MYDB/eoiulrg.dbf
84 Full 152751106 01-APR-11 /data01/bases/MYDB/eoltapp.dbf
85 Full 152751106 01-APR-11 /data01/bases/MYDB/eoppapp.dbf
88 Full 152751106 01-APR-11 /data01/bases/MYDB/eotplrg.dbf
93 Full 152751106 01-APR-11 /data01/bases/MYDB/faapp.dbf
95 Full 152751106 01-APR-11 /data01/bases/MYDB/fawork.dbf
101 Full 152751106 01-APR-11 /data01/bases/MYDB/fgwork.dbf
107 Full 152751106 01-APR-11 /data01/bases/MYDB/fowork.dbf
109 Full 152751106 01-APR-11 /data01/bases/MYDB/fsapp1.dbf
112 Full 152751106 01-APR-11 /data01/bases/MYDB/glapp.dbf
122 Full 152751106 01-APR-11 /data01/bases/MYDB/inlarge.dbf -
Retention policy for incremental cumulative backup question
Hi,
I have a production database configured with retention policy for 30 days window. No catalog is used.
The backup plan is:
Sunday - Level 0 backup.
Weekdays - Incremental 1 cumulative backup.
I also noticed that some archive logs since Mar 07 2010 has become obsolete in the recent few days.
Cannot figure out why the backup of Mar 07 2010 is going to be obsolete today.
Thanks for your help!
RMAN> list backup summary;
using target database control file instead of recovery catalog
List of Backups
===============
Key TY LV S Device Type Completion Time #Pieces #Copies Compressed
*14 B 0 A SBT_TAPE 07-MAR-10 5 1 NO*
*15 B 0 A SBT_TAPE 07-MAR-10 5 1 NO*
*17 B F A SBT_TAPE 07-MAR-10 1 1 NO*
21 B F A SBT_TAPE 08-MAR-10 1 1 NO
24 B 1 A SBT_TAPE 08-MAR-10 1 1 NO
25 B 1 A SBT_TAPE 08-MAR-10 1 1 NO
27 B F A SBT_TAPE 08-MAR-10 1 1 NO
35 B 1 A SBT_TAPE 09-MAR-10 1 1 NO
36 B 1 A SBT_TAPE 09-MAR-10 1 1 NO
38 B F A SBT_TAPE 09-MAR-10 1 1 NO
46 B 1 A SBT_TAPE 10-MAR-10 1 1 NO
47 B 1 A SBT_TAPE 10-MAR-10 1 1 NO
49 B F A SBT_TAPE 10-MAR-10 1 1 NO
57 B 1 A SBT_TAPE 11-MAR-10 1 1 NO
58 B 1 A SBT_TAPE 11-MAR-10 2 1 NO
60 B F A SBT_TAPE 11-MAR-10 1 1 NO
66 B A A SBT_TAPE 12-MAR-10 1 1 NO
67 B A A SBT_TAPE 12-MAR-10 1 1 NO
68 B 1 A SBT_TAPE 12-MAR-10 1 1 NO
69 B 1 A SBT_TAPE 12-MAR-10 2 1 NO
70 B A A SBT_TAPE 12-MAR-10 1 1 NO
71 B F A SBT_TAPE 12-MAR-10 1 1 NO
77 B A A SBT_TAPE 14-MAR-10 1 1 NO
78 B A A SBT_TAPE 14-MAR-10 1 1 NO
79 B 0 A SBT_TAPE 14-MAR-10 6 1 NO
80 B 0 A SBT_TAPE 14-MAR-10 6 1 NO
81 B A A SBT_TAPE 14-MAR-10 1 1 NO
82 B F A SBT_TAPE 14-MAR-10 1 1 NO
88 B A A SBT_TAPE 15-MAR-10 1 1 NO
89 B A A SBT_TAPE 15-MAR-10 1 1 NO
90 B 1 A SBT_TAPE 15-MAR-10 1 1 NO
91 B 1 A SBT_TAPE 15-MAR-10 1 1 NO
92 B A A SBT_TAPE 15-MAR-10 1 1 NO
93 B F A SBT_TAPE 15-MAR-10 1 1 NO
99 B A A SBT_TAPE 16-MAR-10 1 1 NO
100 B A A SBT_TAPE 16-MAR-10 1 1 NO
101 B 1 A SBT_TAPE 16-MAR-10 1 1 NO
102 B 1 A SBT_TAPE 16-MAR-10 1 1 NO
103 B A A SBT_TAPE 16-MAR-10 1 1 NO
104 B F A SBT_TAPE 16-MAR-10 1 1 NO
109 B A A SBT_TAPE 17-MAR-10 4 1 NO
110 B F A SBT_TAPE 17-MAR-10 1 1 NO
111 B A A SBT_TAPE 17-MAR-10 1 1 NO
112 B F A SBT_TAPE 17-MAR-10 1 1 NO
113 B A A SBT_TAPE 17-MAR-10 1 1 NO
114 B A A SBT_TAPE 17-MAR-10 1 1 NO
115 B 1 A SBT_TAPE 17-MAR-10 1 1 NO
116 B 1 A SBT_TAPE 17-MAR-10 2 1 NO
117 B A A SBT_TAPE 17-MAR-10 1 1 NO
118 B F A SBT_TAPE 17-MAR-10 1 1 NO
123 B A A SBT_TAPE 18-MAR-10 2 1 NO
124 B F A SBT_TAPE 18-MAR-10 1 1 NO
125 B A A SBT_TAPE 18-MAR-10 2 1 NO
126 B F A SBT_TAPE 18-MAR-10 1 1 NO
127 B A A SBT_TAPE 18-MAR-10 1 1 NO
128 B F A SBT_TAPE 18-MAR-10 1 1 NO
129 B A A SBT_TAPE 18-MAR-10 1 1 NO
130 B F A SBT_TAPE 18-MAR-10 1 1 NO
131 B A A SBT_TAPE 18-MAR-10 1 1 NO
132 B A A SBT_TAPE 18-MAR-10 1 1 NO
133 B 1 A SBT_TAPE 18-MAR-10 1 1 NO
134 B 1 A SBT_TAPE 18-MAR-10 2 1 NO
135 B A A SBT_TAPE 18-MAR-10 1 1 NO
136 B F A SBT_TAPE 18-MAR-10 1 1 NO
142 B A A SBT_TAPE 19-MAR-10 2 1 NO
143 B F A SBT_TAPE 19-MAR-10 1 1 NO
144 B A A SBT_TAPE 19-MAR-10 1 1 NO
145 B F A SBT_TAPE 19-MAR-10 1 1 NO
146 B A A SBT_TAPE 19-MAR-10 1 1 NO
147 B F A SBT_TAPE 19-MAR-10 1 1 NO
148 B A A SBT_TAPE 19-MAR-10 1 1 NO
149 B F A SBT_TAPE 19-MAR-10 1 1 NO
150 B A A SBT_TAPE 19-MAR-10 1 1 NO
151 B A A SBT_TAPE 19-MAR-10 1 1 NO
152 B 1 A SBT_TAPE 19-MAR-10 1 1 NO
153 B 1 A SBT_TAPE 19-MAR-10 2 1 NO
154 B A A SBT_TAPE 19-MAR-10 1 1 NO
155 B F A SBT_TAPE 19-MAR-10 1 1 NO
161 B A A SBT_TAPE 21-MAR-10 1 1 NO
162 B 0 A SBT_TAPE 21-MAR-10 6 1 NO
163 B 0 A SBT_TAPE 21-MAR-10 6 1 NO
164 B A A SBT_TAPE 21-MAR-10 1 1 NO
165 B F A SBT_TAPE 21-MAR-10 1 1 NO
171 B A A SBT_TAPE 22-MAR-10 1 1 NO
172 B F A SBT_TAPE 22-MAR-10 1 1 NO
173 B A A SBT_TAPE 22-MAR-10 1 1 NO
174 B F A SBT_TAPE 22-MAR-10 1 1 NO
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 30 DAYS;
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'; # default
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE 'SBT_TAPE' TO 1;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt.ccbprod)' FORMAT '%d_inc_%T_%t_%U' MAXPIECESIZE 4608 M;
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/orasw/app/oracle/product/10.2.0/dbs/snapcf_ccbprod.f'; # default
RMAN> report obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 30 days
Report of obsolete backups and copies
Type Key Completion Time Filename/Handle
Control File Copy 108 19-FEB-10 /ccbprod/oradata/ccbprod/arc/control.bak.100219.21.21
Backup Set 8 07-MAR-10 Backup Piece 19 07-MAR-10 CCBPROD_inc_20100307_713034799_07l8031f_5_1
Backup Set 8 07-MAR-10 Backup Piece 18 07-MAR-10 CCBPROD_inc_20100307_713034799_07l8031f_4_1
Backup Set 8 07-MAR-10 Backup Piece 17 07-MAR-10 CCBPROD_inc_20100307_713034799_07l8031f_3_1
Backup Set 8 07-MAR-10 Backup Piece 16 07-MAR-10 CCBPROD_inc_20100307_713034799_07l8031f_2_1
Backup Set 8 07-MAR-10 Backup Piece 15 07-MAR-10 CCBPROD_inc_20100307_713034799_07l8031f_1_1
Backup Set 7 07-MAR-10 Backup Piece 14 07-MAR-10 CCBPROD_inc_20100307_713034799_08l8031f_5_1
Backup Set 7 07-MAR-10 Backup Piece 13 07-MAR-10 CCBPROD_inc_20100307_713034799_08l8031f_4_1
Backup Set 7 07-MAR-10 Backup Piece 12 07-MAR-10 CCBPROD_inc_20100307_713034799_08l8031f_3_1
Backup Set 7 07-MAR-10 Backup Piece 11 07-MAR-10 CCBPROD_inc_20100307_713034799_08l8031f_2_1
Backup Set 7 07-MAR-10 Backup Piece 10 07-MAR-10 CCBPROD_inc_20100307_713034799_08l8031f_1_1
Backup Set 10 07-MAR-10 Backup Piece 21 07-MAR-10 c-2894189962-20100307-00
Edited by: user12019850 on 22-Mar-2010 10:53 AMAnother database with the same configuration and same plan seems fine:
RMAN> show all;
using target database control file instead of recovery catalog
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 30 DAYS;
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'; # default
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE 'SBT_TAPE' TO 1;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt.cisconf)' FORMAT '%d_inc_%T_%t_%U' MAXPIECESIZE 4608 M;
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/orasw/app/oracle/product/10.2.0/dbs/snapcf_cisconf.f'; # default
RMAN> list backup summary;
List of Backups
===============
Key TY LV S Device Type Completion Time #Pieces #Copies Compressed
774 B 0 A SBT_TAPE 19-FEB-10 1 1 NO
775 B 0 A SBT_TAPE 19-FEB-10 2 1 NO
795 B 1 A SBT_TAPE 20-FEB-10 1 1 NO
796 B 1 A SBT_TAPE 20-FEB-10 1 1 NO
797 B A A SBT_TAPE 20-FEB-10 1 1 NO
803 B A A SBT_TAPE 20-FEB-10 1 1 NO
804 B F A SBT_TAPE 20-FEB-10 1 1 NO
805 B A A SBT_TAPE 20-FEB-10 1 1 NO
806 B F A SBT_TAPE 20-FEB-10 1 1 NO
807 B A A SBT_TAPE 20-FEB-10 1 1 NO
808 B F A SBT_TAPE 20-FEB-10 1 1 NO
809 B A A SBT_TAPE 21-FEB-10 1 1 NO
810 B 0 A SBT_TAPE 21-FEB-10 1 1 NO
811 B 0 A SBT_TAPE 21-FEB-10 2 1 NO
812 B A A SBT_TAPE 21-FEB-10 1 1 NO
813 B F A SBT_TAPE 21-FEB-10 1 1 NO
818 B A A SBT_TAPE 21-FEB-10 1 1 NO
819 B F A SBT_TAPE 21-FEB-10 1 1 NO
820 B A A SBT_TAPE 21-FEB-10 1 1 NO
821 B F A SBT_TAPE 21-FEB-10 1 1 NO
822 B A A SBT_TAPE 21-FEB-10 1 1 NO
823 B F A SBT_TAPE 21-FEB-10 1 1 NO
824 B A A SBT_TAPE 22-FEB-10 1 1 NO
825 B 1 A SBT_TAPE 22-FEB-10 1 1 NO
826 B 1 A SBT_TAPE 22-FEB-10 1 1 NO
827 B A A SBT_TAPE 22-FEB-10 1 1 NO
828 B F A SBT_TAPE 22-FEB-10 1 1 NO
833 B A A SBT_TAPE 22-FEB-10 1 1 NO
834 B F A SBT_TAPE 22-FEB-10 1 1 NO
835 B A A SBT_TAPE 22-FEB-10 1 1 NO
836 B F A SBT_TAPE 22-FEB-10 1 1 NO
837 B A A SBT_TAPE 22-FEB-10 1 1 NO
838 B F A SBT_TAPE 22-FEB-10 1 1 NO
839 B A A SBT_TAPE 22-FEB-10 1 1 NO
840 B F A SBT_TAPE 22-FEB-10 1 1 NO
841 B A A SBT_TAPE 23-FEB-10 1 1 NO
842 B 1 A SBT_TAPE 23-FEB-10 1 1 NO
843 B 1 A SBT_TAPE 23-FEB-10 1 1 NO
844 B A A SBT_TAPE 23-FEB-10 1 1 NO
845 B F A SBT_TAPE 23-FEB-10 1 1 NO
850 B A A SBT_TAPE 23-FEB-10 1 1 NO
851 B F A SBT_TAPE 23-FEB-10 1 1 NO
852 B A A SBT_TAPE 23-FEB-10 1 1 NO
853 B F A SBT_TAPE 23-FEB-10 1 1 NO
854 B A A SBT_TAPE 23-FEB-10 1 1 NO
855 B F A SBT_TAPE 23-FEB-10 1 1 NO
856 B A A SBT_TAPE 24-FEB-10 1 1 NO
857 B 1 A SBT_TAPE 24-FEB-10 1 1 NO
858 B 1 A SBT_TAPE 24-FEB-10 1 1 NO
859 B A A SBT_TAPE 24-FEB-10 1 1 NO
860 B F A SBT_TAPE 24-FEB-10 1 1 NO
865 B A A SBT_TAPE 24-FEB-10 1 1 NO
866 B F A SBT_TAPE 24-FEB-10 1 1 NO
867 B A A SBT_TAPE 24-FEB-10 1 1 NO
868 B F A SBT_TAPE 24-FEB-10 1 1 NO
869 B A A SBT_TAPE 24-FEB-10 1 1 NO
870 B F A SBT_TAPE 24-FEB-10 1 1 NO
871 B A A SBT_TAPE 24-FEB-10 1 1 NO
872 B 1 A SBT_TAPE 24-FEB-10 1 1 NO
873 B 1 A SBT_TAPE 24-FEB-10 1 1 NO
874 B A A SBT_TAPE 24-FEB-10 1 1 NO
875 B F A SBT_TAPE 24-FEB-10 1 1 NO
880 B A A SBT_TAPE 24-FEB-10 1 1 NO
881 B F A SBT_TAPE 24-FEB-10 1 1 NO
882 B A A SBT_TAPE 25-FEB-10 1 1 NO
883 B 1 A SBT_TAPE 25-FEB-10 1 1 NO
884 B 1 A SBT_TAPE 25-FEB-10 1 1 NO
885 B A A SBT_TAPE 25-FEB-10 1 1 NO
886 B F A SBT_TAPE 25-FEB-10 1 1 NO
891 B A A SBT_TAPE 25-FEB-10 1 1 NO
892 B F A SBT_TAPE 25-FEB-10 1 1 NO
893 B A A SBT_TAPE 25-FEB-10 1 1 NO
894 B F A SBT_TAPE 25-FEB-10 1 1 NO
895 B A A SBT_TAPE 25-FEB-10 1 1 NO
896 B F A SBT_TAPE 25-FEB-10 1 1 NO
897 B A A SBT_TAPE 25-FEB-10 1 1 NO
898 B F A SBT_TAPE 25-FEB-10 1 1 NO
899 B A A SBT_TAPE 25-FEB-10 1 1 NO
900 B F A SBT_TAPE 25-FEB-10 1 1 NO
901 B A A SBT_TAPE 25-FEB-10 1 1 NO
902 B F A SBT_TAPE 25-FEB-10 1 1 NO
903 B A A SBT_TAPE 26-FEB-10 1 1 NO
904 B 1 A SBT_TAPE 26-FEB-10 1 1 NO
905 B 1 A SBT_TAPE 26-FEB-10 1 1 NO
906 B A A SBT_TAPE 26-FEB-10 1 1 NO
907 B F A SBT_TAPE 26-FEB-10 1 1 NO
912 B A A SBT_TAPE 26-FEB-10 1 1 NO
913 B F A SBT_TAPE 26-FEB-10 1 1 NO
914 B A A SBT_TAPE 26-FEB-10 1 1 NO
915 B F A SBT_TAPE 26-FEB-10 1 1 NO
916 B A A SBT_TAPE 26-FEB-10 1 1 NO
917 B F A SBT_TAPE 26-FEB-10 1 1 NO
918 B A A SBT_TAPE 27-FEB-10 1 1 NO
919 B 1 A SBT_TAPE 27-FEB-10 1 1 NO
920 B 1 A SBT_TAPE 27-FEB-10 1 1 NO
921 B A A SBT_TAPE 27-FEB-10 1 1 NO
922 B F A SBT_TAPE 27-FEB-10 1 1 NO
927 B A A SBT_TAPE 27-FEB-10 1 1 NO
928 B F A SBT_TAPE 27-FEB-10 1 1 NO
929 B A A SBT_TAPE 27-FEB-10 1 1 NO
930 B F A SBT_TAPE 27-FEB-10 1 1 NO
931 B A A SBT_TAPE 27-FEB-10 1 1 NO
932 B F A SBT_TAPE 27-FEB-10 1 1 NO
933 B A A SBT_TAPE 28-FEB-10 1 1 NO
934 B 0 A SBT_TAPE 28-FEB-10 1 1 NO
935 B 0 A SBT_TAPE 28-FEB-10 2 1 NO
936 B A A SBT_TAPE 28-FEB-10 1 1 NO
937 B F A SBT_TAPE 28-FEB-10 1 1 NO
942 B A A SBT_TAPE 28-FEB-10 1 1 NO
943 B F A SBT_TAPE 28-FEB-10 1 1 NO
944 B A A SBT_TAPE 28-FEB-10 1 1 NO
945 B F A SBT_TAPE 28-FEB-10 1 1 NO
946 B A A SBT_TAPE 28-FEB-10 1 1 NO
947 B F A SBT_TAPE 28-FEB-10 1 1 NO
948 B A A SBT_TAPE 01-MAR-10 1 1 NO
949 B 1 A SBT_TAPE 01-MAR-10 1 1 NO
950 B 1 A SBT_TAPE 01-MAR-10 1 1 NO
951 B A A SBT_TAPE 01-MAR-10 1 1 NO
952 B F A SBT_TAPE 01-MAR-10 1 1 NO
957 B A A SBT_TAPE 01-MAR-10 1 1 NO
958 B F A SBT_TAPE 01-MAR-10 1 1 NO
959 B A A SBT_TAPE 01-MAR-10 1 1 NO
960 B F A SBT_TAPE 01-MAR-10 1 1 NO
961 B A A SBT_TAPE 01-MAR-10 1 1 NO
962 B F A SBT_TAPE 01-MAR-10 1 1 NO
963 B A A SBT_TAPE 02-MAR-10 1 1 NO
964 B 1 A SBT_TAPE 02-MAR-10 1 1 NO
965 B 1 A SBT_TAPE 02-MAR-10 1 1 NO
966 B A A SBT_TAPE 02-MAR-10 1 1 NO
967 B F A SBT_TAPE 02-MAR-10 1 1 NO
970 B A A SBT_TAPE 02-MAR-10 1 1 NO
971 B F A SBT_TAPE 02-MAR-10 1 1 NO
972 B A A SBT_TAPE 02-MAR-10 1 1 NO
973 B F A SBT_TAPE 02-MAR-10 1 1 NO
974 B A A SBT_TAPE 02-MAR-10 1 1 NO
975 B F A SBT_TAPE 02-MAR-10 1 1 NO
976 B A A SBT_TAPE 03-MAR-10 1 1 NO
977 B 1 A SBT_TAPE 03-MAR-10 1 1 NO
978 B 1 A SBT_TAPE 03-MAR-10 1 1 NO
979 B A A SBT_TAPE 03-MAR-10 1 1 NO
980 B F A SBT_TAPE 03-MAR-10 1 1 NO
983 B A A SBT_TAPE 03-MAR-10 1 1 NO
984 B F A SBT_TAPE 03-MAR-10 1 1 NO
985 B A A SBT_TAPE 03-MAR-10 1 1 NO
986 B F A SBT_TAPE 03-MAR-10 1 1 NO
987 B A A SBT_TAPE 03-MAR-10 1 1 NO
988 B F A SBT_TAPE 03-MAR-10 1 1 NO
989 B A A SBT_TAPE 04-MAR-10 1 1 NO
990 B 1 A SBT_TAPE 04-MAR-10 1 1 NO
991 B 1 A SBT_TAPE 04-MAR-10 1 1 NO
992 B A A SBT_TAPE 04-MAR-10 1 1 NO
993 B F A SBT_TAPE 04-MAR-10 1 1 NO
996 B A A SBT_TAPE 04-MAR-10 1 1 NO
997 B F A SBT_TAPE 04-MAR-10 1 1 NO
998 B A A SBT_TAPE 04-MAR-10 1 1 NO
999 B F A SBT_TAPE 04-MAR-10 1 1 NO
1000 B A A SBT_TAPE 04-MAR-10 1 1 NO
1001 B F A SBT_TAPE 04-MAR-10 1 1 NO
1002 B A A SBT_TAPE 05-MAR-10 1 1 NO
1003 B 1 A SBT_TAPE 05-MAR-10 1 1 NO
1004 B 1 A SBT_TAPE 05-MAR-10 1 1 NO
1005 B A A SBT_TAPE 05-MAR-10 1 1 NO
1006 B F A SBT_TAPE 05-MAR-10 1 1 NO
1009 B A A SBT_TAPE 05-MAR-10 1 1 NO
1010 B F A SBT_TAPE 05-MAR-10 1 1 NO
1011 B A A SBT_TAPE 05-MAR-10 1 1 NO
1012 B F A SBT_TAPE 05-MAR-10 1 1 NO
1013 B A A SBT_TAPE 05-MAR-10 1 1 NO
1014 B F A SBT_TAPE 05-MAR-10 1 1 NO
1015 B A A SBT_TAPE 06-MAR-10 1 1 NO
1016 B 1 A SBT_TAPE 06-MAR-10 1 1 NO
1017 B 1 A SBT_TAPE 06-MAR-10 1 1 NO
1018 B A A SBT_TAPE 06-MAR-10 1 1 NO
1019 B F A SBT_TAPE 06-MAR-10 1 1 NO
1022 B A A SBT_TAPE 07-MAR-10 1 1 NO
1023 B 0 A SBT_TAPE 07-MAR-10 1 1 NO
1024 B 0 A SBT_TAPE 07-MAR-10 2 1 NO
1025 B A A SBT_TAPE 07-MAR-10 1 1 NO
1026 B F A SBT_TAPE 07-MAR-10 1 1 NO
1029 B A A SBT_TAPE 07-MAR-10 1 1 NO
1030 B F A SBT_TAPE 07-MAR-10 1 1 NO
1031 B A A SBT_TAPE 07-MAR-10 1 1 NO
1032 B F A SBT_TAPE 07-MAR-10 1 1 NO
1033 B A A SBT_TAPE 07-MAR-10 1 1 NO
1034 B F A SBT_TAPE 07-MAR-10 1 1 NO
1035 B A A SBT_TAPE 08-MAR-10 1 1 NO
1036 B 1 A SBT_TAPE 08-MAR-10 1 1 NO
1037 B 1 A SBT_TAPE 08-MAR-10 1 1 NO
1038 B A A SBT_TAPE 08-MAR-10 1 1 NO
1039 B F A SBT_TAPE 08-MAR-10 1 1 NO
1042 B A A SBT_TAPE 08-MAR-10 1 1 NO
1043 B F A SBT_TAPE 08-MAR-10 1 1 NO
1044 B A A SBT_TAPE 08-MAR-10 1 1 NO
1045 B 1 A SBT_TAPE 08-MAR-10 1 1 NO
1046 B 1 A SBT_TAPE 08-MAR-10 1 1 NO
1047 B A A SBT_TAPE 08-MAR-10 1 1 NO
1048 B F A SBT_TAPE 08-MAR-10 1 1 NO
1054 B A A SBT_TAPE 09-MAR-10 1 1 NO
1055 B A A SBT_TAPE 09-MAR-10 1 1 NO
1056 B 1 A SBT_TAPE 09-MAR-10 1 1 NO
1057 B 1 A SBT_TAPE 09-MAR-10 1 1 NO
1058 B A A SBT_TAPE 09-MAR-10 1 1 NO
1059 B F A SBT_TAPE 09-MAR-10 1 1 NO
1065 B A A SBT_TAPE 10-MAR-10 1 1 NO
1066 B 1 A SBT_TAPE 10-MAR-10 1 1 NO
1067 B 1 A SBT_TAPE 10-MAR-10 1 1 NO
1068 B A A SBT_TAPE 10-MAR-10 1 1 NO
1069 B F A SBT_TAPE 10-MAR-10 1 1 NO
1075 B A A SBT_TAPE 11-MAR-10 1 1 NO
1076 B 1 A SBT_TAPE 11-MAR-10 1 1 NO
1077 B 1 A SBT_TAPE 11-MAR-10 1 1 NO
1078 B A A SBT_TAPE 11-MAR-10 1 1 NO
1079 B F A SBT_TAPE 11-MAR-10 1 1 NO
1085 B A A SBT_TAPE 12-MAR-10 1 1 NO
1086 B 1 A SBT_TAPE 12-MAR-10 1 1 NO
1087 B 1 A SBT_TAPE 12-MAR-10 1 1 NO
1088 B A A SBT_TAPE 12-MAR-10 1 1 NO
1089 B F A SBT_TAPE 12-MAR-10 1 1 NO
1094 B A A SBT_TAPE 13-MAR-10 1 1 NO
1095 B A A SBT_TAPE 13-MAR-10 1 1 NO
1096 B 1 A SBT_TAPE 13-MAR-10 1 1 NO
1097 B 1 A SBT_TAPE 13-MAR-10 1 1 NO
1098 B A A SBT_TAPE 13-MAR-10 1 1 NO
1099 B F A SBT_TAPE 13-MAR-10 1 1 NO
1105 B A A SBT_TAPE 14-MAR-10 1 1 NO
1106 B 0 A SBT_TAPE 14-MAR-10 1 1 NO
1107 B 0 A SBT_TAPE 14-MAR-10 2 1 NO
1108 B A A SBT_TAPE 14-MAR-10 1 1 NO
1109 B F A SBT_TAPE 14-MAR-10 1 1 NO
1115 B A A SBT_TAPE 15-MAR-10 1 1 NO
1116 B 1 A SBT_TAPE 15-MAR-10 1 1 NO
1117 B 1 A SBT_TAPE 15-MAR-10 1 1 NO
1118 B A A SBT_TAPE 15-MAR-10 1 1 NO
1119 B F A SBT_TAPE 15-MAR-10 1 1 NO
1125 B A A SBT_TAPE 16-MAR-10 1 1 NO
1126 B A A SBT_TAPE 16-MAR-10 1 1 NO
1127 B 1 A SBT_TAPE 16-MAR-10 1 1 NO
1128 B 1 A SBT_TAPE 16-MAR-10 1 1 NO
1129 B A A SBT_TAPE 16-MAR-10 1 1 NO
1130 B F A SBT_TAPE 16-MAR-10 1 1 NO
1136 B A A SBT_TAPE 17-MAR-10 1 1 NO
1137 B A A SBT_TAPE 17-MAR-10 1 1 NO
1138 B 1 A SBT_TAPE 17-MAR-10 1 1 NO
1139 B 1 A SBT_TAPE 17-MAR-10 1 1 NO
1140 B A A SBT_TAPE 17-MAR-10 1 1 NO
1141 B F A SBT_TAPE 17-MAR-10 1 1 NO
1147 B A A SBT_TAPE 18-MAR-10 1 1 NO
1148 B A A SBT_TAPE 18-MAR-10 1 1 NO
1149 B 1 A SBT_TAPE 18-MAR-10 1 1 NO
1150 B 1 A SBT_TAPE 18-MAR-10 1 1 NO
1151 B A A SBT_TAPE 18-MAR-10 1 1 NO
1152 B F A SBT_TAPE 18-MAR-10 1 1 NO
1158 B A A SBT_TAPE 19-MAR-10 1 1 NO
1159 B A A SBT_TAPE 19-MAR-10 1 1 NO
1160 B 1 A SBT_TAPE 19-MAR-10 1 1 NO
1161 B 1 A SBT_TAPE 19-MAR-10 1 1 NO
1162 B A A SBT_TAPE 19-MAR-10 1 1 NO
1163 B F A SBT_TAPE 19-MAR-10 1 1 NO
1169 B A A SBT_TAPE 20-MAR-10 1 1 NO
1170 B 1 A SBT_TAPE 20-MAR-10 1 1 NO
1171 B 1 A SBT_TAPE 20-MAR-10 1 1 NO
1172 B A A SBT_TAPE 20-MAR-10 1 1 NO
1173 B F A SBT_TAPE 20-MAR-10 1 1 NO
1179 B A A SBT_TAPE 21-MAR-10 1 1 NO
1180 B 0 A SBT_TAPE 21-MAR-10 1 1 NO
1181 B 0 A SBT_TAPE 21-MAR-10 2 1 NO
1182 B A A SBT_TAPE 21-MAR-10 1 1 NO
1183 B F A SBT_TAPE 21-MAR-10 1 1 NO
1189 B A A SBT_TAPE 22-MAR-10 1 1 NO
1190 B 1 A SBT_TAPE 22-MAR-10 1 1 NO
1191 B 1 A SBT_TAPE 22-MAR-10 1 1 NO
1192 B A A SBT_TAPE 22-MAR-10 1 1 NO
1193 B F A SBT_TAPE 22-MAR-10 1 1 NO
RMAN> report obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 30 days
Report of obsolete backups and copies
Type Key Completion Time Filename/Handle
Control File Copy 47 20-FEB-10 /dbbackup/cisconf/control.bak.20100220
Backup Set 804 20-FEB-10
Backup Piece 551 20-FEB-10 c-3316101807-20100220-01
Edited by: user12019850 on 22-Mar-2010 11:03 AM
Maybe you are looking for
-
Audigy 4 Pro...Line-in to Line-o
Hello all, new here I've managed to unite my PC and hifi together in one room and I've stumbled upon a problem, namely a lack of suitable outputs. I thought the line-in 3 phono was a line out. The only solution I've found is to connect a phono from m
-
Verifying Responsibility in a When-New-From-Instance Trigger
Hi All, I want to restrict the accessability of a form to different responsibilities using resp_id, how do I do that? Is there any other method of by which I can restrict the accessibilty to different responsibilities?can we use system variables? Any
-
Hey all, thanks in advance for any info you can provide. All the RoboHelp references below relate to us using the respective version of RoboHelp HTML, and on my XP SP3 pc. For various reasons, we tried migrating our data from RoboHelp v7 directly to
-
I cannot get any document to print in Adobe, but all other programs on my computer print fine. Should I reload? I have the Acrobat Pro one year subscription. If I reload, will it count that I have downloaded twice and not let me reload?
-
I would like to append new binary values to the existing binary file. Write File.vi looks like a good candidate for this, and it has two inputs, pos. mode and pos. offset which looks like something useful for my task. Unfortunately whatever I put int