Archivelogs aren't frm RMAN Delete


Hello world

Linux meachine

11.2.0.3 version of db.

We run backup Rman Level0 Sundays and daily level1.

retention policy is 7 days recovery window,

each backup of Level0, it will clean the obsolete backupset and archivelogs,.

but the two are not the removal of the backup. and again I changed policy rentetion 2 days still I run backup stil, is not delete anything

my destination of archive is FRA,

It comes to my Rman Script for the level 0 backup.

BACKUP

as compressed backupset

TAG hb_level_0_$ {LOGDATE}

INCREMENTAL LEVEL 0 DATABASE plus ARCHIVELOG;

OUTPUT CHANNEL ch00;

}

# list the existing backups

REMOVE WINDOW OF 7 DAYS NOPROMPT OBSOLETE RECOVERY;

I want to delete the archives and the backupset, i.e. older more of 7 days if you please suggest me how to do it.

Thanks in advance,

Kind regards

Sanjay...

2713139 wrote:

Dear EdStevens,

Once again thanks for your response.

I heard clearly,

1 August 30 th I have full backup and 3rd I have full backup.

today is 5 th if I put the recovery of 2 days retention policy window, in my rman script.  If I run this script today so it will remove celebrate 3rd August,?

Now that could go down to the time of day when you issue the command.  You do this on the 5th.  You work with a payback period of 2 days.  Two days before the 5th is 3d, but that 'two days' will be calculated to the second.  If you deliver your DELETE OBSOLETE (with a two-day recovery period) at 13:23:42 5, your window of recovery begins at 13:23:42 of the third.  So it comes up when on the 3d doing backup complete?

or

If I put the window of political recovery of retention 4 days, then will remove obsolete backupset before August 30. Am I wrong?

Should be.

2. Iam using the command to remove the obsolete is 'delete noprompt obsolete recovey window of 3 days' in the rman script

. OK, so which straddles too everything that you had specified with a command SET.  And your recovery window will be exactly 72 hours, zero minutes and zero seconds of time in which you run this command.

3. If I'm not mistaken 'backup archivelog delete all input' this command remove the archivelogs that have been backed up?

It does exactly what the doc says it does.  See BACKUP

4. do I need to issue 'backup archivelog delete all input' command for the archives, because normally when we mention recovery window obsolete in Rman this script will delete all archivelog and backupset?

Once again... Backupsets, removes only DELETE OBSOLETE.

Archivelogs aren't backupsets.

BackupSets can contain the backups of archivelogs.  But a backupset that contains an archivelog backup is not the same as the archivlog itself, which is the archivelog destination.

Thanks for your patience and time...

Kind regards

Sanjay.

Tags: Database

Similar Questions

  • RMAN: Deletion retention policy policy VS Archivelog

    I am a newbie to RMAN, so I did a lot of reading and experimentation, and I'm stuck on a problem.

    TASK: I want to keep two days of archived newspapers and a days worth of backups.

    SOLUTION: set 1 retention policy, set the deletion policy to archive 2

    (CONFIGURE ARCHIVELOG DELETION of SAVED POLICY 2 TIMES TO THE DISK.)

    and it's my simple backup script

    run

    {

    database backup "nightly_backup" tag more archivelog;

    delete noprompt obsolete;

    }

    PROBLEM: it does not work. Oracle documentation clearly (as clearly as possible the documentation) that "remove obsolete" uses the retention policy to clear logs archived. and deletion policy deletion archivelog to use "delete archivelog all;

    My tests verifies this.

    ISSUE. How remove the database obsolete backupsets ONLY by using the delete command?

    -Mark

    Just for clarity - if other people who have this issue will find this thread-I found the answer.

    Two policies are in effect only when you use the quick recovery for all your backup needs area. The database will automatically manage files according to policies. But as soon as you run manually ' rman > delete noprompt obsolete ' Oracle will only follow the retention policy.

    So as soon as FRA got up to about 78 percent full, he began to delete files, you can see in the alert.log

    Deleted Oracle managed file +FRA/sndbox/backupset/2014_07_23/annnf0_nightly_backup_0.435.853650191

    Deleted Oracle managed file +FRA/sndbox/archivelog/2014_07_23/thread_1_seq_204.439.853668327

    Deleted Oracle managed file +FRA/sndbox/autobackup/2014_07_23/s_853650247.441.853650249

    Deleted Oracle managed file +FRA/sndbox/archivelog/2014_07_23/thread_2_seq_189.434.853668653

    Another consequence of this fun is that Oracle will not automatically manage files outside of the FRA. So, if you save FRA on the disk, Oracle removes only files of FRA. If you must manually remove FRA backups, but which will also remove the FRA files according to the retention policies.

  • Help remove backups rman (delete the repository)

    Hi all.

    I will soon be administering a few databases Oracle (11g Rel2). Currently these DBs area in log mode archive with a backup rman in place policy.


    I don't like this policy and you want to use my own, incremental backups from updadateable, so this is the plan I have in mind.


    (1) disable mode archive.


    (2) a clean shutdown and take a backup to cold.


    (3) since after you disable archiving, backups RMAN ALL will be unusable, I want to remove them (including newspapers archive and backup sets).


    (4) after the correct deletion, set up some persistent RMAN settings, such as retention policy, controlfile autobackup and optimization.


    (5) turn on archiving


    (6) to set up the new policy based backups backup incremental updateable with duplex location for archiving logs.


    Help is requested on the best way to clean all the backups (3).


    I can manually delete the backups and do overlap, but according to the Oracle Documentation "Delete backup" will be delete all backups for data recorded in the RMAN Repository.


    So which is the best way easier and faster? Will delete backup include the archive logs?


    Thanks in advance. Luis!


    myluism wrote:

    Can I still use them?

    I would say it is "the wrong answer to evil. When you disable log mode archive, you can only back up the database when it is stopped and only to restore and recover the database until the last stop.

    Looking at your plan, I wonder what you are trying to accomplish first log mode archive disabling and then enabling archive mode log again. Why do you think that this is necessary and what you're trying to accomplish.

    You need not disable and enable log mode archive in order to eliminate the obsolete achivelogs.

    If you are not satisfied with the retention policy, simply change it. All backups that are outside your retention policy will be considered as obsolete and you can remove them using RMAN delete obsolete, which will remove all files as well as the appropriate data backup from the RMAN Repository.

    For example you can archivelog delete all the entries backup and then delete the backupset or remove them at the OS level, do overlap and then use delete noprompt expired archivelog all.

    The retention policy applies to backup and archivelogs. However, you can have a separate archivelog deletion policy that applies to archivelogs.

  • RMAN delete policy has not worked and not delete outdated backup

    Hi all

    I am facing a problem this obsolete backup is not delete unwanted backup.

    I used to take level 0 once weekly and cumulative incremental in 3 times a day.

    I have 2 TB hard drive, every week, I used the backup from command remove obsolete based file can delete based on my redundancy strategy 1.

    The previous week it works fine and deleted obsolete backup based on the deletion policy. but this week when I try to use the delete obsolete command, it is not removed and the hard drive is always full and I couldn't take later backup.

    It's live server, I need to take the free space on the hard drive. Please help me.

    You will find details of error that I met in the log file.

    output channel: C1

    output channel: C2

    RMAN-00571: ===========================================================

    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.

    RMAN-00571: ===========================================================

    RMAN-03002: failure of backup so archivelog command at 05/05/2015 10:57:14

    ORA-19502: write error on file 'G:\RMAN\AWSPROCESS\BACKUP\AWSPROCESS\BACKUPSET\2015_05_05\O1_MF_NNND1_TAG20150505T090032_BNJGC9RR_. BKP", the number of block 7227648 (block size = 8192)

    ORA-27070: async read/write failed

    OSD-04016: error queuing an asynchronous i/o request.

    S/O-error: (OS 112) there is not enough space on the disk.

    Your backup on May 02 is not a valid backup, then you can try something like:

    RMAN > delete database backup completed after 'sysdate-6 ";

  • 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

  • RMAN delete archivelog until time > 2 h

    guys,

    I want to use within rman.

    RMAN {}
    RUN {}
    FORMAT DISK of TYPE ALLOCATE CHANNEL ch01 "lah bla";

    BACKUP
    ARCHIVELOG ALL
    ARCHIVELOG DELETE until "2 hours ago" saved 1 time to the device type sbt;
    Ch01 CHANNEL;
    }


    How to translate that "more than 2 hours there is" language RMAN

    Published by: user2579172 on March 29, 2010 13:19

    NOPROMPT

    Removes the specified files without asking for confirmation or listing the files. DELETE NOPROMPT displays each item as it is removed.

  • The front last backup RMAN delete file even if redundancy on 3 days

    Dear Oracle gurus

    My environment
    Node 2 11g R2 Cluster with ASM
    Database 11.2.0.3.0

    I got to know that file below is delete by RMAN even if redundancy on 3 days
    * 19M rman_bkp_3uo9vf2f_1_1_ORCL_20130518_DATAFILE_LVL1_18_05_2013 * is removed

    can you please provide a reason or recommendations to correct the backup configuration

    =========Before Backup========================================
    917M rman_bkp_1jo97nk1_1_1_ORCL_20130509_DATAFILE_LVL0_09_05_2013
    Rman_bkp_1ko97nk1_1_1_ORCL_20130509_DATAFILE_LVL0_09_05_2013 669M
    Rman_bkp_1ro9ac02_1_1_ORCL_20130510_DATAFILE_LVL1_10_05_2013 101M
    64M rman_bkp_1so9ac02_1_1_ORCL_20130510_DATAFILE_LVL1_10_05_2013
    116M rman_bkp_23o9d0br_1_1_ORCL_20130511_DATAFILE_LVL1_11_05_2013
    Rman_bkp_24o9d0br_1_1_ORCL_20130511_DATAFILE_LVL1_11_05_2013 85M
    1003M rman_bkp_2bo9fko2_1_1_ORCL_20130512_DATAFILE_LVL0_12_05_2013
    689M rman_bkp_2co9fko2_1_1_ORCL_20130512_DATAFILE_LVL0_12_05_2013
    87M rman_bkp_2jo9i942_1_1_ORCL_20130513_DATAFILE_LVL1_13_05_2013
    Rman_bkp_2ko9i942_1_1_ORCL_20130513_DATAFILE_LVL1_13_05_2013 73M
    110M rman_bkp_2so9ktg1_1_1_ORCL_20130514_DATAFILE_LVL1_14_05_2013
    Rman_bkp_2to9ktg1_1_1_ORCL_20130514_DATAFILE_LVL1_14_05_2013 103M
    115M rman_bkp_34o9nhs2_1_1_ORCL_20130515_DATAFILE_LVL1_15_05_2013
    88M rman_bkp_35o9nhs2_1_1_ORCL_20130515_DATAFILE_LVL1_15_05_2013
    1011M rman_bkp_3co9q682_1_1_ORCL_20130516_DATAFILE_LVL0_16_05_2013
    701M rman_bkp_3do9q682_1_1_ORCL_20130516_DATAFILE_LVL0_16_05_2013
    226M rman_bkp_3ko9sqkk_1_1_ORCL_20130517_DATAFILE_LVL1_17_05_2013
    215M rman_bkp_3lo9sqkl_1_1_ORCL_20130517_DATAFILE_LVL1_17_05_2013
    * 230M rman_bkp_3so9vf1v_1_1_ORCL_20130518_DATAFILE_LVL1_18_05_2013 *.
    * 568M rman_bkp_3to9vf20_1_1_ORCL_20130518_DATAFILE_LVL1_18_05_2013 *.
    * 19M rman_bkp_3uo9vf2f_1_1_ORCL_20130518_DATAFILE_LVL1_18_05_2013 *.
    ===========================================================================

    ===================After Backup========================================================
    -rw - r - 1 oracle oinstall 1049755648 12 May 20:05 rman_bkp_2bo9fko2_1_1_ORCL_20130512_DATAFILE_LVL0_12_05_2013
    -rw - r - 1 oracle oinstall 720715776 12 May 20:05 rman_bkp_2co9fko2_1_1_ORCL_20130512_DATAFILE_LVL0_12_05_2013
    -rw - r - 1 oracle oinstall 91013120 13 May 20:05 rman_bkp_2jo9i942_1_1_ORCL_20130513_DATAFILE_LVL1_13_05_2013
    -rw - r - 1 oracle oinstall 75726848 13 May 20:05 rman_bkp_2ko9i942_1_1_ORCL_20130513_DATAFILE_LVL1_13_05_2013
    -rw - r - 1 oracle oinstall 114327552 14 May 20:05 rman_bkp_2so9ktg1_1_1_ORCL_20130514_DATAFILE_LVL1_14_05_2013
    -rw - r - 1 oracle oinstall 107782144 14 May 20:05 rman_bkp_2to9ktg1_1_1_ORCL_20130514_DATAFILE_LVL1_14_05_2013
    -rw - r - 1 oracle oinstall 120307712 15 May 20:05 rman_bkp_34o9nhs2_1_1_ORCL_20130515_DATAFILE_LVL1_15_05_2013
    -rw - r - 1 oracle oinstall 91226112 15 May 20:05 rman_bkp_35o9nhs2_1_1_ORCL_20130515_DATAFILE_LVL1_15_05_2013
    -rw - r - 1 oracle oinstall 1058840576 16 May 20:05 rman_bkp_3co9q682_1_1_ORCL_20130516_DATAFILE_LVL0_16_05_2013
    -rw - r - 1 oracle oinstall 733757440 16 May 20:05 rman_bkp_3do9q682_1_1_ORCL_20130516_DATAFILE_LVL0_16_05_2013
    -rw - r - 1 oracle oinstall 236716032 17 May 20:05 rman_bkp_3ko9sqkk_1_1_ORCL_20130517_DATAFILE_LVL1_17_05_2013
    -rw - r - 1 oracle oinstall 224174080 17 May 20:05 rman_bkp_3lo9sqkl_1_1_ORCL_20130517_DATAFILE_LVL1_17_05_2013
    -rw - r - 1 oracle oinstall 594411520 18 May 20:06 rman_bkp_3to9vf20_1_1_ORCL_20130518_DATAFILE_LVL1_18_05_2013
    -rw - r - 1 oracle oinstall 240123904 18 May 20:06 rman_bkp_3so9vf1v_1_1_ORCL_20130518_DATAFILE_LVL1_18_05_2013
    -rw - r - 1 oracle oinstall 1073741824 19 May 20:06 rman_bkp_45oa23eh_1_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013
    -rw - r - 1 oracle oinstall 1073741824 19 May 20:06 rman_bkp_44oa23eg_1_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013
    -rw - r - 1 oracle oinstall 254590976 19 May 20:06 rman_bkp_45oa23eh_2_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013
    -rw - r - 1 oracle oinstall 709885952 19 May 20:07 rman_bkp_44oa23eg_2_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013
    -rw - r - 1 oracle oinstall 19234816 19 May 20:07 rman_bkp_46oa23f7_1_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013
    ==================================================================================


    Configuration of RMAN
    bash-$3.2 rman target /.

    Recovery Manager: release 11.2.0.3.0 - Production the Sun may 19 14:34:26 2013

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

    connected to target database: ORCL (DBID = 3171721304)

    RMAN > show all.

    using the control file of the target instead of recovery catalog database
    RMAN settings for database with db_unique_name ORCLDR are:
    CONFIGURE REDUNDANCY 3 RETENTION STRATEGY;
    CONFIGURE BACKUP OPTIMIZATION
    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/app/oracle/product/11.2.0/db_1/dbs/snapcf_orcldr2.f'; # by default

    RMAN > exit
    =========================================================================================
    RMAN Full Backup Script
    RMAN level 0
    #! / bin/bash
    . /Home/Oracle/.bash_profile
    logloc = 'date' + rman_backup_lvl0_orcldr_ %m %y hour %M %S %d ".log
    Target of $ORACLE_HOME/bin/rman = / log = / backup/RMAN_Log / $logloc < < EOF
    run
    {
    allocate channels ch1 type disk maxpiecesize = 1024 M;
    allocate channel ch2 type disk maxpiecesize = 1024M;
    database backup incremental level 0 FORMAT ' / backup/RMAN_Backup/rman_bkp_%U_%d_%T_DATAFILE_LVL0_%D_%M_%Y'
    include current controlfile more archivelog delete all entries
    tag 'datafile_full ';
    }
    delete noprompt obsolete;
    EXIT;
    EXPRESSIONS OF FOLKLORE
    =========================================================================================

    Backup logs
    -bash-3, $ 2 cat rman_backup_lvl0_ORCLdr_190513200501.log

    Recovery Manager: release 11.2.0.3.0 - Production the Sun may 19 20:05:01 2013

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

    connected to target database: ORCL (DBID = 3171721304)

    RMAN >
    RMAN > 2 > 3 > 4 > 5 > 6 > 7 > 8 >
    using the control file of the target instead of recovery catalog database
    allocated channel: ch1
    channel ch1: SID = instance 1753 = ORCLdr2 = DISK device type

    allocated channel: ch2
    channel ch2: SID = 5 = device type ORCLdr2 = DISK instance


    From backup may 19, 13
    Current archived log
    archived journal of wire 1 to jump with sequence 84; already saved
    skip the journal archived thread 2 with sequence 79; already saved
    channel ch1: Startup archived log backup set
    channel ch1: specifying the newspapers archived in the backup set
    archived journal entry thread = 2 sequence = 81 RECID = 388 STAMP = 815810424
    archived journal entry thread = 1 sequence = 85 RECID = 385 STAMP = 815793508
    archived journal entry thread = 1 sequence = 86 RECID = 389 STAMP = 815810426
    archived journal entry thread = 1 sequence = 87 RECID = 391 STAMP = 815828071
    channel ch1: from room 1 to May 19, 13
    channel ch2: Startup archived log backup set
    channel ch2: specifying the newspapers archived in the backup set
    archived journal thread = sequence 2 = 82 entry RECID = 396 STAMP = 815861105
    archived journal entry thread = 1 sequence = 88 RECID = 393 = 815846442 STAMP
    archived journal entry thread = 1 sequence = 89 RECID = 397 STAMP = 815861108
    channel ch2: from room 1 to May 19, 13
    channel ch1: finished piece 1 to May 19, 13
    piece handle=/u01/app/oracle/product/11.2.0/db_1/dbs/42oa23bp_1_1 tag = DATAFILE_FULL comment = NONE
    channel ch1: from part 2 to May 19, 13
    channel ch2: finished piece 1 to May 19, 13
    piece handle=/u01/app/oracle/product/11.2.0/db_1/dbs/43oa23bp_1_1 tag = DATAFILE_FULL comment = NONE
    channel ch2: from part 2 to May 19, 13
    channel ch1: finished part 2 to May 19, 13
    piece handle=/u01/app/oracle/product/11.2.0/db_1/dbs/42oa23bp_2_1 tag = DATAFILE_FULL comment = NONE
    channel ch1: from 3 to 19 May 13 piece
    channel ch2: finished part 2 to May 19, 13
    piece handle=/u01/app/oracle/product/11.2.0/db_1/dbs/43oa23bp_2_1 tag = DATAFILE_FULL comment = NONE
    channel ch2: complete set of backups, time: 00:01:10
    channel ch2: archived deletion or newspapers
    name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_2_82_814540431.arc RECID archived log file = 396 STAMP = 815861105
    name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_1_88_814540431.arc RECID archived log file = 393 = 815846442 STAMP
    RMAN-08137: WARNING: log archived not deleted, necessary for intelligence or upstream collection procedure
    Archive log file name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_1_89_814540431.arc thread = 1 sequence = 89
    channel ch2: archived deletion or newspapers
    name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_1_84_814540431.arc RECID archived log file = 383 STAMP = 815774802
    name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_2_79_814540431.arc RECID archived log file = 378 STAMP = 815774705
    channel ch1: finished part 3 to 19 May 13
    piece handle=/u01/app/oracle/product/11.2.0/db_1/dbs/42oa23bp_3_1 tag = DATAFILE_FULL comment = NONE
    channel ch1: complete set of backups, time: 00:01:25
    channel ch1: archived deletion or newspapers
    name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_2_81_814540431.arc RECID archived log file = 388 STAMP = 815810424
    name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_1_85_814540431.arc RECID archived log file = 385 STAMP = 815793508
    name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_1_86_814540431.arc RECID archived log file = 389 STAMP = 815810426
    name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_1_87_814540431.arc RECID archived log file = 391 STAMP = 815828071
    Backup finished on 19 May 13

    From backup may 19, 13
    channel ch1: start the incremental level 0 datafile backup set
    channel ch1: specification-datafile in the backup set (s)
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/statistics2013_5.dbf 00009
    Enter a number of file datafile = 00001 name=+ORASYS/ORCLdr/datafile/system.257.814500985
    Enter a number of file datafile = name=+ORASYS/ORCLdr/datafile/undotbs1.259.814500991 00003
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/app2.dbf 00006
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/app.dbf 00008
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/users01.dbf 00011
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/users03.dbf 00013
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/users05.dbf 00015
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/users07.dbf 00017
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/cdr2013_5.dbf 00019
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/cdr2013_7.dbf 00021
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/cdr2013_9.dbf 00023
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/cdr2013_11.dbf 00025
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/cdrmaxdat.dbf 00027
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/sidradcdr.dbf 00029
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/statistics2013_8.dbf 00031
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/statistics2013_10.dbf 00033
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/interimcdr2013_5.dbf 00037
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/nterimcdr2013_7.dbf 00039
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/interimcdr2013_9.dbf 00041
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/nterimcdr2013_11.dbf 00043
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/nterimcdrmaxdat.dbf 00045
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/sidradinterimcdr.dbf 00047
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/reports.dbf 00048
    channel ch1: from room 1 to May 19, 13
    channel ch2: start the incremental level 0 datafile backup set
    channel ch2: specification-datafile in the backup set (s)
    Enter a number of file datafile = name=+ORASYS/ORCLdr/datafile/sysaux.256.814500977 00002
    Enter a number of file datafile = 00005 name=+ORASYS/ORCLdr/datafile/undotbs2.258.814500987
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/namestatistics.dbf 00035
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/gidstatistics.dbf 00036
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/stat01.dbf 00007
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/statistics2013_6.dbf 00010
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/users02.dbf 00012
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/users04.dbf 00014
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/users06.dbf 00016
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/users08.dbf 00018
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/cdr2013_6.dbf 00020
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/cdr2013_8.dbf 00022
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/cdr2013_10.dbf 00024
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/cdr2013_12.dbf 00026
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/unameradcdr.dbf 00028
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/statistics2013_7.dbf 00030
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/statistics2013_9.dbf 00032
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/statisticsmaxdate.dbf 00034
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/radintdr2013_6.dbf 00038
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/radiusintcdr2013_8.dbf 00040
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/radinterimcdr2013_10.dbf 00042
    Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/tb2013_12.dbf 00044
    Enter a file datafile 00046 name=+ORADATA1/ORCLdr/datafile/tberimcdr.dbf = number
    Enter a number of file datafile = name=+ORASYS/ORCLdr/datafile/users.260.814500995 00004
    channel ch2: from room 1 to May 19, 13
    channel ch1: finished piece 1 to May 19, 13
    total, handle = / backup/RMAN_Backup/rman_bkp_44oa23eg_1_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013 tag = comment TAG20130519T200640 = NONE
    channel ch1: from part 2 to May 19, 13
    channel ch2: finished piece 1 to May 19, 13
    total, handle = / backup/RMAN_Backup/rman_bkp_45oa23eh_1_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013 tag = comment TAG20130519T200640 = NONE
    channel ch2: from part 2 to May 19, 13
    channel ch1: finished part 2 to May 19, 13
    total, handle = / backup/RMAN_Backup/rman_bkp_44oa23eg_2_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013 tag = comment TAG20130519T200640 = NONE
    channel ch1: complete set of backups, time: 00:00:22
    channel ch1: start the incremental level 0 datafile backup set
    channel ch1: specification-datafile in the backup set (s)
    channel ch2: finished part 2 to May 19, 13
    total, handle = / backup/RMAN_Backup/rman_bkp_45oa23eh_2_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013 tag = comment TAG20130519T200640 = NONE
    channel ch2: complete set of backups, time: 00:00:22
    including the current control in the backup set file
    channel ch1: from room 1 to May 19, 13
    channel ch1: finished piece 1 to May 19, 13
    total, handle = / backup/RMAN_Backup/rman_bkp_46oa23f7_1_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013 tag = comment TAG20130519T200640 = NONE
    channel ch1: complete set of backups, time: 00:00:01
    Backup finished on 19 May 13

    From backup may 19, 13
    Current archived log
    channel ch1: Startup archived log backup set
    channel ch1: specifying the newspapers archived in the backup set
    archived journal entry thread = 2 sequence = 83 RECID = 399 STAMP = 815861227
    channel ch1: from room 1 to May 19, 13
    channel ch2: Startup archived log backup set
    channel ch2: specifying the newspapers archived in the backup set
    archived journal entry thread = 1 sequence = 90 RECID = 401 STAMP = 815861227
    channel ch2: from room 1 to May 19, 13
    channel ch1: finished piece 1 to May 19, 13
    piece handle=/u01/app/oracle/product/11.2.0/db_1/dbs/47oa23fd_1_1 tag = DATAFILE_FULL comment = NONE
    channel ch1: complete set of backups, time: 00:00:01
    channel ch1: archived deletion or newspapers
    name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_2_83_814540431.arc RECID archived log file = 399 STAMP = 815861227
    channel ch2: finished piece 1 to May 19, 13
    piece handle=/u01/app/oracle/product/11.2.0/db_1/dbs/48oa23fd_1_1 tag = DATAFILE_FULL comment = NONE
    channel ch2: complete set of backups, time: 00:00:01
    channel ch2: archived deletion or newspapers
    RMAN-08137: WARNING: log archived not deleted, necessary for intelligence or upstream collection procedure
    Archive log file name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_1_90_814540431.arc thread = 1 sequence = 90
    Backup finished on 19 May 13

    From control file and SPFILE Autobackup 19 May 13
    room handle=/u01/app/oracle/product/11.2.0/db_1/dbs/c-3171721304-20130519-00 comment = NONE
    File control finished and Autobackup SPFILE to 19 May 13
    output channel: ch1
    output channel: ch2

    RMAN >
    RMAN >
    RMAN retention policy apply to the order
    RMAN retention policy is set to 3 redundancy
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID = instance 1753 = ORCLdr2 = DISK device type
    Remove the following obsolete backups and copies:
    Making key time filename/handle type
    -------------------- ------ ------------------ --------------------
    8 4 may control file copy 13 /u01/app/oracle/product/11.2.0/db_1/dbs/snapcf_ORCLdr1.f
    Game save 40 9 May 13
    Save the piece 40 9 May 13/backup/RMAN_Backup/rman_bkp_1jo97nk1_1_1_ORCL_20130509_DATAFILE_LVL0_09_05_2013
    Save game 39 may 9, 13
    Save the song 39 9 May 13/backup/RMAN_Backup/rman_bkp_1ko97nk1_1_1_ORCL_20130509_DATAFILE_LVL0_09_05_2013
    Backs up the entire 42 9 May 13
    Backup total 42 9 May 13 /u01/app/oracle/product/11.2.0/db_1/dbs/1mo97nkl_1_1
    Backs up the entire 43 9 May 13
    Backup total 43 9 May 13 /u01/app/oracle/product/11.2.0/db_1/dbs/1no97nkl_1_1
    Save game 46 may 10, 13
    Backup total 46 may 10, 13 /u01/app/oracle/product/11.2.0/db_1/dbs/1po9abvp_1_1
    Game backup 45 may 10, 13
    Backup total 45 10 May 13 /u01/app/oracle/product/11.2.0/db_1/dbs/1qo9abvp_1_1
    Save game 47 10 May 13
    Save room 47 10 May 13/backup/RMAN_Backup/rman_bkp_1ro9ac02_1_1_ORCL_20130510_DATAFILE_LVL1_10_05_2013
    Backs up the entire 48 may 10, 13
    Save the piece 48 10 May 13/backup/RMAN_Backup/rman_bkp_1so9ac02_1_1_ORCL_20130510_DATAFILE_LVL1_10_05_2013
    Backs up the entire 50 10 May 13
    Backup total 50 10 May 13 /u01/app/oracle/product/11.2.0/db_1/dbs/1uo9ac0l_1_1
    Backs up the entire 51 may 10, 13
    Backup total 51 may 10, 13 /u01/app/oracle/product/11.2.0/db_1/dbs/1vo9ac0l_1_1
    Backs up the entire 54 may 11, 13
    Backup total 54 may 11, 13 /u01/app/oracle/product/11.2.0/db_1/dbs/21o9d0bi_1_1
    Save game 53 may 11, 13
    Backup total 53 may 11, 13 /u01/app/oracle/product/11.2.0/db_1/dbs/22o9d0bi_1_1
    Save game 55 may 11, 13
    Save the piece 55 may 11, 13/backup/RMAN_Backup/rman_bkp_23o9d0br_1_1_ORCL_20130511_DATAFILE_LVL1_11_05_2013
    Backs up the entire 56 may 11, 13
    Save the song 56 11 May 13/backup/RMAN_Backup/rman_bkp_24o9d0br_1_1_ORCL_20130511_DATAFILE_LVL1_11_05_2013
    Backs up the entire 58 may 11, 13
    Backup total 58 may 11, 13 /u01/app/oracle/product/11.2.0/db_1/dbs/26o9d0cj_1_1
    Save game 59 may 11, 13
    Backup total 59 may 11, 13 /u01/app/oracle/product/11.2.0/db_1/dbs/27o9d0cj_1_1
    Backs up the entire 62 12 May 13
    Backup total 62 12 May 13 /u01/app/oracle/product/11.2.0/db_1/dbs/29o9fknp_1_1
    Save game 61 12 May 13
    Backup total 61 12 May 13 /u01/app/oracle/product/11.2.0/db_1/dbs/2ao9fknp_1_1
    Save game 77 14 May 13
    Backup total 77 14 May 13 /u01/app/oracle/product/11.2.0/db_1/dbs/c-3171721304-20130514-00
    Game backup 101 16 May 13
    Backup total 101 16 May 13 /u01/app/oracle/product/11.2.0/db_1/dbs/c-3171721304-20130516-00
    Backs up the entire 114 18 May 13
    Save the song 117 may 18, 13/backup/RMAN_Backup/rman_bkp_3uo9vf2f_1_1_ORCL_20130518_DATAFILE_LVL1_18_05_2013
    remove the item from backup
    backup piece handle = / backup/RMAN_Backup/rman_bkp_1jo97nk1_1_1_ORCL_20130509_DATAFILE_LVL0_09_05_2013 RECID = 40 STAMP = 814997122
    remove the item from backup
    backup piece handle = / backup/RMAN_Backup/rman_bkp_1ko97nk1_1_1_ORCL_20130509_DATAFILE_LVL0_09_05_2013 RECID = STAMP 39 = 814997122
    remove the item from backup
    handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/1mo97nkl_1_1 element of backup RECID = STAMP 42 = 814997141
    remove the item from backup
    handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/1no97nkl_1_1 element of backup RECID = STAMP 43 = 814997141
    remove the item from backup
    handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/1po9abvp_1_1 element of backup RECID = STAMP 46 = 815083513
    remove the item from backup
    handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/1qo9abvp_1_1 element of backup RECID = STAMP 45 = 815083514
    remove the item from backup
    backup piece handle = / backup/RMAN_Backup/rman_bkp_1ro9ac02_1_1_ORCL_20130510_DATAFILE_LVL1_10_05_2013 RECID = STAMP 47 = 815083522
    remove the item from backup
    backup piece handle = / backup/RMAN_Backup/rman_bkp_1so9ac02_1_1_ORCL_20130510_DATAFILE_LVL1_10_05_2013 RECID = 48 STAMP = 815083522
    remove the item from backup
    handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/1uo9ac0l_1_1 element of backup RECID = STAMP 50 = 815083541
    remove the item from backup
    handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/1vo9ac0l_1_1 element of backup RECID = STAMP 51 = 815083541
    remove the item from backup
    handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/21o9d0bi_1_1 backup RECID piece = 54 STAMP = 815169906
    remove the item from backup
    handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/22o9d0bi_1_1 element of backup RECID = STAMP 53 = 815169906
    remove the item from backup
    backup piece handle = / backup/RMAN_Backup/rman_bkp_23o9d0br_1_1_ORCL_20130511_DATAFILE_LVL1_11_05_2013 RECID = STAMP 55 = 815169915
    remove the item from backup
    backup piece handle = / backup/RMAN_Backup/rman_bkp_24o9d0br_1_1_ORCL_20130511_DATAFILE_LVL1_11_05_2013 RECID = STAMP 56 = 815169917
    remove the item from backup
    handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/26o9d0cj_1_1 element of backup RECID = STAMP 58 = 815169939
    remove the item from backup
    handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/27o9d0cj_1_1 element of backup RECID = 59 STAMP = 815169939
    remove the item from backup
    handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/29o9fknp_1_1 element of backup RECID = 62 STAMP = 815256313
    remove the item from backup
    handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/2ao9fknp_1_1 backup RECID piece = 61 = 815256313 STAMP
    remove the item from backup
    handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/c-3171721304-20130516-00 element of backup RECID = 101 STAMP = 815601943
    remove the item from backup
    backup piece handle = / backup/RMAN_Backup/rman_bkp_3uo9vf2f_1_1_ORCL_20130518_DATAFILE_LVL1_18_05_2013 RECID = 117 STAMP = 815774800
    20 objects deleted

    RMAN-06207: WARNING: 2 items could not be removed for DISC due channels
    RMAN-06208: status do not match. Use the OVERLAP command to set status
    RMAN-06210: list of relevant objects
    RMAN-06211: =.
    RMAN-06212: filename/Type object Handle
    RMAN-06213: --------------- ---------------------------------------------------
    RMAN-06214: copy of the data /u01/app/oracle/product/11.2.0/db_1/dbs/snapcf_ORCLdr1.f file
    RMAN-06214: /u01/app/oracle/product/11.2.0/db_1/dbs/c-3171721304-20130514-00 piece of backup


    RMAN >
    RMAN >

    Complete recovery manager.
    -bash - $3.2

    Concerning
    Hitgon

    Published by: hitgon on May 20, 2013 02:09

    Published by: hitgon on May 20, 2013 02:15

    It contained a real data file? Or was it a backup controlfile? A backup controlfile may be outdated if another backup controlfile does not capture the same information it contains.

    Hemant K Collette

  • BACKUPS RMAN DELETE

    Hi all

    We backup 11203-db with rman (11203). One of our databases has been removed (by design). Now we have backups remains in the rman catalog I see when you set the appropriate dbid. As the PB in question no longer exists I cannot connect to the ddb and therefore cannot delete these backups.

    Is it possible to delete the catalog rman backups.

    Any help appreciated.

    AMAZON

    Hello

    • Use CHANGE ... UNCATALOG to delete the records in the catalog.

    ex:

    RMAN > Change backuppiece ' / u01/oracle/RMAN/mydb/mydb_user01_01.bak' uncatalog;

    Thank you

  • RMAN delete channels

    Hi all

    oracle 11g r2 version, I create two channels as rman:

    CONFIGURE CHANNEL 1 DEVICE TYPE DISK FORMAT ' / u01/database_%U';
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT ' / u01/%U';

    now I am trying to delete these channels such as:

    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT CLEAR 1;
    CONFIGURE DEVICE TYPE DISK FORMAT CLEAR CHANNEL;

    But it gives

    RMAN-00558: error occurred during parsing of order entry
    RMAN-01009: syntax error: found 'Clear': expected an a: "new, double-quoted-string, single-quoted-string,"
    RMAN-01007: in the file column 46 line 1: entry standard


    error. I don't know where is error. could you please get out me of here.

    Thank you!

    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT CLEAR 1;

    When cleaning the channel, you don't have to specify "FORMAT". It should be like:

    Configure the channel drive peripheral;

    CONFIGURE CHANNEL DEVICE TYPE DISK CLEAR 1;

  • No Archivelog database - Undo Data files Deleted-how open database?

    I do a few tests in laboratory server.

    Unforunately Undo Tablespace data files are deleted from the server.
    Database is running in no archivelog Mode and I have not any any type of backup.

    Last week, I did only read only work with the database. So not really concern how I is coward.

    The biggest concern is how to open the database with existing data files?

    Kind regards
    Sumit

    Published by: Sumit2 on August 27, 2009 12:57

    If no active transaction or data required by one of the session to restore, then it will be difficult to recover these transactions and your database data will be in a State of incoherence. As you only read only activity you can safely recover the database.

    Comment just undo tablespace and undomanagement parameters init.ora file and restart the database.

    Once the database is in place create undo tablespace and assigning like default undo tablespace tablesapce.

  • Error at DB startup

    Hello

    11.2.0.3

    AIX 6.1

    It is a UAT server.

    We had complete archiver error, as far as I know that I have already disabled check-in. To disable our archivelog, I tried to cancel the shutdown to force shutdown since the normal shutdown is suspended.

    But when I have the PB I've had startup errors:

    / as sysdba

    SQL * more: Production release 11.2.0.3.0 on Mon Jan 13 17:50:59 2014

    Copyright (c) 1982, 2011, Oracle.  All rights reserved.

    Connect to an instance is idle.

    SQL > startup

    ORACLE instance started.

    Total System Global Area 1720328192 bytes

    Bytes of size 2222200 fixed

    1291847560 variable size bytes

    419430400 of database buffers bytes

    Redo buffers 6828032 bytes

    Mounted database.

    ORA-03113: end of file on communication channel

    Process ID: 6422568

    Session ID: 355 serial number: 5

    Help, please...

    Thank you

    pK

    Hello

    On the RMAN tool, remove old archivelog to a week.
    rman target # /.
    RMAN > startup mount;
    RMAN > delete archivelog until 'sysdate-7 ';

    or
    RMAN > remove force archivelog all;

    or
    RMAN > delete backup is complete before 'sysdate-3 ";

    Thank you

  • "ORA-19554: device allocation error, device type: SBT_TAPE device name:

    Hello expert.
    why I can't delete obsolete?
    I have this error:
    "ORA-19554: device allocation error, device type: SBT_TAPE device name:
    but I did not all bands. How can I remove this from my config of rman?
    Thank you very much, as usual.
    see you soon,
    Lain

    RMAN> show all;

RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/oraclesvi/TMP/backup_db_archive/cf_%F';
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO '%F'; # default
CONFIGURE DEVICE TYPE 'SBT_TAPE' BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 1;
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 1;
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 CHANNEL DEVICE TYPE DISK FORMAT   '/oraclesvi/TMP/backup_db_archive/ora_df%t_s%s_s%p';
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 '/opt/oracle/product/10.2.0/SvilTMP/dbs/snapcf_DBTMP.f'; # default


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
-------------------- ------ ------------------ --------------------
Archive Log          1      28-MAY-10          /oraclesvi/TMP/flash_recovery_area/DBTMP/archivelog/2010_05_28/o1_mf_1_22_60086j50_.arc
Archive Log          2      29-MAY-10          /oraclesvi/TMP/flash_recovery_area/DBTMP/archivelog/2010_05_29/o1_mf_1_23_6014bh9j_.arc
Archive Log          3      30-MAY-10          /oraclesvi/TMP/flash_recovery_area/DBTMP/archivelog/2010_05_30/o1_mf_1_24_603o6gls_.arc

RMAN> delete obsolete;

RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of delete command at 06/14/2010 14:43:17
ORA-19554: error allocating device, device type: SBT_TAPE, device name: 
ORA-27211: Failed to load Media Management Library
Additional information: 2

    Try

    CONFIGURE DEVICE TYPE 'SBT_TAPE' clear;

    Werner

  • ASM diskgroup space do not free themselves after RMAN archivelog delete

    Version Infra grid: 11.2.0.4

    DB version: 11.2.0.4

    OS: Oracle Linux 6.4

    Storage: Enterprise-class storage (EMC VMAX)

    We are in the Bank we have a database of CARS of Production 2 nodes very critical.

    Newspaper archives are stored in ARCH_DG diskgroup. Because of the unexpectedly heavy workload, our diskgroup ARCH_DG became full and we got the usual error

    ORA-00257: archiver error. Connect internal only, until this just released.

    To wear the DB back to business quickly, I tried to delete the old archive logs more than 1 day of the diskgroup first using the following command

    RMAN > delete noprompt archivelog until ' SYSDATE-1';

    So, I started to see the following message


    RECID = STAMP 19807 = 849396325 name=+ARCH_DG/bsoaprd/archivelog/2014_06_04/thread_2_seq_10066.331.849396309 archived log file

    Delete archived log

    RECID = STAMP 19809 = 849396940 name=+ARCH_DG/bsoaprd/archivelog/2014_06_04/thread_2_seq_10067.274.849396925 archived log file

    Delete archived log

    name=+ARCH_DG/bsoaprd/archivelog/2014_06_04/thread_2_seq_10068.341.849397529 RECID archived log file = 19810 STAMP = 849397543

    Delete archived log

    name=+ARCH_DG/bsoaprd/archivelog/2014_06_04/thread_2_seq_10069.298.849398167 RECID archived log file = 19812 STAMP = 849398182

    Delete archived log

    RECID = STAMP 19813 = 849398806 name=+ARCH_DG/bsoaprd/archivelog/2014_06_05/thread_2_seq_10070.317.849398783 archived log file

    Delete archived log

    name=+ARCH_DG/bsoaprd/archivelog/2014_06_05/thread_2_seq_10071.342.849399327 RECID archived log file = 19814 STAMP = 849399337

    Although I could see messages "deleted archived newspaper" as stated above there are 2 inconsistencies (odd behavior)

    1 inconsistency. Not a single byte released upwards of archive diskgroup. Each log archiving is 4 GB in size. I got "journal archived deleted" message at least 25 archived log files. For example, 100 GB should have been released.

    The diskgroup to archive has remained at 99.9% as shown below and the DB was inaccessible.

    SQL > select name,.

    Round(total_mb/1024,2) Total_GB.

    Round(free_mb/1024,2) Free_GB.

    free_mb/total_mb * 100 "% free"

    ABS ((free_mb/total_mb*100)-100) '% complete '.

    v $ asm_diskgroup;  2 3 4 5 6

    NAME TOTAL_GB FREE_GB % free full
    ------------------------------ ---------- ---------- ---------- ------------
    ARCH_DG 1000.78 99.9223633.077636719
    DATA_DG 10000.02 1188.19 11.8818616 88.1181384
    OCR_VOTE_DG 12 11.09 92.4623525 7.53764754
    < snipped >


    Inconsistency2. The number of available archived newspapers remained unchanged. He was always showing 301

    SQL > select count (*) from v$ archived_log where status = 'A ';

    COUNT (*)

    ----------

    301

    RMAN later > remove obsolete; command removed 17 archived newspapers.

    This means that 17 x 4 = 68 GB should have been released.

    But Diskgroup of free space and the County of v$ archived_log.status = 'A' is unchanged, as mentioned above.

    , Of ASMCMD, I deleted manually a full archive directory connects using rm-rf command.

    Even after running rm - rf on a whole directory full of archived newspaper space was not released and we always receive ""ORA-00257: archiver error '. "

    So, we had to shoot down the cluster using "stop crsctl crs. After the cluster has been raised using 'crsctl start crs' on both nodes,

    space has been freed up, and the DB became accessible.

    I wonder why the ASM diskgroup space was not release despite the removal of the archive logs. Are the 1 & 2 above mentioned inconsistencies caused by something handle to open the file ?

    Hello

    Please run command you at the level of the ASM, below

    SQL > alter diskgroup check all the repair;

    -At the end of the same thing, run below command and enable it to perform

    SQL > alter diskgroup rebalance power 4.

    -To validate the space

    $ asmcmd Pei lsdg

    Kind regards
    Loriette

  • RMan is missing some files when deleting obsolete archivelogs

    Hi all

    in one of our databases 9iR2, I noticed a rather strange behavior of the RMan delete obsolete archivelogs. The RMan script has the "OBSOLETE RECOVERY WINDOW DELETE 7 DAYS DEVICE TYPE DISK"-command. If RMan deletes the archivelogs regularly. But unfortunately, in every race, it leaves 3 files cancelled. The log file is (only relevant lines):

    Remove the following obsolete backups and copies:
    Making key time filename/handle type
    ---- ----
    Archive 24779 08 - SEVEN journal.-10 /oralogs/oraArchive/VG41MED/VG41MED_12402.ora
    Archive Log 24780 08-SEVEN.-10 /oralogs/oraArchive/VG41MED/VG41MED_12403.ora
    ...
    Archive 24785 08 - SEVEN journal.-10 /oralogs/oraArchive/VG41MED/VG41MED_12408.ora

    on the next race (the next day) the log file says:

    Remove the following obsolete backups and copies:
    Making key time filename/handle type
    ---- ----
    Archive Log 24799 09-SEPT.-10 /oralogs/oraArchive/VG41MED/VG41MED_12412.ora
    Archive 24800 09 - SEVEN journal.-10 /oralogs/oraArchive/VG41MED/VG41MED_12413.ora
    ...
    Archive Log 24805 09-SEPT.-10 /oralogs/oraArchive/VG41MED/VG41MED_12418.ora

    As you can see, RMan lack VG41MED12409.ora log file, VG41MED12410.ora, and VG41MED_12411.ora that are available before and after the backup procedure. We treat archivelogs on operating system level. A "overlap archivelog all ' - command does not list these 3 files, if the database thinks that they are removed - which is not really true. This odd pattern is repeated every day, so my archivelog directory is growing everyday with the 3 files not deleted.

    This behavior appears still more strange, because the RMan backup script even run on 3 other databases with same structure does not show this "error". I checked the configuration of 4 databases and not detected no difference.

    Maybe it's a corrupt controlfile (we do not catalog-db). Someone has any idea how to solve this problem?

    Thank you
    Friedhelm

    Edited by: user8964905 the 20.09.2010 00:18

    Hello
    (1) I think the command of OVERLAP is the only way to know what archivelogs are always specific to the database (expired or available) kn.
    (2) thank you for your explanations. You're right - the order REPORT OBSOLETE list backups, but my problem are the obsolete archivelogs of backups. If my humble opinion REPORT OBSOLETE wouldn't help.

    In fact no and no :).

    (1) a simple

    list archivelog all;

    lists the known archivelog (expired or available) files.

    crosscheck archivelog all;

    will check if the information on their availability is still topical, but it will not help you in this case (they exist!)

    2.

    report obsolete recovery...;

    http://download.Oracle.com/docs/CD/B10501_01/server.920/a96566/rcmconc3.htm#463220
    Order REPORT displays OBSOLETE backups and copies of data files, control files, and archived redo logs that can be deleted because they are no longer needed.
    ...
    OK, but if you read a little more of the documentation:
    ...
    In addition to backups of file obsolete data, RMAN reports obsolete archived newspapers and archived backups of logs. When backups of files of data from one point in time are obsolete, then archived logs that can apply to these data files are also is no longer necessary and become obsolete according to the specified retention policy.

    ---------------------------------------------------------------------------------------------------------------------------

    I have increased the CONTROLFILE_RECORD_KEEP_TIME now and watch the results next night. Perhaps the reason for this behavior is the fact that this database is very small compared to other databases, which do not show the effect.
    I'll post the result of this strategy, here the next few days.
    Wait & see

    Best regards
    Phil

  • ARCHIVELOG deletion policy vs v$ flash_Recovery_Area_usage - delicate...

    Hi all

    Reading of

    http://docs.Oracle.com/CD/E11882_01/backup.112/e10643/rcmsynta016.htm#RCMRF121

    DELETE ARCHIVELOG ALLconsiders that the deletion of archived newspaper policy


    Reading on archivelog deletion policy

    Only newspapers in the field of quick recovery can be deleted automatically by the database.
    When the deletion policy is set on NONE , RMAN considers archived redo log files as eligible for deletion if they meet both of the following


    -The archive redo logs, whether in or outside of it, fast recovery area have been transferred to remote required destinations specified byLOG_ARCHIVE_DEST_n


    -Log redo archived in the area of fast recovery, files have been saved at least once to the disk or SBT or newspapers are obsolete according to the backup retention policy.

    The esteem newspapers backup retention policy obsolete If newspapers are needed by a guaranteed restore not point and that newspapers are not required by Flashback Database

    =======================================================

    LOG_ARCHIVE_DEST_1 Q1) is configured to use 'db_recovery_file_dest' and archivelogs are kept here-> I have meet the #1 condition?

    Q2) I have a retention policy recovery backup window 1 day and I haven't done ANY backup at all yet. I don't have a flashback database, or doesn't I created a ganrantee restore point - I meet the #2 condition?


    Q3) I am able to issue "delete archivelog all ', what does that say I satisfy the condition #1 and #2 and the archivelogs are eligible for deletion?

    Q4) if above is a Yes, and with newspapers in fast recovery area may be removed automatically-> why is he in V$ FLASH_RECOVERY_AREA_USAGE, 'PERCENT_SPACE_RECLAIMABLE' always show 0 for the log archiving?

    I thought that the space which are recyclable are files that are eligible for deletion
    ?

    Kind regards

    Noob

    So, this giving some more thought and reading the documentation again. I conclude the following:

    The confusion might be in the context of "eligible for deletion" and management of automatic space of files inside the fast recovery area.

    If the Archivelog deletion policy is set to 'none', then delete archivelog all the will remove all archivelogs, without worrying. Otherwise, the archivelogs policy are not deleted.

    According to the documentation:


    DELETE ARCHIVELOG ALL considers only the deletion of archived newspaper policy and does not take into account the configured retention policy.

    Everything under "eligible for deletion" applies to the space management FRA, who considers the RMAN retention policy and, as far as I understand it, also believes the Archivelog deletion policy when it is not set to 'none '.

    Archive redo log deletion policy is set to NONE by default. In this case, RMAN considers archived redo log files in the recovery area as eligible for deletion if they fulfill the following two conditions:

    • The archived redo logs, whether in the flash recovery area or outside of it, have been transferred to the required remote destinations specified by LOG_ARCHIVE_DEST_ n .
    • Archived recovery logs have been saved at least once to the disk or SBT or newspapers are obsolete according to the backup retention policy.

    Regarding your recoverable space issue... If you have access to MOS, I suggest to see Doc ID 315098.1.

    What I take from this document, is that archivelogs are included in the column SPACE RECUPERABLE if the free space of FRA becomes less then 15% and the archivelogs are not required by the current backups. Or, archivelogs were saved and not deleted.

Maybe you are looking for