RMAN Obsolete

Hi Guys,
I'm having 15 days of backup in RMAN Catalog and my initial RMAN config is as per below:
CONFIGURE RETENTION POLICY TO REDUNDANCY 10;
Since I only want to keep the backup for latest 10 days, so I have changed the config to:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 10 DAYS;
But after the change, when I ran report obsolete; , I'm not seeing any obsolete backups. Suppose in this case, I should be able to see the obsolete backups for first 5 days. This cause me unable to delete the obsolete backups and my server is running out of space.
Highly appreciate your input in this matter.
Thanks,
Nesan

From my observation (for RECOVERY WINDOW):
Level 0 backup won't get obsoletes until all the level 1 backups get obsolete.
Wrong perception
Setting RMAN recovery window to 2 days make any backup older than 2 days become obsolete is a myth.
See below the scenario which make you understand what need to consider when you are setting RMAN recovery window.
For Non Incremental Level backup
================================
Assume no backup exist before 13th of Oct
Assume recovery window is 2
POR = Point of recoverability
date          backup type          status               POR (Current date-recovery window)
13-OCT-2009     Full backup          No obsolete found     13-OCT-2009-2 = 11-OCT-2009
15-OCT-2009     Full backup          No obsolete found     15-OCT-2009-2 = 13-OCT-2009
16-OCT-2009     Full backup          No obsolete found     16-OCT-2009-2 = 14-OCT-2009See above table data on 16-OCT-2009 , POR is 14-OCT-2009 and you dont have any backup on 14th of oct within yours backup schedule, in this case 13th Oct backup will enable you POR of 14th Oct , 13th Oct backup will not be marked obsoleted
What would be happen on 17th of october
date          backup type          status               POR (Current date-recovery window=POR)
13-OCT-2009     Full backup          No obsolete found     13-OCT-2009-2 = 11-OCT-2009
15-OCT-2009     Full backup          No obsolete found     15-OCT-2009-2 = 13-OCT-2009
16-OCT-2009     Full backup          No obsolete found     16-OCT-2009-2 = 14-OCT-2009
17-OCT-2009     No   backup          13th Oct Full backup     17-OCT-2009-2 = 15-OCT-2009
                         will be marked
                         obsoletedSee above table data on 17-OCT-2009 , POR is 15-OCT-2009 you have backup on 15th of oct within yours backup schedule, in this case 13th Oct backup will not be needed for the point of recoverability for 15th of Oct ,15th Oct backup already exist for the POR,15th Oct backup will provide you POR and hence 13th Oct backup will be marked obsoleted.
For Incremental Level backup
================================
Assume no backup exist before 13th of Oct
Assume recovery window is 2
POR = Point of recoverability
date          backup type          status               POR (Current date-recovery window)
13-OCT-2009     L0               No obsolete found     13-OCT-2009-2 = 11-OCT-2009
14-OCT-2009     L1               No obsolete found     14-OCT-2009-2 = 12-OCT-2009
15-OCT-2009     L1               No obsolete found     15-OCT-2009-2 = 13-OCT-2009
16-OCT-2009     L1               No obsolete found     16-OCT-2009-2 = 14-OCT-2009See above table data on 16-OCT-2009 , POR is 14-OCT-2009 you have backup on 14th of oct within yours backup schedule but this backup is L1 not L0 , in this case 13th Oct backup will be needed for the point of recoverability for 14th of Oct ,13th Oct backup will not be marked obsoleted.
date          backup type          status               POR (Current date-recovery window)
13-OCT-2009     L0               No obsolete found     13-OCT-2009-2 = 11-OCT-2009
14-OCT-2009     L1               No obsolete found     14-OCT-2009-2 = 12-OCT-2009
15-OCT-2009     L1               No obsolete found     15-OCT-2009-2 = 13-OCT-2009
16-OCT-2009     L1               No obsolete found     16-OCT-2009-2 = 14-OCT-2009
17-OCT-2009     L1               No obsolete found     17-OCT-2009-2 = 15-OCT-2009See above table data on 17-OCT-2009 , POR is 15-OCT-2009 you have backup on 15th of oct within yours backup schedule but this backup is L1 not L0 ,in this case 13th Oct backup will be needed for the point of recoverability for 15th of Oct ,13th Oct backup will not me marked obsoleted yet.
date          backup type          status               POR (Current date-recovery window)
13-OCT-2009     L0               No obsolete found     13-OCT-2009-2 = 11-OCT-2009
14-OCT-2009     L1               No obsolete found     14-OCT-2009-2 = 12-OCT-2009
15-OCT-2009     L1               No obsolete found     15-OCT-2009-2 = 13-OCT-2009
16-OCT-2009     L1               No obsolete found     16-OCT-2009-2 = 14-OCT-2009
17-OCT-2009     L1               No obsolete found     17-OCT-2009-2 = 15-OCT-2009
18-OCT-2009     L1               No obsolete found     18-OCT-2009-2 = 16-OCT-2009
19-OCT-2009     L1               No obsolete found     19-OCT-2009-2 = 17-OCT-2009
20-OCT-2009     L0               No obsolete found     20-OCT-2009-2 = 18-OCT-2009
21-OCT-2009     No backup          No obsolete found     21-OCT-2009-2 = 19-OCT-2009
22-OCT-2009     No backup          obsolete found          22-OCT-2009-2 = 20-OCT-2009
                         13th L0 and its alls
                         L1 See above table data on 22-OCT-2009 , POR is 20-OCT-2009 you have L0 backup on 20th of oct within yours backup schedule and this backup is L0 not L1 ,in this case 20th Oct backup will be needed for the point of recoverability for 20th of Oct ,before 20th L0 backup 13th L0 backup will marked obsoleted and hence alls its incremental level backup will be marked as obsoleted.
Khurram

Similar Messages

RMAN - obsolete - expired

Dear buddies,
I am using RMAN to backup my database.
What does it mean by obsolete backup and expired backup?
When do they achieve such a state?
Please guide me.
Thanks

RMAN considers backups of datafiles and control files as obsolete, that is, no longer needed for recovery, according to criteria that we specify in the CONFIGURE command. We can then use the REPORT OBSOLETE command to view obsolete files and DELETE OBSOLETE to delete them .
For ex : we set our retention policy to redundancy 2. this means we always want to keep at least 2 backup, after 2 backup, if we take an another backup oldest one become obsolete because there is 3 backup and we want to keep 2. if our flash recovery area is full then obsolete backups can be overwrite.
A status of "expired" means that the backup piece or backup set is not found in the backup destination or missing .Since backup info is hold in our controlfile and catalog . Our controlfile thinks that there is a backup under a directory with a name but someone delete this file from operating system. We can run crosscheck command to check if these files are exist and if rman found a file is missing then mark that backup record as expired which means is no more exists.
--neeraj

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

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.

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

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

RMan removal of obsolete

Hello,
I have the following rman command to control my backups
RUN {
BACKUP
DATABASE
FORMAT '/mnt/backup/rman/nocdb_es/%d_%T_bkpdonl_%s_%t_%p'
TAG 'backup_daily'
CURRENT CONTROLFILE
FORMAT '/mnt/backup/rman/nocdb_es/%d_%T_cf_%s_%t_%p'
TAG 'controlfile_daily'
PLUS ARCHIVELOG
FORMAT '/mnt/backup/rman/nocdb_es/%d_%T_al_%s_%t_%p' delete all input
TAG 'archivelog_daily'
delete noprompt obsolete;
I have a retention policy of 5 days.
This was working fine on 9i. I mean after de backup all the obsoletes including Control Files, and Archivelogs were removed. Now, under 10g, only the backup is removed, the archive log are kept in the disk, dont know the reason. I tried many configurations but none of them worked.
I can I do so rman automatically removes the obsoletes(more than 5 days) archived logs. ?
BTW, I dont use flashback.
thanks alot in advance,
JOao,

Found out what the problem is.Actually, it is not a problem. It is just the way 10g works right now.
1. How it worked on oracle 9i.
The script generated backups for Control Files, Data Files, and Archived logs. All the backups were tagged, in such a way we could remove all backups of a certain date easily looking at the name.
Oracle removed everything, including archive log backups, when they became obsolete.
2. How it works on oracle 10g.
Basically the same way, except that 10g also carries the init.ora to the backup. Additionally, at the removal time 10g does not remove all the archived logs from according to the tagged day they supposedly become obsolete, but two or three day later.
Ex. I backup on the first day of the month, have a retention policy of 2 days.
On the 4th it was supposed to remove all the backups from disk, including ; datafile, archivelogs, controlfiles.
I excludes everything but archivelogs. Two day later they are removed. Probably because they have any unfinished transaction for the current backups. Maybe, just precaution.
Joao,

RMAN "delete noprompt obsolete" not deleted

OS: AIX 5.3L; Oracle 10g R2
I have "delete noppropt obsolete" in my RMAN backup script as {
delete noprompt obsolete;
crosscheck backupset;
crosscheck archivelog all;
delete noprompt expired backup;
delete noprompt expired archivelog all;
backup as compressed backupset incremental level 1 cumulative device type disk tag 'Baan_bkup$LEVEL1' database plus archivelog delete input; }
but the incremental level 1 cumulative backupsets, outside my 7 days window, did not been deleted as prompted, even they are under the obsolete list. Why?
Message was edited by:
user508054

I also observed that with "REPORT OBSOLETE", only partial of the backupset piece of backup were "OBSOLETE". For example, after this morning LEVEL 1 incremental backup, my last Sunday, Mar 4 level 0 backup has 12 backup pieces (including controlfile and archivelog), but only two have been on the obsolete list. The two are controlfile and archivelog, and other 10 datafaile backupsets are still there in the list. Really confused! Are they supposed to be treated as a bunch?

RMAN delete noprompt obsolete

Hi,
I'm keen to know what does this comand mean in RMAN backup. "delete noprompt obsolete;" .Can I apply this comand for no catalog too or it's just meant for rman catalog.
Thanks
M.Kaur

Hi,
I'm trying to do house keeping on RMAN backups,following is my script,but this does not remove hte last year's backups on the tape,thou the tape is mounted to the lib.Must I add in another command? but yes the last year's backup is not even shown in the rman backup list,but it's still in the sbt_tape,how do I remove it from there.
Note: RMAN no catalog running on oracle 9i 9.2.0.7
allocate channel for delete type disk;
allocate channel for delete type 'sbt_tape'
PARMS 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
report obsolete orphan;
report obsolete;
crosscheck backup;
crosscheck copy;
crosscheck backup of controlfile;
delete noprompt expired backup;
delete noprompt expired archivelog all;
delete noprompt expired backup of controlfile;
delete force noprompt expired copy;
delete force noprompt obsolete orphan;
delete force noprompt obsolete;
release channel;
Thanks

Rman with commvault mml: database crash while delete obsolete

Hello!
I have a problem concerning RMAN, delete obsolete and CommVault media management library: Every night at 23:00 we run a RMAN "Backup" to delete the obsolete backup files from tape. Since the update to CommVault agent 8 (from version 7) the database crashes while the delete obsolete command. The normal backup (incremental 0/1) works without problem.
After restarting the database i tried the delete obsolete via shell -> same result: CRASH.
The CommVault support says that there is an Oracle bug with different MML's, that causes this behaviour - but i can't find anything at Metalink.
This is the output of RMAN (tell me which other logs can be helpful):
RMAN-Sperr-Policy wird f³r den Befehl angewendet
RMAN-Sperr-Policy ist auf ein Recovery-Fenster von 0 Tagen festgelegt
Die folgenden veralteten Backups und Kopien werden gel÷scht:
Typ Schl³ssel Abschlusszeit Dateiname/Handle
Backup Set 7 01.09.10
Backup Piece 12 01.09.10 c-190884945-20100901-01
Backup Set 9 01.09.10
Backup Piece 17 01.09.10 c-190884945-20100901-02
M÷chten Sie die obigen Objekte wirklich l÷schen (geben Sie YES oder NO ein)? yes
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00601: fatal error in recovery manager
RMAN-03004: Abbruchfehler bei der Ausf³hrung des Befehls
ORA-12514: TNS: Listener kann in Connect-Deskriptor angegebenen Service aktuell nicht aufl÷sen -> listener can not resolve service name
RMAN-03009: Fehler bei delete Befehl in ORA_MAINT_SBT_TAPE_1 Kanal auf 09/02/2010 08:57:37 -> error at delete command
ORA-03135: connection lost contact
Recovery Manager nicht kompatibel mit TARGET Datenbank: RMAN 14155912.14155908.14312748.1 bis 1651797107.0.27143.0 erforderlich -> recovery not compatible with TARGET database
Best regards,
Christian

Hi,
show parameter plsq
plsql_code_type           string     INTERPRETED
plsql_compiler_flags          string     INTERPRETED, NON_DEBUG
That database is in interpreted mode.
Check also the pacakages:
select OWNER, OBJECT_NAME , PARAM_NAME ||'='||PARAM_VALUE param from DBA_STORED_SETTINGS where OBJECT_NAME in ( 'DBMS_RCVCAT','DBMS_RCVMAN' )and param_name = 'plsql_code_type'
OWNER               OBJECT_NAME
PARAM
SYS               DBMS_RCVMAN plsql_code_type=INTERPRETED
SYS               DBMS_RCVMAN plsql_code_type=INTERPRETED
If it is native you have an issue!
François,

Rman - backups not reporting obsolete

Hi,
Please see below of our now cleaned up rman catalog:
RMAN> list backup of database summary;
List of Backups
===============
Key TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
1531 B 0 A DISK 20-APR-10 1 1 YES TAG20100420T172430
1543 B F A DISK 15-AUG-11 1 1 NO TAG20110815T140126
1549 B F A DISK 15-AUG-11 1 1 NO TAG20110815T144719
1553 B F A DISK 15-AUG-11 1 1 NO TAG20110815T160724
1557 B F A DISK 15-AUG-11 1 1 NO TAG20110815T170223
RMAN> report obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
Based on the fact I see five backups of our current database (produced with "backup database") and we see "retention policy is set to redundancy 1", I would expect to see four backups reported, however the next line is:
no obsolete backups found;
Naturally, my scheduled "delete noprompt obsolete" never seems to remove anything. Any advise appreciated.

Hi,
Please post here the script that you use to perform this backup.
Check if you are using KEEP UNTIL clause.
DELETE OBSOLETE Behavior When KEEP UNTIL Time Expires
If the KEEP UNTIL TIME period has not expired for an archival backup, RMAN does not consider the backup as obsolete. As soon as the KEEP UNTIL period expires, however, the backup is immediately considered to be obsolete, regardless of any configured backup retention policy. Thus, DELETE OBSOLETE deletes any backup created with BACKUP ... KEEP UNTIL TIME if the KEEP time has expired.
http://download.oracle.com/docs/cd/E11882_01/backup.112/e10642/rcmmaint.htm#BRADV89640
V$BACKUP_FILES
KEEP- Indicates whether the backup has a retention policy different from the value for CONFIGURE RETENTION POLICY (YES) or not (NO)
KEEP_UNTIL - If the KEEP UNTIL TIME clause of the BACKUP command was specified, then this column shows the date after which the backup becomes obsolete. If the column is null and KEEP_OPTIONS is not null, the backup never becomes obsolete.V$BACKUP_FILES displays information about all RMAN backups (both image copies and backup sets) and archived logs.
http://download.oracle.com/docs/cd/E11882_01/server.112/e17110/dynviews_1057.htm#REFRN30022
Regards,
Levi Pereira
Edited by: Levi Pereira on Aug 17, 2011 12:07 AM
Edited by: Levi Pereira on Aug 17, 2011 12:11 AM - Add V$BACKUP_FILES

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

Restoring backup that was marked obsolete by RMAN

Hello,
Is it possible to restore a BACKUPSET that is outside the retention period? The backup was claimed absolete according to RMAN retention settings and the records were therefore deleted from the catalog.
Can we still use/restore this backupset?

If you have Time Machine setup, you can use it to recover the backup with it. Then just restore the iPhone from backup as usual.
If you haven't setup Time Machine, you can try searching the web for backup extractors (not made by Apple). One of those Extractors may be able to recover some of the data from the backup, which you can just re-import and sync to the iPhone again.

RMAN Issue

I am having issue with RMAN
I have Oracle 11gR2 database on HP-UX. when I issue any command in RMAN prompt, its displaying the information but it's not returning to RMAN prompt, I have to hit CTRL+C to come out. But I have 2 more database on the same home, and I don't have this problem on that database.
oracle@hublhp10:/home/oracle$ rman target /
Recovery Manager: Release 11.2.0.1.0 - Production on Mon Mar 19 15:00:53 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: IMGPROD (DBID=2867365220)
RMAN> show all;
using target database control file instead of recovery catalog
RMAN configuration parameters for database with db_unique_name IMGPROD are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/imgback/RMAN/cf-IMGPROD-%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 COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/imgback/RMAN/snapcf_imgprod.f';
RMAN>
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
Archive Log 1 19-MAR-12 /imgarch/ORACLE/imgprod/al_imgprod_1_283_777982948.dbf

I traced the session, see the following
WAIT #2: nam='control file sequential read' ela= 143 file#=0 block#=17 blocks=1 obj#=-1 tim=11750515395399
WAIT #2: nam='control file sequential read' ela= 143 file#=0 block#=1 blocks=1 obj#=-1 tim=11750515395853
WAIT #2: nam='control file sequential read' ela= 144 file#=0 block#=15 blocks=1 obj#=-1 tim=11750515396024
WAIT #2: nam='control file sequential read' ela= 145 file#=0 block#=17 blocks=1 obj#=-1 tim=11750515396192
WAIT #2: nam='control file sequential read' ela= 206 file#=0 block#=1 blocks=1 obj#=-1 tim=11750515396719
WAIT #2: nam='control file sequential read' ela= 142 file#=0 block#=15 blocks=1 obj#=-1 tim=11750515396909
WAIT #2: nam='control file sequential read' ela= 168 file#=0 block#=17 blocks=1 obj#=-1 tim=11750515397102
FETCH #2:c=0,e=16905,p=0,cr=0,cu=0,mis=0,r=1,dep=0,og=1,plh=818693323,tim=11750515397527
WAIT #2: nam='SQL*Net message from client' ela= 450 driver id=1650815232 #bytes=1 p3=0 obj#=-1 tim=11750515398178
CLOSE #2:c=0,e=27,dep=0,type=3,tim=11750515398262
=====================
PARSING IN CURSOR #4 len=205 dep=0 uid=0 oct=3 lid=0 tim=11750515399507 hv=1796820951 ad='c0000004fe449f88' sqlid='gq4u3dppjkmyr'
select /*+ rule */ round(sum(MBYTES_PROCESSED)), round(sum(INPUT_BYTES)), round(sum(OUTPUT_BYTES)) from V$RMAN_STATUS START WITH RECID = :row_id and STAMP = :row_stamp CONNECT BY PRIOR RECID = parent_recid
END OF STMT
PARSE #4:c=0,e=556,p=0,cr=0,cu=0,mis=1,r=0,dep=0,og=1,plh=0,tim=11750515399506

RMAN Obsolete

Similar Messages

Maybe you are looking for