-Obsolete - RMAN expired

Dear friends,

I'm with RMAN to back up my database.

That means backup obsolete and outdated?

When they reach such a State?

Please guide me.

Thank you

>
A backup is obsolete when the REPORT OUTDATED or OBSOLETE REMOVE determines, based on the user-defined retention policy, it is not necessary for recovery. A backup is considered a backup expired only when RMAN performs an overlap and can not find the file. In short, obsolete means that a file is not necessary, whereas expired way, it is not found.
>

Please read about the RMAN backup retention policies: http://download.oracle.com/docs/cd/E11882_01/backup.112/e10642/rcmcncpt.htm#BRADV99966.

Tags: Database

Similar Questions

  • obsolete RMAN County

    Hi all

    DB-used: 11203

    RMAN-Version 11203

    OPERATING SYSTEM: SOLARIS

    Is there a way to COUNT the obsolete backups, archivelogs in RMAN?

    AMAZON

    Hello

    You can use the view v$ backup_files. If you use the rman catalog, then you can query view rc_backup_files. There is a column called "obsolete" as saratpvv said.

  • RMAN expired Backup

    Hello
    10 g R2 on Win 2003 Server
    in my backup RMAN script, I have this command:
    crosscheck backup
    and I always (since some month ego):
    crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=S:\BACKUP\ARCHIVE_LOGS\DATABASE\DATABASE_RMAN_ARCH_LOG_20090329_03H30.BCK recid=5 stamp=682745403
................................
.......................................
    and many lines like this.
    What should issue for either these?

    Thank you.

    'backup expired' means a backup that no longer exists on the mentioned place.
    This occurs when you delete backups using o/s instead of RMAN commands.
    To get rid of these lines, you must
    -question
    delete the backup expired;
    in RMAN
    -engage adequate maintenance procedures, that is to say: do NOT delete the backups using del or erase, but using RMAN
    -read the documentation of RMAN. Your question is a question of doc, and you shouldn't need to ask here, demonstrate that you refuse to read the documentation.

    -------------
    Sybrand Bakker
    Senior Oracle DBA

    Experts: those who don't read the documentation

  • RMAN - obsolete command to delete without confirmation

    Hello world

    I created a small script witch remove obsolete or expired RMAN backups.

    The problem is: the delete "obsolete" and the command "delete expired backup" needs a confirmation by YES. Could I give the script the command this way, that I don't need to confirm the order and it deletes the backups directly?

    Here is my small script:
    #!/bin/ksh

export ORACLE_SID=dbtest2
export ORACLE_HOME=/home/oracle/srv/ora/product/11.2.0/dbtest_2
export ORACLE_BIN=/home/oracle/srv/ora/product/11.2.0/dbtest_2/bin
alias RMAN=$ORACLE_BIN/rman

RMAN target / > report_del_obsolete 2>&1 <<EOI

    delete expired backup;
    delete obsolete;
    quit

EOI
    Thanks for the answers and ideas!

    Kind regards
    David

    noprompt

  • RMAN delete obsolete job fails due to the error of peripheral distribution

    Experts, I need help, please.

    It's on Windows 10.2.0.1

    RMAN > DELETE NOPROMPT OBSOLETE;

    RMAN retention policy apply to the order
    RMAN retention policy is set to 3 days recovery window
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid = 130 devtype = DISK
    output channel: ORA_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
    RMAN-00571: ===========================================================
    RMAN-03002: failure of the delete command at 15/05/2012 14:10:17
    ORA-19554: error device allocation, type of device: SBT_TAPE device name:
    ORA-27211: unable to load the media management library


    I ran RMAN > set up the device type 'SBT_TAPE' clear;
    but I still get the same error.

    I backup to disk, not tape

    Note the reference to SBT_TAPE:

    RMAN configuration parameters are:
    SET UP THE DEVICE TYPE DISK PARALLELISM BACKUPSET BACKUP TYPE 1;
    SET UP THE DEVICE TYPE SBT_TAPE PARALLELISM 1 BACKUP BACKUPSET TYPE; # by default

    What should I do to be able to run REMOVE OBSOLETE;?

    Thank you, John

    Try to use the OVERLAPPING BACKUP first and then repeat DELETE OBSOLETE

  • Backups RMAN does not match its retention policy

    Hello

    I have two or three instances of PROD on Windows environment with 11.2.0.3 version of DB. RMAN retention policy is set to 14 days, but I noticed that the backup is showing greater than that.

    For example: backups whows LIST BACKUP OF DATABASE since October 13. I also checked the elements of part of netapp backup and they are present.

    DELETE NOPROMPT OBSOLETE do not remove whatever it is like expired backup.

    I have clear and defined retention to 14 days over policy but doesn't seem to work.

    I would be grateful suggestion (s) about the strange.

    Thank you very much.

    Best regards

    John-MK wrote:

    Hello

    I have two or three instances of PROD on Windows environment with 11.2.0.3 version of DB. RMAN retention policy is set to 14 days, but I noticed that the backup is showing greater than that.

    For example: backups whows LIST BACKUP OF DATABASE since October 13. I also checked the elements of part of netapp backup and they are present.

    DELETE NOPROMPT OBSOLETE do not remove whatever it is like expired backup.

    I have clear and defined retention to 14 days over policy but doesn't seem to work.

    I would be grateful suggestion (s) about the strange.

    Thank you very much.

    Best regards

    We would need to know what kind of backups and where they were taken.  Imagine this scenario:

    7-day retention strategy.

    Level 0 incremental backup taken on Sunday

    Backup incremental level 1 taken Monday at Sam.

    Let's say that October 1 is a Sunday, so we take an Inc.-0 backup on October 1 and again on Oct. 8.

    Now let's say that we are at 10 Oct.  Our 7-day retention policy dicatates that we can recover any day of return to 3 Oct.

    The only way we can find to 3 Oct is to start with this backup Inc.-0 Oct. 1.

    Recovery all starts with last Inc.-0 backup before the point in time to be recovered.  In a normal life, regularly cycling calendar of backups, actually will end you with backups 1 day far twice also older than your retention period.

    A more extreme example.  Same period of retention of 7 days, but after a single backup Inc. - 0, you don't take any backups of 3 months.  That only a backup is always necessary to apply your window of recovery and therefore is not obsolete, despite the fact it is 3 months old and your recovery window is 7 days.

    Also, you mention "expiration".  Regarding backups oracle, 'expired' isn't the same as "obsolete".

    "Obsolète" means "is more necessary to apply the principle of recovery."

    "Expired" is a little more complex.

    When a backup is performed, or an archivelog is written, an account of which is written in the repository.  When you do a 'crossover' rman, these repository records are compared to reality - to see if the archivelog or saved backup file actually exists.  Maybe someone used an OS command to delete them.  Any file found "go walkabout" have their directory of files marked as "expired".  An rman "expiration to delete" then delete the records in the repository.

  • Purge the rman backup

    Hello, since the alert.log file find this error:

    Errors in the /u01/oratest/diag/rdbms/test/TEST1/trace/TEST1_arc3_25352.trc file:
    ORA-19809: limit exceeded for file recovery
    ORA-19804: cannot retrieve 12582912 bytes limit 59055800320 disk space
    ARC3: 19809 creation error archive log file ' DATA01'+.
    Sea 25 09:51:58 Jan 2012
    Errors in the /u01/oratest/diag/rdbms/test/TEST1/trace/TEST1_arc0_25306.trc file:
    ORA-19815: WARNING: 59055800320 bytes db_recovery_file_dest_size is 100.00% used and has 0 bytes remaining available.
    ************************************************************************
    You have choice to free up space in the recovery area:
    + 1. Consider changing the RMAN RETENTION POLICY. If you are using Data Guard +.
    then consider changing POLICY of DELETE ARCHIVELOG RMAN.
    + 2. Back up files on a tertiary device such as a tape using RMAN.
    SAFEGUARDING RECOVERY AREA command.
    + 3. Add disk space and increase the db_recovery_file_dest_size setting to +.
    reflect the new space.
    + 4. Delete unnecessary files by using the RMAN DELETE command. If operation +.
    the system control has been used to remove the files, and then use the RMAN DUPLICATION and
    Commands DELETE has EXPIRED.
    ************************************************************************
    Errors in the /u01/oratest/diag/rdbms/test/TEST1/trace/TEST1_arc0_25306.trc file:
    ORA-19809: limit exceeded for file recovery
    ORA-19804: cannot retrieve 12582912 bytes limit 59055800320 disk space
    ARC0: error creating 19809 archive log file ' DATA01'+.

    So I'm trying to purge the rman backup, but I have an error message:


    rman target = oratest@oraprdlnx1:~$ /+.
    Recovery Manager: release 11.2.0.1.0 - Production on sea Jan 25 09:47:30 2012
    Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.
    connected to target database: TEST (DBID = 2044700519)

    + RMAN > show all; +.

    using the control file of the target instead of recovery catalog database
    RMAN settings for database with db_unique_name TEST are:
    CONFIGURE REDUNDANCY 1 RETENTION STRATEGY; # by default
    CONFIGURE BACKUP OPTIMIZATION # by default
    SET UP DEFAULT DISK DEVICE TYPE; # by default
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # by default
    SET UP THE DEVICE TYPE DISK PARALLELISM 1 BACKUP BACKUPSET TYPE; # by default
    CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default
    CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default
    CONFIGURE MAXSETSIZE TO UNLIMITED; # by default
    CONFIGURE ENCRYPTION OF DATABASE # by default
    CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default
    CONFIGURE COMPRESSION ALGORITHM 'BASIC' AND 'DEFAULT' LIBERATION OPTIMIZE FOR TRUE LOAD; # by default
    CONFIGURE THE NONE ARCHIVELOG DELETION POLICY; # by default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' / u01/oratest/product/11.2.0/dbhome_1/dbs/snapcf_TEST1.f'; # by default

    + RMAN > allocate channel for maintenance of type; disc +.

    allocated channel: ORA_MAINT_DISK_1
    channel ORA_MAINT_DISK_1: SID = 237 instance = type of TEST1 = DISK

    + RMAN > crosscheck backup; +.

    "" element of verified backup: turned out to be "AVAILABLE"
    backup handle piece = RECID = 68 = 758320264 STAMP DATA01/test/autobackup/2011_08_04/s_758320263.794.758320265 +.
    Cut objects 1

    RMAN > delete obsolete; ** +

    RMAN retention policy apply to the order
    RMAN retention policy is set to 1 redundancy
    Remove the following obsolete backups and copies:
    Making key time filename/handle type
    -------------------- ------ ------------------ --------------------
    Backup Set 25 July 4, 11
    Backup total 25 4 July 11 1omgk64v_1_1
    Backup Set 26 July 4, 11
    Backup total 26 July 4, 11 1pmgk650_1_1
    Backup Set 24 July 4, 11
    Total backup, 24 4 July 11 1qmgk650_1_1
    Backup Set 21 July 4, 11
    Backup total 21 4 July 11 1rmgk650_1_1
    Backup Set 28 July 4, 11
    28 1vmgk69v_1_1 July 4, 11 total backup
    Save game 29 July 4, 11
    Backup total 29 July 4, 11 20mgk6a0_1_1
    Backup Set 30 July 4, 11
    Backup total 30 4 July 11 21mgk6a0_1_1
    Save game 31 July 4, 11
    Backup total 31 July 4, 11 22mgk6a0_1_1
    Backup Set 34 4 July 11
    Backup total 34 4 July 11 c-2044700519-20110704-07
    Backup Set 35 July 4, 11
    Total backup, 35 26mgk8ib_1_1 4 July 11
    Backup Set 36 4 July 11
    Backup total 36 4 July 11 c-2044700519-20110704-08
    Backup Set 41 4 July 11
    Backup total 41 4 July 11 28mgk94i_1_1
    Backup Set 42 4 July 11
    Backup total 42 4 July 11 29mgk94j_1_1
    Backup Set 37 July 4, 11
    Backup total 37 4 July 11 2amgk94j_1_1
    Backup Set 40 July 4, 11
    Backup total 40 July 4, 11 2bmgk94j_1_1
    Backup Set 38 July 4, 11
    Backup total 38 4 July 11 2cmgk95c_1_1
    Backup Set 39 July 4, 11
    Backup total 39 4 July 11 2dmgk95k_1_1
    Backup Set 43 July 4, 11
    Backup total 43 July 4, 11 c-2044700519-20110704-09
    Backup Set 46 4 July 11
    Backup total 46 4 July 11 2fmgk99f_1_1
    Backup Set 47 July 4, 11
    Backup total 47 4 July 11 2gmgk99g_1_1
    Backup Set 44 4 July 11
    Backup total 44 4 July 11 2hmgk99g_1_1
    Backup Set 48 4 July 11
    Backup total 48 4 July 11 2imgk99g_1_1
    Backup Set 45 4 July 11
    Backup total 45 4 July 11 2jmgk9a9_1_1
    Backup Set 50 4 July 11
    Backup total 50 4 July 11 2kmgk9aq_1_1
    Backup Set 49 July 4, 11
    Backup total 49 4 July 11 2lmgk9aq_1_1
    Backup Set 51 4 July 11
    51 4 July total backup has 11 c-2044700519-20110704-0
    Backup Set 56 4 July 11
    Total backup 56 2rmgk9qb_1_1 July 4, 11
    Backup Set 55 July 4, 11
    Backup total 55 4 July 11 2smgk9qb_1_1
    Backup Set 58 4 July 11
    Backup total 58 4 July 11 b c-2044700519-20110704-0
    Backup Set 60 4 July 11
    Total backup 60 2umgk9tb_1_1 July 4, 11
    Backup Set 61 4 July 11
    Backup total 61 4 July 11 2vmgk9tc_1_1
    Backs up the entire 62 4 July 11
    Backup total 62 4 July 11 30mgk9tc_1_1
    Backup Set 66 4 July 11
    Backup total 66 4 July 11 34mgk9ua_1_1
    Backs up the entire 65 4 July 11
    Backup total 65 4 July 11 35mgk9ua_1_1
    Backup Set 67 4 July 11
    Total backup, July 4, 11 c-2044700519-20110704-0 67C
    RMAN-00571: ===========================================================
    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
    RMAN-00571: ===========================================================
    RMAN-03002: failure of the delete command to the 25/01/2012 09:48:42
    RMAN-06091: any string allocated for maintenance (of a suitable type)

    How can I purge the db dest file recovery?

    Thank you!!!

    RMAN-00571: ===========================================================
    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
    RMAN-00571: ===========================================================
    RMAN-03002: failure of the delete command to the 25/01/2012 09:48:42
    RMAN-06091: any string allocated for maintenance (of a suitable type)

    There is a metalink note that talks about this error.

    Met RMAN-03002 and RMAN-06091 when deleting obsolete backups [567555.1 ID]
    RMAN could not remove obsolete in right Backupsets change Sbt_tape to disk and again Server [ID 1287755.1]

    HTH

    Kind regards
    Nagendra Chillale

    Published by: NC on January 25, 2012 17:00

  • last available retention policy backup RMAN

    Hi all

    I'm on 11.2 and had a question regarding the rman... my ploicy of retention is set to 22 days see below
    RMAN> show all;

RMAN configuration parameters for database with db_unique_name TEST are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 22 DAYS;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO BACKUPSET PARALLELISM 1;
CONFIGURE DEVICE TYPE SBT_TAPE PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE 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

List of Backup Sets
===
    Published by: user8363520 on September 28, 2011 15:08

    Published by: user8363520 on September 28, 2011 15:09

    user8363520 wrote:
    Hi all

    I'm on 11.2 and had a question regarding the rman... my ploicy of retention is set to 8 days see below

    RMAN> show all;

RMAN configuration parameters for database with db_unique_name TRGT are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 8 DAYS;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/cont_spfile_%F';
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '%d_ctl_spfile_%F';
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO BACKUPSET PARALLELISM 1;
CONFIGURE DEVICE TYPE SBT_TAPE PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT   '/backups/%d_%t_%s_%p_%T';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 2 TIMES TO 'SBT_TAPE';
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/home/112_64/dbs/snapcf_TRGT.f'; # default

RMAN>

    but when I login and backup list... back were taken log time back still shows as AVAILABLE... I thought that it would be marked obsolete or expired... any reason why his does not like that? I had to change my couple of time format is why it dose not match the above... but just that I do not understand why his watch available?

    They are not 'marked' as outdated. They are "evaluated" as obsolete when necessary to meet demand for obsolete series. Notice what happens when I take three backups with a REDUNDANCY 2 retention policy

    RMAN> show retention policy;

using target database control file instead of recovery catalog
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;

RMAN> backup database;

Starting backup at 27-SEP-11

channel ORA_DISK_1: backup set complete, elapsed time: 00:01:25
Finished backup at 27-SEP-11

Starting Control File and SPFILE Autobackup at 27-SEP-11
piece handle=/orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983259_784vod4r_.bkp comment=NONE
Finished Control File and SPFILE Autobackup at 27-SEP-11

RMAN> backup database;

Starting backup at 27-SEP-11

channel ORA_DISK_1: backup set complete, elapsed time: 00:01:45
Finished backup at 27-SEP-11

Starting Control File and SPFILE Autobackup at 27-SEP-11
piece handle=/orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983476_784vw59k_.bkp comment=NONE
Finished Control File and SPFILE Autobackup at 27-SEP-11

RMAN> backup database;

Starting backup at 27-SEP-11

channel ORA_DISK_1: backup set complete, elapsed time: 00:01:55
Finished backup at 27-SEP-11

Starting Control File and SPFILE Autobackup at 27-SEP-11
piece handle=/orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983663_784w20hx_.bkp comment=NONE
Finished Control File and SPFILE Autobackup at 27-SEP-11

RMAN> list backup;

List of Backup Sets
===================

BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
113     Full    94.59M     DISK        00:01:18     27-SEP-11
        BP Key: 113   Status: AVAILABLE  Compressed: YES  Tag: TAG20110927T194613
        Piece Name: /orafra/HOUSTON/backupset/2011_09_27/o1_mf_nnndf_TAG20110927T194613_784vlpho_.bkp
  List of Datafiles in backup set 113


BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
114     Full    6.89M      DISK        00:00:01     27-SEP-11
        BP Key: 114   Status: AVAILABLE  Compressed: NO  Tag: TAG20110927T194739
        Piece Name: /orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983259_784vod4r_.bkp
  Control File Included: Ckp SCN: 1185229      Ckp time: 27-SEP-11
  SPFILE Included: Modification time: 27-SEP-11

BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
115     Full    94.59M     DISK        00:01:38     27-SEP-11
        BP Key: 115   Status: AVAILABLE  Compressed: YES  Tag: TAG20110927T194931
        Piece Name: /orafra/HOUSTON/backupset/2011_09_27/o1_mf_nnndf_TAG20110927T194931_784vrvqb_.bkp


BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
116     Full    6.89M      DISK        00:00:02     27-SEP-11
        BP Key: 116   Status: AVAILABLE  Compressed: NO  Tag: TAG20110927T195116
        Piece Name: /orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983476_784vw59k_.bkp
  Control File Included: Ckp SCN: 1185400      Ckp time: 27-SEP-11
  SPFILE Included: Modification time: 27-SEP-11

BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
117     Full    94.59M     DISK        00:01:50     27-SEP-11
        BP Key: 117   Status: AVAILABLE  Compressed: YES  Tag: TAG20110927T195228
        Piece Name: /orafra/HOUSTON/backupset/2011_09_27/o1_mf_nnndf_TAG20110927T195228_784vydks_.bkp


BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
118     Full    6.89M      DISK        00:00:02     27-SEP-11
        BP Key: 118   Status: AVAILABLE  Compressed: NO  Tag: TAG20110927T195423
        Piece Name: /orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983663_784w20hx_.bkp
  Control File Included: Ckp SCN: 1185555      Ckp time: 27-SEP-11
  SPFILE Included: Modification time: 27-SEP-11

RMAN> report obsolete;

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           113    27-SEP-11
  Backup Piece       113    27-SEP-11          /orafra/HOUSTON/backupset/2011_09_27/o1_mf_nnndf_TAG20110927T194613_784vlpho_.bkp
Backup Set           114    27-SEP-11
  Backup Piece       114    27-SEP-11          /orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983259_784vod4r_.bkp

RMAN> delete obsolete;

RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
using channel ORA_DISK_1
Deleting the following obsolete backups and copies:
Type                 Key    Completion Time    Filename/Handle
-------------------- ------ ------------------ --------------------
Backup Set           113    27-SEP-11
  Backup Piece       113    27-SEP-11          /orafra/HOUSTON/backupset/2011_09_27/o1_mf_nnndf_TAG20110927T194613_784vlpho_.bkp
Backup Set           114    27-SEP-11
  Backup Piece       114    27-SEP-11          /orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983259_784vod4r_.bkp

Do you really want to delete the above objects (enter YES or NO)? y
deleted backup piece
backup piece handle=/orafra/HOUSTON/backupset/2011_09_27/o1_mf_nnndf_TAG20110927T194613_784vlpho_.bkp recid=113 stamp=762983174
deleted backup piece
backup piece handle=/orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983259_784vod4r_.bkp recid=114 stamp=762983260
Deleted 2 objects

RMAN> exit

    or note this:

    RMAN> report obsolete;

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           115    27-SEP-11
  Backup Piece       115    27-SEP-11          /orafra/HOUSTON/backupset/2011_09_27/o1_mf_nnndf_TAG20110927T194931_784vrvqb_.bkp
Backup Set           116    27-SEP-11
  Backup Piece       116    27-SEP-11          /orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983476_784vw59k_.bkp

RMAN> CONFIGURE RETENTION POLICY TO REdundancy 6;

old RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
new RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO REDUNDANCY 6;
new RMAN configuration parameters are successfully stored

RMAN> report obsolete;

RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 6
no obsolete backups found

RMAN> CONFIGURE RETENTION POLICY TO REdundancy 1;

old RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO REDUNDANCY 6;
new RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
new RMAN configuration parameters are successfully stored

RMAN> report obsolete;

RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
Report of obsolete backups and copies
Type                 Key    Completion Time    Filename/Handle
-------------------- ------ ------------------ --------------------
Backup Set           115    27-SEP-11
  Backup Piece       115    27-SEP-11          /orafra/HOUSTON/backupset/2011_09_27/o1_mf_nnndf_TAG20110927T194931_784vrvqb_.bkp
Backup Set           116    27-SEP-11
  Backup Piece       116    27-SEP-11          /orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983476_784vw59k_.bkp
Backup Set           117    27-SEP-11
  Backup Piece       117    27-SEP-11          /orafra/HOUSTON/backupset/2011_09_27/o1_mf_nnndf_TAG20110927T195228_784vydks_.bkp
Backup Set           118    27-SEP-11
  Backup Piece       118    27-SEP-11          /orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983663_784w20hx_.bkp

RMAN> exit

  • RMAN - location on the backup disk full

    Hi guys, I have problem with RMAN backup of some databases is strongly exploited during a day. We have storage problem (disk backup destination) when you do the backup of it. I would like to change retention for this database from 2 to only 1 day because these disk backupsets heading a tape every night. But before I do that, I need free space on the backup disk that is almost 100% full.

    So my question is possible to delete old backup sets and continue the backup operation? If this is the case, I could just delete backupsets of RMAN, simply delete all backups of full disk location and simply take the new backup?

    I use this script to do the full backup:

    target connection.

    Run {}
    cross-checking of backup;
    obsolete report;
    delete noprompt obsolete;
    delete expired backup noprompt.
    backup database more entered archivelog delete;
    obsolete report;
    delete noprompt obsolete;
    delete expired backup noprompt.
    cross-checking of backup;
    }

    "exit";

    Published by: rootsman Sep 14, 2011 23:51

    Rootsman wrote:
    I'm sorry that I forgot to put numbers's database version 10.2.0.3 on RHEL4 OS 64-bit.
    I would like to delete the backup more to buy disc because this database uses disk storage space, and is to develop the database so therefor I decide to do in this way.

    Could you please give me a link or try to explain how to remove the backupsets that I have on the storage of full disk and continue with the operation to bakup? IM new in RMAN and I want to make sure that I'm doing the correct things.

    Thank you!

    According to my understandig of your question... you want to remove the last backup because you save it to tape. If it is problem, then remove the rman backup.

    RMAN > delete noprompt backup; and continue the backup for the next days

    RMAN > run {}
    backup database archivelog;
    delete noprompt obsolete;
    }

    I hope this help you :)

    Neeraj-

  • My backup archivelog never becomes obsolete for the deletion

    Hello

    I am running version 11.1.0.7.0 and backup using rman and tivoli backup as media management layer.

    I make daily backups for a week, weekly full backups for a month, complete monthly full backups kept for one year and annual full backups kept for 7 years.

    My general retention policy is 30 days:

    RMAN > show all.

    using the control file of the target instead of recovery catalog database
    RMAN settings for database with db_unique_name PRODPRIM are:
    CONFIGURE RETENTION POLICY to the WINDOW of RECOVERY OF 30 DAYS; *
    CONFIGURE BACKUP OPTIMIZATION
    SET UP DEFAULT DISK DEVICE TYPE;
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # by default
    SET UP THE DEVICE TYPE DISK PARALLELISM 8 TYPE OF BACKUP TO COMPRESSED BACKUPSET;
    CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1;
    CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default
    CONFIGURE MAXSETSIZE TO UNLIMITED;
    CONFIGURE ENCRYPTION OF DATABASE # by default
    CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default
    CONFIGURE COMPRESSION ALGORITHM 'BZIP2 '; # by default
    CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' / oracle/PROD/db/tech_st/11.1.0/dbs/snapcf_PROD_PRIM.f';


    The daily backup script is as below:

    RMAN > print script prod_daily;

    printing stored script: prod_daily
    +{+
    allocate channel t1 type 'sbt_tape' parms 'ENV=(TDPO_usrFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.usr) ';
    allocate channel t2 type 'sbt_tape' parms 'ENV=(TDPO_usrFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.usr) ';
    allocate channel t3 type 'sbt_tape' parms 'ENV=(TDPO_usrFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.usr) ';
    format "prod_dailybackup_ % d_ % s_ %t" Dungeon of the database backup to the time = ' sysdate 7' newspapers. +
    backup format 'prodarchbackup_ % d_ % s_ %t' archivelog all not saved 1 time;
    cross-checking of backup;
    overlap archivelog all;
    delete noprompt obsolete;
    delete expired backup noprompt.
    delete noprompt expired archivelog all;
    outline report;
    output channel t1;
    output channel t2;
    output channel t3;
    +}+

    This line: backup format + database "prod_dailybackup_ % d_ % s_ %t" keep until time = 'sysdate-7'-newspapers; I don't expect the archivelogs compulsory to recover from that backup backups will be kept and will expire when this backup expires.

    But when I list backup of archivelogs, I find archivelogs backups that were taken as early as next January, and the archivelog backups never get deleted or obsolete:

    RMAN >

    List of backup sets
    +===================+


    Time of accomplishment time BS key size Device Type
    ------- ---------- ----------- ------------ ---------------
    + 9485 M 326.00 SBT_TAPE 00:00:10: 28 - JAN-11 +.
    BP key: 9758 situation: AVAILABLE Tablet: NO Tag: TAG20110128T201149
    Handle: prodarchbackup_PROD_927_741643910 Media:

    List of newspapers archived in defined backup 9485
    The next time that THRD Seq YVERT low low time next YVERT
    ---- ------- ---------- --------- ---------- ---------
    4266 + 1 220134037 28 JANUARY 11 220161176 28 - JAN-11 +.
    + 1 4267 220161176 28 JANUARY 11 220184892 28 - JAN-11 +.
    4268 + 1 220184892 28 JANUARY 11 220218518 28 - JAN-11 +.
    + 1 4269 220218518 28 JANUARY 11 220230438 28 - JAN-11 +.
    + 1 4270 220230438 28 JANUARY 11 220273374 28 - JAN-11 +.
    4271 + 1 220273374 28 JANUARY 11 220278622 28 - JAN-11 +.
    4272 + 1 220278622 28 JANUARY 11 220282989 28 - JAN-11 +.
    4273 + 1 220282989 28 JANUARY 11 220285629 28 - JAN-11 +.
    + 1 4274 220285629 28 JANUARY 11 220287861 28 - JAN-11 +.
    + 1 4275 220287861 28 JANUARY 11 220290432 28 - JAN-11 +.
    4276 + 1 220290432 28 JANUARY 11 220293038 28 - JAN-11 +.
    + 1 4277 220293038 28 JANUARY 11 220295570 28 - JAN-11 +.
    4278 + 1 220295570 28 JANUARY 11 220302972 28 - JAN-11 +.

    Time of accomplishment time BS key size Device Type
    ------- ---------- ----------- ------------ ---------------
    + 9486 435,25 M SBT_TAPE 00:00:13: 28 - JAN-11 +.
    BP key: 9759 situation: AVAILABLE Tablet: NO Tag: TAG20110128T201149
    Handle: prodarchbackup_PROD_925_741643910 Media:

    List of newspapers archived in defined backup 9486
    The next time that THRD Seq YVERT low low time next YVERT
    + 'archivelog.log' [read-only] 11993 lines, characters 647140 +.


    Time of accomplishment time BS key size Device Type
    ------- ---------- ----------- ------------ ---------------
    + 9486 435,25 M SBT_TAPE 00:00:13: 28 - JAN-11 +.
    BP key: 9759 situation: AVAILABLE Tablet: NO Tag: TAG20110128T201149
    Handle: prodarchbackup_PROD_925_741643910 Media:

    List of newspapers archived in defined backup 9486
    The next time that THRD Seq YVERT low low time next YVERT
    ---- ------- ---------- --------- ---------- ---------
    + 1 4254 219859033 28 JANUARY 11 219894422 28 - JAN-11 +.
    + 1 4255 219894422 28 JANUARY 11 219919680 28 - JAN-11 +.
    + 1 4256 219919680 28 JANUARY 11 219942950 28 - JAN-11 +.
    4257 + 1 219942950 28 JANUARY 11 219967656 28 - JAN-11 +.
    4258 + 1 219967656 28 JANUARY 11 219976051 28 - JAN-11 +.
    4259 + 1 219976051 28 JANUARY 11 219987397 28 - JAN-11 +.
    + 1 4260 219987397 28 JANUARY 11 220006347 28 - JAN-11 +.
    + 1 4261 220006347 28 JANUARY 11 220025985 28 - JAN-11 +.
    4262 + 1 220025985 28 JANUARY 11 220047061 28 - JAN-11 +.
    4263 + 1 220047061 28 JANUARY 11 220074802 28 - JAN-11 +.
    + 1 4264 220074802 28 JANUARY 11 220102835 28 - JAN-11 +.
    + 1 4265 220102835 28 JANUARY 11 220134037 28 - JAN-11 +.

    Time of accomplishment time BS key size Device Type
    ------- ---------- ----------- ------------ ---------------
    + 9487 427,25 SBT_TAPE 00:00:14 M 28 - JAN-11 +.
    BP key: 9760 situation: AVAILABLE Tablet: NO Tag: TAG20110128T201149
    Handle: prodarchbackup_PROD_926_741643910 Media:

    List of newspapers archived in defined backup 9487
    The next time that THRD Seq YVERT low low time next YVERT
    ---- ------- ---------- --------- ---------- ---------
    + 1 4231 218972478 28 JANUARY 11 218974637 28 - JAN-11 +.
    + 1 4232 218974637 28 JANUARY 11 218976683 28 - JAN-11 +.
    + 1 4233 218976683 28 JANUARY 11 218979456 28 - JAN-11 +.
    4234 + 1 218979456 28 JANUARY 11 218981788 28 - JAN-11 +.
    + 1 4235 218981788 28 JANUARY 11 218984100 28 - JAN-11 +.
    4236 + 1 218984100 28 JANUARY 11 218986873 28 - JAN-11 +.
    + 1 4237 218986873 28 JANUARY 11 218990404 28 - JAN-11 +.
    + 1 4238 218990404 28 JANUARY 11 218993848 28 - JAN-11 +.
    + 1 4239 218993848 28 JANUARY 11 218998167 28 - JAN-11 +.
    ---------------------------------------------------------------------------------------------


    My question is, when these archivelog backups become obsolete and are deleted?

    Dula

    Published by: user13005731 on May 19, 2011 10:10

    Published by: user13005731 on May 19, 2011 10:11

    10.2, you have to specify NEWSPAPERS.

    10.2 documentation:
    http://download.Oracle.com/docs/CD/B19306_01/backup.102/b14194/rcmsynta035.htm#sthref554

    However, 11.1 and above, it is NOT necessary and, I would say, must not be specified.
    11.1 documentation:
    http://download.Oracle.com/docs/CD/B28359_01/backup.111/b28273/rcmsubcl011.htm#i97063
    «+ An archive backup is autonomous because is contains all the files needed to restore the backup and recover in a consistent state.» "If the database is open during backup, then RMAN automatically generates and saves them archived redo logs necessary for the protection of the compatible database.

    and
    http://download.Oracle.com/docs/CD/B28359_01/backup.111/b28270/wnbradv.htm#sthref6
    "+ Long term + improved backup management.
    + You can create a backup archiving or long-term with the BACKUP... "KEEP that keeps only the required log files archived to make consistent backup.

    and
    http://download.Oracle.com/docs/CD/B28359_01/backup.111/b28270/rcmbckba.htm#CHDHAFHJ
    "+ When you specify the DUNGEON on the BACKUP command, RMAN generates multiple backup sets. ...... It automatically generates a recovery archived log backup to ensure that the backup of the database can be recovered to a consistent state. »

    You could log a SR with support of Oracle to confirm if you need the key word "LOGS" in the BACKUP... KEEP and to identify the behavior if you happen to keep this in your backup command.

    In my humble OPINION, not be specify the LOGS of the BACKUP... KEEP.
    You could test this in a test environment by doing a BACKUP... MAINTAIN a database that has a very small WINDOW of RETENTION.

    Hemant K Collette
    http://hemantoracledba.blogspot.com

    Published by: Hemant K grapple on May 20, 2011 15:21
    Quotations in italics of the documentation.

  • recover before rman Windows

    Hello
    on 10 gr 2 on AIX.
    my windows of retention is 14 days.
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 14 DAYS;
    I have backups of March 30. I can copy them on the drive where the backup is stored (and deleted by RMAN expired) and then use the START CATALOG. I can't get to 30 March?
    Any changes made to the configuration of RMAN should be done before?
    Thank you.

    Yes, you should be able to recover
    Make sure that you do not delete obsolete ;)

  • RMAN BACKUP/RECOVERY OF DATA

    Hi friendz,.

    I have a legacy of or copied from earlier sources, RMAN backup scripts, which is the ff:

    (on the PROD server)
    rman
run {
     CONFIGURE CONTROLFILE AUTOBACKUP ON;
     CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u03/rman/%F';
     crosscheck archivelog all;
     backup format '/u03/rman/%d_LVL0_%T_%u_s%s_p%p' database plus archivelog;
     delete obsolete;
     delete expired archivelog all;
     }
    Then, I got the following output in/u03/rman:
    [root@oracleprod rman]# ls -l
total 75200672
-rw-rw----  1 oraprod oraprod    16089088 Feb 18 19:40 c-4174489363-20110218-01
-rw-rw----  1 oraprod oraprod 76882624512 Feb 18 19:39 OAPROD_LVL0_20110218_0gm50de6_s16_p1
-rw-rw----  1 oraprod oraprod    31554048 Feb 18 19:40 OAPROD_LVL0_20110218_0hm50fks_s17_p1
    I copied the files above to/u03/rman to the TEST server. I have also the same Oracle Home.
    How can I recover these files on our TEST Server?

    I tried:
    rman
run {
     startup mount;
     restore database;
     recover database;
    alter database open;
}
    but I got error:
    [oraprod@oel5 ~]$ rman target /

Recovery Manager: Release 9.2.0.6.0 - Production

Copyright (c) 1995, 2002, Oracle Corporation.  All rights reserved.

connected to target database (not started)

RMAN> startup mount;

Oracle instance started
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of startup command at 02/21/2011 22:31:09
ORA-00205: error in identifying controlfile, check alert log for more info

RMAN>
    Help, please...


    Thank you

    You must restore the controlfile first.

    STARTUP NOMOUNT
RESTORE CONTROLFILE FROM '/u03/rman/c-4174489363-20110218-01' ;
sql 'alter database mount';
RESTORE DATABASE;
RECOVER DATABASE;

    Hemant K Collette

  • RMAN script exit shell after backup

    Hello

    I have the following on AIX 6.1, Oracle 11.2.0.1.0 script:

    export ORACLE_HOME=/oracle/medprod/product/11.2.0/dbhome_1
    export ORACLE_SID = MEDPROD
    export PATH = $ORACLE_HOME/bin: $PATH
    Export LOG_DIR = / home/medinous/backup/logs
    Export LOG_FILE = $LOG_DIR/medprod_daily_backup_ ' date of +%d%m%Y%X'.log
    RMAN target / catalog log rman/rman@rman = $LOG_FILE < < EOF
    *{*
    Run the medinous_daily script.
    *}*
    "exit";
    EXIT;
    EXPRESSIONS OF FOLKLORE


    and:

    printing stored script: medinous_daily
    +{+
    allocate channel t1 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt) ';
    allocate channel t2 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt) ';
    allocate channel t3 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt) ';
    database backup in format "medinous_dailybackup_ % d_ % s_ %t ';
    backup format 'medinous_dailyarchbackup_ % d_ % s_ %t' archivelog all not saved 1 time;
    cross-checking of backup;
    delete noprompt obsolete;
    delete expired backup noprompt.
    delete noprompt expired archivelog all;
    output channel t1;
    output channel t2;
    output channel t3;
    +}+


    For some reason, the rman, on demand via crontab script was not released after successful backup, the process just to stay alive, even if there is a command explicitly to leave at the end.


    Any idea?

    Dula

    Have you tried with a block of the RACE:

    run
{
execute script medinous_daily;
}
exit;

  • backup with rman

    Hello, I have several questions about rman.

    I have an Oracle RAC with 3 knots in Suse Linux Enterprise Server 10 on IBM's PowerPC, and I want a script for the backup of this database.

    My database is in archivelog and I multiplex that it again online connects two diferent locations
    Location 1 = >/u01/redo_log
    Site 2 = >/u02/redo_log

    Also, I have MUX logs oracle archived in two different places:

    Location 1 = >/u01/archive_log
    Site 2 = >/u02/archive_log

    I want a full backup of my database, for that, I think I have to configure somethings in Oracle rman like this:


    -Configure the backup to a disc (AREA of RECOVERY FLASH)
    DATABASE BACKUP AS BACKUPSET DEVICE TYPE DISK;

    -Backup of database and archivelog and delete all archive logs after backup. is true?
    DATABASE BACKUP AS BACKUPSET MORE ARCHIVELOG DELETE ALL ENTRIES;

    -Implementation of a strategy for retention of 7 days (I'm going to recovery all data from my database in 7 days)
    CONFIGURE RETENTION POLICY TO RECOVERY OF 7-DAY WINDOW;

    -Save our backup controlfile
    CONFIGURE CONTROLFILE AUTOBACKUP ON;

    OK, I want archivelogs auto removal in slot 1 (/ u01/archive_log) and 2 (archive_log/u02 /) when I have a backup of it, because I don't have a lot of space on the disk.

    My AREA of RECOVERY FLASH did not have a lot of space and I put a 7 day recovery window, then oracle delete backups obsolete or expired, IS TRUE?

    Well, I have the peripheral band but connect directly to any of my 3 knots, because I do not have the drivers for IBM PowePC, so I want to periodically copy to another server, and then copy the FRA in this new server Ribbon. I need before Oracle removes the obsolete backupset, is true?

    If I save all my backupsets to Ribbon I will be can restore all data to 3 months ago?

    Thank you very much

    PD: Excuseme, but I'm Spanish and my English is terrible, horrible!

    The RECOVERY WINDOW is part of the RETENTION STRATEGY.

    If you have defined a RECOVERY WINDOW of 5 days and you daily full backups or full backups every 2/3 days, over 5 days of backups would be OBSOLETE.
    However, if you perform only full weekly backups, full backup of last Sunday is not obsolete (even if it seems to be beyond the 5 day window). Oracle expects that the backup is available.
    However, if you moved it off disc then you have to manually restore this backup to disk first before the DATABASE RESTORE is on it.

    Therefore, to answer your question: even if the RECOVERY WINDOW is 5 days, if my last (or 'later') full backup is 6 or 7 days ago, that the backup is NOT deprecated by Oracle and is used for the RESTORATION. Of course, Oracle then, in my example above, apply to an incremental backup on Friday and then updated by ArchiveLogs on Friday has left.

    (Similarly for the full backup being restrained, ArchiveLogs are also retained by Oracle and not obsolete, because they are needed for the revival of this full backup)

  • Problem with deleting obsolete controlfile copy

    Hello gurus,

    Please help me with this problem.

    RMAN backup failure on a database, run 11.2.0.3 on win 2008R2 x 64.

    H:\ > target rman.

    Recovery Manager: release 11.2.0.3.0 - Production on Fri 22 12:11:17 June 2012

    Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.

    connected to target database: ECDB (DBID = 3504538967)

    RMAN > obsolete report.

    using the control file of the target instead of recovery catalog database
    RMAN retention policy apply to the order
    RMAN retention policy is set to 1 redundancy
    Report of obsolete backups and copies
    Making key time filename/handle type
    -------------------- ------ ------------------ --------------------
    Control file copy 74 11 April 12 E:\ECDB\BACKUPSET\SNCDECDB. ORA

    RMAN > delete noprompt obsolete;

    RMAN retention policy apply to the order
    RMAN retention policy is set to 1 redundancy
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID = 385 type device = DISK
    Remove the following obsolete backups and copies:
    Making key time filename/handle type
    -------------------- ------ ------------------ --------------------
    Control file copy 74 11 April 12 E:\ECDB\BACKUPSET\SNCDECDB. ORA
    delete the copy of control files
    control file copy file name = E:\ECDB\BACKUPSET\SNCDECDB. ORA RECID = STAMP 74 = 780321276
    1 items deleted


    RMAN > obsolete report.

    RMAN retention policy apply to the order
    RMAN retention policy is set to 1 redundancy
    Report of obsolete backups and copies
    Making key time filename/handle type
    -------------------- ------ ------------------ --------------------
    Control file copy 74 11 April 12 E:\ECDB\BACKUPSET\SNCDECDB. ORA

    RMAN > DELETE FORCE CONTROLFILECOPY ' E:\ECDB\BACKUPSET\SNCDECDB. ORA';

    output channel: ORA_DISK_1
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID = 385 type device = DISK
    List of Copies of control files
    ===========================

    S time delay key cash YVERT cash
    ------- - --------------- ---------- ---------------
    74 X 11-APR-12 61418837 11 APRIL 12
    Name: E:\ECDB\BACKUPSET\SNCDECDB. ORA
    Tag: TAG20120411T115434


    You sure you want to delete the items above (enter YES or NO)? YES
    delete the copy of control files
    control file copy file name = E:\ECDB\BACKUPSET\SNCDECDB. ORA RECID = STAMP 74 = 780321276
    1 items deleted


    RMAN > obsolete report.

    RMAN retention policy apply to the order
    RMAN retention policy is set to 1 redundancy
    Report of obsolete backups and copies
    Making key time filename/handle type
    -------------------- ------ ------------------ --------------------
    Control file copy 74 11 April 12 E:\ECDB\BACKUPSET\SNCDECDB. ORA

    RMAN >

    My question is why is the obsolete file not deleted with the time to end 11-Apr-12.

    Please try this command

    RMAN > overlapping copies of the controlfile;
    RMAN > remove copy out-of-date controlfile;

    Also try this one

    RMAN > remove obsolete force.

    Talip Hakan Öztürk
    http://taliphakanozturken.WordPress.com/

Maybe you are looking for

  • I me no sound notification messages and delete automatically

    I upgraded my software and now I get no notification sound for my messages and delete messages after a certain time.

  • I use Time Machine?

    I use a Mac mini (end of 2014), and I pretty much only contained iTunes, a few documents and Pages numbers I really protect. Most of my use of this Mac mini is surfing on the internet and the steam games. The question is do I really Time Machine, my

  • iPhone 4S syncs not on iTunes

    I have an iPhone 4S which I inherited from my son.  I would like to sync the iPhone to my MacBook (OS X 10.6.8) 2.1 with iTunes 11.4, but when I plug my iPhone into the MacBook SB, I get a notification that I have to update my iTunes to the latest ve

  • second battery

    Hello I would like to know what model (type) is the second battery for Elitbook HP 8540p. thenk much

  • Button of the camera - a big problem

    Is there anyway to cancel the camera button when on the standby or home screen. The phone is so big that my hand every time keep pressing the camera button. It's really a big problem.