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                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

Similar Messages

  • 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 opening database after cold backup

    OS: RHES4
    10g R2
    I am having a problem using RMAN to run a cold backup. The error from the log tell me that the database is already open. However when I check the database, the status is that it is in MOUNT. I can then open it but am not sure why RMAN cannot. The log is below:
    Output Log
    SQL*Plus: Release 10.1.0.3.0 - Production on Thu May 11 02:00:13 2006
    Copyright (c) 1982, 2004, Oracle. All rights reserved.
    SQL> Connected.
    SQL> Database closed.
    Database dismounted.
    ORACLE instance shut down.
    SQL> Disconnected from Oracle Database 10g Enterprise Edition Release 10.1.0.3.0 - Production
    With the Partitioning, OLAP and Data Mining options
    SQL*Plus: Release 10.1.0.3.0 - Production on Thu May 11 02:00:32 2006
    Copyright (c) 1982, 2004, Oracle. All rights reserved.
    SQL> Connected to an idle instance.
    SQL> ORACLE instance started.
    Total System Global Area 687865856 bytes
    Fixed Size          780700 bytes
    Variable Size          149165668 bytes
    Database Buffers     536870912 bytes
    Redo Buffers          1048576 bytes
    Database mounted.
    SQL> Disconnected from Oracle Database 10g Enterprise Edition Release 10.1.0.3.0 - Production
    With the Partitioning, OLAP and Data Mining options
    Recovery Manager: Release 10.1.0.3.0 - Production
    Copyright (c) 1995, 2004, Oracle. All rights reserved.
    RMAN>
    connected to target database: TEST10G (DBID=3717786770)
    using target database controlfile instead of recovery catalog
    RMAN> 2> 3> 4> 5>
    allocated channel: oem_disk_backup
    channel oem_disk_backup: sid=160 devtype=DISK
    Starting recover at 11-MAY-06
    no copy of datafile 1 found to recover
    no copy of datafile 2 found to recover
    no copy of datafile 3 found to recover
    no copy of datafile 4 found to recover
    no copy of datafile 5 found to recover
    no copy of datafile 6 found to recover
    no copy of datafile 7 found to recover
    no copy of datafile 8 found to recover
    no copy of datafile 9 found to recover
    no copy of datafile 10 found to recover
    no copy of datafile 11 found to recover
    no copy of datafile 12 found to recover
    no copy of datafile 13 found to recover
    no copy of datafile 14 found to recover
    no copy of datafile 15 found to recover
    no copy of datafile 16 found to recover
    no copy of datafile 17 found to recover
    no copy of datafile 18 found to recover
    Finished recover at 11-MAY-06
    Starting backup at 11-MAY-06
    no parent backup or copy of datafile 18 found
    no parent backup or copy of datafile 1 found
    no parent backup or copy of datafile 8 found
    no parent backup or copy of datafile 9 found
    no parent backup or copy of datafile 10 found
    no parent backup or copy of datafile 11 found
    no parent backup or copy of datafile 13 found
    no parent backup or copy of datafile 14 found
    no parent backup or copy of datafile 15 found
    no parent backup or copy of datafile 17 found
    no parent backup or copy of datafile 4 found
    channel oem_disk_backup: starting compressed incremental level 1 datafile backupset
    channel oem_disk_backup: specifying datafile(s) in backupset
    input datafile fno=00003 name=/home/oracle/oradata/dev10g/sysaux01.dbf
    input datafile fno=00002 name=/home/oracle/oradata/dev10g/undotbs01.dbf
    input datafile fno=00005 name=/home/oracle/oradata/dev10g/example01.dbf
    input datafile fno=00012 name=/home/oracle/oradata/dev10g/FLOW_7.dbf
    input datafile fno=00016 name=/home/oracle/oradata/dev10g/FLOW_11.dbf
    input datafile fno=00006 name=/home/oracle/oradata/dev10g/FLOW_1.dbf
    input datafile fno=00007 name=/home/oracle/oradata/dev10g/FLOW_2.dbf
    channel oem_disk_backup: starting piece 1 at 11-MAY-06
    channel oem_disk_backup: finished piece 1 at 11-MAY-06
    piece handle=/home/oracle/flash_recovery_area/DEV10G/backupset/2006_05_11/o1_mf_nnnd1_TAG20060511T020039_265nr8h8_.bkp comment=NONE
    channel oem_disk_backup: backup set complete, elapsed time: 00:01:15
    channel oem_disk_backup: starting datafile copy
    input datafile fno=00018 name=/home/oracle/oradata/dev10g/designer1.dbf
    output filename=/home/oracle/flash_recovery_area/DEV10G/datafile/o1_mf_designer_265ntmow_.dbf tag=ORA$OEM_LEVEL_0 recid=9 stamp=590119379
    channel oem_disk_backup: datafile copy complete, elapsed time: 00:01:05
    channel oem_disk_backup: starting datafile copy
    input datafile fno=00001 name=/home/oracle/oradata/dev10g/system01.dbf
    output filename=/home/oracle/flash_recovery_area/DEV10G/datafile/o1_mf_system_265nwnw0_.dbf tag=ORA$OEM_LEVEL_0 recid=10 stamp=590119436
    channel oem_disk_backup: datafile copy complete, elapsed time: 00:01:05
    channel oem_disk_backup: starting datafile copy
    input datafile fno=00008 name=/home/oracle/oradata/dev10g/FLOW_3.dbf
    output filename=/home/oracle/flash_recovery_area/DEV10G/datafile/o1_mf_flow_3_265nyp5w_.dbf tag=ORA$OEM_LEVEL_0 recid=11 stamp=590119448
    channel oem_disk_backup: datafile copy complete, elapsed time: 00:00:03
    channel oem_disk_backup: starting datafile copy
    input datafile fno=00009 name=/home/oracle/oradata/dev10g/FLOW_4.dbf
    output filename=/home/oracle/flash_recovery_area/DEV10G/datafile/o1_mf_flow_4_265nysc5_.dbf tag=ORA$OEM_LEVEL_0 recid=12 stamp=590119452
    channel oem_disk_backup: datafile copy complete, elapsed time: 00:00:07
    channel oem_disk_backup: starting datafile copy
    input datafile fno=00010 name=/home/oracle/oradata/dev10g/FLOW_5.dbf
    output filename=/home/oracle/flash_recovery_area/DEV10G/datafile/o1_mf_flow_5_265nz0jc_.dbf tag=ORA$OEM_LEVEL_0 recid=13 stamp=590119458
    channel oem_disk_backup: datafile copy complete, elapsed time: 00:00:03
    channel oem_disk_backup: starting datafile copy
    input datafile fno=00011 name=/home/oracle/oradata/dev10g/FLOW_6.dbf
    output filename=/home/oracle/flash_recovery_area/DEV10G/datafile/o1_mf_flow_6_265nz3oo_.dbf tag=ORA$OEM_LEVEL_0 recid=14 stamp=590119463
    channel oem_disk_backup: datafile copy complete, elapsed time: 00:00:07
    channel oem_disk_backup: starting datafile copy
    input datafile fno=00013 name=/home/oracle/oradata/dev10g/FLOW_8.dbf
    output filename=/home/oracle/flash_recovery_area/DEV10G/datafile/o1_mf_flow_8_265nzbvj_.dbf tag=ORA$OEM_LEVEL_0 recid=15 stamp=590119469
    channel oem_disk_backup: datafile copy complete, elapsed time: 00:00:03
    channel oem_disk_backup: starting datafile copy
    input datafile fno=00014 name=/home/oracle/oradata/dev10g/FLOW_9.dbf
    output filename=/home/oracle/flash_recovery_area/DEV10G/datafile/o1_mf_flow_9_265nzg1k_.dbf tag=ORA$OEM_LEVEL_0 recid=16 stamp=590119473
    channel oem_disk_backup: datafile copy complete, elapsed time: 00:00:07
    channel oem_disk_backup: starting datafile copy
    input datafile fno=00015 name=/home/oracle/oradata/dev10g/FLOW_10.dbf
    output filename=/home/oracle/flash_recovery_area/DEV10G/datafile/o1_mf_flow_10_265nzo6x_.dbf tag=ORA$OEM_LEVEL_0 recid=17 stamp=590119480
    channel oem_disk_backup: datafile copy complete, elapsed time: 00:00:07
    channel oem_disk_backup: starting datafile copy
    input datafile fno=00017 name=/home/oracle/oradata/dev10g/FLOW_12.dbf
    output filename=/home/oracle/flash_recovery_area/DEV10G/datafile/o1_mf_flow_12_265nzwdb_.dbf tag=ORA$OEM_LEVEL_0 recid=18 stamp=590119487
    channel oem_disk_backup: datafile copy complete, elapsed time: 00:00:03
    channel oem_disk_backup: starting datafile copy
    input datafile fno=00004 name=/home/oracle/oradata/dev10g/users01.dbf
    output filename=/home/oracle/flash_recovery_area/DEV10G/datafile/o1_mf_users_265nzzo0_.dbf tag=ORA$OEM_LEVEL_0 recid=19 stamp=590119489
    channel oem_disk_backup: datafile copy complete, elapsed time: 00:00:03
    channel oem_disk_backup: starting compressed incremental level 1 datafile backupset
    channel oem_disk_backup: specifying datafile(s) in backupset
    including current controlfile in backupset
    including current SPFILE in backupset
    channel oem_disk_backup: starting piece 1 at 11-MAY-06
    channel oem_disk_backup: finished piece 1 at 11-MAY-06
    piece handle=/home/oracle/flash_recovery_area/DEV10G/backupset/2006_05_11/o1_mf_ncsn1_TAG20060511T020039_265o04n1_.bkp comment=NONE
    channel oem_disk_backup: backup set complete, elapsed time: 00:00:03
    Finished backup at 11-MAY-06
    released channel: oem_disk_backup
    RMAN>
    Recovery Manager complete.
    SQL*Plus: Release 10.1.0.3.0 - Production on Thu May 11 08:03:38 2006
    Copyright (c) 1982, 2004, Oracle. All rights reserved.
    SQL> Connected.
    SQL> alter database open
    ERROR at line 1:
    ORA-01531: a database already open by the instance
    Unable to open the database.

    Do you have an OMS configured for OEM? You'll need to connect to an OMS to perform backups thru OEM. The process is explained here Managing Backup and Recovery.
    Here is a SAMPLE configuration script:
    configure device type disk parallelism 1;
    configure channel device type disk format 'd:\oracle_backup\%d_%U.%p';
    configure controlfile autobackup on;
    configure controlfile autobackup format for device type disk to 'd:\oracle_backup\cf_auto_%F.bkp';
    configure retention policy to recovery window of 2 days;
    configure backup optimization on;and a SAMPLE backup script:
    rem
    rem  rman_backup.cmd
    rem
    rem  Full database backup plus archivelogs.
    for /f "tokens=2-4" %%i in ('echo %date:/= %') do set vdate=%%i_%%j_%%k
    echo backup database plus archivelog;
    echo sql "alter database backup controlfile to trace as ''d:\oracle_backup\controlORCL9%vdate%.txt''";
    echo sql "create pfile=''d:\oracle_backup\initORCL9%vdate%.ora'' from spfile";
    echo crosscheck backup;
    echo crosscheck archivelog all;
    echo delete noprompt obsolete recovery window of 2 days;
    echo delete noprompt archivelog all completed before 'sysdate-7';
    ) | rman target / log=backup.logYou could scheduled the rman_backup.cmd script to run every night at 10pm thru the Windows task scheduler.

  • 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

  • RMAN backup archive logs on tape that has not been backuped yet...

    We are using RMAN with catalog on Legato. Oracle 10gR2.
    Our archive log backup is taking every 2 hours with scriipt:
    run {                                                            
    allocate channel t1 type 'SBT_TAPE';
    allocate channel t2 type 'SBT_TAPE';
    send 'NSR_ENV=(NSR_SERVER=hitbackup.hit.hypohr,NSR_CLIENT=a22ff020.hit.hypobck)';
    # 0.0840278 = 121 minutes!
    backup archivelog FROM TIME = 'sysdate-0.0840278' filesperset 50 format '/arch1_%d_%u/';
    release channel t1;
    release channel t2;
    }In the night we take everyday full backup where we delete all 9 days old archive log which has been backuped on tape at least once. The script is following:
    run {
    allocate channel t1 type 'SBT_TAPE';
    allocate channel t2 type 'SBT_TAPE';
    send 'NSR_ENV=(NSR_SERVER=hitbackup.hit.hypohr,NSR_CLIENT=a22ff020.hit.hypobck)';
    backup full database filesperset 2 format '/full_%d_%U/';
    release channel t1;
    release channel t2;
    allocate channel d2 type disk;
    delete archivelog until time 'trunc(sysdate)-9'
    backed up 1 times to device type SBT_TAPE;
    release channel d2;
    }Problem is that sometimes archive log backup is not performed (Legato head is busy with other backups or some restore that happened in the time when backup is scheduled and later 2hours frame is missing those logs) and then we backup them with some manual script.
    We'd like to know how to backup to tape all archive logs in last 5 days that has not been backuped once to tape. I.E:
    backup archivelog FROM TIME = 'sysdate-7' filesperset  50 format '/arch1_%d_%u/'
    backed up 0 times to device type SBT_TAPE;This part will be included in daily job...which should recollect all missing archive logs from last seven days.
    THX

    You could try to use the NOT BACKED UP x TIMES clause from BACKUP command.

  • Why should not hot backup in rman

    Hi ,
    Please let me know why should not take tablespace begin backup mode in rman

    Hi ,
    SARAT point is correct.
    what do you mean backup set ? its like
    A backup set contains one or more binary files in an RMAN-specific format. Each of these files is known as a backup piece. A backup set can contain multiple datafiles. For example, you can back up 10 datafiles into a single backup set consisting of a single backup piece. In this case, RMAN creates one backup piece as output. The backup set contains only this backup piece."
    Thats reason all datafiles one set, all archivelogs one set, and spfile & controlfile is another set.
    Let us know if anything you required.
    Thanks
    Murali.

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

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

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

  • 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 report need backup

    We have an incremental level-1 backup Mon-Sat and cold full backup on Sundays with retention policy of 7 days. While troubleshooting some backup issues (space issue, expired backups) I ran the following commands and trying to understand the output.
    RMAN> report need backup database;
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to recovery window of 7 days
    Report of files whose recovery needs more than 7 days of archived logs
    File Days Name
    100 146 /orahprdidx/hprd/psindex05.dbf
    RMAN> report unrecoverable;
    Report of files that need backup due to unrecoverable operations
    File Type of Backup Required Name
    RMAN> report need backup days = 7 database;
    Report of files whose recovery needs more than 7 days of archived logs
    File Days Name
    100 146 /orahprdidx/hprd/psindex05.dbf
    RMAN> report obsolete recovery window of 7 days;
    no obsolete backups found
    RMAN>
    I looks like I need 146 days worth of archive log files to recover the psindex05.dbf. If so, what I could do to bring that into the 7 days policy?
    The database is fine, I am not trying to recover the database.
    This was setup by someone and now I am taking over with minimum RMAN experience.
    I appreciate any help in this subject.

    The datafile was offline. I guess it was created my mistake and hanging in there. Once I do the cleanup it should go away.

  • How to list all obsolete backuped archivelog

    today I backup the whole database(this is the
    first time I backup the database) with command
    " backup database",and alse backup all
    archivelog,and the oldest archivelog is three days
    ago,and after the backup,I want to report obsolete
    backup,but using
    "report obsolete until time 'SYSDATE-1'"
    command get a output of nothing,and IMO because I
    backup the whole database,at least the archivelogs
    before yesterday are not usefull for restore,and
    it should be obsolete.When I read rman reference,it
    sames that obsolete only apply to datafile,but no
    archivedlog.

    You are right, in the 8i doc, it contains an "until" clause and does not list obsolete archive logs.
    http://download-uk.oracle.com/docs/cd/A87860_01/doc/server.817/a76990/rmansy35.htm#23596
    You should then try to write your own script in sqlplus.
    Example, which delete all backups of archive logs older then yesterday.
    $ sqlplus rman/rman@RMANREP
    SQL> select db_name, max(THREAD#), max(SEQUENCE#) from rc_backup_redolog where completion_time < sysdate-1 group by db_name;
    DB_NAME  MAX(THREAD#) MAX(SEQUENCE#)
    PROD                1            133
    $ rman sys/change_on_install@PROD rman/rman@RMANREP
    RMAN> delete noprompt archivelog until sequence 133 thread 1;

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

  • Obsolete backup

    Hello all,
    I am using Oracle 11g R2.
    on RMAN i wanted to report the obsolete backup and the below result appear, but i am not able to analyze it:
    RMAN> report obsolete
    2> ;
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to redundancy 1
    Report of obsolete backups and copies
    Type                 Key    Completion Time    Filename/Handle
    Backup Set           252    11-SEP-11
      Backup Piece       452    11-SEP-11          C:\APP\ORACLE\FLASH_RECOVERY_AREA\WINDB\AUTOBACKUP\2011_09_11\O1_MF_S_761565747_76RTRRNP_.BKP
    Backup Set           254    11-SEP-11
      Backup Piece       454    11-SEP-11          C:\APP\ORACLE\FLASH_RECOVERY_AREA\WINDB\AUTOBACKUP\2011_09_11\O1_MF_S_761565802_76RTTFF2_.BKPwhat i understood that key= 452 and key = 454 are obsolete. but what are the 252 and the 254 ?
    what the key is for ? is that logged in any table/view?
    Regards,

    Hello,
    A backup set is a logical structure created by RMAN when you lanuch a backup. A backup set can contain one or more backup pieces, which are the binary files you can see at OS level. In your case, each backup set contains only one backup piece.
    The backup sets 252 and 254 are obsolete, which means that the backup pieces inside, 452 and 454 are obsolete too.
    The key is the identifier of backup sets and backup pieces.
    Here is the explanation of backup pieces and backup sets :
    http://download.oracle.com/docs/cd/E11882_01/backup.112/e10642/rcmcncpt.htm#BRADV106
    And the explanation of the informations given by the LIST command, that can be helpful for understanding your output :
    http://download.oracle.com/docs/cd/E11882_01/backup.112/e10643/rcmsynta027.htm#sthref1173
    And the list of recovery catalog views :
    http://download.oracle.com/docs/cd/E11882_01/backup.112/e10643/rcviews.htm#RCMRF003
    Hope this will help.
    Regards,
    Sylvie

  • If I need a full rman restore which backups will it use?

    Hello,
    I have a database 11.1.0.7 with 8TB. Block change tracking is enabled.
    At the weekend I take level 0 backup and during the week level 1 cumulative.
    For some weeks the level 0 backup is failing, so I only have level 1 cumulative backups taken every week day with a 4 weeks old level 0 backup.
    If I need a full rman restore which backups will it use? Will it be the last level 0 backup with the last level 1 cumulative?
    I ask this because grid crontrol tells me that the recent level 1 backups input size is smaller than last week level 1 backups and in between I dont have any level 0 sucessfull backups. Shouldn't the input size of level 1 cumulative increase until the next level 0 backup ?
    The grid reports:
    Backup Name Status Start Time Time Taken Type Output Devices Input Size Output Size Output Rate (Per Sec)
    rman_df_lv1c COMPLETED 25/Jul/2011 21H00m WEST 02:33:29 DB INCR SBT_TAPE *1.32T* 289.02G 32.14M
    rman_df_lv0 FAILED 23/Jul/2011 02H01m WEST DB INCR SBT_TAPE 8.78T 8.06T
    rman_df_lv1c COMPLETED 21/Jul/2011 21H00m WEST 04:39:38 DB INCR SBT_TAPE *3.46T* 550.82G 33.62M
    rman_df_lv1c COMPLETED 20/Jul/2011 21H00m WEST 04:47:36 DB INCR SBT_TAPE *3.37T* 524.36G 31.12M
    rman_df_lv1c COMPLETED 19/Jul/2011 21H00m WEST 04:06:09 DB INCR SBT_TAPE *3.15T* 490.75G 34.03M
    rman_df_lv1c COMPLETED 18/Jul/2011 21H00m WEST 03:40:24 DB INCR SBT_TAPE *2.49T* 410.88G 31.82M
    rman_df_lv0 FAILED 16/Jul/2011 22H16m WEST DB INCR SBT_TAPE 6.27T 5.69T
    rman_df_lv1c FAILED 14/Jul/2011 21H00m WEST 06:13:40 DB INCR SBT_TAPE 4.38T 714.30G 32.62M
    rman_df_lv1c FAILED 13/Jul/2011 21H01m WEST 04:40:45 DB INCR SBT_TAPE 3.25T 542.98G 33.01M
    rman_df_lv1c COMPLETED 12/Jul/2011 21H00m WEST 07:15:54 DB INCR SBT_TAPE 4.74T 847.93G 33.20M
    rman_df_lv1c COMPLETED 11/Jul/2011 21H00m WEST 07:26:40 DB INCR SBT_TAPE 3.78T 766.40G 29.28M
    rman_df_lv0 FAILED 9/Jul/2011 02H32m WEST 04:30:44 DB INCR SBT_TAPE 749.89G 716.02G 45.14M
    rman_df_lv1c FAILED 7/Jul/2011 21H01m WEST 04:49:24 DB INCR SBT_TAPE 2.16T 515.90G 30.42M
    rman_df_lv1c FAILED 6/Jul/2011 21H00m WEST 01:26:06 DB INCR SBT_TAPE 745.83G 165.48G 32.80M
    rman_df_lv1c FAILED 5/Jul/2011 21H01m WEST 00:05:48 DB INCR SBT_TAPE 58.56G 7.56G 22.24M
    rman_df_lv1c FAILED 4/Jul/2011 21H00m WEST 01:55:03 DB INCR SBT_TAPE 422.40G 79.55G 11.80M
    rman_df_lv0 FAILED 3/Jul/2011 16H32m WEST 30:22:04 DB INCR SBT_TAPE 4.53T 4.21T 40.40M

    >
    If I need a full rman restore which backups will it use? Will it be the last level 0 backup with the last level 1 cumulative?
    From http://download.oracle.com/docs/cd/B28359_01/backup.111/b28270/rcmvalid.htm
    Validating Backups Before Restoring Them
    You can run RESTORE ... VALIDATE to test whether RMAN can restore a specific file or set of files from a backup. RMAN chooses which backups to use.
    The database must be mounted or open for this command. You do not have to take datafiles offline when validating the restore of datafiles, because validation of backups of the datafiles only reads the backups and does not affect the production datafiles.
    When validating files on disk or tape, RMAN reads all blocks in the backup piece or image copy. RMAN also validates offsite backups. The validation is identical to a real restore operation except that RMAN does not write output files.
    You can monitor what RESTORE VALIDATE does.
    Make precautions, so you do not damage the production DB!!!
    Iordan Iotzov
    http://iiotzov.wordpress.com/

  • Restore from OSB. RMAN-06024: no backup or copy of the control file found

    I backed up controlfile for standby on production server to OSB media:
    -bash-3.00$ rman target / catalog rman/rman@emgc
    Recovery Manager: Release 10.2.0.5.0 - Production on Tue Jan 25 15:15:33 2011
    Copyright (c) 1982, 2007, Oracle. All rights reserved.
    connected to target database: EMGC (DBID=1838014073)
    connected to recovery catalog database
    RMAN>
    RMAN> CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 2 BACKUP TYPE TO COMPRESSED BACKUPSET;
    RUN
    ALLOCATE CHANNEL ch1 DEVICE TYPE 'SBT_TAPE';
    BACKUP CURRENT CONTROLFILE FOR STANDBY tag 'stb_ctl';
    RELEASE CHANNEL ch1;
    CONFIGURE DEVICE TYPE 'SBT_TAPE' CLEAR;
    new RMAN configuration parameters:
    CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 2 BACKUP TYPE TO COMPRESSED BACKUPSET;
    new RMAN configuration parameters are successfully stored
    starting full resync of recovery catalog
    full resync complete
    RMAN> 2> 3> 4> 5> 6>
    allocated channel: ch1
    channel ch1: sid=1085 devtype=SBT_TAPE
    channel ch1: Oracle Secure Backup
    Starting backup at 25-JAN-11
    channel ch1: starting compressed full datafile backupset
    channel ch1: specifying datafile(s) in backupset
    including standby control file in backupset
    channel ch1: starting piece 1 at 25-JAN-11
    channel ch1: finished piece 1 at 25-JAN-11
    piece handle=1em30ngu_1_1 tag=STB_CTL comment=API Version 2.0,MMS Version 10.3.0.2
    channel ch1: backup set complete, elapsed time: 00:00:27
    Finished backup at 25-JAN-11
    released channel: ch1
    RMAN> list backup of controlfile;
    old RMAN configuration parameters:
    CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 2 BACKUP TYPE TO COMPRESSED BACKUPSET;
    RMAN configuration parameters are successfully reset to default value
    starting full resync of recovery catalog
    full resync complete
    List of Backup Sets
    ===================
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    1479 Full 512.00K SBT_TAPE 00:00:18 25-JAN-11
    BP Key: 1480 Status: AVAILABLE Compressed: YES Tag: STB_CTL
    Handle: 1em30ngu_1_1 Media: mf_rman-000003
    Standby Control File Included: Ckp SCN: 33567224 Ckp time: 25-JAN-11
    RMAN>
    On standby server I try to restore this control file but there is some trouble with restore... By the way I can delete that backup piece...
    -bash-3.00$ rman target / catalog rman/rman@emgc
    Recovery Manager: Release 10.2.0.5.0 - Production on Tue Jan 25 15:34:32 2011
    Copyright (c) 1982, 2007, Oracle. All rights reserved.
    connected to target database: emgc (not mounted)
    connected to recovery catalog database
    RMAN> set DBID=1838014073;
    executing command: SET DBID
    database name is "EMGC" and DBID is 1838014073
    RMAN> RUN
    ALLOCATE CHANNEL ch1 DEVICE TYPE 'SBT_TAPE';
    crosscheck backup of controlfile;
    2> 3> 4> 5>
    allocated channel: ch1
    channel ch1: sid=1093 devtype=SBT_TAPE
    channel ch1: Oracle Secure Backup
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=1em30ngu_1_1 recid=40 stamp=741367328
    Crosschecked 1 objects
    released channel: ch1
    RMAN> list backup of controlfile;
    List of Backup Sets
    ===================
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    1479 Full 512.00K SBT_TAPE 00:00:18 25-JAN-11
    BP Key: 1480 Status: AVAILABLE Compressed: YES Tag: STB_CTL
    Handle: 1em30ngu_1_1 Media: mf_rman-000003
    Standby Control File Included: Ckp SCN: 33567224 Ckp time: 25-JAN-11
    RMAN> RUN
    ALLOCATE CHANNEL ch1 DEVICE TYPE 'SBT_TAPE';
    RESTORE CONTROLFILE FROM TAG 'STB_CTL';
    2> 3> 4> 5>
    allocated channel: ch1
    channel ch1: sid=1093 devtype=SBT_TAPE
    channel ch1: Oracle Secure Backup
    Starting restore at 25-JAN-11
    released channel: ch1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 01/25/2011 15:35:20
    RMAN-06026: some targets not found - aborting restore
    RMAN-06024: no backup or copy of the control file found to restore
    RMAN> RUN
    ALLOCATE CHANNEL ch1 DEVICE TYPE 'SBT_TAPE';
    delete noprompt backup of controlfile;
    2> 3> 4> 5>
    allocated channel: ch1
    channel ch1: sid=1093 devtype=SBT_TAPE
    channel ch1: Oracle Secure Backup
    List of Backup Pieces
    BP Key BS Key Pc# Cp# Status Device Type Piece Name
    1480 1479 1 1 AVAILABLE SBT_TAPE 1em30ngu_1_1
    deleted backup piece
    backup piece handle=1em30ngu_1_1 recid=40 stamp=741367328
    Deleted 1 objects
    released channel: ch1
    RMAN>

    You cannot specify a tag for a standby control file.
    read here
    http://download.oracle.com/docs/cd/B10501_01/server.920/a96566/rcmstand.htm#1002594
    Edited by: Adigozalov Gurban on Jan 25, 2011 2:14 PM

  • RMAN-06023: no backup or copy of datafile 5 found to restore ??

    Hi,
    Am on
    Apps 12.0.4
    DB 10gR2
    Am trying to recover a datafile: got below error ?
    Hex dump of (file 5, block 11701) in trace file /u01/app/oracle/admin/ora10g/udump/ora10g_ora_6482.trc
    Corrupt block relative dba: 0x01402db5 (file 5, block 11701)
    Bad check value found during backing up datafile
    Data in bad block:
    type: 0 format: 2 rdba: 0x01402db5
    last change scn: 0×0000.00000000 seq: 0×1 flg: 0×05
    spare1: 0×0 spare2: 0×0 spare3: 0×0
    consistency value in tail: 0×00000001
    check value in block header: 0x8bf5
    computed block checksum: 0×2
    Reread of blocknum=11701, file=/u01/app/oracle/oradata/ora10g/example01.dbf. found same corrupt data
    RMAN> blockrecover datafile 5 block 11701;
    Starting blockrecover at 23-AUG-11
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=139 devtype=DISK
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of blockrecover command at 10/23/2011 19:40:13
    RMAN-06026: some targets not found – aborting restore
    RMAN-06023: no backup or copy of datafile 5 found to restore
    i dont have a backup of this datafile
    Thanks
    Edited by: NewAppsDBA on Oct 24, 2011 6:23 AM

    RMAN-03002: failure of blockrecover command at 10/23/2011 19:40:13
    RMAN-06026: some targets not found – aborting restore
    RMAN-06023: no backup or copy of datafile 5 found to restoreSearch MOS for those errors and go through the docs.
    Thanks,
    Hussein

Maybe you are looking for