Archives missing in rman backup

Hi all,
I am able to backup few archives using rman. But its taking some archivelogs in the same directory. Can anybody tell me the reason.
After registering the archivelog using catalog command am able to take the backup of all the files.
Can anybody tell me the exact reason behind this.
many thanx in advance. . .

BALAKRIS005 wrote:
Hi all,
I am able to backup few archives using rman. But its taking some archivelogs in the same directory. Can anybody tell me the reason.
After registering the archivelog using catalog command am able to take the backup of all the files.
Can anybody tell me the exact reason behind this.Hi, there are no problems.Consider you have two archive destinations,then you want bakup archivelogs,in during backup operation rman read information from repository(controlfile or catalog) and backup each log(get only one copy).Rman see one destination and continue backup if there something fails(some logs missing or corrupted) then read other locations and will backup all archivelogs.This is normal situation.

Similar Messages

  • Archive files and rman backup

    Hi Experts,
    For testing, I creates a testing DB. after that, I delete some archive file from physical side.
    testing DB works well.
    However, I tyr to back up thsi testing DB. I got below error message
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=142 devtype=DISK
    new RMAN configuration parameters:
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT 'D:\Oraclebackup\CLS\exports\RMAN\%U
    new RMAN configuration parameters are successfully stored
    released channel: ORA_DISK_1
    Starting backup at 15-JAN-09
    current log archived
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=142 devtype=DISK
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of backup plus archivelog command at 01/15/2009 15:18:13
    RMAN-06059: expected archived log not found, lost of archived log compromises re
    coverability
    ORA-19625: error identifying file D:\test\ARC00001_0675529905.001
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 2) The system cannot find the file specified.
    So How to fix this issue?
    That means we can not delete any archive log files that we do not need it.
    Otherwise there are a problemwhen we try to backup later
    JIm

    Hi Jim,
    change archivelog all crosscheck ;
    will do the trick.
    You can purge archive files but do it within rman.
    Add a line in your rman backup script which makes backup your database and archive files like this.
    delete noprompt copy of archivelog all completed before 'SYSDATE-3';
    Regards,
    Tycho

  • Archive Log vs Full Backup Concept

    Hi,
    I just need some clarification on how backups and archive logs work. Lets say starting at 1PM I have archive logs 1,2,3,4,5 and then I perform a full backup at 6PM.
    Then I resume generating archive logs at 6PM to get logs 6,7,8,9,10. I then stop at 11PM.
    If my understanding is correct, the archive logs should allow me to restore oracle to a point in time anywhere between 1PM and 11PM. But if I only have the full backup then I can only restore to a single point, which is 6PM. Is my understanding correct?
    Do the archive logs only get applied to the datafiles when the backup occurs or only when a restore occurs? It doesn't seem like the archive logs get applied on the fly.
    Thanks in advance.

    thelok wrote:
    Thanks for the great explanation! So I can do a point in time restore from any time since the datafiles have last been written (or from when I have the last set of backed up datafiles plus the archive logs). From what you are saying, I can force the datafiles to be written from the redo logs (by doing a checkpoint with "alter set archive log current" or "backup database plus archivelog"), and then I can delete all the archive logs that have a SCN less than the checkpoint SCN on the datafiles. Is this true? This would be for the purposes of preserving disk space.Hi,
    See this example. I hope this explain your doubt.
    # My current date is 06-11-2011 17:15
    # I not have backup of this database
    # My retention policy is to have 1 backup
    # I start listing  archive logs.
    RMAN> list archivelog all;
    using target database control file instead of recovery catalog
    List of Archived Log Copies
    Key     Thrd Seq     S Low Time            Name
    29      1    8       A 29-10-2011 12:01:58 +HR/dbhr/archivelog/2011_10_31/thread_1_seq_8.399.766018837
    30      1    9       A 31-10-2011 23:00:30 +HR/dbhr/archivelog/2011_11_03/thread_1_seq_9.409.766278025
    31      1    10      A 03-11-2011 23:00:23 +HR/dbhr/archivelog/2011_11_04/thread_1_seq_10.391.766366105
    32      1    11      A 04-11-2011 23:28:23 +HR/dbhr/archivelog/2011_11_06/thread_1_seq_11.411.766516065
    33      1    12      A 05-11-2011 23:28:49 +HR/dbhr/archivelog/2011_11_06/thread_1_seq_12.413.766516349
    ## See I have archive logs from time "29-10-2011 12:01:58" until "05-11-2011 23:28:49" but I dont have any backup of database.
    # So I perfom backup of database including archive logs.
    RMAN> backup database plus archivelog delete input;
    Starting backup at 06-11-2011 17:15:21
    ## Note above RMAN forcing archive current log, this archivelog generated will be usable only for previous backup.
    ## Is not my case... I don't have backup of database.
    current log archived
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=159 devtype=DISK
    channel ORA_DISK_1: starting archive log backupset
    channel ORA_DISK_1: specifying archive log(s) in backup set
    input archive log thread=1 sequence=8 recid=29 stamp=766018840
    input archive log thread=1 sequence=9 recid=30 stamp=766278027
    input archive log thread=1 sequence=10 recid=31 stamp=766366111
    input archive log thread=1 sequence=11 recid=32 stamp=766516067
    input archive log thread=1 sequence=12 recid=33 stamp=766516350
    input archive log thread=1 sequence=13 recid=34 stamp=766516521
    channel ORA_DISK_1: starting piece 1 at 06-11-2011 17:15:23
    channel ORA_DISK_1: finished piece 1 at 06-11-2011 17:15:38
    piece handle=+FRA/dbhr/backupset/2011_11_06/annnf0_tag20111106t171521_0.268.766516525 tag=TAG20111106T171521 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:16
    channel ORA_DISK_1: deleting archive log(s)
    archive log filename=+HR/dbhr/archivelog/2011_10_31/thread_1_seq_8.399.766018837 recid=29 stamp=766018840
    archive log filename=+HR/dbhr/archivelog/2011_11_03/thread_1_seq_9.409.766278025 recid=30 stamp=766278027
    archive log filename=+HR/dbhr/archivelog/2011_11_04/thread_1_seq_10.391.766366105 recid=31 stamp=766366111
    archive log filename=+HR/dbhr/archivelog/2011_11_06/thread_1_seq_11.411.766516065 recid=32 stamp=766516067
    archive log filename=+HR/dbhr/archivelog/2011_11_06/thread_1_seq_12.413.766516349 recid=33 stamp=766516350
    archive log filename=+HR/dbhr/archivelog/2011_11_06/thread_1_seq_13.414.766516521 recid=34 stamp=766516521
    Finished backup at 06-11-2011 17:15:38
    ## RMAN finish backup of Archivelog and Start Backup of Database
    ## My backup start at "06-11-2011 17:15:38"
    Starting backup at 06-11-2011 17:15:38
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting full datafile backupset
    channel ORA_DISK_1: specifying datafile(s) in backupset
    input datafile fno=00001 name=+HR/dbhr/datafile/system.386.765556627
    input datafile fno=00003 name=+HR/dbhr/datafile/sysaux.396.765556627
    input datafile fno=00002 name=+HR/dbhr/datafile/undotbs1.393.765556627
    input datafile fno=00004 name=+HR/dbhr/datafile/users.397.765557979
    input datafile fno=00005 name=+BFILES/dbhr/datafile/bfiles.257.765542997
    channel ORA_DISK_1: starting piece 1 at 06-11-2011 17:15:39
    channel ORA_DISK_1: finished piece 1 at 06-11-2011 17:16:03
    piece handle=+FRA/dbhr/backupset/2011_11_06/nnndf0_tag20111106t171539_0.269.766516539 tag=TAG20111106T171539 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:24
    Finished backup at 06-11-2011 17:16:03
    ## And finish at "06-11-2011 17:16:03", so I can recovery my database from this time.
    ## I will need archivelogs (transactions) which was generated during backup of database.
    ## Note during backup some blocks are copied others not. The SCN is inconsistent state.
    ## To make it consistent I need apply archivelog which have all transactions recorded.
    ## Starting another backup of archived log generated during backup.
    Starting backup at 06-11-2011 17:16:04
    ## So automatically RMAN force another "checkpoint" after backup finished,
    ## forcing archive current log, because this archivelog have all transactions to bring database in a consistent state.
    current log archived
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting archive log backupset
    channel ORA_DISK_1: specifying archive log(s) in backup set
    input archive log thread=1 sequence=14 recid=35 stamp=766516564
    channel ORA_DISK_1: starting piece 1 at 06-11-2011 17:16:05
    channel ORA_DISK_1: finished piece 1 at 06-11-2011 17:16:06
    piece handle=+FRA/dbhr/backupset/2011_11_06/annnf0_tag20111106t171604_0.272.766516565 tag=TAG20111106T171604 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:02
    channel ORA_DISK_1: deleting archive log(s)
    archive log filename=+HR/dbhr/archivelog/2011_11_06/thread_1_seq_14.414.766516565 recid=35 stamp=766516564
    Finished backup at 06-11-2011 17:16:06
    ## Note: I can recover my database from time "06-11-2011 17:16:03" (finished backup full)
    ##  until "06-11-2011 17:16:04" (last archivelog generated) that is my recover window in this scenary.
    ## Listing Backup I have:
    ## Archive Logs in backupset before backup full start - *BP Key: 40*
    ## Backup Full database in backupset - *BP Key: 41*
    ##  Archive Logs in backupset after backup full stop - *BP Key: 42*
    RMAN> list backup;
    List of Backup Sets
    ===================
    BS Key  Size       Device Type Elapsed Time Completion Time
    40      196.73M    DISK        00:00:15     06-11-2011 17:15:37
            *BP Key: 40*   Status: AVAILABLE  Compressed: NO  Tag: TAG20111106T171521
            Piece Name: +FRA/dbhr/backupset/2011_11_06/annnf0_tag20111106t171521_0.268.766516525
      List of Archived Logs in backup set 40
      Thrd Seq     Low SCN    Low Time            Next SCN   Next Time
      1    8       766216     29-10-2011 12:01:58 855033     31-10-2011 23:00:30
      1    9       855033     31-10-2011 23:00:30 896458     03-11-2011 23:00:23
      1    10      896458     03-11-2011 23:00:23 937172     04-11-2011 23:28:23
      1    11      937172     04-11-2011 23:28:23 976938     05-11-2011 23:28:49
      1    12      976938     05-11-2011 23:28:49 1023057    06-11-2011 17:12:28
      1    13      1023057    06-11-2011 17:12:28 1023411    06-11-2011 17:15:21
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    41      Full    565.66M    DISK        00:00:18     06-11-2011 17:15:57
            *BP Key: 41*   Status: AVAILABLE  Compressed: NO  Tag: TAG20111106T171539
            Piece Name: +FRA/dbhr/backupset/2011_11_06/nnndf0_tag20111106t171539_0.269.766516539
      List of Datafiles in backup set 41
      File LV Type Ckp SCN    Ckp Time            Name
      1       Full 1023422    06-11-2011 17:15:39 +HR/dbhr/datafile/system.386.765556627
      2       Full 1023422    06-11-2011 17:15:39 +HR/dbhr/datafile/undotbs1.393.765556627
      3       Full 1023422    06-11-2011 17:15:39 +HR/dbhr/datafile/sysaux.396.765556627
      4       Full 1023422    06-11-2011 17:15:39 +HR/dbhr/datafile/users.397.765557979
      5       Full 1023422    06-11-2011 17:15:39 +BFILES/dbhr/datafile/bfiles.257.765542997
    BS Key  Size       Device Type Elapsed Time Completion Time
    42      3.00K      DISK        00:00:02     06-11-2011 17:16:06
            *BP Key: 42*   Status: AVAILABLE  Compressed: NO  Tag: TAG20111106T171604
            Piece Name: +FRA/dbhr/backupset/2011_11_06/annnf0_tag20111106t171604_0.272.766516565
      List of Archived Logs in backup set 42
      Thrd Seq     Low SCN    Low Time            Next SCN   Next Time
      1    14      1023411    06-11-2011 17:15:21 1023433    06-11-2011 17:16:04
    ## Here make sense what I trying explain
    ## As I don't have backup of database before of my Last backup, all archivelogs generated before of my backup full is useless.
    ## Deleting what are obsolete in my env, RMAN choose backupset 40 (i.e all archived logs generated before my backup full)
    RMAN> delete obsolete;
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to redundancy 1
    using channel ORA_DISK_1
    Deleting the following obsolete backups and copies:
    Type                 Key    Completion Time    Filename/Handle
    *Backup Set           40*     06-11-2011 17:15:37
      Backup Piece       40     06-11-2011 17:15:37 +FRA/dbhr/backupset/2011_11_06/annnf0_tag20111106t171521_0.268.766516525
    Do you really want to delete the above objects (enter YES or NO)? yes
    deleted backup piece
    backup piece handle=+FRA/dbhr/backupset/2011_11_06/annnf0_tag20111106t171521_0.268.766516525 recid=40 stamp=766516523
    Deleted 1 objectsIn the above example, I could before starting the backup run "delete archivelog all" because they would not be needed, but to show the example I follow this unnecessary way. (backup archivelog and delete after)
    Regards,
    Levi Pereira
    Edited by: Levi Pereira on Nov 7, 2011 1:02 AM

  • Archive logs are missing in hot backup

    Hi All,
    We are using the following commands to take hot backup of our database. Hot backup is fired by "backup" user on Linux system.
    =======================
    rman target / nocatalog <<EOF
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '$backup_dir/$date/%F';
    run {
    allocate channel oem_backup_disk1 type disk format '$backup_dir/$date/%U';
    #--Switch archive logs for all threads
    sql 'alter system archive log current';
    backup as COMPRESSED BACKUPSET database include current controlfile;
    #--Switch archive logs for all threads
    sql 'alter system archive log current';
    #--Backup Archive logs and delete what we've backedup
    backup as COMPRESSED BACKUPSET archivelog all not backed up delete all input;
    release channel oem_backup_disk1;
    allocate channel for maintenance type disk;
    delete noprompt obsolete device type disk;
    release channel;
    exit
    EOF
    =======================
    Due to which after command (used 2 times) "sql 'alter system archive log current';" I see the following lines in alert log 2 times. Because of this all the online logs are not getting archived (Missing 2 logs per day), the backup taken is unusable when restoring. I am worried about this. I there any to avoid this situation.
    =======================
    Errors in file /u01/oracle/admin/rac/udump/rac1_ora_3546.trc:
    ORA-19504: failed to create file "+DATA/rac/1_32309_632680691.dbf"
    ORA-17502: ksfdcre:4 Failed to create file +DATA/rac/1_32309_632680691.dbf
    ORA-15055: unable to connect to ASM instance
    ORA-01031: insufficient privileges
    =======================
    Regards,
    Kunal.

    All thanks you for help, pleas find additional information. I goth the following error as log sequence was missing. Everyday during hotbackup, there are 2 missing archive logs, which makes our backup inconsistent and useless.
    archive log filename=/mnt/xtra-backup/ora_archivelogs/1_32531_632680691.dbf thread=1 sequence=32531
    archive log filename=/mnt/xtra-backup/ora_archivelogs/2_28768_632680691.dbf thread=2 sequence=28768
    archive log filename=/mnt/xtra-backup/ora_archivelogs/2_28769_632680691.dbf thread=2 sequence=28769
    archive log filename=/mnt/xtra-backup/ora_archivelogs/2_28770_632680691.dbf thread=2 sequence=28770
    archive log filename=/mnt/xtra-backup/ora_archivelogs/1_32532_632680691.dbf thread=1 sequence=32532
    archive log filename=/mnt/xtra-backup/ora_archivelogs/2_28771_632680691.dbf thread=2 sequence=28771
    archive log filename=/mnt/xtra-backup/ora_archivelogs/2_28772_632680691.dbf thread=2 sequence=28772
    archive log filename=/mnt/xtra-backup/ora_archivelogs/2_28772_632680691.dbf thread=2 sequence=28773
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 12/13/2012 04:22:56
    RMAN-11003: failure during parse/execution of SQL statement: alter database recover logfile '/mnt/xtra-backup/ora_archivelogs/2_28772_632680691.dbf'
    ORA-00310: archived log contains sequence 28772; sequence 28773 required
    ORA-00334: archived log: '/mnt/xtra-backup/ora_archivelogs/2_28772_632680691.dbf'
    Let me try the susggestions provided above.

  • Rman backup with a missing archivelog.

    hello,
    I backed my database up yesterday after you guys helped me fix few problems I had on it. I used RMAN with the following command in a run block:
    *run {*
    allocate channel t1 type disk;
    backup current controlfile ;
    backup database;
    backup archivelog all delete input;
    release channel c1;
    At the end of the operation, RMAN indicates that and archivelog is missing and it couldn't find it. As a result, recover operation can be compromised. Now am confused because I do not know whether the command executed successfully or not and how to fix the missing archivelog.
    Below is the entire output of the operation along with error message:
    canal affectÚ : t1
    canal t1 : sid=131 typedev=DISK
    DÚmarrage de backup dans 16/04/09
    canal t1 : dÚmarrage de l'ensemble de sauvegarde de tous les fichiers de donnÚes
    canal t1 : insertion du fichier de donnÚes dans l'ensemble de sauvegarde
    insertion du fichier de contr¶le en cours dans l'ensemble de sauvegarde
    canal t1 : dÚmarrage de l'ÚlÚment 1 dans 16/04/09
    canal t1 : ÚlÚment 1 terminÚ dans 16/04/09
    pointeur=+ASMTEST/meta4/backupset/2009_04_16/ncnnf0_tag20090416t211049_0.334.684
    *364257 Útiquette=TAG20090416T211049 commentaire=NONE*
    canal t1 : ensemble de sauvegarde terminÚ, temps ÚcoulÚ : 00:00:14
    Fin de backup dans 16/04/09
    DÚmarrage de backup dans 16/04/09
    canal t1 : dÚmarrage de l'ensemble de sauvegarde de tous les fichiers de donnÚes
    canal t1 : insertion du fichier de donnÚes dans l'ensemble de sauvegarde
    fichier de donnÚes en entrÚe fno=00008 nom=+ASMTEST/meta4/m4prod.dbf
    fichier de donnÚes en entrÚe fno=00010 nom=H:\ORADATA\M4REC.DBF
    fichier de donnÚes en entrÚe fno=00009 nom=E:\DATAFILEMETA4\M4PROD02.DBF
    fichier de donnÚes en entrÚe fno=00001 nom=+ASMTEST/meta4/system01.dbf
    fichier de donnÚes en entrÚe fno=00003 nom=+ASMTEST/meta4/sysaux01.dbf
    fichier de donnÚes en entrÚe fno=00006 nom=C:\TEST.DBF
    fichier de donnÚes en entrÚe fno=00007 nom=+ASMTEST/meta4/meta4.dbf
    fichier de donnÚes en entrÚe fno=00005 nom=+ASMTEST/meta4/example01.dbf
    fichier de donnÚes en entrÚe fno=00002 nom=+ASMTEST/meta4/undotbs01.dbf
    fichier de donnÚes en entrÚe fno=00004 nom=+ASMTEST/meta4/users01.dbf
    canal t1 : dÚmarrage de l'ÚlÚment 1 dans 16/04/09
    canal t1 : ÚlÚment 1 terminÚ dans 16/04/09
    pointeur=+ASMTEST/meta4/backupset/2009_04_16/nnndf0_tag20090416t211107_0.333.684
    *364271 Útiquette=TAG20090416T211107 commentaire=NONE*
    canal t1 : ensemble de sauvegarde terminÚ, temps ÚcoulÚ : 00:51:10
    canal t1 : dÚmarrage de l'ensemble de sauvegarde de tous les fichiers de donnÚes
    canal t1 : insertion du fichier de donnÚes dans l'ensemble de sauvegarde
    insertion du fichier de contr¶le en cours dans l'ensemble de sauvegarde
    inclusion du SPFILE en cours dans l'ensemble de sauvegarde
    canal t1 : dÚmarrage de l'ÚlÚment 1 dans 16/04/09
    canal t1 : ÚlÚment 1 terminÚ dans 16/04/09
    pointeur=+ASMTEST/meta4/backupset/2009_04_16/ncsnf0_tag20090416t211107_0.345.684
    *367351 Útiquette=TAG20090416T211107 commentaire=NONE*
    canal t1 : ensemble de sauvegarde terminÚ, temps ÚcoulÚ : 00:00:26
    Fin de backup dans 16/04/09
    DÚmarrage de backup dans 16/04/09
    journal en cours archivÚ
    canal libÚrÚ : t1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: Úchec de la commande backup Ó 04/16/2009 22:04:03
    RMAN-06059: journal d'archivage attendu introuvable ; la perte du journal d'arch
    ivage compromet la possibilitÚ de rÚcupÚration
    ORA-19625: erreur lors de l'identification du fichier H:\ARCHIVEMETA4\ARC00001_0
    *682674928.001*
    ORA-27041: ouverture du fichier impossible
    OSD-04002: ouverture impossible du fichier
    O/S-Error: (OS 2) Le fichier spÚcifiÚ est introuvable.
    Here's my nderstanding and please correct me if am wrong:
    The first 3 instructions of the run block executed successfully, but
    the last one didn't. Is that so?
    Whatever the understanding, do I have a backup? WHat can I do to have a consistent backup?
    Thanks in advance.

    Adomi,
    It is sad to see you are still running RMAN in 8i fashion where you are on 10g.
    The script is bs, sorry
    run {
    allocate channel t1 type disk; -- not required
    backup current controlfile ; -- not required, as this is already done by backup database
    backup database;
    backup archivelog all delete input;
    release channel c1; -- not required.
    If you have controlfile autobackup on, you could just
    backup database plus archivelog
    and be done with it.
    As you didn't make a RMAN backup from the start, your backup archivelog statement should have read
    backup archivelog all skip inaccessible delete input;
    Once that succeeds Oracle shouldn't need the archivelog anymore, and you should make a second backup without the skip inaccessible clause.
    Sybrand Bakker
    Senior Oracle DBA

  • Rman backup archive log

    Hi Guys,
    Can advise on the syntax to perform rman backup of archive logs generated in last 2 days?
    Should it be 1 or 2?
    thanks!
    1. BACKUP ARCHIVELOG UNTIL TIME 'SYSDATE-2';
    2. BACKUP ARCHIVELOG FROM TIME 'SYSDATE-2';

    What prevents you from trying both?
    I'm not trying to be difficult here but why take the time to ask people in a forum, not even supplying a version number, and not just find out?
    It took me less than 60 seconds to cut-and-paste both of your command lines into RMAN and look at the output.
    Edited by: damorgan on Jan 19, 2013 4:11 PM

  • RMAN BACKUP hangs up on archive logs

    Hi,
    in 9i on Linux, My rman backup script is :
    RMAN> run {
    2> allocate channel t1 type disk;
    3> backup incremental level=0 format '/mnt/rman/MYDB/full_%d_%t_%s_%p' database;
    4> sql 'alter system switch logfile';
    5> backup format '/mnt/rman/MYDB/al_%d_%t_%s_%p'
    6> archivelog all delete input;
    7> backup format '/mnt/rman/MYDB/ctl_%d_%t_%s_%p' current controlfile;
    8> }
    It works well until :
    backup format '/mnt/rman/MYDB/al_%d_%t_%s_%p' archivelog all delete input;
    Here it hangs up (may be there are many many archive log files). What do you propose ? How can we ask RMAN just backup archive logs since some recent dates ? How can we delete most of ancient archive logs ? Since many times RMAN backup was in error then archive logs were not deleted. Now impossible to finish RMAN backup. Many thanks for your help.

    Hi,
    I launched following since last night but it is always waiting :
    RMAN> crosscheck archivelog all;
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=110 devtype=DISK
    What can I do ? Any other way to say to RMAN that archived logs are not available ?
    Many thanks.

  • Setting up rman backups - am I missing something?

    I have inherited an oracle 10g database on Windows and I need to set up RMAN backups. I am going through the steps and I think I am still missing something.
    I am trying to put the database in archivelog mode and it gives me this error:
    ORA-01126: database must be mounted in this instance and not open in any instance
    So I try to mount the database (alter database mount;) and it says:
    ORA-01100: database already mounted
    So I figure someone else has it open so I shut it down (shutdown immediate), which works fine, but when I try to restart it (startup mount;) it tells me:
    ORA-24324: service handle not initialized
    ORA-01041: internal error. hostdef extension doesn't exist
    So I try to log into a new session and it tells me:
    ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
    The only way I can find to restart it is to restart the service OracleServiceDATABASENAME. When it is restarted, it lets me log in, but then I get the same errors as above when I try to mount the database or put it in archivelog mode.
    Please let me know what I am missing.
    Thanks!

    Over Windows, database service has a vital role in the management of the database. Without it being started, you can't do anything with oracle db. Fro your error,
    >
    ORA-24324:
    service handle not initialized
    Cause:     An attempt was made to use an improper service context handle.
    Action:     Verify that the service context handle has all the parameters initialized prior to this call.>
    It may be possible that you have used an inappropriate service name to start teh database. The other error comes up when the datbase is either just started or is unaware about teh name being requested by teh client to get connected, due to wrong name being chosen or an unknown name being chosen.
    All this basically means that you may have either done typos or tried to start some service which was never there. The best way is to set Oracle sid using
    set oracle_sid=<your sid>And then do what ever you want to.
    HTH
    Aman....

  • Restoring archives from rman backups

    i have taken backup of all archive logs as follows
    backup archivelog all delete all input;
    how to restore th archives at their original location

    816669 wrote:
    i have taken backup of all archive logs as follows
    backup archivelog all delete all input;
    how to restore th archives at their original locationWhile you can directly have rman restore the archivelogs, please note that if an archivelog is needed for database recovery, rman will know to restore said archivelog anyway.

  • RMAN BACKUPS AND ARCHIVED LOG ISSUES

    제품 : RMAN
    작성날짜 : 2004-02-17
    RMAN BACKUPS AND ARCHIVED LOG ISSUES
    =====================================
    Scenario #1:
    1)RMAN이 모든 archived log들을 삭제할 때 실패하는 경우.
    database는 두 개의 archive destination에 archive file을 생성한다.
    다음과 같은 스크립트를 수행하여 백업후에 archived redo logfile을 삭제한다.
    run {
    allocate channel c1 type 'sbt_tape';
    backup database;
    backup archivelog all delete input;
    Archived redo logfile 삭제 유무를 확인하기 위해 CROSSCHECK 수행시 다음과
    같은 메시지가 발생함.
    RMAN> change archivelog all crosscheck;
    RMAN-03022: compiling command: change
    RMAN-06158: validation succeeded for archived log
    RMAN-08514: archivelog filename=
    /oracle/arch/dest2/arcr_1_964.arc recid=19 stamp=368726072
    2) 원인분석
    이 문제는 에러가 아니다. RMAN은 여러 개의 arhive directory중 하나의
    directoy안에 있는 archived file들만 삭제한다. 그래서 나머지 directory안의
    archived log file들은 삭제되지 않고 남게 되는 것이다.
    3) 해결책
    RMAN이 강제로 모든 directory안의 archived log file들을 삭제하게 하기 위해서는
    여러 개의 채널을 할당하여 각 채널이 각 archive destination안의 archived file을
    백업하고 삭제하도록 해야 한다.
    이것은 아래와 같이 구현될 수 있다.
    run {
    allocate channel t1 type 'sbt_tape';
    allocate channel t2 type 'sbt_tape';
    backup
    archivelog like '/oracle/arch/dest1/%' channel t1 delete input
    archivelog like '/oracle/arch/dest2/%' channel t2 delete input;
    Scenario #2:
    1)RMAN이 archived log를 찾을 수 없어 백업이 실패하는 경우.
    이 시나리오에서 database를 incremental backup한다고 가정한다.
    이 경우 RMAN은 recover시 archived redo log대신에 incremental backup을 사용할
    수 있기 때문에 백업 후 모든 archived redo log를 삭제하기 위해 OS utility를 사용한다.
    그러나 다음 번 backup시 다음과 같은 Error를 만나게 된다.
    RMAN-6089: archive log NAME not found or out of sync with catalog
    2) 원인분석
    이 문제는 OS 명령을 사용하여 archived log를 삭제하였을 경우 발생한다. 이때 RMAN은
    archived log가 삭제되었다는 것을 알지 못한다. RMAN-6089는 RMAN이 OS 명령에 의해
    삭제된 archived log가 여전히 존재하다고 생각하고 백업하려고 시도하였을 때 발생하게 된다.
    3) 해결책
    가장 쉬운 해결책은 archived log를 백업할 때 DELETE INPUT option을 사용하는 것이다.
    예를 들면
    run {
    allocate channel c1 type 'sbt_tape';
    backup archivelog all delete input;
    두 번째로 가장 쉬운 해결책은 OS utility를 사용하여 archived log를 삭제한 후에
    다음과 같은 명령어를 RMAN prompt상에서 수행하는 것이다.
    RMAN>allocate channel for maintenance type disk;
    RMAN>change archivelog all crosscheck;
    Oracle 8.0:
         RMAN> change archivelog '/disk/path/archivelog_name' validate;
    Oracle 8i:
    RMAN> change archivelog all crosscheck ;
    Oracle 9i:
    RMAN> crosscheck archivelog all ;
    catalog의 COMPATIBLE 파라미터가 8.1.5이하로 설정되어 있으면 RMAN은 찾을 수 없는
    모든 archived log의 status를 "DELETED" 로 셋팅한다. 만약에 COMPATIBLE이 8.1.6이상으로
    설정되어 있으면 RMAN은 Repository에서 record를 삭제한다.

    Very strange, I issue following command in RMAN on both primary and standby machine, but it they don't delete the 1_55_758646076.dbf, I find in v$archived_log, this "/home/oracle/app/oracle/dataguard/1_55_758646076.dbf" had already been applied.
    RMAN> connect target /
    RMAN> CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
    old RMAN configuration parameters:
    CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
    new RMAN configuration parameters:
    CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
    new RMAN configuration parameters are successfully stored
    RMAN>
    ----------------------------------------------------------------------------------

  • How to control RMAN backup of archive logs in FRA

    Setup:
    11.2.0.2 GI
    ASM Diskgroup for Fast Recovery Area
    10.2.0.4 Enterprise Database
    Without Catalog Database
    To get familiar with Flashback Database we set up RMAN Backups
    without deleting the archive logs,
    as published in Oracle10g / 11g - Getting Started with Recovery Manager (RMAN) (Doc ID 360416.1)
    "These deletions are managed by Oracle when space is required."
    We observed that RMAN takes backups of all archive logs every time,
    here we go with backing up archive logs every 30 minutes.
    So the question is:
    Is this (backing up all archive logs every time) the expected behavior or
    the result of not using a catalog database or
    any other mismatch?
    thanx for any hint
    Michael

    Hi Michael,
    In Note 360416.1 it refers to two archivelog backup commands.
    BACKUP ARCHIVELOG ALL;and
    BACKUP ARCHIVELOG FROM TIME 'SYSDATE-30' UNTIL TIME 'SYSDATE-7';Your question:
    Is this (backing up all archive logs every time) the expected behavior or the result of not using a catalog database or any other mismatch?If you used the first script you will backup alle archivelogs everytime.
    If you use the second one it will do a subset (probably not the range you want to backup...)
    You could implement another script
    BACKUP ARCHIVELOG NOT BACKED UP 2 TIMES;So every archivelog is only backed up twice.
    Check
    http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta009.htm#i78895
    for more information.
    Regards,
    Tycho

  • RMAN Backup Issue when Full backup file was missing

    Hi,
    On : 11.2.0.2 version, Recovery Manager
    RMAN Backup issue
    Last week we had the NFS Issue where we backup the files onto NFS.
    The problem occurred in the below sequence
    Saturday the backup was successful
    Saturday before deleting the backup files they are copied to tape
    Deleting the backup files via OS command
    Sunday Full backup started but due the NFS issue backup failed(Killed the instance and restarted)
    Did the RMAN Incremental backup which worked on Monday
    On Tuesday RMAN started complaining and started doing the Full backup.
    no parent backup or copy of datafile 1 found
    no parent backup or copy of datafile 3 found
    no parent backup or copy of datafile 24 foundSony any idea why the Incremental backup worked on Monday but not on Tuesday
    Regards
    NM

    Ok here is why I would like exact filenames..
    1) to speed the time of recovery. I am much more familiar with traditional recovery methods than RMAN, and while I myself installed and suggested RMAN for backups, our other (11i) database does not use RMAN and so I am more familiar with traditional recovery. So to be able to recover quickly I want to have these files as close as possible to the original names so that I can use my standard script (from a trace file) to recreate the control fiile. If I can get RMAN to spit out the filies with original names but keep RMAN for making the backup, I may ditch the rman bacjup script in chron and write a traditional hot backup script which copies the files the old fashioned way.
    2) to reduce cloning time. The RMAN duplicate command is not as good as I thought. I was actually easier for me to restore RMAN backups first to a box that has all the same paths, and THEN shutdown (cold) these files and copy them cold to another server, and restore from there. Agaiin if I can get the original file names, I could choose to do recovery either way (RMAN or traditional) in a real emergency instead of being forced to use rman.
    3) to be able to switch to a backup file in the FRA without having to rename it. Seems logical if it is already named correctly.
    thanks ! Marvi

  • When the archive disk group and RMAN backup location is full

    11.2.0.2 on Solaris 10
    2-Node RAC
    Sometimes I am faced with a situation where the disk group meant for storing archivelogs is full and the Disk based
    RMAN backup location is full as well. What would you do in such a situation ?
    This usually happens with our QA/UAT DBs during apps testing of certain type which causes huge amount of redo is generated.
    We don't directly backup to tape. The disk based backups are moved to tape every two weeks by our SysAdmin.

    Thank you Hemant, Tsharma, Asahideo
    If I have free space left in my local filesystem in any of the nodes in my 2-node RAC, I can run something like
    -- Untested
    BACKUP AS COMPRESSED BACKUPSET ARCHIVELOG ALL DELETE INPUT format '/localNode_pATH/ora_Arch%t_s%s_s%p';and later when the space is freed up in the original RMAN backup location , I can move it there and use CATALOG command to catalog this backup . Right ?

  • Unable to restore and recover my Database from RMAN Backup

    Dear All,
    Iam practicing RMAN in Windows environment.
    My configurations are
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
    CONFIGURE BACKUP OPTIMIZATION ON; # default
    CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
    CONFIGURE CONTROLFILE AUTOBACKUP ON; # default
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'F:\Backup\%F'; # default
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'E:\ORACLE\DATABASE\SNCFORCL.ORA';
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT 'F:\Backup\%U.bak';
    Then i took the RMAN backup, now iam shutdown my DB and removed one logfile..
    then i tried to startup the DB but it is saying
    ORA-00313: open failed for members of log group 3 of thread 1
    ORA-00312: online log 3 thread 1: 'E:\ORADATA\ORCL\REDO03.LOG'
    So i tried to restore the Database with my rman backup
    RMAN> restore database;
    But i am unable to restore my logfile in the Datafiles location where as all other datafiles are restored but redo logfiles are not restored.
    So, i am unable to recover my DB
    Please tell me whether i am doing any mistake, what is the solution for my problem.
    Thanks in advance
    Mahi

    All you restored was your datafiles.
    Now issue recover database and that will apply the archive logs.
    This is in the oracle documentation.
    "You must restore backups of these archived logs for recovery to proceed. You can restore either to the default or nondefault location. If you do not have backups, then you must performing incomplete recovery up to an SCN before the first missing redo log and open RESETLOGS."
    http://download.oracle.com/docs/cd/B28359_01/backup.111/b28270/osrecvry.htm
    In this case after issuing restore database in RMAN, then issue this.
    "Recover database"
    It will then be an incomplete recovery. They should have been multiplexed. Did you restore your controlfile with this backup? You may have to issue an "Alter database open resetlogs;"

  • Rman backup errors..

    hi guru's
    please tell me the answeres..for this
    what will happen if we re run the Rman backup due to the job failure...will take a new backup from the begining? or will start from the first backup end where it left ?
    i am deleting some archieved logs on the archieved destination before takeing the RMAN backup, and then running rman backup ...then any error will raised for the missing files during Rman archive log backup for missing files? i have the files like 1 to 10 ...in that 5 and 6 logs are deleted before takeing the Rman backup..how to resolve this?

    user13014926 wrote:
    hi guru's
    please tell me the answeres..for this
    what will happen if we re run the Rman backup due to the job failure...will take a new backup from the begining? or will start from the first backup end where it left ?
    You can continue backup from which files not backed up and this is call restartable backup.Please refer below link
    http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmconc1.htm#i1008543
    >
    i am deleting some archieved logs on the archieved destination before takeing the RMAN backup, and then running rman backup ...then any error will raised for the missing files during Rman archive log backup for missing files? i have the files like 1 to 10 ...in that 5 and 6 logs are deleted before takeing the Rman backup..how to resolve this?If you manually delete archivelogs then you will get an error so before executing this backup command you have to execute CROSSCHECK ARCHIVELOG ALL and DELETE EXPIRED ARCHIVELOG ALL then your problem will solve.

Maybe you are looking for