Delete obsolete

please tell me about this error
when i delete obsolete i have this error
1.error allocating device, device type: SBT_TAPE, device name:
2.Failed to load Media Management Library
altho my retention policy is 1 its cant delete this obsolete
thank you

Hi,
Change Your Device Type.
C:\>RMAN TARGET=SYS
PASSWORD:
RMAN>CONFIGURE DEFAULT DEVICE TYPE TO DISK;Regards
Taj

Similar Messages

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

RMAN Delete Obsolete job fails due to Error Allocating Device

Experts, I need help, please.
This is 10.2.0.1 on Windows
RMAN> DELETE NOPROMPT OBSOLETE;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 3 days
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=130 devtype=DISK
released channel: ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of delete command at 05/15/2012 14:10:17
ORA-19554: error allocating device, device type: SBT_TAPE, device name:
ORA-27211: Failed to load Media Management Library
I ran RMAN> configure device type 'SBT_TAPE' clear;
but I still get the same error.
I backup to Disk, not tape
Notice the reference to SBT_TAPE:
RMAN configuration parameters are:
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO BACKUPSET PARALLELISM 1;
CONFIGURE DEVICE TYPE SBT_TAPE PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
What do I need to do to be able to run DELETE OBSOLETE; ?
Thanks, John

as anand mention ,you've to reset this parameter to default value.
and clear cmd with configure will remove it from configuration parameter
see below
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO '%F'; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
*CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 1 BACKUP TYPE TO BACKUPSET;*
CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
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; # 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 ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/10/db/dbs/snapcf_GG1.f'; # default
RMAN> delete obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of delete command at 05/16/2012 12:04:34
ORA-19554: error allocating device, device type: SBT_TAPE, device name:
ORA-27211: Failed to load Media Management Library
Additional information: 2
RMAN> CONFIGURE DEVICE TYPE 'SBT_TAPE' clear;
old RMAN configuration parameters:
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 1 BACKUP TYPE TO BACKUPSET;
RMAN configuration parameters are successfully reset to default value
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
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 ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/10/db/dbs/snapcf_GG1.f'; # default
RMAN> delete obsolete;
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=1591 instance=GG1 devtype=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: sid=1627 instance=GG1 devtype=DISK
no obsolete backups found

How do I delete obsolete email addresses from the "to:" line. All of the addresses a person has had show up. I only want the correct one to be displayed.

I would like to delete obsolete email addresses from appearing in the Address line of my outgoing email. My address book only has the current email address of each person. Why does the old addresses appear?

Check Window > Previous Recipients for that user name and see if the old addresses are there. If they are delete them.
Allan

Scheduled DELETE OBSOLETE fails

I have a script which runs nightly to DELETE OBSOLETE. It fails with an error.
When I enter the commands into the RMAN console all works fine.
Here are the commands......
ALLOCATE CHANNEL FOR MAINTENANCE DEVICE TYPE DISK FORMAT 'E:\temp\work';
DELETE NOPROMPT OBSOLETE DEVICE TYPE DISK;
If i put this into a script it complians about the "FOR" in the ALLOCATE statement.
How can I get the DELETE to work properly in the scheduled script? I am running Recovery Manager: Release 9.2.0.3.0 - Production.

The error message I get is shown here...
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 276 17/OCT/05
Backup Piece 274 17/OCT/05 D:\ORACLE\ORA92\HPCS\BACKUPS\HPCS_DF571960814_S324_S1
Backup Set 277 17/OCT/05
Backup Piece 275 17/OCT/05 D:\ORACLE\ORA92\HPCS\BACKUPS\HPCS_DF571961352_S325_S1
Backup Set 278 17/OCT/05
Backup Piece 276 17/OCT/05 D:\ORACLE\ORA92\HPCS\BACKUPS\HPCS_CFC-2091383776-20051017-00
Backup Set 279 18/OCT/05
Backup Piece 277 18/OCT/05 D:\ORACLE\ORA92\HPCS\BACKUPS\HPCS_DF572047211_S327_S1
Backup Set 280 18/OCT/05
Backup Piece 278 18/OCT/05 D:\ORACLE\ORA92\HPCS\BACKUPS\HPCS_DF572047216_S328_S1
Backup Set 281 18/OCT/05
Backup Piece 279 18/OCT/05 D:\ORACLE\ORA92\HPCS\BACKUPS\HPCS_DF572047753_S329_S1
Backup Set 282 18/OCT/05
Backup Piece 280 18/OCT/05 D:\ORACLE\ORA92\HPCS\BACKUPS\HPCS_CFC-2091383776-20051018-00
Backup Set 283 19/OCT/05
Backup Piece 281 19/OCT/05 D:\ORACLE\ORA92\HPCS\BACKUPS\HPCS_DF572084334_S331_S1
Backup Set 284 19/OCT/05
Backup Piece 282 19/OCT/05 D:\ORACLE\ORA92\HPCS\BACKUPS\HPCS_DF572084336_S332_S1
Backup Set 285 19/OCT/05
Backup Piece 283 19/OCT/05 D:\ORACLE\ORA92\HPCS\BACKUPS\HPCS_DF572084872_S333_S1
Backup Set 286 19/OCT/05
Backup Piece 284 19/OCT/05 D:\ORACLE\ORA92\HPCS\BACKUPS\HPCS_CFC-2091383776-20051019-00
Backup Set 287 19/OCT/05
Backup Piece 285 19/OCT/05 D:\ORACLE\ORA92\HPCS\BACKUPS\HPCS_DF572133611_S335_S1
Archive Log 269 19/OCT/05 D:\ORACLE\ORA92\HPCS\ARCHIVELOGS\ARC00323.001
Archive Log 268 19/OCT/05 D:\ORACLE\ORA92\HPCS\ARCHIVELOGS\ARC00322.001
Archive Log 267 19/OCT/05 D:\ORACLE\ORA92\HPCS\ARCHIVELOGS\ARC00321.001
Archive Log 266 18/OCT/05 D:\ORACLE\ORA92\HPCS\ARCHIVELOGS\ARC00320.001
Archive Log 265 18/OCT/05 D:\ORACLE\ORA92\HPCS\ARCHIVELOGS\ARC00319.001
Archive Log 264 17/OCT/05 D:\ORACLE\ORA92\HPCS\ARCHIVELOGS\ARC00318.001
allocated channel: d01
channel d01: sid=36 devtype=DISK
released channel: d01
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of allocate command at 10/21/2005 16:00:14
RMAN-06181: multiple channels require Enterprise Edition
Recovery Manager complete.
If I run this from the DOS prompt it all works.

Delete obsolete fails

Hi
I have an (upgraded) database v. 10.1.0.4.0. When executing 'delete obsolete' from RMAN I get the following errors:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of delete command at 08/30/2005 16:59:54
RMAN-06004: ORACLE error from recovery catalog database: ORA-06550: line 1, column 274:
PLS-00306: wrong number or types of arguments in call to 'LISTBACKUP'
ORA-06550: line 1, column 267:
PL/SQL: Statement ignored
According to Metalink document 311798.1 this is because the database was upgraded to 10.1.0.4 and the DBMS_RCVMAN package was not.
The solution is to run the following scripts ( as sysdba):
$ORACLE_HOME\rdbms\admin\dbmsrman.sql
$ORACLE_HOME\rdbms\admin\prvtrmns.plb
which I did .
But I still get the same the same error when doing 'delete obsolete' !
Any clues ?
KR
Rolf

Hi oradba
Yes, the error stack refers to the catalog.
Funny thing is that I have several other databases upgraded to 10.1.0.4, and none of those gives an error in 'delete obsolete' ! These db's use the same catalog.(10.1.0.3)
To my knowledge, these databases were upgraded in a standard fashion, using standard upgrade scripts.
May be I should do what you did and upgrade the catalog as well.
By the way; is it possible to identify the version of the DBMS_RCVMAN package ?
Thanks
rolf

Issue during delete obsolete

Hi,
I have 10.2.0.4 database on AIX and taking the backup using RMAN. While running Delete obsolete command, it is giving below message at last:
DELETE OBSOLETE;
Deleted 198 objects
For record type DELETED OBJECT recids from 522 to 523 are re-used before resync
released channel: t1
Recovery Manager complete.
Could you please let me know that what is the issue?
Thx

I think you left out the error code message.
Did you get RMAN-06610 ?!
if yes
RMAN-06610: For record type string recids from number to number are re-used before resync
Cause: This messages is issued when the control file records were re-used before resyncing to catalog database.
Action: Increase control_file_keep_record_time setting or issue BACKUP command that it will generate fewer control file records, e.g., backup few tablespaces instead of the complete database in one BACKUP command.BTW error message info comes from here
http://download.oracle.com/docs/cd/B19306_01/server.102/b14219/rmanus.htm
Edited by: Kecskemethy on Sep 12, 2011 12:43 AM
added link

Delete obsolete combinations in /SAPAPO/MC62 - how to use?

Hello SAP-experts,
We are using SAP APO Demand planning SAP SCM 7.0 with SP 15 for most of components.
I have some questions related to the button "delete obsolete combinations" in TA /SAPAPO/MC62. We want to use option "list combinations without planning data" to reduce CVC's quantity. What I have read it checks for CVC's without any entries at key figures. It sounds useful, but it doesn't seem to work in our company for some reason.
1. Where exactly does system check if there are key figures for the selected CVC's? In livecache directly? Or in an internal generated info cube for the planning area? Is it possible to view these key figures (on same base as done from system with option "list combinations without planning data") before using the deletion? Is there a report / table to do so? What's the best practise for this check (maybe on daily base)?
2. I have (some) CVC's without any key figure filled (for my opinion...). At the moment I check this with an info cube used for daily backup (means I see always the data from last night and I know that noone changed data because of blocked planning access). But it isn't found with "list combinations without planning data". When displaying the data in this backup-cube all key figures are shown as zero (the one which are shown for deletion and in same way the cvc's which are not shown). In the key figure settings "differentiation between zero and initial value" is not marked... I think this is correct, but maybe I have a misunderstanding here... any ideas about this setting? I don't believe this setting is wrong, because it shows me some CVC's to be deleted, but some of them are not shown (the setting should work for all cvc's in same way...?).
All ideas are most welcome, thank you all in advance!
Best regards
Harald Leissl

Hello Ali,
thank you for your reply!
My plan was to use standard tool, because it's available since some releases. I don't prefer to implement own programming instead of using an existing tool (talking about the built ABAP tool, the idea with alert makro sounds good).
Is the standard tool effective??? Good question. We talk about 2 steps.
If the mentioned function "delete obsolete" would work like designed (maybe it does, but I don't understand how...) it would do 2 steps combined:
- find out obsolete CVC's (your alert makro)
- delete obsolete CVC's (your ABAP tool)
Combining these 2 steps would be really effective, but it doesn't work for some reason. My estimation is that standard is not effective, because complete process of deletions of CVC's is very slow and causes sometimes performance trouble.
But this is the reason why I search for a standard tool to run periodically (maybe each week) for a check of "old" CVC's. I think our problem of slow running deletions is caused by too many CVC's in an planning object structure (together with the fact that our CVC's have a lot of key figures / characteristics).
To be honest my main task is to find the best possibility to delete a list of completely different CVC's (no unique selection possible). I tested a lot of things found in SCN (realignment, background deletion,...), but all the solutions have s lack in performance (at least in our system...).
Regards
Harald

Delete obsolete not deleting archives

Hi,
Platform : Windows 2003
Oracle : 10.2.0.4.0
We've following policy for RMAN :
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
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 'G:\Hot_BKP\controlfile\%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 MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'C:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\SNCFPROJECT.ORA'; # default
There is cascaded standby setup on this database. Now even if the archives are applied on the standby database, the "delete obsolete" is deleting obsolete backups but not the archives.
Regards,
S.K.

Hi Khurram,
The "_log_deletion_policy" parameter is set to ALL. So keeping archive log destination 'mandatory' is not necessary.
Reference: [728053.1|https://metalink2.oracle.com/metalink/plsql/f?p=130:14:1194704985657950048::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,728053.1,1,1,1,helvetica]
Regards,
S.K.

"Delete obsolete" problem

Dear Friend,
In our production server , we use IBM - Tivoli Storage Manager - Software for our RMAN backup purpose . The backup data backup piece are stored on a Storage Library . It works fine but the problem is when I am going to delete "obsolete backup" then it shows the following error :
RMAN> Delete pbsolete;
Backup Set 870 06-OCT-08
Backup Piece 870 06-OCT-08 c-1077970889-20081006-00
Backup Set 871 07-OCT-08
Backup Piece 871 07-OCT-08 rfjsj6d8_1_1
Backup Set 872 07-OCT-08
Backup Piece 872 07-OCT-08 rgjsj6n1_1_1
Backup Set 873 07-OCT-08
Backup Piece 873 07-OCT-08 c-1077970889-20081007-00
Backup Set 875 08-OCT-08
Backup Piece 875 08-OCT-08 rjjslh0e_1_1
Backup Set 876 08-OCT-08
Backup Piece 876 08-OCT-08 c-1077970889-20081008-00
Backup Set 878 11-OCT-08
Backup Piece 878 11-OCT-08 rmjsstps_1_1
Backup Set 879 11-OCT-08
Backup Piece 879 11-OCT-08 c-1077970889-20081011-00
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of delete command at 10/14/2008 19:14:20
RMAN-06091: no channel allocated for maintenance (of an appropriate type)
Anybody has idea about the above error ?
Plz inform .. ..

Hi,
Always you need to check the Issue of RMAN from last
Check link
Re: RMAN clean-up
Channel allocation is required..
- Pavan Kumar N

Deleting Obsolete Archiveslogs

Hi all,
I'm trying to delete my obsolete archiveslog but if i issue the command 'delete obsolete' it gives me the below error
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of delete command at 12/14/2009 09:31:17
RMAN-06091: no channel allocated for maintenance (of an appropriate type)
RMAN>
Kindly assist pls.

hi user;
Please follow below and see its helpful for your issue:
Encountered RMAN-03002 and RMAN-06091 when Deleting Obsolete Backups [ID 567555.1]
Also check:
Re: RMAN-06091 error
RMAN backups dissapeared...
Re: HOW TO DELETE OBSOLETE BACKUP ON TAPE WHEN USING FLASHBACK? RMAN-06091
Regard
Helios

Delete obsolete does not delete all backupset

Dear friends,
I take backup with the "backup database plus archivelog". For example, it took 3 backup, 3 archivelog and 1 control files. I took a backup 5 minutes later to try "delete obsolete" command. It also took same number of files.
When i typed "delete obsolete" command, it only removes 1 backup and 1 control file from old backupset. 2 backup and 3 archivelog files are still there.
What am i wrong? OR How can i delete all old backupset files(backups,copies,controlfiles,...)?
You can find the details below,
Thanks in advance and Best Regards;
Onur
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/oranew/arch/cf_%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE CHANNEL 1 DEVICE TYPE DISK FORMAT '/oranew/arch/%U.bak';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/oranew/9i/dbs/snapcf_....f'; # default
CONFIGURE EXCLUDE FOR TABLESPACE 'CWMLITE';
CONFIGURE EXCLUDE FOR TABLESPACE 'EXAMPLE';
List of Backup Sets
===================
BS Key Device Type Elapsed Time Completion Time
812 DISK 00:00:01 11-JUL-06
BP Key: 813 Status: AVAILABLE Tag:
Piece Name: /oranew/arch/1hhntfj9_1_1.bak
List of Archived Logs in backup set 812
Thrd Seq Low SCN Low Time Next SCN Next Time
1 270 1147860 11-JUL-06 1147877 11-JUL-06
BS Key Type LV Size Device Type Elapsed Time Completion Time
816 Full 313M DISK 00:01:50 11-JUL-06
BP Key: 817 Status: AVAILABLE Tag:
Piece Name: /oranew/arch/1ihntfjd_1_1.bak
List of Datafiles in backup set 816
File LV Type Ckp SCN Ckp Time Name
1 Full 1147880 11-JUL-06 /oranew/oradb/oradata/.../system01.dbf
2 Full 1147880 11-JUL-06 /oranew/oradb/oradata/.../undotbs01.dbf
4 Full 1147880 11-JUL-06 /oranew/oradb/oradata/.../drsys01.dbf
6 Full 1147880 11-JUL-06 /oranew/oradb/oradata/.../indx01.dbf
7 Full 1147880 11-JUL-06 /oranew/oradb/oradata/.../tools01.dbf
8 Full 1147880 11-JUL-06 /oranew/oradb/oradata/.../users01.dbf
BS Key Device Type Elapsed Time Completion Time
828 DISK 00:00:01 11-JUL-06
BP Key: 829 Status: AVAILABLE Tag:
Piece Name: /oranew/arch/1jhntfn4_1_1.bak
List of Archived Logs in backup set 828
Thrd Seq Low SCN Low Time Next SCN Next Time
1 271 1147877 11-JUL-06 1147884 11-JUL-06
BS Key Type LV Size Device Type Elapsed Time Completion Time
832 Full 1M DISK 00:00:01 11-JUL-06
BP Key: 833 Status: AVAILABLE Tag:
Piece Name: /oranew/arch/cf_c-4041210959-20060711-00
Controlfile Included: Ckp SCN: 1147886 Ckp time: 11-JUL-06
BS Key Device Type Elapsed Time Completion Time
839 DISK 00:00:01 11-JUL-06
BP Key: 840 Status: AVAILABLE Tag:
Piece Name: /oranew/arch/1lhntfod_1_1.bak
List of Archived Logs in backup set 839
Thrd Seq Low SCN Low Time Next SCN Next Time
1 270 1147860 11-JUL-06 1147877 11-JUL-06
1 271 1147877 11-JUL-06 1147884 11-JUL-06
1 272 1147884 11-JUL-06 1147890 11-JUL-06
BS Key Type LV Size Device Type Elapsed Time Completion Time
845 Full 313M DISK 00:01:51 11-JUL-06
BP Key: 846 Status: AVAILABLE Tag:
Piece Name: /oranew/arch/1mhntfoh_1_1.bak
List of Datafiles in backup set 845
File LV Type Ckp SCN Ckp Time Name
1 Full 1147893 11-JUL-06 /oranew/oradb/oradata/.../system01.dbf
2 Full 1147893 11-JUL-06 /oranew/oradb/oradata/.../undotbs01.dbf
4 Full 1147893 11-JUL-06 /oranew/oradb/oradata/.../drsys01.dbf
6 Full 1147893 11-JUL-06 /oranew/oradb/oradata/.../indx01.dbf
7 Full 1147893 11-JUL-06 /oranew/oradb/oradata/.../tools01.dbf
8 Full 1147893 11-JUL-06 /oranew/oradb/oradata/.../users01.dbf
BS Key Device Type Elapsed Time Completion Time
857 DISK 00:00:01 11-JUL-06
BP Key: 858 Status: AVAILABLE Tag:
Piece Name: /oranew/arch/1nhntfs8_1_1.bak
List of Archived Logs in backup set 857
Thrd Seq Low SCN Low Time Next SCN Next Time
1 273 1147890 11-JUL-06 1147898 11-JUL-06
BS Key Type LV Size Device Type Elapsed Time Completion Time
861 Full 1M DISK 00:00:01 11-JUL-06
BP Key: 862 Status: AVAILABLE Tag:
Piece Name: /oranew/arch/cf_c-4041210959-20060711-01
Controlfile Included: Ckp SCN: 1147900 Ckp time: 11-JUL-06
RMAN> delete obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
using channel ORA_DISK_1
Deleting the following obsolete backups and copies:
Type Key Completion Time Filename/Handle
Backup Set 816 11-JUL-06
Backup Piece 817 11-JUL-06 /oranew/arch/1ihntfjd_1_1.bak
Backup Set 832 11-JUL-06
Backup Piece 833 11-JUL-06 /oranew/arch/cf_c-4041210959-20060711-00
Do you really want to delete the above objects (enter YES or NO)?

Dear Kuljeet,
I am new in rman. As i understood from your reply that rman only deletes the backup piece which includes all dbfs and its related control file. These two files are deleted from catalog and also from filesystem.
But other archievelogs (from first backup) joins to the second backup,as you said. This goes on like that in every backup if we take backup with "plus archivelog" parameter. Am i right?
And they won't be deleted from the file system.
I think the answers to the following questions will solve my confusion.
1. Should not we delete (from catalog and fs, for ex. "delete archivelog ...") the previous archivelogs, even the latest backup set is enough to recover database?
2. Let's say, we moved all these files (old archivelogs and latest dbf backups) to tape. I don't think so but should we keep all the old archivelogs to recover db even the ones from the latest backup is enough?
3. Is "plus archivelog" parameter very important for a backup?
I was confused about the principles of "delete obsolete" when the backup was taken with "plus archivelog" parameter. If you can explain it shortly, i will be very pleased. Why it did not delete all pieces of the previous backup set (from catalog and fs.), while the latest backup set is enough to recover db? I could not understand this.
Thanks in advance and best regards,
Onur

Can't delete obsolete and expired backups.

Every Sundays I create 0 level backup.
Every Thuesdays I create 1 level comulative backup.
Every other days I create 1 level incremental backup.
Sometimes I need a free space for new backups and I try clean old backups.
As I can understand, rman remove backups from 'list backup', but doens't delete physically from disk storage.
SQL> select banner from v$version;
BANNER
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
PL/SQL Release 11.2.0.2.0 - Production
CORE 11.2.0.2.0 Production
TNS for Solaris: Version 11.2.0.2.0 - Production
NLSRTL Version 11.2.0.2.0 - Production
0 level backup
CONNECT TARGET / ;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/u06/backup/df_%d_%s_%U';
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u06/backup/cf_%F';
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 3 DAYS;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u06/backup/snapcf.f';
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE MAXSETSIZE TO 20G;
BACKUP CURRENT CONTROLFILE;
BACKUP INCREMENTAL LEVEL 0 DATABASE FILESPERSET 100 ;
BACKUP ARCHIVELOG ALL DELETE ALL INPUT;
RESTORE VALIDATE DATABASE;
RESTORE VALIDATE CONTROLFILE TO '$ORACLE_BASE/admin/rman_scripts/cf_tmp.ctl';
RESTORE VALIDATE SPFILE TO '$ORACLE_BASE/admin/rman_scripts/spf_tmp.ora';
RESTORE VALIDATE ARCHIVELOG FROM TIME 'SYSDATE-4';
REPORT NEED BACKUP;
DELETE OBSOLETE;
LIST BACKUP;
LIST BACKUP SUMMARY;
1 level comulative backup
CONNECT TARGET / ;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/u06/backup/df_%d_%s_%U';
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u06/backup/cf_%F';
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 3 DAYS;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u06/backup/snapcf.f';
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE MAXSETSIZE TO 20G;
BACKUP CURRENT CONTROLFILE;
BACKUP INCREMENTAL LEVEL 1 CUMULATIVE DATABASE FILESPERSET 100;
BACKUP ARCHIVELOG ALL DELETE ALL INPUT;
RESTORE VALIDATE DATABASE;
RESTORE VALIDATE CONTROLFILE TO '$ORACLE_BASE/admin/rman_scripts/cf_tmp.ctl';
RESTORE VALIDATE SPFILE TO '$ORACLE_BASE/admin/rman_scripts/spf_tmp.ora';
RESTORE VALIDATE ARCHIVELOG FROM TIME 'SYSDATE-4';
REPORT NEED BACKUP;
DELETE OBSOLETE;
LIST BACKUP;
LIST BACKUP SUMMARY;
1 level incremental backup
CONNECT TARGET / ;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/u06/backup/df_%d_%s_%U';
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u06/backup/cf_%F';
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 3 DAYS;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u06/backup/snapcf.f';
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE MAXSETSIZE TO 20G;
BACKUP CURRENT CONTROLFILE;
BACKUP INCREMENTAL LEVEL 1 DATABASE FILESPERSET 100;
BACKUP ARCHIVELOG ALL DELETE ALL INPUT;
RESTORE VALIDATE DATABASE;
RESTORE VALIDATE CONTROLFILE TO '$ORACLE_BASE/admin/rman_scripts/cf_tmp.ctl';
RESTORE VALIDATE SPFILE TO '$ORACLE_BASE/admin/rman_scripts/spf_tmp.ora';
RESTORE VALIDATE ARCHIVELOG FROM TIME 'SYSDATE-4';
REPORT NEED BACKUP;
DELETE OBSOLETE;
LIST BACKUP;
LIST BACKUP SUMMARY;
Try delete old backups:
CONNECT TARGET / ;
RMAN> CROSSCHECK BACKUP;
Crosschecked 173 objects
RMAN> DELETE EXPIRED BACKUP;
using channel ORA_DISK_1
specification does not match any backup in the repository
RMAN> DELETE OBSOLETE;
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
no obsolete backups found
RMAN>
Edited by: 848540 on 31.10.2011 23:15

I try to ask one more time.
I make all backups in the folder \u06\backup.
I make full backups every week.
After command "crosscheck backup" all backups older 2 weeks must be mark as "OBSOLETE". This operation works correctly, becouse in "list backup" i look all backups for last two weeks and no older (for today they all made earlyer then 06/11/2011)!
After crosscheck operation i try to delete old backups from HDD.
RMAN> delete expired backup;
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=2 device type=DISK
specification does not match any backup in the repository
RMAN> delete obsolete;
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
no obsolete backups found
But after this operation I look in my backup folder files since 02/10/2011. How to sync backups (delete obsolete backups from HDD) in rman list (command 'list backup') and in operation system list (command 'ls' in sun10)?
Edited by: 848540 on 14.11.2011 0:32

Crosscheck backup and delete obsolete;

Hi,
on 10g R2 on a Win 2003. Connected to catalog and Target database I issue :
RMAN>crosscheck backup
RMAN>delete obsolete;
FILE 1
FILE 2
Do you want to delet the above file ? Y/N :YES
Then again :
RMAN>crosscheck backup
RMAN>delete obsolete;
FILE 1
FILE 2
Do you want to delet the above file ? Y/N
I can not understand. If the first time I answered YES and the obsolete files where deleted why they appear again and again ?
Can any one be kind to explain me ?
Thank you.

'crosscheck' has nothing to do with obsolete backups, this command checks for backups,which are still recorded in the controlfile/recovery catalog,but don't exist physically on disk/tape. The correct command after a 'crosscheck' is 'delete expired', 'obsolete' are backups no longer needed due to the defined retention policy.
I guess your backups are both , obsolete and expired, but 'delete obsolete' does not work, because these backups were removed outside RMAN. It could also be a permission problem, RMAN is not allowed to remove the backups on OS level. That happens on Windows, when shared drives are used.
Werner

Delete obsolete causing issue with archivelog backups......or is it?

Hi, hoping someone will have the answer for me.
Oracle 10g R2 on Windows 2003 R2 Sever.
The start of my RMAN script runs, i do crosschecks and delete obsolete backups from type disk. My redundancy is set to 1. I then run compressed backups of the datafiles and archivelogs with 2 channels. This leaves me with two days of full backups on disk (i have months worth on netbackup) the only problem is that one of the archivelog channel backups from the previous day is missing when i know it was there before the delete obsolete was run.
here is the script:
run{
CROSSCHECK BACKUP;
CROSSCHECK archivelog all;
CROSSCHECK COPY;
CROSSCHECK backup of database;
CROSSCHECK backup of controlfile;
delete noprompt obsolete device type disk;
run {
allocate channel ch1 type disk format 'Z:\backup\rman\orcl\%d_%T_%U';
allocate channel ch2 type disk format 'Z:\backup\rman\orcl\%d_%T_%U';
backup as COMPRESSED BACKUPSET
     format='Z:\backup\rman\orcl\full_%d_%T_%U'
     tag='full_DBbackup_ris'
     database;
backup as COMPRESSED BACKUPSET
     format='Z:\backup\rman\orcl\arch_%d_%T_%U'
     tag='full_ARCHbackup_ris'
archivelog all not backed up delete all input;
sql "alter database backup controlfile to trace as ''Z:\backup\rman\orcl\controlfile_backup_trace.txt''";
release channel ch1;
release channel ch2;
This is my (simplified) list of backups on disk:
Full_day1_chan1
Full_day1_chan2
Arc_day1_chan1
Arc_day1_chan2
Full_day2_chan1
Full_day2_chan2
Arc_day2_chan1
It looks like channel2, days2, archivelog backup is missing. Is this correct? If not does anyone have an idea how to fix this?
thanks in advance.
Steven.

Hi Steven,
The data backed up by rman is written to backup pieces.
Are you missing pieces containing archive logs?
Could it be there was only 1 arc file available so the second channel could not create any backup piece?
Did you could check the output of the backup in v$rman_output?
Regards,
Tycho

Delete obsolete

Similar Messages

Maybe you are looking for