RMAN fails to delete obsolete backup in OSB

Hi All,
I am trying to delete my obsolete backups through RMAN and I get this error:
ORA-19511: Error received from media manager layer, error text:
sbt__rpc_cat_delete: delete failed for piece 0hmlsu6q_1_2 (Oracle Secure Backup error: user does not have sufficient rights)
I am not clear why Oracle Secure backup throws error that the user does not have sufficient rights./.
Below are the commands that I am using in the script:
3> ALLOCATE CHANNEL TAPE01 DEVICE TYPE SBT_TAPE;
4> CROSSCHECK BACKUP;
5> CROSSCHECK ARCHIVELOG ALL;
6> CROSSCHECK COPY;
7> report obsolete recovery window of 60 days device type
8> report obsolete recovery window of 7 days device type disk
9> delete noprompt obsolete recovery window of 60 days device type SBT_TAPE;
10> delete noprompt obsolete recovery window of 7 days device type DISK;
Any help is appreciated..
Thanks..

In my case, the problem was on OSB user permition.
On user you have to preauth. admin users to the host where database is located.
regards..
Virgilio

Similar Messages

Rman optimization conflicting with obsolete backups?

Hello,
Suppose I have the following configuration.
I have a partitioned table with each (month-)partition on a different tablespace. I need to keep 10yrs of data. Switch a tablespace with e.g. April2008 data to read-only.
Rman set REDUNDANCY 1 and OPTIMIZATION ON.
Now redundancy 1 should keep only 1 backup of each file wouldn't it?
I do a backup database: it backups every file.
I do a backup database again: it backups every file again.
I do a backup database third time: it says "skipping file n allready backed up 2 times".
Now I do a report obsolete: it marks one of the backups op my file with April2008 data as obsolete.
After performing a delete obsolete, it is gone.
Next day I do a backup database: it backups every file again, so I have two!! backups of file n.
I would like to have only 1 and just 1 backup of the file, and it should never be backed up anymore. The redundancy cannot be set to zero.
How to deal with this?

I think we disagree on this. I can make a single-partition rman backup if:
It is on it's own tablespace, on it's own datafile. No problem with that. It is only the redundancy-problem I have.
Even if I configure redundancy to 1, it makes two backups, and one of these is obsolete. This obsolete gets deleted in a 'delete obsolete' action, and a new obsolete will be created with the next backup.
How would you backup the database with 120 partitions as I described above? Each day a full backup??

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

RMAN-06207 when DELETE NOPROMPT OBSOLETE;

Hello all
I want to backup and delete backuped archivelogs on a standby instance using the following script:
RUN
ALLOCATE CHANNEL ch1 DEVICE TYPE sbt PARMS='ENV=......';
BACKUP ARCHIVELOG ALL DELETE INPUT;
DELETE NOPROMPT OBSOLETE;
RELEASE CHANNEL ch1;
When deleting all obsolete backup pieces, I receive the following error:
RMAN-06207: WARNING: 1 objects could not be deleted for SBT_TAPE channel(s) due
RMAN-06208: to mismatched status. Use CROSSCHECK command to fix status
RMAN-06210: List of Mismatched objects
RMAN-06211: ==========================
RMAN-06212: Object Type Filename/Handle
RMAN-06214: Backup Piece c-2414804385-20080820-02
As a workaround, I then manually delete obsolete backup pieces using:
delete force noprompt obsolete device type sbt_tape
What is the cause for rman-06207 ? How can I change my rman script to safely delete backuped archivelogs?
I work with Oracle 10G release 10.2.0.3 both on standby and catalog DB.
Casi

Did you try using the CROSSCHECK command to verify the backup files status?
From your comments, it doesn't seem like you did. CROSSCHECK checks the status of the RMAN backups against the disk/tape and updates the RMAN repository. CROSSCHECK does not remove any files just updates the status. The status options are - expired, available, and unavailable.

When is delete all obsolete backups triggered in Oracle 11g DB

I have a query as to when delete all obsolete backups triggered in Oracle 11g DB. We changed the RMAN retention policy to 10 days from 14 days in our setup. Is it triggered manually by delete all obsolete from Availablity->Manage Current Backups in OEM or is it triggered automatically every time RMAN backup is done?
I hope, my question is clear.
Please revert with the reply to my query.
Regards

975148 wrote:
I have a query as to when delete all obsolete backups triggered in Oracle 11g DB. We changed the RMAN retention policy to 10 days from 14 days in our setup. Is it triggered manually by delete all obsolete from Availablity->Manage Current Backups in OEM or is it triggered automatically every time RMAN backup is done?
I hope, my question is clear.
Please revert with the reply to my query.
Regards
First, I would never manage my backups in OEM. When the crunch comes at 2:00 am, I don't want ever more moving parts to be involved in recovery.
Second, the only thing approaching a "triggering" of deletion of backups is if your backups are in the FRA ... rman will, at the time of making a backup .. attempt to delete obsolete backups if necessary to free up space in the FRA.
Other than that, oboslete backups are only deleted in response to a direct DELETE OBSOLETE command. This command may optionally ( as shown by TigerDBA) include a run-time obsolesence rule, or it may depend on the standing configuration.
Another thing to note is that backups are NOT marked as obsolete. They are EVALUATED for obsolescence in response to a DELETE OBSOLETE or REPORT OBSOLETE command.
And one final thing to not is that all recovery must begin with a full backup. That would be the most recent full (or level 0 incremental) backup prior to the point in time to which you need to recover. That means the most recent full (or level 0 incremental) backup will never be considered obsolete, regardless of how old it is.

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

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 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

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

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.

RMAN Failed Backup.

Hello Folks,
DB 10.2.0.4
OS AIX 5.3
How RMAN handles failed backup. If I have failed backups in between two successful backups, and under my retention policy window. When RMAN is going to obsolete failed backups? After my retention window ?
Thanks for your time.

+5) you issue 'delete obsolete' - again nothing is deleted,the backup from Friday is still needed (although meanwhile 8 days old) ,because the second backup from Tuesday is incomplete.+
I'm definitely not sure of this and already tested it: (oracle 10.2.0.4 - rman - AIX)
If you have a recovery windows of 3 days. If your backups are good or failed, after 3 days they'll be all deleted after these kind of commands:
crosscheck backup of database;
delete expired backup;
If the date is older then the 3 days, even if it will delete all the backup of the database from the catalog, then all will be deleted. Then your job is to not have this kind of things happening. (Rman will not say "Oh there's only one backup avalaible I'll keep it to be safe".)
The difference here is that a failed backup will immediately be marked as "obsolete" even before the 3 days and the normal backups will have the rentention policy of 3 days but not more.
Add to this that the retention is sometime shared with other party like tape manager that can automatically delete the backup on tape after 3 days to clean tapes and free space. (So if Rman was able to "think" and change the rule alone it'll not be good anyway)
If you have a recovery window in term of number of backups then it'll be quite different.
In this case all the failer backup will be immediately marked as "obsolete" and will not be counted in the database backup.
Means that if you have the number of backup to 2, it'll take 2 good backup

RMAN Recovery Window 7 days setting - shows no obsolete backups

Hi All. Quick question about RMAN retention policy....
I have the current backup strategy:
Full backup (0) -> Sunday
Incremental backup (1) -> Monday - Saturday
Archive log backups -> every hour
This is a new database I just started taking backups on last month. (1st full backup was run October 4th)
I currently have not deleted any of them.
The old RMAN RETENTION POLICY was set to REDUNDANCY = 1
REPORT OBSOLETE lists all of them up to the last full which ran this past Sunday (Nov 1st)
I just switched the RMAN RETENTION POLICY to RECOVERY WINDOW of 7 DAYS
REPORT OBSOLETE lists no backups obsolete...
Shouldn't I see all the backups prior to a week ago or does it only take affect for backups run under the new policy?
Any help/replies are apprecitaed.
Thanks

Ran crosscheck with no problems:
Crosschecked 200 objects
But still same results for:
RMAN> report obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 7 days
no obsolete backups found
Am I missing something here? Or like I mentioned is this expected behaviour because all of my other backups were run with REDUNDANCY = 1 retention policy?
Thanks

RMAN not obsoleting backup

Hi,
In my 10gR2 database, level1 backup is taken every nigh except sunday, retention policy is set to redundancy 1.
but rman not considering previous backup as obsolete.
below is level1 backup script.
{color:#0000ff}cp $ORACLE_HOME/dbs/orapworampls /backup/RMANBACKUP/orapworampls_backup
# start the rman backup
# only use the next line if this script needs run via root CRON
#su - $ORACLE_OWNER -c "$ORACLE_HOME/bin/rman 'target /'"<< EOF
$ORACLE_HOME/bin/rman 'target /' catalog rman/rman@rman<< EOF
configure retention policy to redundancy 1;
resync catalog;
configure backup optimization on;
configure controlfile autobackup on;
configure default device type to Disk;
configure device type Disk parallelism 2;
configure channel device type Disk format '/backup/RMANBACKUP/%d_LEVEL1_DATAFILE_%s_%p_%D_%M_%Y.bak';
configure maxsetsize to unlimited;
configure snapshot controlfile name to '/backup/RMANBACKUP/ORAMPLS_SNAPCF.f';
set controlfile autobackup format for device type Disk to '/backup/RMANBACKUP/ORAMPLS_CONTROLFILE_%F';
show all;
run {
allocate channel ch1 type Disk maxpiecesize = 1024M;
allocate channel ch2 type Disk maxpiecesize = 1024M;
backup
format '/backup/RMANBACKUP/ORAMPLS_CONTROLFILE_%u_%p_%c' (current controlfile);
backup
incremental level 1
tag 'ORAMPLS_DATAFILE_LEVEL_1'
format '/backup/RMANBACKUP/%d_LEVEL1_DATAFILE_%s_%p_%D_%M_%Y.bak' (database);
release channel ch1;
release channel ch2;
run {
delete noprompt backup of archivelog all completed before 'sysdate - 1';
run {
allocate channel ch1 type Disk maxpiecesize = 1024M;
allocate channel ch2 type Disk maxpiecesize = 1024M;
backup archivelog all
delete all input
format '/backup/RMANBACKUP/%d_ARCHIVELOG_%s_%p_%D_%M_%Y.bak'
tag 'ORAMPLS_ARCHIVELOG_FULL';
release channel ch1;
release channel ch2;
delete noprompt obsolete;
list backup of database;
quit
{color}{color:#000000}id i manually take backup of any datafile twice, its obsoleting older one.
{color}

Retention policy will not affect incremental level 1 backups directly ,it will become obsoleted when its full backups obsoleted ,backup retention policy directly affect only full,level 0 and controlfile backups,archivlelog as well level 1 backup retention policy will affect indirectly.
For detail read that link i have created some sample cases over here within this threads debate
Re: About RMAN backup !!!!
Khurram

How to delete old backups in RMAN (

Hello,
if I run below rman command lines in 10g and 11g RMAN, it works well, but NOT in RMAN (Release 8.1.7.4.0), so which commandlines I should use to get to the same pursposes in RMAN 8.1.7.4?
run {
ALLOCATE CHANNEL c1 TYPE 'sbt_tape';
ALLOCATE CHANNEL c2 TYPE 'sbt_tape';
ALLOCATE CHANNEL c3 TYPE 'sbt_tape';
ALLOCATE CHANNEL c4 TYPE 'sbt_tape';
ALLOCATE CHANNEL c5 TYPE 'sbt_tape';
ALLOCATE CHANNEL c6 TYPE 'sbt_tape';
ALLOCATE CHANNEL c7 TYPE 'sbt_tape';
ALLOCATE CHANNEL c8 TYPE 'sbt_tape';
CROSSCHECK BACKUP;
delete force noprompt obsolete;
DELETE EXPIRED BACKUP;
RELEASE CHANNEL c1;
RELEASE CHANNEL c2;
RELEASE CHANNEL c3;
RELEASE CHANNEL c4;
RELEASE CHANNEL c5;
RELEASE CHANNEL c6;
RELEASE CHANNEL c7;
RELEASE CHANNEL c8;
thank you

for example like below... thank you
RMAN> CROSSCHECK BACKUP;
RMAN-03022: compiling command: XCHECK
RMAN-03026: error recovery releasing channel resources
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure during compilation of command
RMAN-03013: command type: XCHECK
RMAN-06091: no channel allocated for maintenance (of an appropriate type)
RMAN> ALLOCATE CHANNEL c1 TYPE 'sbt_tape';
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01005: syntax error: found "identifier": expecting one of: "for"
RMAN-01008: the bad identifier was: c1
RMAN-01007: at line 1 column 18 file: standard input

RMAN fails to delete obsolete backup in OSB

Similar Messages

Maybe you are looking for