How does oracle suggest the archive log

Hi All,
My question is about user managed backup and recovery.
For User managed hot database refreshes.
We  create a new controlfile and do cancel based recovery.
How does oracle suggest the next archive to apply when we do "recover database using backup controlfile until cancel;"
I mean we created a new control file ..rt.
where is the information about the archivelogs stored.
Thanks,
Silver

In the controlfile.
The "using backup controlfile" means using a backed up controlfile, and you want to fool Oracle into thinking a point in time recovery will happen so don't use what would be the controlfiles current scn time to automatically say the recovery is complete.  If you have created a new controlfile, all it can know about is where the logs should be and compare to what log sequences the datafile headers have.  So it uses the init.ora parameters and what the data file headers have in them to figure it out. http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:3151992035532#36651366990046
If you backup controlfile to trace you can see log files that have the incarnation history.  See "Recovering Through a RESETLOGS with a Created Control File"  in Performing User-Managed Recovery: Advanced Scenarios

Similar Messages

  • Online Consistent brbackup - How does SAP lock the archive files?

    With an Oracle online consistent brbacup, i believe that SAP locks the archive log files so they are not deleted during the backup.
    How do they do this?
    If a backup crashes how do I unlock these locks?

    Here is the statement (from the netbackup trace)  that caused brachive to stop.
    Set file /oracle/BP1/oraarch/BP1arch1_207989.dbf to QUIESCE status.
    Here is relevenmat part of the NetBAckup/backint log...
    5:21:36.691 [11248] <4> adjustObjectStatus: File </oracle/BP1/oraarch/BP1arch1_207989.dbf> in VxBSA_INPROGRESS status. No ch
    ange of status needed.
    15:21:36.691 [11248] <4> adjustObjectStatus: Done.
    15:21:36.691 [11248] <4> VxBSAWaitForFileListStatus: INF - entering WaitForFileListStatus.
    15:21:36.691 [11248] <4> bsa_handle_std_backup: INF - entering bsa_handle_std_backup.
    15:21:36.691 [11248] <4> bsa_comm_w_bkar: INF - entering bsa_comm_w_bkar.
    15:21:38.714 [11248] <4> bsa_comm_w_bkar: Recieved bpbkar message: #END /oracle/BP1/oraarch/BP1arch1_207989.dbf
    15:21:38.714 [11248] <4> bsa_comm_w_bkar: Comparing physical file  path: /oracle/BP1/oraarch/BP1arch1_207989.dbf
    15:21:38.714 [11248] <4> bsa_comm_w_bkar: to file from bpbkar message:   /oracle/BP1/oraarch/BP1arch1_207989.dbf
    15:21:38.714 [11248] <4> bsa_comm_w_bkar: File paths matched.
    15:21:38.714 [11248] <4> bsa_comm_w_bkar: Set file /oracle/BP1/oraarch/BP1arch1_207989.dbf to VxBSA_UNQUIESCE status.
    15:21:38.714 [11248] <4> bsa_comm_w_bkar: Recieved bpbkar message: #BEGIN /oracle/BP1/oraarch/BP1arch1_207989.dbf
    15:21:38.714 [11248] <4> bsa_comm_w_bkar: Comparing physical file  path: /oracle/BP1/oraarch/BP1arch1_207989.dbf
    15:21:38.714 [11248] <4> bsa_comm_w_bkar: to file from bpbkar message:   /oracle/BP1/oraarch/BP1arch1_207989.dbf
    15:21:38.714 [11248] <4> bsa_comm_w_bkar: File paths matched.
    15:21:38.714 [11248] <4> bsa_comm_w_bkar: Set file /oracle/BP1/oraarch/BP1arch1_207989.dbf to QUIESCE status.
    15:21:38.714 [11248] <4> bsa_comm_w_bkar: File /oracle/BP1/oraarch/BP1arch1_207989.dbf not in VxBSA_NOTREADY state.
    15:21:38.714 [11248] <16> bsa_comm_w_bkar: Can't change state.
    15:21:38.714 [11248] <4> do_file_backup: The sequence of calls is incorrect.
    15:21:38.715 [11248] <4> do_backup: Exit with status: <2>.
    15:21:38.715 [11248] <4> /usr/sap/BP1/SYS/exe/run/backint 6.0: **************************************************************

  • How does one name an Archive Log file in ARC%S_%R.%T format

    Hallo!I have been trying to enable Archive Log mode for the Oracle 10g database.
    In OEM,I went via the links Maintenance->Recovery Settings->Media Recovery
    There,a text box by the name Log Archive Filename Format requires one to name the Archive Log file in ARC%S_%R.%T format.
    I have tried several times to name the Archive log e.g ARC001_001.001 but when I shutdown and restart the database instance,the error below appears
    ORA-19905: log_archive_format must contain %s, %t and %r.
    This error has proved impossible to rectify and I am forced to uninstall then re-install Oracle 10g.
    I would like to have back-ups in archive log mode.Please give me the best way to name the Archive Log file i.e with an example name so that I can have online back-ups.
    Thanks.

    Hi,
    If you try to change the LOG_ARCHIVE_FORMAT to something other than the default %s,%t,%r, it will fail
    Perform as the below steps in order to enable archive log mode
    SQL>create pfile from spfile
    SQL>create pfile='c:\temp\init.ora' from spfile;
    SQL>created;
    SQL>shutdown immediate;
    edit the init.ora file by adding the following information
    *.LOG_ARCHIVE_DEST_1='LOCATION=C:\db\archive1'
    *.LOG_ARCHIVE_FORMAT='%t_%s_%r.dbf'
    Start the DB with modified pfile.
    - Pavan Kumar N
    Edited by: Pavan Kumar on May 2, 2010 2:17 PM

  • How does oracle know the databse is inconsistent and needs recovery?

    Hello,
    How does Oracle know that the datafiles are inconsistent and db needs recovery when rebuilding the db off of the online/hot backups? Whereas, it doesn’t ask for recovery when rebuilding the database from cold backup (I understand that, for cold backup, database is shutdown immediate and hence the db is consistent). In both scenarios, a new control file is created (that means it won’t have SCN) and only datafile header will have the SCN. What’s that piece of info that oracle check to know if the database is consistent or inconsistent during the backup restore and recovery and where that info resides?
    Thank you for any hints and answers.
    Jay

    Oracle uses the datafiles to identify if they are consistent. If the datafiles backup was taken when the database was OPEN, they are marked as "fuzzy" in the header. Also, likely, the Checkpoint SCNs may be different if tablespace checkpoints (e.g. by ALTER TABLESPACE BEGIN BACKUP) are at different points in time.
    If the backup was a cold backup with the database shutdown normal/immediate, the headers are marked appropriately.
    When you run CREATE CONTROLFILE, it has to read the datafiles because the controlfile, itself, has no SCN and LogSequenceNumbers information.
    Hemant K Chitale

  • How  can i see the Archive log backup contens from th tapes

    hello
    I am taking Archive log Backup regularly
    i want ot chk my backup contents from tape through the db2 command
    From DB13 it  is showing successfully  Completed
    but for the comfirmation where and how i can see the contents of tape
    Point in advance from me
    Jayesh

    Hello Jayesh ,
    using db2tapemgr you can display the tape header DB2TAPEMGR.HEADER using
    db2tapemgr SHOW TAPE HEADER  <tape device>
    in "contents:" field you can see , which logfiles are on tape at which position .
    see
    [db2tapemgr - Manage log files on tape  command|http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/index.jsp?topic=/com.ibm.db2.luw.admin.cmd.doc/doc/r0011704.html]
    [IBM DB2 Universal Database for UNIX and Windows:New Log File Management|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/50c7d3ef-5a59-2a10-a3ab-fb3b0887f479]
    Best regards
    dirk

  • How does Oracle fills the Blocks of an extent ?

    Hi,
    does anybody know why Oracle uses p.e. the fourth block of the first extent, then the 8th block, and not continous amount of blocks?
    So the HWM is higher then necessary.
    Thanks
    Marco

    Thanks Mark for the fast Reply.
    Yes, you are right, seeing is beliving ... :-)
    I had imported a table into the db (and there were NO deletes!)
    SQL> select tablespace_name, initial_extent, ALLOCATION_TYPE, SEGMENT_SPACE_MANAGEMENT from dba_tablespaces where tablespace_name='KUNDEN';
    TABLESPACE_NAME INITIAL_EXTENT ALLOCATIO SEGMEN
    KUNDEN 5242880 UNIFORM AUTO
    SQL> select count(*) from orte;
    COUNT(*)
    1628
    SQL> select segment_name, tablespace_name, header_block, bytes, blocks, extents from dba_segments where segment_name='ORTE';
    SEGMENT_NAME TABLESPACE_NAME HEADER_BLOCK BYTES BLOCKS EXTENTS
    ORTE KUNDEN 28820 5242880
    640 1
    SQL> SELECT DBMS_ROWID.ROWID_BLOCK_NUMBER(ROWID) AS block_nr, COUNT(*) AS anzahl FROM orte
    GROUP BY DBMS_ROWID.ROWID_BLOCK_NUMBER(ROWID)
    BLOCK_ID ROWS_IN_BLOCK
    28844 255
    28848 218
    28852 230
    28856 233
    28864 241
    28860 244
    28868 207
    Thanks
    Marco

  • How does Oracle handles the delete ?

    Hi ,
    I have a unix loder that does the issue this command
    EXEC SQL DELETE FROM TBl1 where id in (select id from TMP)
    if any user is accessing a record in TBL1 , will Oracle wait for the record to be released before it does the delete or it simply skip it ?
    pls advise
    tks & rgds

    It will wait please look at the example below:
    Session 1:
    [email protected]> select * from dept;
    DEPTNO DNAME LOC
    10 ACCOUNTING NEW YORK
    20 RESEARCH DALLAS
    30 SALES CHICAGO
    40 OPERATIONS BOSTON
    [email protected]> update dept set loc = 'WARSAW' where deptno = 10;
    1 row updated.
    Session 2:
    [email protected]> delete dept;
    -- waiting
    Session 1:
    [email protected]> commit;
    Commit complete.
    Session 2:
    4 rows deleted.
    [email protected]> select * from dept;
    DEPTNO DNAME LOC
    10 ACCOUNTING WARSAW
    20 RESEARCH DALLAS
    30 SALES CHICAGO
    40 OPERATIONS BOSTON
    Location was changed
    Best Regards
    Krystian Zieja / mob

  • How to find out who deleted the archive logs

    Hi All,
    Recently some archive logs were deleted from one of our servers. Is there any way to find out which user has deleted the archive logs through OS or through database ?
    OS Version :-
    SunOS Generic_Virtual sun4u sparc SUNW,SPARC-Enterprise
    Database Version:-
    SQL*Plus: Release 9.2.0.8.0 - Production on Mon Apr 9 01:12:15 2012

    888132 wrote:
    Hi All,
    Recently some archive logs were deleted from one of our servers. Is there any way to find out which user has deleted the archive logs through OS or through database ?
    OS Version :-
    SunOS Generic_Virtual sun4u sparc SUNW,SPARC-Enterprise
    Database Version:-
    SQL*Plus: Release 9.2.0.8.0 - Production on Mon Apr 9 01:12:15 2012As explained by others, from oracle database there is no record if they are deleted from OS.
    But you can probably find the history of OS command been run with history command :). You can get the date and time.
    Following link can help
    http://stackoverflow.com/questions/99755/how-do-i-get-the-command-buffer-in-solaris-10
    http://www.cyberciti.biz/faq/unix-linux-bash-history-display-date-time/
    http://www.linuxquestions.org/questions/solaris-opensolaris-20/in-solaris-command-line-how-to-get-the-previous-commands-573814/
    But i suggest you to post in Sun OS forum to get more details as its nothing to do with Database(in this scenario)

  • *HOW TO DELETE THE ARCHIVE LOGS ON THE STANDBY*

    HOW TO DELETE THE ARCHIVE LOGS ON THE STANDBY
    I have set the RMAN CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY; on my physical standby server.
    My archivelog files are not deleted on standby.
    I have set the CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default on the Primary server.
    I've checked the archivelogs with the FRA and they are not beign deleted on the STANDBY. Do I have to do something for the configuation to take effect? Like run a RMAN backup?
    I've done a lot ofresearch and i'm getting mixed answers. Please help. Thanks in advanced.
    J

    Setting the Policy will not delete the Archive logs on the Standby. ( I found a thread where the Data Guard product manager says "The deletion policy on both sides will do what you want" ). However I still
    like to clean them off with RMAN.
    I would use RMAN to delete them so that it can use that Policy are you are protected in case of Gap, transport issue etc.
    There are many ways to do this. You can simply run RMAN and have it clean out the Archive.
    Example :
    #!/bin/bash
    # Name: db_rman_arch_standby.sh
    # Purpose: Database rman backup
    # Usage : db_rman_arch_standby <DBNAME>
    if [ "$1" ]
    then DBNAME=$1
    else
    echo "basename $0 : Syntax error : use . db_rman_full <DBNAME> "
    exit 1
    fi
    . /u01/app/oracle/dba_tool/env/${DBNAME}.env
    echo ${DBNAME}
    MAILHEADER="Archive_cleanup_on_STANDBY_${DBNAME}"
    echo "Starting RMAN..."
    $ORACLE_HOME/bin/rman target / catalog <user>/<password>@<catalog> << EOF
    delete noprompt ARCHIVELOG UNTIL TIME 'SYSDATE-8';
    exit
    EOF
    echo `date`
    echo
    echo 'End of archive cleanup on STANDBY'
    mailx -s ${MAILHEADER} $MAILTO < /tmp/rmandbarchstandby.out
    # End of ScriptThis uses ( calls an ENV) so the crontab has an environment.
    Example ( STANDBY.env )
    ORACLE_BASE=/u01/app/oracle
    ULIMIT=unlimited
    ORACLE_SID=STANDBY
    ORACLE_HOME=$ORACLE_BASE/product/11.2.0.2
    ORA_NLS33=$ORACLE_HOME/ocommon/nls/admin/data
    LD_LIBRARY_PATH=$ORACLE_HOME/lib:/lib:/usr/lib
    LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib
    LIBPATH=$LD_LIBRARY_PATH:/usr/lib
    TNS_ADMIN=$ORACLE_HOME/network/admin
    PATH=$ORACLE_HOME/bin:$ORACLE_BASE/dba_tool/bin:/bin:/usr/bin:/usr/ccs/bin:/etc:/usr/sbin:/usr/ucb:$HOME/bin:/usr/bin/X11:/sbin:/usr/lbin:/GNU/bin/make:/u01/app/oracle/dba_tool/bin:/home/oracle/utils/SCRIPTS:/usr/local/bin:.
    #export TERM=linux=80x25 wrong wrong wrong wrong wrong
    export TERM=vt100
    export ORACLE_BASE ORACLE_SID ORACLE_TERM ULIMIT
    export ORACLE_HOME
    export LIBPATH LD_LIBRARY_PATH ORA_NLS33
    export TNS_ADMIN
    export PATH
    export MAILTO=?? your email hereNote use the env command in Unix to get you settings.
    There are probably ten other/better ways to do this, but this works.
    other options ( you decide )
    Configure RMAN to purge archivelogs after applied on standby [ID 728053.1]
    http://www.oracle.com/technetwork/database/features/availability/rman-dataguard-10g-wp-1-129486.pdf
    Maintenance Of Archivelogs On Standby Databases [ID 464668.1]
    Tip I don't care myself but in some of the other forums people seem to mind if you use all caps in the subject. They say it shouting. My take is if somebody is shouting at me I'm probably going to just move away.
    Best Regards
    mseberg
    Edited by: mseberg on May 8, 2012 11:53 AM
    Edited by: mseberg on May 8, 2012 11:56 AM

  • RMAN-20242: specification does not match any archive log in the recovery ca

    Hi,
    I'm working with an 9i Oracle RAC (yes, I know this version is out of support...). I'm launching my backup from node 1 with this script
    run {
    sql 'alter system switch logfile'
    sql 'alter system archive log current'
    allocate channel TSM1 type 'sbt_tape' connect *
    parms='ENV=(TDPO_OPTFILE=/home/adsmadm/rman_INF01T01/opt/tdpo.opt)'
    allocate channel TSM2 type 'sbt_tape' connect *
    parms='ENV=(TDPO_OPTFILE=/home/adsmadm/rman_INF01T01/opt/tdpo.opt)'
    backup
    format 'brman_arch_%s_%p'
    (archivelog like '/logs/bbdd/oracle/INF01T01/archiver/%' channel TSM1 delete input )
    (archivelog like '/logs/bbdd/oracle/INF01T03/archiver/%' channel TSM2 delete input )
    release channel TSM2
    release channel TSM1
    And fail with this error:
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of backup command at 08/13/2012 22:36:43
    RMAN-06004: ORACLE error from recovery catalog database: RMAN-20242: specification does not match any archive log in the recovery catalog
    I've take a look to the archives directories and both nodes have archives:
    ora10g:/opt/ora10g > ls -lrt /logs/bbdd/oracle/INF01T01/archiver
    total 97896
    -rw-r----- 1 ora10g dba 2048 Aug 13 22:36 T0001S00000061440648489222.ARC
    -rw-rw---- 1 ora10g dba 38132224 Aug 13 22:36 T0001S00000061430648489222.ARC
    -rw-r----- 1 ora10g dba 11984896 Aug 13 22:36 T0002S00000044040648489222.ARC
    ora10g:/opt/ora10g > ls -lrt /logs/bbdd/oracle/INF01T03/archiver
    total 392984
    -rw-r----- 1 ora10g dba 49364992 Mar 24 2009 T0002S00000007020648489222.ARC
    -rw-r----- 1 ora10g dba 49364992 Mar 25 2009 T0002S00000007030648489222.ARC
    -rw-rw---- 1 ora10g dba 19314688 Mar 25 2009 T0002S00000007040648489222.ARC
    -rw-rw---- 1 ora10g dba 4733952 Mar 25 2009 T0002S00000007050648489222.ARC
    -rw-rw---- 1 ora10g dba 4608 Apr 09 2009 T0002S00000007440648489222.ARC
    -rw-rw---- 1 ora10g dba 2541056 Sep 26 2009 T0002S00000015420648489222.ARC
    -rw-rw---- 1 ora10g dba 49373184 Sep 28 2009 T0002S00000015430648489222.ARC
    -rw-rw---- 1 ora10g dba 3410432 Feb 11 2010 T0002S00000018680648489222.ARC
    -rw-rw---- 1 ora10g dba 599552 Feb 12 2010 T0002S00000018710648489222.ARC
    -rw-rw---- 1 ora10g dba 6574080 Mar 03 2010 T0002S00000019200648489222.ARC
    -rw-rw---- 1 ora10g dba 1663488 Mar 08 2010 T0002S00000019340648489222.ARC
    -rw-rw---- 1 ora10g dba 431104 Apr 07 2010 T0002S00000020160648489222.ARC
    -rw-rw---- 1 ora10g dba 13811712 Apr 19 2010 T0002S00000020460648489222.ARC
    I've tried to made a crosscheck but, only found node1 archives:
    RMAN> change archivelog all crosscheck;
    validation succeeded for archived log
    archive log filename=/logs/bbdd/oracle/INF01T01/archiver/T0001S00000061430648489222.ARC recid=10685 stamp=791246196
    validation succeeded for archived log
    archive log filename=/logs/bbdd/oracle/INF01T01/archiver/T0001S00000061440648489222.ARC recid=10686 stamp=791246196
    validation succeeded for archived log
    archive log filename=/logs/bbdd/oracle/INF01T01/archiver/T0002S00000044040648489222.ARC recid=10687 stamp=791246197
    Crosschecked 3 objects
    Any idea about the way to solve it?
    Thanks in advance!
    dbajug

    Hi,
    Connect to target through rman
    crosscheck archivelog all;
    Then re run the backup. This will work if those two locations provided are archive log destinations.
    In case the issue still persists then
    Connect to target through rman
    catalog start with '/logs/bbdd/oracle/INF01T01/archiver/';
    catalog start with '/logs/bbdd/oracle/INF01T03/archiver/';
    Then re run the backup.
    Thanks,
    Vivek
    Edited by: 952807 on Aug 16, 2012 5:21 PM

  • I accidently delete the archived log, how to recover?

    There was old archived log file in a directory, I delete the directory, so when I backup whole archived log with RMAN, I often got error like this,
    RMAN-06059: expected archived log not found, lost of archived log compromises recoverabiligy
    ora-196525: error identifying file G:\oracle\oradata\archive\arc00081.001
    I am using oracle 9.2 on windows XP
    Edited by: user8117130 on Jun 14, 2009 9:35 PM

    HI..
    I delete the directory, so when I backup other archived log with RMAN, I often got error like this From metalink:-
    Error:     RMAN-06059 (RMAN-6059)Text:     expected archived log not found, lost of archived log compromises
         recoverability
    Cause:     The archived log was not found. The repository thinks it does
         exist. If the archived log has in fact been lost and there is no
         backup, then the database is no longer recoverable across the
         point in time covered by the archived log. This may occur because
         the archived log was removed by an outside utility without
         updating the repository.
    Action:     If the archived log has been removed with an outside utility and
         the archivelog has already been backed up, then you can
         synchronize the repository by running CROSSCHECK ARCHIVELOG ALL.
         If the archivelog has not been previously backed up, then you
         should take a full backup of the database and archivelogs to
         preserve recoverability. Previous backups are not fully
         recoverable.
    >
    Anand

  • RMAN - specification does not match any archived log in the repository

    Hi All,
    Oracle 11G R2 on WIndows woo8 R2 Std Edition
    I am running RMAN (almost for the first time), and i am using a script previously used. As i am checking through the log, i notice some 'errors' though the backup finishes successfully.
    RMAN> crosscheck archivelog all;
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=352 device type=DISK
    specification does not match any archived log in the repository
    RMAN> crosscheck backupset;
    using channel ORA_DISK_1
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=D:\ORACLE\DATABASE\ORADATA\MMSPRD7\ORAFRA\MMSPRD7\BACKUPSET\
    2013_04_23\O1_MF_NCNNF_TAG20130423T134331_8QFL24F7_.BKP RECID=16 STAMP=813505412
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=D:\ORACLE\DATABASE\ORADATA\MMSPRD7\ORAFRA\MMSPRD7\BACKUPSET\
    2013_04_23\O1_MF_ANNNN_TAG20130423T134334_8QFL26K1_.BKP RECID=17 STAMP=813505414
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=D:\ORACLE\DATABASE\ORADATA\MMSPRD7\ORAFRA\MMSPRD7\BACKUPSET\
    2013_04_23\O1_MF_NCNNF_TAG20130423T134423_8QFL3S48_.BKP RECID=18 STAMP=813505465
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=D:\ORACLE\DATABASE\ORADATA\MMSPRD7\ORAFRA\MMSPRD7\BACKUPSET\
    2013_04_23\O1_MF_ANNNN_TAG20130423T134427_8QFL3V9J_.BKP RECID=19 STAMP=813505467
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=D:\ORACLE\DATABASE\ORADATA\MMSPRD7\ORAFRA\MMSPRD7\BACKUPSET\
    2013_04_23\O1_MF_NNNDF_TAG20130423T134428_8QFL3XDT_.BKP RECID=20 STAMP=813505469
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=D:\ORACLE\DATABASE\ORADATA\MMSPRD7\ORAFRA\MMSPRD7\BACKUPSET\
    2013_04_23\O1_MF_NCSNF_TAG20130423T134428_8QFM4C5S_.BKP RECID=21 STAMP=813506507
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=D:\ORACLE\DATABASE\ORADATA\MMSPRD7\ORAFRA\MMSPRD7\BACKUPSET\
    2013_04_23\O1_MF_ANNNN_TAG20130423T140148_8QFM4DOT_.BKP RECID=22 STAMP=813506508
    Crosschecked 7 objects
    RMAN> crosscheck copy;
    released channel: ORA_DISK_1
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=352 device type=DISK
    specification does not match any datafile copy in the repository
    specification does not match any control file copy in the repository
    specification does not match any archived log in the repositorySo there are 2 instances of the errors:
    1) crosscheck archivelog all - when the error happens here, i think this means that there are no archived redo logs in the archivelog destination?? ..or something to that nature.
    2) crosscheck copy - not sure what the other errors mean here.
    Thx in advance!

    1) crosscheck archivelog all - when the error happens here, i think this means that there are no archived redo logs in the archivelog destination?? ..or something to that nature.
    2) crosscheck copy - not sure what the other errors mean here.
    specification does not match any archived log in the repositoryI don't see the error here, it's only a msg that mean : There is no files on XXX destination, which is normal when no files found.

  • "specification does not match any archived log in the recovery catalog"

    I would like to know about this message.
    I Validated my backup and archivelogs yesterday.
    Today when I tried to do - CROSSCHECK ARCHIVELOG ALL;
    I gave me the following error -
    RMAN> crosscheck archivelog all;
    released channel: ORA_SBT_TAPE_1
    released channel: ORA_DISK_1
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=291 device type=DISK
    specification does not match any archived log in the recovery catalog
    when I tried to list all the archivelogs then also I am getting this message -
    RMAN> list archivelog all;
    specification does not match any archived log in the recovery catalog
    I have retention policy of 15 Days.
    Waiting for your inputs.

    Thanks Werner..This means that it is just a message.
    One more question related to Archive Log backups -
    traditionally DBAs used to take backup of an Archivelog by spupplying "alter system archive log current" before taking the backup. somewhat like -
    run
    allocate channel t1 device type 'sbt_tape' PARMS="ENV=(TDPO_OPTFILE=/oracle/TESTDB/tdpo.opt)";
    sql 'alter system archive log current';
    backup archivelog all delete input;
    release channel t1;
    But, since RMAN automatically archives CURRENT redo log at the start of the archivelog backup, do we REALLY need to pass sql 'alter system archive log current'; before starting the archivelog backup in the script?
    RMAN> backup archivelog all;
    Starting backup at 11-MAR-10
    current log archived ===========> RMAN automatically archived the CURRENT redo log
    released channel: ORA_DISK_1
    allocated channel: ORA_SBT_TAPE_1
    related question to this is - Since it generates one archived log everytime it takes the archived log backup, this backup may get hung if the archived destination is 100% full. Is there any way we can take the archive log backup without generating an extra archived log before the start of the backup?
    Thanks,
    Roopesh

  • Specification does not match any archive log in the recovery catalog

    Hi
    My rman backups sometimes fails with below error, any idea the reason ?
    run {
    allocate channel t1 type 'SBT_TAPE';
    backup
    incremental level 0
    format '/%d_%p_%t.%s/'
    maxsetsize = 8G
    (database);
    backup
    format '/%d_%p_%t_al.%s/'
    (archivelog from time 'SYSDATE-2');
    backup
    format '/%d_%p_%t_al.%s/'
    (archivelog until time 'SYSDATE-2' delete input);
    release channel t1;
    Starting backup at 2011-01-18 22:41:59
    current log archived
    channel t1: starting archive log backupset
    channel t1: specifying archive log(s) in backup set
    input archive log thread=1 sequence=7348 recid=6260 stamp=740682001
    input archive log thread=1 sequence=7349 recid=6261 stamp=740702540
    input archive log thread=1 sequence=7350 recid=6262 stamp=740739604
    input archive log thread=1 sequence=7351 recid=6263 stamp=740746801
    input archive log thread=1 sequence=7352 recid=6264 stamp=740757602
    input archive log thread=1 sequence=7353 recid=6265 stamp=740768401
    input archive log thread=1 sequence=7354 recid=6266 stamp=740788921
    channel t1: starting piece 1 at 2011-01-18 22:42:04
    channel t1: finished piece 1 at 2011-01-18 22:42:29
    channel t1: backup set complete, elapsed time: 00:00:26
    Finished backup at 2011-01-18 22:42:29
    Starting backup at 2011-01-18 22:42:31
    released channel: t1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of backup command at 01/18/2011 22:42:31
    RMAN-06004: ORACLE error from recovery catalog database: RMAN-20242: specification does not match any archive log in the recovery catalog
    Recovery Manager complete.

    Hi Ora 83,
    What is the reason of this error ? The reason for the RMAN-20242 is there are no archivelogs which comply to the filter "until time 'SYSDATE-2'" at 18 Jan 22:42.
    Probably you run a purge command more frequent because the oldest logsequence available for backup was created at:
    2011 JAN 17 17 00 01 (=sequence=7348)
    and the latest at:
    2011 JAN 18 22 42 01 (=sequence=7354)
    according to your output.
    So for some reason the archivelogs created before 16th Jan 22:42 are not on the system as well as the archivelogs created between 16th Jan 22:42 and 17 Jan 17:00.
    Maybe there are none (you can check in the alertlog and let us know)?
    Regards,
    Tycho

  • Pecification does not match any archive log in the recovery catalog

    MAN> list archivelog all;
    pecification does not match any archive log in the recovery catalog
    RMAN> list backup of archivelog all
    BS Key Size Device Type Elapsed Time Completion Time
    671197 5.17M DISK 00:00:03 29-MAY-11
    BP Key: 671200 Status: AVAILABLE Compressed: YES Tag: TAG20110529T180030
    Piece Name: F:\OSSTDBY_BACKUP\ARCH\OSONDEMA_ARC_20110529_FVMDIGPU_S25087_P1
    List of Archived Logs in backup set 671197
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 44836 503663671 29-MAY-11 503675934 29-MAY-11
    2 22517 503663669 29-MAY-11 503675932 29-MAY-11
    BS Key Size Device Type Elapsed Time Completion Time
    671232 5.12M DISK 00:00:02 29-MAY-11
    BP Key: 671235 Status: AVAILABLE Compressed: YES Tag: TAG20110529T200050
    Piece Name: F:\OSSTDBY_BACKUP\ARCH\OSONDEMA_ARC_20110529_G1MDINRJ_S25089_P1
    List of Archived Logs in backup set 671232
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 44837 503675934 29-MAY-11 503688661 29-MAY-11
    2 22518 503675932 29-MAY-11 503688659 29-MAY-11
    BS Key Size Device Type Elapsed Time Completion Time
    671267 5.14M DISK 00:00:03 29-MAY-11
    BP Key: 671270 Status: AVAILABLE Compressed: YES Tag: TAG20110529T220036
    Piece Name: F:\OSSTDBY_BACKUP\ARCH\OSONDEMA_ARC_20110529_G3MDIUS4_S25091_P1
    List of Archived Logs in backup set 671267
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 44838 503688661 29-MAY-11 503701009 29-MAY-11
    2 22519 503688659 29-MAY-11 503701007 29-MAY-11
    BS Key Size Device Type Elapsed Time Completion Time
    671302 16.55M DISK 00:00:05 30-MAY-11
    BP Key: 671305 Status: AVAILABLE Compressed: YES Tag: TAG20110530T000048
    Piece Name: F:\OSSTDBY_BACKUP\ARCH\OSONDEMA_ARC_20110530_G5MDJ5TG_S25093_P1
    List of Archived Logs in backup set 671302
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 44839 503701009 29-MAY-11 503716961 30-MAY-11
    2 22520 503701007 29-MAY-11 503716959 30-MAY-11
    BS Key Size Device Type Elapsed Time Completion Time
    671337 5.13M DISK 00:00:02 30-MAY-11
    BP Key: 671340 Status: AVAILABLE Compressed: YES Tag: TAG20110530T020121
    Piece Name: F:\OSSTDBY_BACKUP\ARCH\OSONDEMA_ARC_20110530_G7MDJCVI_S25095_P1
    List of Archived Logs in backup set 671337
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 44840 503716961 30-MAY-11 503729544 30-MAY-11
    2 22521 503716959 30-MAY-11 503729542 30-MAY-11
    BS Key Size Device Type Elapsed Time Completion Time
    671372 5.25M DISK 00:00:03 30-MAY-11
    BP Key: 671375 Status: AVAILABLE Compressed: YES Tag: TAG20110530T040055
    Piece Name: F:\OSSTDBY_BACKUP\ARCH\OSONDEMA_ARC_20110530_G9MDJJVN_S25097_P1
    the archives are in the location of
    F:\OSSTDBY_BACKUP\ARCH\OSONDEMA_ARC_20110529_G1MDINRJ_S25089_P1
    when it is not specified in catalog how can i delete archives from f location i.e
    F:\OSSTDBY_BACKUP\ARCH\OSONDEMA_ARC_20110529_G1MDINRJ_S25089_P1
    please let me know from rman how can i delete archives from f location...........................
    do i need to register with catalog?
    i have used Delete archivelog all completed before 'SYSDATE-10';
    but no use
    out put is
    MAN> Delete archivelog all completed before 'SYSDATE-10';
    eleased channel: ORA_DISK_1
    llocated channel: ORA_DISK_1
    hannel ORA_DISK_1: sid=311 devtype=DISK
    pecification does not match any archive log in the recovery catalog
    MAN> crosscheck backup archivelog all;
    please send me the query which i can delete ......................thanks
    cheers
    mahesh

    EdStevens wrote:
    856483 wrote:
    <snip>
    can i have you mobile contact phone number if possible?
    I have seen some pretty astonishing requests on this board, but this one really raises (or lowers) the bar. Just what is it your boss is paying you to do?
    Some listserves have lots of people giving their number. I find it odd that people would, but not astonishing for someone to ask. Outside the norm here, but how would someone know ahead of time? It's a bravely connected new world.

Maybe you are looking for