Open resetlogs after RMAN duplicate fails

Hi,
I wonder if anybody else has come across this issue, or is able to shed any light on it.
I have done a duplicate database to a new host with RMAN.
At the point where the duplicate opens the new database with resetlogs
I get this error in the alert log:
alter database open resetlogs
Tue Apr 7 02:10:06 2009
Errors in file /oracle/admin/udump/db1_ora_13931.trc:
ORA-00367: checksum error in log file header
ORA-00305: log 1 of thread 1 inconsistent; belongs to another database
ORA-00312: online log 1 thread 1: '/oracle/oradata/redo/db1_REDO_01A.log'
additional info: Oracle 10.2.0.4, Linux o/s.
thanks.

i have used the logfile keyword in the duplicate script to tell the duplicate
location and size of redologs.
duplicate target database to db1
logfile
group 1 ('/oracle/oradata/redo/db1_REDO_01A.log'
,'/oracle/oradata/redo/db1_REDO_01B.log') SIZE 200M REUSE,
group 2 ('/oracle/oradata/redo/db1_REDO_02A.log'
,'/oracle/oradata/redo/db1_REDO_02B.log') SIZE 200M REUSE,
group 3 ('/oracle/oradata/redo/db1_REDO_03A.log'
,'/oracle/oradata/redo/db1_REDO_03B.log') SIZE 200M REUSE,
group 4 ('/oracle/oradata/redo/db1_REDO_04A.log
','/oracle/oradata/redo/db1_REDO_04B.log') SIZE 200M REUSE;
my thoughts are that the resetlogs will make automatically recreate the redo logs.
there were pre-existing ones in this location, but REUSE should overcome this issue?

Similar Messages

  • After  RMAN duplicate  adcfgclone dbconfig completing with error

    we have R12.1.1 on redhat 5.3 ( 64 bit ).
    i am clonning my TEST server with RMAN hot full backup.
    i am using command
    rman target sys/prod_sys@PROD catalog rman/rman@PROD auxiliary /
    run {
    set until scn 5967654364306;
    allocate auxiliary channel ch1 type disk;
    allocate auxiliary channel ch2 type disk;
    duplicate target database to TEST8002;}
    when this command has restored database then i have to perform a
    CANCEL based recovery
    alter database open resetlogs;
    after that when i run
    perl adcfgclone dbconfig it is ending with error at 50%
    Controlfile creation failed.
    How to proceed ?
    Edited by: user13376823 on Nov 13, 2012 7:03 PM

    '/opt/R12.1.3/oracle/db/apps_st/data/a_ref01.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/a_int01.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/a_summ01.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/a_nolog01.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/a_archive01.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/a_queue01.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/a_media01.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/a_ref02.dbf'
    RESETLOGS MAXDATAFILES 512
    MAXINSTANCES 8
    MAXLOGFILES 32
    MAXLOGHISTORY 14607
    MAXLOGMEMBERS 5
    WARNING: Default Temporary Tablespace not specified in CREATE DATABASE command
    Default Temporary Tablespace will be necessary for a locally managed database in future release
    Setting recovery target incarnation to 1
    Successful mount of redo thread 1, with mount id 3760580547
    Completed: CREATE CONTROLFILE REUSE SET DATABASE "TEST8002"
    LOGFILE
    GROUP 1 ('/opt/R12.1.3/oracle/db/apps_st/data/log01a.dbf', '/opt/R12.1.3/oracle/db/apps_st/data/log01b.dbf') SIZE 1048576000,
    GROUP 2 ('/opt/R12.1.3/oracle/db/apps_st/data/log02a.dbf', '/opt/R12.1.3/oracle/db/apps_st/data/log02b.dbf') SIZE 1048576000
    DATAFILE
    '/opt/R12.1.3/oracle/db/apps_st/data/system12.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/system11.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/system10.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/system01.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/system02.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/system03.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/system04.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/system05.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/system06.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/system07.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/system08.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/system09.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/system13.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/sysaux01.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/sysaux02.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/ctxd01.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/a_txn_data04.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/a_txn_ind06.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/a_txn_data05.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/a_txn_data06.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/a_txn_ind07.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/a_txn_data07.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/a_txn_data01.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/a_txn_ind01.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/a_txn_data02.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/a_txn_data03.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/a_txn_ind02.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/a_txn_ind03.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/a_txn_ind04.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/a_txn_ind05.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/owad01.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/a_queue02.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/odm.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/olap.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/apps_ts_tools01.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/a_ref03.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/a_int02.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/a_media02.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/undo02.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/sscards_01.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/rman_01.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/a_summ02.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/a_summ03.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/portal01.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/undo01.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/a_ref01.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/a_int01.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/a_summ01.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/a_nolog01.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/a_archive01.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/a_queue01.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/a_media01.dbf',
    '/opt/R12.1.3/oracle/db/apps_st/data/a_ref02.dbf'
    RESETLOGS MAXDATAFILES 512
    MAXINSTANCES 8
    MAXLOGFILES 32
    MAXLOGHISTORY 14607
    MAXLOGMEMBERS 5
    alter database open resetlogs
    ORA-1194 signalled during: alter database open resetlogs...
    alter tablespace TEMP1 add tempfile '/opt/R12.1.3/oracle/db/apps_st/data/temp01.dbf' REUSE
    ORA-1109 signalled during: alter tablespace TEMP1 add tempfile '/opt/R12.1.3/oracle/db/apps_st/data/temp01.dbf' REUSE...
    alter tablespace TEMP2 add tempfile '/opt/R12.1.3/oracle/db/apps_st/data/temp02.dbf' REUSE
    ORA-1109 signalled during: alter tablespace TEMP2 add tempfile '/opt/R12.1.3/oracle/db/apps_st/data/temp02.dbf' REUSE...
    alter tablespace TEMP1 add tempfile '/opt/R12.1.3/oracle/db/apps_st/data/temp01A.dbf' REUSE
    ORA-1109 signalled during: alter tablespace TEMP1 add tempfile '/opt/R12.1.3/oracle/db/apps_st/data/temp01A.dbf' REUSE...
    alter tablespace TEMP2 add tempfile '/opt/R12.1.3/oracle/db/apps_st/data/temp02A.dbf' REUSE
    ORA-1109 signalled during: alter tablespace TEMP2 add tempfile '/opt/R12.1.3/oracle/db/apps_st/data/temp02A.dbf' REUSE...
    alter tablespace TEMP1 add tempfile '/opt/R12.1.3/oracle/db/apps_st/data/temp03.dbf' REUSE
    ORA-1109 signalled during: alter tablespace TEMP1 add tempfile '/opt/R12.1.3/oracle/db/apps_st/data/temp03.dbf' REUSE...
    Wed Nov 14 20:44:52 2012
    Shutting down instance (abort)
    License high water mark = 1
    USER (ospid: 4918): terminating the instance
    Instance terminated by USER, pid = 4918
    Wed Nov 14 20:44:53 2012
    Instance shutdown complete
    Wed Nov 14 20:45:58 2012
    Starting ORACLE instance (normal)
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    Picked latch-free SCN scheme 3
    Using LOG_ARCHIVE_DEST_1 parameter default value as /opt/R12.1.3/oracle/db/tech_st/11.1.0/dbs/arch
    Autotune of undo retention is turned on.
    IMODE=BR
    ILAT =44
    LICENSE_MAX_USERS = 0
    SYS auditing is disabled
    Starting up ORACLE RDBMS Version: 11.1.0.7.0.
    Using parameter settings in client-side pfile /opt/R12.1.3/oracle/db/tech_st/11.1.0/dbs/initTEST8002.ora on machine testing.fgho.com
    System parameters with non-default values:
    processes = 200
    sessions = 400
    timed_statistics = TRUE
    shared_pool_size = 400M
    shared_pool_reserved_size= 40M
    nls_language = "american"
    nls_territory = "america"
    nls_sort = "binary"
    nls_date_format = "DD-MON-RR"
    nls_numeric_characters = ".,"
    nls_comp = "binary"
    nls_length_semantics = "BYTE"
    sga_target = 1G
    control_files = "/opt/R12.1.3/oracle/db/apps_st/data/cntrl01.dbf"
    control_files = "/opt/R12.1.3/oracle/db/apps_st/data/cntrl02.dbf"
    control_files = "/opt/R12.1.3/oracle/db/apps_st/data/cntrl03.dbf"
    db_block_checksum = "TRUE"
    db_block_size = 8192
    compatible = "11.1.0"
    log_buffer = 10485760
    log_checkpoint_interval = 100000
    log_checkpoint_timeout = 1200
    db_files = 512
    log_checkpoints_to_alert = TRUE
    dml_locks = 10000
    undo_management = "AUTO"
    undo_tablespace = "APPS_UNDOTS1"
    db_block_checking = "FALSE"
    sec_case_sensitive_logon = FALSE
    session_cached_cursors = 500
    utl_file_dir = "/usr/tmp"
    utl_file_dir = "/usr/tmp"
    utl_file_dir = "/opt/R12.1.3/oracle/db/tech_st/11.1.0/appsutil/outbound/TEST8002_testing"
    utl_file_dir = "/usr/tmp"
    plsql_native_library_dir = "/opt/R12.1.3/oracle/db/tech_st/11.1.0/plsql/nativelib"
    plsql_native_library_subdir_count= 149
    plsql_code_type = "INTERPRETED"
    plsql_optimize_level = 2
    job_queue_processes = 2
    systemtrig_enabled = TRUE
    cursor_sharing = "EXACT"
    parallel_min_servers = 0
    parallel_max_servers = 8
    db_name = "TEST8002"
    open_cursors = 600
    ifile = "/opt/R12.1.3/oracle/db/tech_st/11.1.0/dbs/TEST8002_testing_ifile.ora"
    sortelimination_cost_ratio= 5
    btree_bitmap_plans = FALSE
    fastfull_scan_enabled = FALSE
    query_rewrite_enabled = "true"
    indexjoin_enabled = FALSE
    sqlexecprogression_cost= 2147483647
    likewith_bind_as_equality= TRUE
    pga_aggregate_target = 1G
    workarea_size_policy = "AUTO"
    optimizerautostats_job = FALSE
    optimizer_secure_view_merging= FALSE
    aq_tm_processes = 1
    olap_page_pool_size = 4M
    diagnostic_dest = "/opt/R12.1.3/oracle/db/tech_st/11.1.0/admin/TEST8002_testing"
    tracefiles_public = TRUE
    max_dump_file_size = "20480"
    Wed Nov 14 20:45:58 2012
    PMON started with pid=2, OS id=5067
    Wed Nov 14 20:45:58 2012
    VKTM started with pid=3, OS id=5069
    VKTM running at (100ms) precision
    Wed Nov 14 20:45:58 2012
    DIAG started with pid=4, OS id=5073
    Wed Nov 14 20:45:58 2012
    DBRM started with pid=5, OS id=5075
    Wed Nov 14 20:45:58 2012
    PSP0 started with pid=6, OS id=5077
    Wed Nov 14 20:45:58 2012
    DIA0 started with pid=7, OS id=5079
    Wed Nov 14 20:45:58 2012
    MMAN started with pid=8, OS id=5081
    Wed Nov 14 20:45:58 2012
    DBW0 started with pid=9, OS id=5083
    Wed Nov 14 20:45:58 2012
    DBW1 started with pid=10, OS id=5085
    Wed Nov 14 20:45:58 2012
    LGWR started with pid=11, OS id=5087
    Wed Nov 14 20:45:58 2012
    CKPT started with pid=12, OS id=5089
    Wed Nov 14 20:45:58 2012
    SMON started with pid=13, OS id=5091
    Wed Nov 14 20:45:58 2012
    RECO started with pid=14, OS id=5093
    Wed Nov 14 20:45:58 2012
    MMON started with pid=15, OS id=5095
    Wed Nov 14 20:45:58 2012
    MMNL started with pid=16, OS id=5097
    ORACLE_BASE not set in environment. It is recommended
    that ORACLE_BASE be set in the environment
    Wed Nov 14 20:45:58 2012
    ALTER DATABASE MOUNT
    Set as converted control file due to db_unique_name mismatch
    Changing di2dbun from to TEST8002
    Setting recovery target incarnation to 1
    Successful mount of redo thread 1, with mount id 3760563974
    Database mounted in Exclusive Mode
    Lost write protection disabled
    Completed: ALTER DATABASE MOUNT
    Wed Nov 14 20:46:02 2012
    ALTER DATABASE OPEN
    ORA-1589 signalled during: ALTER DATABASE OPEN...
    Wed Nov 14 20:46:47 2012
    alter database open resetlogs
    ORA-1194 signalled during: alter database open resetlogs...
    Wed Nov 14 20:47:11 2012
    ALTER DATABASE RECOVER database until cancel using backup controlfile
    Media Recovery Start
    Fast Parallel Media Recovery enabled
    Errors in file /opt/R12.1.3/oracle/db/tech_st/11.1.0/admin/TEST8002_testing/diag/rdbms/test8002/TEST8002/trace/TEST8002_ora_5127.trc (incident=6537):
    ORA-00600: internal error code, arguments: [kcvhvdf_1], [], [], [], [], [], [], [], [], [], [], []
    Incident details in: /opt/R12.1.3/oracle/db/tech_st/11.1.0/admin/TEST8002_testing/diag/rdbms/test8002/TEST8002/incident/incdir_6537/TEST8002_ora_5127_i65 37.trc
    Media Recovery failed with error 600
    ORA-283 signalled during: ALTER DATABASE RECOVER database until cancel using backup controlfile ...
    Wed Nov 14 20:47:13 2012
    Trace dumping is performing id=[cdmp_20121114204713]
    Wed Nov 14 20:47:13 2012
    Sweep Incident[6537]: completed

  • RMAN duplicate failed

    Hi all,
    have below doubts.
    IF RMAN duplicate failed in the middle of the process due to disk full or any other reason.
    Do I start from the beginning again or is there anyway to sort of "resume" from where it stopped?
    Please consider what need to do in 9i or in 10G.
    Please also reply what need to do for FS or for ASM.
    Please also share if you have any doc or link.

    Hi,
    IF RMAN duplicate failed in the middle of the process due to disk full or any other reason.See always perform fresh duplicate.
    it will overwrite the existing files... so you need to check in alert log file like how many files restored & recovered during duplicate..
    sybrand_b wrote:
    Duplicate database is a quite robust command.
    It will automatically skip what has already been done, so you can safely re-execute it without problems.
    Been there, done that.
    Sybrand Bakker
    Senior Oracle DBA@sybrand
    What it automatically skips?
    1)did RMAN duplicate knows about earlier restores...
    2)if i restored system,sysaux,users,undo datafiles of another database and again I'm performing another database in same location.. so it will skip?
    are you sure...
    Thanks
    *Manual Completion of a Failed RMAN Duplicate [ID 360962.1]*
    Edited by: CKPT on Dec 11, 2010 12:40 PM

  • RMAN DUPLICATE  FAIL

    hi guru's
    i am duplicating database using RMAN from ORCL to DUP
    i having the following error
    RMAN-03002: failure of Duplicate Db command at 11/05/2007 11:38:34
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-06026: some targets not found - aborting restore
    i used the command for duplicate as follows
    DUPLICATE TARGET DATABASE TO DUP;
    please help me....gurus

    hi,
    I assume you are using a recovery catalog?
    Have you created proper password files on both servers?
    what connection string are you using to connect to the recovery catalog
    something similar to
    connect to the recovery catalog as follows: -
    rman catalog_name rman/password@rman_name target system/password auxiliary internal/chef@$SID
    regards
    ALan

  • Cleaning up ASM disk group after failed rman duplicate session?

    I am using rman duplicate to create a clone of a production database. The rman duplicate failed in phase 1 (retoration of datafiles) and my datafile are being restored to an ASM diskgroup.
    I read in the metalink note Manual Completion of a Failed RMAN Duplicate [ID 360962.1] the following...
    Note : From 10g onwards, if duplicate failed during step 1, which is the restore of datafiles, it is probably best to restart the duplicate process. Any files that have already been restored will be skipped and the duplicate process can continue without manual intervention
    So I followed the advice in the note and started the rman duplcate script over again from the beggining. I am hoping it will have the intelligence to skip any files that have already been restored but if it is not since this is 10.1.0.3 and I cannot use the asmcmd command to connect to the ASM instance to delete any files that have been created then how can I delete and of the files since the database instance never got created correctly and cannot open?
    Any thought on how I can now cleanup the files in the ASM disk group? Also, has anyone started an rman duplicate again after it has previously failed and did it actually skip the files that are already there as stated in the metalink note?
    Thanks.

    Unfortunately the v$asm_file does not have the entire file name or path it just gives you the follwing...
    SQL> desc v$asm_file
    Name Null? Type
    GROUP_NUMBER NUMBER
    FILE_NUMBER NUMBER
    COMPOUND_INDEX NUMBER
    INCARNATION NUMBER
    BLOCK_SIZE NUMBER
    BLOCKS NUMBER
    BYTES NUMBER
    SPACE NUMBER
    TYPE VARCHAR2(64)
    REDUNDANCY VARCHAR2(6)
    STRIPED VARCHAR2(6)
    CREATION_DATE DATE
    MODIFICATION_DATE
    This really stinks I wish I didn't have to work with 10gr1 at all but the database I am trying to move to a ew server and new storage is running this version and we did not want to upgrade the existing database first before attempting the migration because it is reliant upon tape backups which I do not have alot of confidence in...

  • RMAN Restoration failed from ASM to non asm

    While restoring the database, we are getting this error frequently, updated the media center they said media is intact, but there is some "NO POLICY" NO SCHEDULE" error. what does this mean.
    Could some one please help us why and how to resolve this issue. We are stuck in between our restoration.
    ORA-19870: error reading backup piece ROCT_rman_db_weekly_20110719_2jmhrat3_1_1
    ORA-19507: failed to retrieve sequential file, handle="ROCT_rman_db_weekly_20110719_2jmhrat3_1_1", parms=""
    ORA-27029: skgfrtrv: sbtrestore returned error
    ORA-19511: Error received from media manager layer, error text:
    Failed to process backup file <ROCT_rman_db_weekly_20110719_2jmhrat3_1_1>

    784786 wrote:
    While restoring the database, we are getting this error frequently, updated the media center they said media is intact, but there is some "NO POLICY" NO SCHEDULE" error. what does this mean.
    Could some one please help us why and how to resolve this issue. We are stuck in between our restoration.
    ORA-19870: error reading backup piece ROCT_rman_db_weekly_20110719_2jmhrat3_1_1
    ORA-19507: failed to retrieve sequential file, handle="ROCT_rman_db_weekly_20110719_2jmhrat3_1_1", parms=""
    ORA-27029: skgfrtrv: sbtrestore returned error
    ORA-19511: Error received from media manager layer, error text:
    Failed to process backup file <ROCT_rman_db_weekly_20110719_2jmhrat3_1_1>where is No policy/no schedule errors?
    Error reading backup piece can occur even the handle was corrupt (or) handle was unable to read (or) did tapes loaded in MML ?
    *RMAN Duplicate fails with ORA-19870, ORA-19507, ORA-27029 and ORA-19511 [ID 562780.1]*

  • Question on OPEN RESETLOGS

    Db version: 11g
    What will happen if we don't use
    ALTER DATABASE OPEN RESETLOGS;after an incomplete recovery?

    hi,
    check this out from oracle doc
    About Opening with the RESETLOGS Option
    The RESETLOGS option is always required after incomplete
    media recovery or recovery using a backup control file. Resetting
    the redo log does the following:
    Archives the current online redo logs (if they are accessible) and then
    erases the contents of the online redo logs and resets the log sequence
    number to 1. For example, if the current online redo logs are sequence
    1000 and 1001 when you open RESETLOGS, then the database archives
    logs 1000 and 1001 and then resets the online logs to sequence 1 and 2.
    Creates the online redo log files if they do not currently exist.
    Reinitializes the control file metadata about online redo logs and redo threads.
    Updates all current datafiles and online redo logs and all subsequent archived
    redo logs with a new RESETLOGS SCN and time stamp.
    Because the database will not apply an archived log to a datafile unless the
    RESETLOGS SCN and time stamps match, the RESETLOGS prevents you
    from corrupting datafiles with archived logs that are not from direct
    parent incarnations of the current incarnation.
    In prior releases, it was recommended that you back up the database
    immediately after the RESETLOGS. Because you can now easily recover
    a pre-RESETLOGS backup like any other backup, making a new database
    backup is optional. In order to perform recovery through resetlogs you
    must have all archived logs generated since the last backup and at least
    one control file (current, backup, or created).this might help
    thanks and regards
    VD

  • RESTORE VALIDATE possible prior to an OPEN RESETLOGS?

    Is it possible to perform a RESTORE VALIDATE to a point in time prior to an OPEN RESETLOGS?
    RMAN> list incarnation;
    List of Database Incarnations
    DB Key  Inc Key DB Name  DB ID            STATUS  Reset SCN  Reset Time
    1       1       AA02     2787653425       PARENT  1          29.FEB.2008 15:56:3
    3
    2       2       AA02     2787653425       CURRENT 182455     29.FEB.2008 16:55:5
    5
    RMAN> run
    2> {
    3> set until time = "to_date('29.FEB.2008 16:00:00','DD.MON.YYYY HH24:MI:SS')";
    4> restore database validate;
    5> }
    executing command: SET until clause
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of set command at 06/11/2009 11:13:35
    RMAN-20207: UNTIL TIME or RECOVERY WINDOW is before RESETLOGS timeUsing the RESET DATABASE TO INCARNATION clause it should be possible to perform the RESTORE however that is not the intention (yet), only to RESTORE VALIDATE.

    That's what I'm finding... I don't want to have to restart the database to reset the incarnation to have to test restore a backup prior to open resetlogs (no catalog only controlfile used).
    "If RMAN is connected NOCATALOG, then you can only specify TO INCARNATION if the database is mounted and the control file contains a record of the prior incarnation. If you do not run RESET DATABASE, RMAN recovers to the last incarnation recorded in the control file."
    http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta050.htm
    Yet another reason to have a RMAN catalog.

  • Open resetlogs

    hi,
    we are facing the following problems again and again in cloning process.
    we should the database properly and listener.then backup the files and transfer the files from source(instance name is pix) to target (instance name is prod).
    os:red hat 4.2
    db:9.2 no archivelog mode
    SQL> startup nomount pfile=/prod/p02/oracle/proddb/9.2.0/dbs/initprod.ora
    and created the controlfile and set the database name prod instead of pix
    SQL> alter database open resetlogs;
    alter database open resetlogs
    ERROR at line 1:
    ORA-01194: file 1 needs more recovery to be consistent
    ORA-01110: data file 1: '/prod/p02/oracle/proddata/sys1.dbf'
    SQL> recover database using backup controlfile until cancel;
    ORA-00279: change 8173880387520 generated at 11/30/2009 01:43:55 needed for
    thread 1
    ORA-00289: suggestion : /prod/p02/oracle/proddb/9.2.0/dbs/arch1_22.dbf
    ORA-00280: change 8173880387520 for thread 1 is in sequence #22
    then i shut the db and add the entires ALLOWRESETLOGS_CORRUPTION = TRUE inti initprod.ora
    again i started the db.
    SQL> startup nomount pfile=/prod/p02/oracle/proddb/9.2.0/dbs/initprod.ora
    ORACLE instance started.
    Total System Global Area 581506668 bytes
    Fixed Size 452204 bytes
    Variable Size 402653184 bytes
    Database Buffers 167772160 bytes
    Redo Buffers 10629120 bytes
    SQL> alter database mount;
    Database altered.
    SQL> alter database open resetlogs; After 10 to 10 minutes i got the following errors
    alter database open resetlogs
    ERROR at line 1:
    ORA-03113: end-of-file on communication channel
    SQL>
    i got the alert.log info
    Errors in file /prod/p02/oracle/proddb/9.2.0/admin/prod_oraapps/udump/prod_ora_25303.trc:
    ORA-00600: internal error code, arguments: [2662], [1903], [557623276], [1903], [557640061], [41943049], [], []
    Tue Dec 1 01:56:43 2009
    Error 600 happened during db open, shutting down database
    USER: terminating instance due to error 600
    Instance terminated by USER, pid = 25303
    ORA-1092 signalled during: alter database open resetlogs...
    Tue Dec 1 02:01:43 2009
    USER: terminating instance due to error 1092
    Instance terminated by USER, pid = 25303
    cat: tail: No such file or directory
    cat: 50: No such file or directory
    Edited by: user3266490 on Dec 1, 2009 2:47 PM

    SQL> alter database open resetlogs;
    alter database open resetlogs
    ERROR at line 1:
    ORA-01194: file 1 needs more recovery to be consistent
    ORA-01110: data file 1: '/prod/p02/oracle/proddata/sys1.dbf'
    SQL> recover database using backup controlfile until cancel;
    ORA-00279: change 8173880387520 generated at 11/30/2009 01:43:55 needed for
    thread 1
    ORA-00289: suggestion : /prod/p02/oracle/proddb/9.2.0/dbs/arch1_22.dbf
    ORA-00280: change 8173880387520 for thread 1 is in sequence #22
    Try providing one of the online redo log files as input here and see if that helps in the recovery process.

  • Unable to recover database after rman recovery and database open resetlogs

    I am running Oracle 10.2.0.5 on OpenSUSE 9. I have been trying to upgrade the database to 11g, through dbua. I was getting stuck at one point during the Oracle Server install and the upgrade failed and I was forced to restore the database to an earlier backup.
    Below is the current place that I am stuck. As you can see I opened the database multiple times and reset the logs. Now I am afraid that my controlfile and redo log backups are out of sync and i can't get them back on track. Before when I actually got the database recovered RMAN would immediately throw:
    RMAN-06900: WARNING: unable to generate V$RMAN_STATUS or V$RMAN_OUTPUT row
    RMAN-06901: WARNING: disabling update of the V$RMAN_STATUS and V$RMAN_OUTPUT rows
    OPA-00600: ORA-00600: internal error code, arguments: ...
    The database would open with ALTER DATABASE RESETLOGS but any query on non-system tables would fail and throw:
    ORA-04045: errors during recompilation/revalidation of LCRS_DEV1.FACILITY_REF
    ORA-00600: internal error code, arguments: [17069], [0x1158ED180], [], [], [],
    I hope I have not dug myself into too deep of a hole here.
    Here is the trace from my most recent attempt.
    RMAN> startup nomount;
    connected to target database (not started)
    Oracle instance started
    Total System Global Area 3070230528 bytes
    Fixed Size 2099424 bytes
    Variable Size 301991712 bytes
    Database Buffers 2751463424 bytes
    Redo Buffers 14675968 bytes
    RMAN> list incarnation of database;
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of list command at 08/02/2011 15:49:04
    ORA-01507: database not mounted
    RMAN> restore controlfile from autobackup;
    Starting restore at 02-AUG-11
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=156 devtype=DISK
    recovery area destination: /opt/oracle/flash_recovery_area
    database name (or database unique name) used for search: LCRSDEV
    channel ORA_DISK_1: autobackup found in the recovery area
    channel ORA_DISK_1: autobackup found: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758129928_73jr2s7p_.bkp
    channel ORA_DISK_1: control file restore from autobackup complete
    output filename=/opt/oracle/oradata/LCRSDEV/control01.ctl
    output filename=/opt/oracle/oradata/LCRSDEV/control02.ctl
    output filename=/opt/oracle/oradata/LCRSDEV/control03.ctl
    Finished restore at 02-AUG-11
    RMAN> alter database mount;
    database mounted
    released channel: ORA_DISK_1
    RMAN> list incarnation of database;
    List of Database Incarnations
    DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
    1 1 LCRSDEV 756543625 PARENT 1 22-OCT-05
    2 2 LCRSDEV 756543625 PARENT 525876 20-JAN-11
    3 3 LCRSDEV 756543625 PARENT 92348137 18-JUL-11
    4 4 LCRSDEV 756543625 PARENT 95654931 01-AUG-11
    5 5 LCRSDEV 756543625 PARENT 95675699 01-AUG-11
    6 6 LCRSDEV 756543625 PARENT 95676699 02-AUG-11
    7 7 LCRSDEV 756543625 PARENT 95676700 02-AUG-11
    8 8 LCRSDEV 756543625 CURRENT 95676701 02-AUG-11
    RMAN> restore database until scn 95676700;
    Starting restore at 02-AUG-11
    Starting implicit crosscheck backup at 02-AUG-11
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=156 devtype=DISK
    Crosschecked 6 objects
    Finished implicit crosscheck backup at 02-AUG-11
    Starting implicit crosscheck copy at 02-AUG-11
    using channel ORA_DISK_1
    Finished implicit crosscheck copy at 02-AUG-11
    searching for all files in the recovery area
    cataloging files...
    cataloging done
    List of Cataloged Files
    =======================
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758129928_73jr2s7p_.bkp
    using channel ORA_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 08/02/2011 15:52:04
    RMAN-20208: UNTIL CHANGE is before RESETLOGS change
    RMAN> restore database;
    Starting restore at 02-AUG-11
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting datafile backupset restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    restoring datafile 00001 to /opt/oracle/oradata/LCRSDEV/system01.dbf
    restoring datafile 00002 to /opt/oracle/oradata/LCRSDEV/undotbs01.dbf
    restoring datafile 00003 to /opt/oracle/oradata/LCRSDEV/sysaux01.dbf
    restoring datafile 00004 to /opt/oracle/oradata/LCRSDEV/users01.dbf
    restoring datafile 00005 to /opt/oracle/oradata/LCRSDEV/LCRS_TBS.dbf
    channel ORA_DISK_1: reading from backup piece /opt/oracle/flash_recovery_area/LCRSDEV/backupset/2011_07_22/o1_mf_nnndf_TAG20110722T111922_72m8rc5x_.bkp
    channel ORA_DISK_1: restored backup piece 1
    piece handle=/opt/oracle/flash_recovery_area/LCRSDEV/backupset/2011_07_22/o1_mf_nnndf_TAG20110722T111922_72m8rc5x_.bkp tag=TAG20110722T111922
    channel ORA_DISK_1: restore complete, elapsed time: 00:23:36
    Finished restore at 02-AUG-11
    RMAN> recover database until scn 95676700;
    Starting recover at 02-AUG-11
    using channel ORA_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 08/02/2011 16:16:28
    RMAN-20208: UNTIL CHANGE is before RESETLOGS change
    RMAN> recover database;
    Starting recover at 02-AUG-11
    using channel ORA_DISK_1
    starting media recovery
    archive log thread 1 sequence 90 is already on disk as file /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_90_72ml85v3_.arc
    archive log filename=/opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73jr20qc_.arc thread=1 sequence=1
    unable to find archive log
    archive log thread=1 sequence=1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 08/02/2011 16:25:04
    RMAN-06054: media recovery requesting unknown log: thread 1 seq 1 lowscn 95676701

    Thanks for the reply Hemant. I have reset the database for the controlfile that I am using as backup and now I am not able to recover until the correct SCN. I am thinking that my recovery catalog is bad. If I mount with the current controlfile I have this list of incarnations:
    List of Database Incarnations
    DB Key  Inc Key DB Name  DB ID            STATUS  Reset SCN  Reset Time
    *1 1 LCRSDEV 756543625 PARENT 1 22-OCT-05*
    *2 2 LCRSDEV 756543625 PARENT 525876 20-JAN-11*
    *3 3 LCRSDEV 756543625 PARENT 92348137 18-JUL-11*
    *4 4 LCRSDEV 756543625 PARENT 95654931 01-AUG-11*
    *5 5 LCRSDEV 756543625 PARENT 95675699 01-AUG-11*
    *6 6 LCRSDEV 756543625 PARENT 95676699 02-AUG-11*
    *7 7 LCRSDEV 756543625 PARENT 95676700 02-AUG-11*
    *8 8 LCRSDEV 756543625 PARENT 95676701 02-AUG-11*
    *9 9 LCRSDEV 756543625 CURRENT 95676702 02-AUG-11*
    However if I restore the controlfile to the earlier version I am getting the following output from the process:
    RMAN> startup nomount;
    connected to target database (not started)
    Oracle instance started
    Total System Global Area 3070230528 bytes
    Fixed Size 2099424 bytes
    Variable Size 301991712 bytes
    Database Buffers 2751463424 bytes
    Redo Buffers 14675968 bytes
    RMAN> restore controlfile from '/opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_07_22/o1_mf_s_757164997_72m9rqw3_.bkp';
    Starting restore at 03-AUG-11
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=156 devtype=DISK
    channel ORA_DISK_1: restoring control file
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:03
    output filename=/opt/oracle/oradata/LCRSDEV/control01.ctl
    output filename=/opt/oracle/oradata/LCRSDEV/control02.ctl
    output filename=/opt/oracle/oradata/LCRSDEV/control03.ctl
    Finished restore at 03-AUG-11
    RMAN> alter database mount;
    database mounted
    released channel: ORA_DISK_1
    RMAN> list incarnation of database;
    List of Database Incarnations
    DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
    1 1 LCRSDEV 756543625 PARENT 1 22-OCT-05
    2 2 LCRSDEV 756543625 PARENT 525876 20-JAN-11
    3 3 LCRSDEV 756543625 CURRENT 92348137 18-JUL-11
    RMAN> restore database until scn 92348137;
    Starting restore at 03-AUG-11
    Starting implicit crosscheck backup at 03-AUG-11
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=156 devtype=DISK
    Crosschecked 1 objects
    Finished implicit crosscheck backup at 03-AUG-11
    Starting implicit crosscheck copy at 03-AUG-11
    using channel ORA_DISK_1
    Finished implicit crosscheck copy at 03-AUG-11
    searching for all files in the recovery area
    cataloging files...
    cataloging done
    List of Cataloged Files
    =======================
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_01/o1_mf_1_1_73g3hn6o_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_01/o1_mf_1_2_73g3hnxq_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_01/o1_mf_1_1_73g0rts6_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_134_72v9gv4s_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_138_72v9p4b4_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_120_72v8wwg0_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_121_72v8x5ty_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_131_72v9cnrv_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_139_72v9q5ok_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_137_72v9n4t5_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_136_72v9l88q_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_123_72v8ytm8_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_132_72v9dcxd_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_124_72v8zkg0_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_128_72v96qm1_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_135_72v9jqmx_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_129_72v98q3r_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_125_72v91g3b_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_118_72v8v8r4_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_127_72v9626w_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_130_72v9bqtb_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_141_72vncy6g_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_122_72v8ycd4_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_126_72v94cns_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_133_72v9fb17_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_140_72vn6wgo_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_119_72v8v9hf_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73j3wo01_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_2_73josgf1_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73jr20qc_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_2_73jh223h_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73josflf_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73jvqdqs_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_3_73josh91_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73j91rh9_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_91_72mqlnx9_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_111_72mrdr5m_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_96_72mqx958_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_114_72mrgsf9_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_94_72mqs6gj_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_102_72mr3893_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_99_72mr2h6c_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_104_72mr5hfm_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_109_72mrc83z_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_98_72mr080w_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_93_72mqq36m_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_97_72mqz0mm_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_116_72mrk268_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_101_72mr31yv_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_110_72mrddhg_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_95_72mqv3hp_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_105_72mr5vq4_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_115_72mrjd2s_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_106_72mr7hnt_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_100_72mr2qfc_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_112_72mrfc5j_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_107_72mr909t_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_103_72mr4pol_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_113_72mrfsb9_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_117_72mrl5mf_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_108_72mrb13l_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_90_72ml85v3_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_92_72mqnxz1_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_26/o1_mf_1_143_72y6ww71_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_26/o1_mf_1_144_72ybybps_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_26/o1_mf_1_142_72xt10j7_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_26/o1_mf_1_145_72yccy5z_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_01/o1_mf_s_758043324_73g3jfxx_.bkp
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_01/o1_mf_s_758035850_73fw6vrc_.bkp
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758133684_73jvr5px_.bkp
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758127608_73jot9x0_.bkp
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758109276_73j3xfom_.bkp
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758129928_73jr2s7p_.bkp
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_07_22/o1_mf_s_757164997_72m9rqw3_.bkp
    using channel ORA_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 08/03/2011 12:53:19
    RMAN-20208: UNTIL CHANGE is before RESETLOGS change
    Edited by: K Doyle on Aug 3, 2011 10:22 AM

  • The RMAN Duplicate Command Fails During The Recover.

    This exact script works fine in our lab. We are using Oracle 10.2.0.4.0.
    The hot backup for standby is also a script which runs without error in both the lab and
    the production machine.
    I am obviously missing something.
    Any help would be greatly appreciated.
    Thanks,
    Jeff
    =================
    RMAN BACKUP SCRIPT
    =================
    RMAN> run
    2> {
    3> allocate channel c1 device type disk format '/u03/oradata/apoint/DB_BACKUPS/1NETCMN1_3261_BK4STDBY_%U';
    4> backup current controlfile for standby format '/u03/oradata/apoint/DB_BACKUPS/1NETCMN1_3261_CNTRL4STDBY_%U';
    5> backup as compressed backupset check logical tag='1NETCMN1_3261_BK4STDBY' database include current controlfile for standby;
    6> backup archivelog from sequence 463 format '/u03/oradata/apoint/DB_BACKUPS/1NETCMN1_3261_LOGS4STDBY_%U';
    7> release channel c1;
    8> }
    released channel: ORA_DISK_1
    allocated channel: c1
    channel c1: sid=578 devtype=DISK
    Starting backup at 22-JAN-13
    channel c1: starting full datafile backupset
    channel c1: specifying datafile(s) in backupset
    including standby control file in backupset
    channel c1: starting piece 1 at 22-JAN-13
    channel c1: finished piece 1 at 22-JAN-13
    piece handle=/u03/oradata/apoint/DB_BACKUPS/1NETCMN1_3261_CNTRL4STDBY_05o02f01_1_1 tag=TAG20130122T144104 comment=NONE
    channel c1: backup set complete, elapsed time: 00:00:02
    Finished backup at 22-JAN-13
    Starting backup at 22-JAN-13
    channel c1: starting compressed full datafile backupset
    channel c1: specifying datafile(s) in backupset
    input datafile fno=00004 name=/u01/oradata/apoint/users01.dbf
    input datafile fno=00001 name=/u01/oradata/apoint/system01.dbf
    input datafile fno=00002 name=/u01/oradata/apoint/undotbs01.dbf
    input datafile fno=00003 name=/u01/oradata/apoint/sysaux01.dbf
    channel c1: starting piece 1 at 22-JAN-13
    channel c1: finished piece 1 at 22-JAN-13
    piece handle=/u03/oradata/apoint/DB_BACKUPS/1NETCMN1_3261_BK4STDBY_06o02f05_1_1 tag=1NETCMN1_3261_BK4STDBY comment=NONE
    channel c1: backup set complete, elapsed time: 00:22:35
    channel c1: starting compressed full datafile backupset
    channel c1: specifying datafile(s) in backupset
    including standby control file in backupset
    channel c1: starting piece 1 at 22-JAN-13
    channel c1: finished piece 1 at 22-JAN-13
    piece handle=/u03/oradata/apoint/DB_BACKUPS/1NETCMN1_3261_BK4STDBY_07o02gah_1_1 tag=1NETCMN1_3261_BK4STDBY comment=NONE
    channel c1: backup set complete, elapsed time: 00:00:07
    Finished backup at 22-JAN-13
    Starting backup at 22-JAN-13
    current log archived
    channel c1: starting archive log backupset
    channel c1: specifying archive log(s) in backup set
    input archive log thread=1 sequence=463 recid=5 stamp=805323439
    input archive log thread=1 sequence=464 recid=6 stamp=805331764
    input archive log thread=1 sequence=465 recid=7 stamp=805387242
    input archive log thread=1 sequence=466 recid=8 stamp=805387245
    input archive log thread=1 sequence=467 recid=9 stamp=805388633
    channel c1: starting piece 1 at 22-JAN-13
    channel c1: finished piece 1 at 22-JAN-13
    piece handle=/u03/oradata/apoint/DB_BACKUPS/1NETCMN1_3261_LOGS4STDBY_08o02gaq_1_1 tag=TAG20130122T150354 comment=NONE
    channel c1: backup set complete, elapsed time: 00:00:36
    Finished backup at 22-JAN-13
    released channel: c1
    RMAN> exit
    Recovery Manager complete.
    =====================
    RMAN DUPLICATE SCRIPT
    =====================
    RMAN> run
    2> {
    3> allocate auxiliary channel c1 device type disk;
    4>
    5> duplicate target database for standby dorecover nofilenamecheck;
    6> release channel c1;
    7> }
    allocated channel: c1
    channel c1: sid=299 devtype=DISK
    Starting Duplicate Db at 21-JAN-13
    contents of Memory Script:
    set until scn 143395851;
    restore clone standby controlfile;
    sql clone 'alter database mount standby database';
    executing Memory Script
    executing command: SET until clause
    Starting restore at 21-JAN-13
    channel c1: starting datafile backupset restore
    channel c1: restoring control file
    channel c1: reading from backup piece /u03/oradata/apoint/DB_BACKUPS/1NETCMN1_6874_BK4STDBY_03o008gn_1_1
    channel c1: restored backup piece 1
    piece handle=/u03/oradata/apoint/DB_BACKUPS/1NETCMN1_6874_BK4STDBY_03o008gn_1_1 tag=1NETCMN1_6874_BK4STDBY
    channel c1: restore complete, elapsed time: 00:00:04
    output filename=/u01/oradata/apoint/control01.ctl
    output filename=/u02/oradata/apoint/control02.ctl
    output filename=/u03/oradata/apoint/control03.ctl
    Finished restore at 21-JAN-13
    sql statement: alter database mount standby database
    contents of Memory Script:
    set until scn 143395851;
    set newname for tempfile 1 to
    "/u01/oradata/apoint/temp01.dbf";
    switch clone tempfile all;
    set newname for datafile 1 to
    "/u01/oradata/apoint/system01.dbf";
    set newname for datafile 2 to
    "/u01/oradata/apoint/undotbs01.dbf";
    set newname for datafile 3 to
    "/u01/oradata/apoint/sysaux01.dbf";
    set newname for datafile 4 to
    "/u01/oradata/apoint/users01.dbf";
    restore
    check readonly
    clone database
    executing Memory Script
    executing command: SET until clause
    executing command: SET NEWNAME
    renamed temporary file 1 to /u01/oradata/apoint/temp01.dbf in control file
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    Starting restore at 21-JAN-13
    channel c1: starting datafile backupset restore
    channel c1: specifying datafile(s) to restore from backup set
    restoring datafile 00001 to /u01/oradata/apoint/system01.dbf
    restoring datafile 00002 to /u01/oradata/apoint/undotbs01.dbf
    restoring datafile 00003 to /u01/oradata/apoint/sysaux01.dbf
    restoring datafile 00004 to /u01/oradata/apoint/users01.dbf
    channel c1: reading from backup piece /u03/oradata/apoint/DB_BACKUPS/1NETCMN1_6874_BK4STDBY_02o0076b_1_1
    channel c1: restored backup piece 1
    piece handle=/u03/oradata/apoint/DB_BACKUPS/1NETCMN1_6874_BK4STDBY_02o0076b_1_1 tag=1NETCMN1_6874_BK4STDBY
    channel c1: restore complete, elapsed time: 00:21:32
    Finished restore at 21-JAN-13
    contents of Memory Script:
    switch clone datafile all;
    executing Memory Script
    datafile 1 switched to datafile copy
    input datafile copy recid=5 stamp=805323205 filename=/u01/oradata/apoint/system01.dbf
    datafile 2 switched to datafile copy
    input datafile copy recid=6 stamp=805323205 filename=/u01/oradata/apoint/undotbs01.dbf
    datafile 3 switched to datafile copy
    input datafile copy recid=7 stamp=805323206 filename=/u01/oradata/apoint/sysaux01.dbf
    datafile 4 switched to datafile copy
    input datafile copy recid=8 stamp=805323206 filename=/u01/oradata/apoint/users01.dbf
    contents of Memory Script:
    set until scn 143395851;
    recover
    standby
    clone database
    delete archivelog
    executing Memory Script
    executing command: SET until clause
    Starting recover at 21-JAN-13
    starting media recovery
    channel c1: starting archive log restore to default destination
    channel c1: restoring archive log
    archive log thread=1 sequence=462
    channel c1: reading from backup piece /u03/oradata/apoint/DB_BACKUPS/1NETCMN1_6874_LOGS4STDBY_04o008gu_1_1
    channel c1: restored backup piece 1
    piece handle=/u03/oradata/apoint/DB_BACKUPS/1NETCMN1_6874_LOGS4STDBY_04o008gu_1_1 tag=TAG20130121T183822
    channel c1: restore complete, elapsed time: 00:00:03
    archive log filename=/u03/oradata/apoint/DB_ARCHIVE_LOGS/apoint_1_688761648_462.arch thread=1 sequence=462
    Oracle Error:
    ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
    ORA-01152: file 1 was not restored from a sufficiently old backup
    ORA-01110: data file 1: '/u01/oradata/apoint/system01.dbf'
    released channel: c1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 01/21/2013 20:53:44
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-11003: failure during parse/execution of SQL statement: alter database recover logfile '/u03/oradata/apoint/DB_ARCHIVE_LOGS/apoint_1_688761648_462.arch'
    ORA-16145: archival for thread# 1 sequence# 462 in progress
    RMAN> exit

    Jeff;
    I think the issue is in your backup. If you compare your command with mine, you may or may not see the issue, but this is how I got this to work.
    Yours
    RMAN run
    allocate channel c1 device type disk format '/u03/oradata/apoint/DB_BACKUPS/1NETCMN1_3261_BK4STDBY_%U';
    backup current controlfile for standby format '/u03/oradata/apoint/DB_BACKUPS/1NETCMN1_3261_CNTRL4STDBY_%U';
    backup as compressed backupset check logical tag='1NETCMN1_3261_BK4STDBY' database include current controlfile for standby;
    backup archivelog from sequence 463 format '/u03/oradata/apoint/DB_BACKUPS/1NETCMN1_3261_LOGS4STDBY_%U';
    release channel c1;
    Mine
    RMAN RUN {
    allocate channel d1 type disk;
    backup format '/u01/backups/PRIMARY/df_t%t_s%s_p%p' database;
    sql 'alter system archive log current';
    backup format '/u01/backups/PRIMARY/al_t%t_s%s_p%p' archivelog all;
    backup current controlfile for standby format '/u01/backups/PRIMARY/sb_t%t_s%s_p%p';
    release channel d1;
    }Your duplicate is very close to what I use :
    Yours
    RMAN> run
    allocate auxiliary channel c1 device type disk;
    duplicate target database for standby dorecover nofilenamecheck;
    release channel c1;
    Mine
    RMAN> run {
    allocate channel C1 device type disk;
    allocate auxiliary channel C2 device type disk;
    duplicate target database for standby nofilenamecheck;
    }Short notes :
    http://www.visi.com/~mseberg/duprman.html
    Best Regards
    mseberg

  • Duplicate open resetlogs

    Hi everyone,
    According to oracle manuals, duplicate command must perform "open resetlogs" implicitly.
    I just issued "backup database plus archivelog" and copied accross all backupsets. However oracle doesnt open the database with open resetlogs and still waiting for archivelogs.
    Any idea why?
    C:\Users\>rman TARGET sys/sys@ORCL AUXILIARY sys/sys
    Recovery Manager: Release 10.2.0.5.0 - Production on Sat Feb 5 22:32:32 2011
    Copyright (c) 1982, 2007, Oracle.  All rights reserved.
    connected to target database: ORCL (DBID=262315494)
    connected to auxiliary database: TEST (not mounted)
    RMAN> run{
    2> SET NEWNAME FOR DATAFILE  'F:\ORACLE\ORADATA\ORCL\DATAFILES\ORCL_SYSTEM01.DBF' to 'F:\ORACLE\ORADATA\TEST\DATAFILES\TEST_SYSTEM01.DBF
    3> SET NEWNAME FOR DATAFILE 'F:\ORACLE\ORADATA\ORCL\DATAFILES\ORCL_UNDOTBS01.DBF' to 'F:\ORACLE\ORADATA\TEST\DATAFILES\TEST_UNDOTBS01.DB
    4> SET NEWNAME FOR DATAFILE 'F:\ORACLE\ORADATA\ORCL\DATAFILES\ORCL_SYSAUX01.DBF' to 'F:\ORACLE\ORADATA\TEST\DATAFILES\TEST_SYSAUX01.DBF'
    5> SET NEWNAME FOR DATAFILE 'F:\ORACLE\ORADATA\ORCL\DATAFILES\ORCL_USERS01.DBF' to 'F:\ORACLE\ORADATA\TEST\DATAFILES\TEST_USERS01.DBF';
    6> SET NEWNAME FOR DATAFILE 'F:\ORACLE\ORADATA\ORCL\DATAFILES\ORCL_STATSPACKTBS01.DBF'to 'F:\ORACLE\ORADATA\TEST\DATAFILES\TEST_STATSPACKTBS01.DBF';
    DUPLICATE TARGET DATABASE TO TEST
    9> LOGFILE
    10> GROUP 1 ('F:\ORACLE\ORADATA\TEST\REDOLOGS\TEST_REDO1A.LOG','G:\ORACLE\ORADATA\TEST\REDOLOGS\TEST_REDO1B.ORA') SIZE 50m REUSE,
    11> GROUP 2 ('F:\ORACLE\ORADATA\TEST\REDOLOGS\TEST_REDO2A.LOG', 'G:\ORACLE\ORADATA\TEST\REDOLOGS\TEST_REDO2B.ORA') SIZE 50m REUSE,
    12> GROUP 3 ('F:\ORACLE\ORADATA\TEST\REDOLOGS\TEST_REDO3A.LOG', 'G:\ORACLE\ORADATA\TEST\REDOLOGS\TEST_REDO3B.ORA') SIZE 50m REUSE
    13> NOFILENAMECHECK;
    14> }
    executing command: SET NEWNAME
    using target database control file instead of recovery catalog
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    Starting Duplicate Db at 05-FEB-11
    allocated channel: ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: sid=321 devtype=DISK
    contents of Memory Script:
       set until scn  5366311383;
       set newname for datafile  1 to
    "F:\ORACLE\ORADATA\TEST\DATAFILES\TEST_SYSTEM01.DBF";
       set newname for datafile  2 to
    "F:\ORACLE\ORADATA\TEST\DATAFILES\TEST_UNDOTBS01.DBF";
       set newname for datafile  3 to
    "F:\ORACLE\ORADATA\TEST\DATAFILES\TEST_SYSAUX01.DBF";
       set newname for datafile  4 to
    "F:\ORACLE\ORADATA\TEST\DATAFILES\TEST_USERS01.DBF";
       set newname for datafile  5 to
    "F:\ORACLE\ORADATA\TEST\DATAFILES\TEST_STATSPACKTBS01.DBF";
       restore
       check readonly
       clone database
    executing Memory Script
    executing command: SET until clause
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    Starting restore at 05-FEB-11
    using channel ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: starting datafile backupset restore
    channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
    restoring datafile 00001 to F:\ORACLE\ORADATA\TEST\DATAFILES\TEST_SYSTEM01.DBF
    restoring datafile 00002 to F:\ORACLE\ORADATA\TEST\DATAFILES\TEST_UNDOTBS01.DBF
    restoring datafile 00003 to F:\ORACLE\ORADATA\TEST\DATAFILES\TEST_SYSAUX01.DBF
    restoring datafile 00004 to F:\ORACLE\ORADATA\TEST\DATAFILES\TEST_USERS01.DBF
    restoring datafile 00005 to F:\ORACLE\ORADATA\TEST\DATAFILES\TEST_STATSPACKTBS01.DBF
    channel ORA_AUX_DISK_1: reading from backup piece H:\RMAN\BACKUPSET\DATABASE_ORCL_5HM3U85N_177_20110205
    Finished restore at 05-FEB-11
    sql statement: CREATE CONTROLFILE REUSE SET DATABASE "TEST" RESETLOGS ARCHIVELOG
      MAXLOGFILES     16
      MAXLOGMEMBERS      3
      MAXDATAFILES      100
      MAXINSTANCES     8
      MAXLOGHISTORY     1168
    LOGFILE
      GROUP  1 ( 'F:\ORACLE\ORADATA\TEST\REDOLOGS\TEST_REDO1A.LOG', 'G:\ORACLE\ORADATA\TEST\REDOLOGS\TEST_REDO1B.ORA' ) SIZE 5
      GROUP  2 ( 'F:\ORACLE\ORADATA\TEST\REDOLOGS\TEST_REDO2A.LOG', 'G:\ORACLE\ORADATA\TEST\REDOLOGS\TEST_REDO2B.ORA' ) SIZE 5
      GROUP  3 ( 'F:\ORACLE\ORADATA\TEST\REDOLOGS\TEST_REDO3A.LOG', 'G:\ORACLE\ORADATA\TEST\REDOLOGS\TEST_REDO3B.ORA' ) SIZE 5
    DATAFILE
      'F:\ORACLE\ORADATA\TEST\DATAFILES\TEST_SYSTEM01.DBF'
    CHARACTER SET WE8ISO8859P1
    contents of Memory Script:
       switch clone datafile all;
    executing Memory Script
    datafile 2 switched to datafile copy
    input datafile copy recid=1 stamp=742344389 filename=F:\ORACLE\ORADATA\TEST\DATAFILES\TEST_UNDOTBS01.DBF
    datafile 3 switched to datafile copy
    input datafile copy recid=2 stamp=742344390 filename=F:\ORACLE\ORADATA\TEST\DATAFILES\TEST_SYSAUX01.DBF
    datafile 4 switched to datafile copy
    input datafile copy recid=3 stamp=742344390 filename=F:\ORACLE\ORADATA\TEST\DATAFILES\TEST_USERS01.DBF
    datafile 5 switched to datafile copy
    input datafile copy recid=4 stamp=742344390 filename=F:\ORACLE\ORADATA\TEST\DATAFILES\TEST_STATSPACKTBS01.DBF
    contents of Memory Script:
       set until scn  5366311383;
       recover
       clone database
        delete archivelog
    executing Memory Script
    executing command: SET until clause
    Starting recover at 05-FEB-11
    using channel ORA_AUX_DISK_1
    starting media recovery
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 02/05/2011 22:46:38
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-06053: unable to perform media recovery because of missing log
    RMAN-06025: no backup of log thread 1 seq 3024 lowscn 5366311185 found to restore
    RMAN-06025: no backup of log thread 1 seq 3023 lowscn 5366310982 found to restore
    RMAN-06025: no backup of log thread 1 seq 3022 lowscn 5366310786 found to restore
    RMAN-06025: no backup of log thread 1 seq 3021 lowscn 5366310462 found to restore
    RMAN-06025: no backup of log thread 1 seq 3020 lowscn 5366310260 found to restore
    RMAN-06025: no backup of log thread 1 seq 3019 lowscn 5366310044 found to restore
    RMAN-06025: no backup of log thread 1 seq 3018 lowscn 5366309846 found to restore
    RMAN-06025: no backup of log thread 1 seq 3017 lowscn 5366309646 found to restore
    RMAN-06025: no backup of log thread 1 seq 3016 lowscn 5366309451 found to restore
    RMAN-06025: no backup of log thread 1 seq 3015 lowscn 5366309117 found to restore
    RMAN-06025: no backup of log thread 1 seq 3014 lowscn 5366308914 found to restore
    RMAN-06025: no backup of log thread 1 seq 3013 lowscn 5366308702 found to restore
    RMAN-06025: no backup of log thread 1 seq 3012 lowscn 5366308505 found to restore
    RMAN-06025: no backup of log thread 1 seq 3011 lowscn 5366308151 found to restore
    One day later, I ran the same command using same backup sets, this time it fires:
    starting media recovery
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 02/06/2011 08:09:53
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-06053: unable to perform media recovery because of missing log
    RMAN-06025: no backup of log thread 1 seq 3079 lowscn 5366325358 found to restor
    RMAN-06025: no backup of log thread 1 seq 3078 lowscn 5366325153 found to restor
    RMAN-06025: no backup of log thread 1 seq 3077 lowscn 5366324955 found to restor
    RMAN-06025: no backup of log thread 1 seq 3076 lowscn 5366324690 found to restor
    RMAN-06025: no backup of log thread 1 seq 3075 lowscn 5366324435 found to restor
    RMAN-06025: no backup of log thread 1 seq 3074 lowscn 5366324230 found to restor
    RMAN-06025: no backup of log thread 1 seq 3073 lowscn 5366324030 found to restor
    RMAN-06025: no backup of log thread 1 seq 3072 lowscn 5366323823 found to restor
    RMAN-06025: no backup of log thread 1 seq 3071 lowscn 5366323624 found to restor
    RMAN-06025: no backup of log thread 1 seq 3070 lowscn 5366323361 found to restor
    RMAN-06025: no backup of log thread 1 seq 3069 lowscn 5366323099 found to restor
    RMAN-06025: no backup of log thread 1 seq 3068 lowscn 5366322893 found to restor
    RMAN-06025: no backup of log thread 1 seq 3067 lowscn 5366322693 found to restor
    RMAN-06025: no backup of log thread 1 seq 3066 lowscn 5366322486 found to restor
    RMAN-06025: no backup of log thread 1 seq 3065 lowscn 5366322228 found to restor
    RMAN-06025: no backup of log thread 1 seq 3064 lowscn 5366322034 found to restor
    RMAN-06025: no backup of log thread 1 seq 3063 lowscn 5366321773 found to restor
    RMAN-06025: no backup of log thread 1 seq 3062 lowscn 5366321575 found to restor
    RMAN-06025: no backup of log thread 1 seq 3061 lowscn 5366321370 found to restor
    RMAN-06025: no backup of log thread 1 seq 3060 lowscn 5366321173 found to restor
    RMAN-06025: no backup of log thread 1 seq 3059 lowscn 5366320911 found to restor
    RMAN-06025: no backup of log thread 1 seq 3058 lowscn 5366320716 found to restor
    RMAN-06025: no backup of log thread 1 seq 3057 lowscn 5366320453 found to restor
    RMAN-06025: no backup of log thread 1 seq 3056 lowscn 5366320251 found to restor
    RMAN-06025: no backup of log thread 1 seq 3055 lowscn 5366320043 found to restor
    RMAN-06025: no backup of log thread 1 seq 3054 lowscn 5366319846 found to restor
    RMAN-06025: no backup of log thread 1 seq 3053 lowscn 5366319572 found to restor
    RMAN-06025: no backup of log thread 1 seq 3052 lowscn 5366319373 found to restor
    RMAN-06025: no backup of log thread 1 seq 3051 lowscn 5366319098 found to restor
    RMAN-06025: no backup of log thread 1 seq 3050 lowscn 5366318897 found to restor
    RMAN-06025: no backup of log thread 1 seq 3049 lowscn 5366318693 found to restor
    RMAN-06025: no backup of log thread 1 seq 3048 lowscn 5366318490 found to restor
    RMAN-06025: no backup of log thread 1 seq 3047 lowscn 5366318231 found to restor
    RMAN-06025: no backup of log thread 1 seq 3046 lowscn 5366318027 found to restor
    RMAN-06025: no backup of log thread 1 seq 3045 lowscn 5366317751 found to restor
    RMAN-06025: no backup of log thread 1 seq 3044 lowscn 5366317553 found to restor
    RMAN-06025: no backup of log thread 1 seq 3043 lowscn 5366317340 found to restor
    RMAN-06025: no backup of log thread 1 seq 3042 lowscn 5366317137 found to restor
    RMAN-06025: no backup of log thread 1 seq 3041 lowscn 5366316885 found to restor
    RMAN-06025: no backup of log thread 1 seq 3040 lowscn 5366316689 found to restor
    RMAN-06025: no backup of log thread 1 seq 3039 lowscn 5366316421 found to restor
    RMAN-06025: no backup of log thread 1 seq 3038 lowscn 5366316221 found to restor
    RMAN-06025: no backup of log thread 1 seq 3037 lowscn 5366316016 found to restor
    RMAN-06025: no backup of log thread 1 seq 3036 lowscn 5366315815 found to restor
    RMAN-06025: no backup of log thread 1 seq 3035 lowscn 5366315522 found to restor
    RMAN-06025: no backup of log thread 1 seq 3034 lowscn 5366315327 found to restor
    RMAN-06025: no backup of log thread 1 seq 3033 lowscn 5366315045 found to restor
    RMAN-06025: no backup of log thread 1 seq 3032 lowscn 5366314839 found to restor
    RMAN-06025: no backup of log thread 1 seq 3031 lowscn 5366314447 found to restor
    RMAN-06025: no backup of log thread 1 seq 3030 lowscn 5366314246 found to restor
    RMAN-06025: no backup of log thread 1 seq 3029 lowscn 5366312316 found to restor
    RMAN-06025: no backup of log thread 1 seq 3028 lowscn 5366312120 found to restor
    RMAN-06025: no backup of log thread 1 seq 3027 lowscn 5366311841 found to restor
    RMAN-06025: no backup of log thread 1 seq 3026 lowscn 5366311630 found to restor
    RMAN-06025: no backup of log thread 1 seq 3025 lowscn 5366311383 found to restor
    RMAN-06025: no backup of log thread 1 seq 3024 lowscn 5366311185 found to restor

    hi,
    The database does not open with reset logs until the duplicate command is complete, the process ahs not got completed sucessfully here, do the media recovery now with the help of command below and it must open fine
    contents of Memory Script:
    recover database until cancel;
    clone database
    delete archivelog
    you can also use the recover database till the available archivelog sequence if knowm to you.
    Vijay..

  • RMAN vs. SQL alter database open resetlogs

    Hello,
    Reading http://download.oracle.com/docs/cd/B28359_01/backup.111/b28273/rcmsynta006.htm
    Apparently some restrictions apply when not using a recovery catalog in regard to automatically creating the tempfile and also the reset database command when using resetlogs in SQL rather than RMAN.
    a) Is there an easy way to explain the situation?
    b) What are the consequences when forgetting to reset the database incarnation?
    Thanks.

    RMAN will automatically issue a RESET DATABASE command to the recovery catalog and this will let the catalog know to make the new incarnation the current one. However, if you OPEN RESETLOGS via SQL*Plus a RESET DATABASE will not automatically be issued.
    If you do not issue a RESET DATABASE, then the new incarnation will not be registered in the recovery catalog and you'll encounter an error the next time you try to use the recovery catalog.
    As for the tempfiles, I believe it's referring to any new tempfiles that you may have added after you backed up the controlfile (the same one you used to do the restore) will not be created. However, if you were using a recovery catalog and it was in sync with the current controlfile, then the up-to-date tempfile information could be obtained from the recovery catalog to create any new temp files that may have been created.
    Another wonderful way that Oracle documentation is confusing in how it explains concepts.

  • Hi, after installing Adobe CC I tried opening Adobe Photoshop. This failed. I get the opening window where it says installing plugins searching etc, after which PS opens in full screen. Just moments after that there's a fail warning, no code number, only

    Hi, after installing Adobe CC I tried opening Adobe Photoshop. This failed.
    I get the opening window where it says installing plugins searching etc, after which PS opens in full screen.
    Just moments after that there's a failure warning, no code number, only the warning that PS failed to open and PS will close.
    I tried downloading it for a second time, but this did'nt solve the problem.
    Befor the CC version I used a one year student version of Adobe CS6.
    What can I do?

    Regarding the Flash Player problem, disable Hardware Acceleration to circumvent driver incompatibilities.
    Regarding the Flash Pro installation problems, post in the Flash forums or http://forums.adobe.com/community/download_install_setup

  • Failure when trying to open db with resetlogs after restore of hot backup

    Hello,
    i know that ora-600 errors should be directed to oracle instead of here, but as i have no access to oracle support you may be able / willing to give me some hint anyway. here is what i tried to do:
    1. Make a Hot Backup of an Oracle DB running on Win2003, Version 9.2.0.5
    2. Trying to restore this backup on a new host, running WinXP, Oracle 9.2.0.5
    I can create the new controlfile and do a recovery with the syntax
    "recover database using backup controlfile until cancel"
    However, after this i'm trying to open the DB with the following syntax:
    "alter database open resetlogs"
    This takes a few seconds, then the instance gets terminated, showing an ora-600 error in the alert.log (i guess its useless to show the specific ora-600 error here, or am i wrong at this point?)
    now i'm wondering if the difference in the operating system could be the reason ? I also have to mention that the database files from the hot backup were transfered over a WAN line, could a damage to this files, happened during the transfer cause something like this ?

    These are from Howard
    When you re-create a controlfile using a script or command that says 'create controlfile...', that command will require you to spell out the path to all the datafiles and online redo logs. It is a simple matter for your server process to visit each of the files mentioned in the create controlfile and read the SCN stored in the datafile header. It can also read the online redo logs and read the latest checkpoint change number stored there.
    If all those numbers agree, that is obviously the age to which the rest of the database had gotten before the controlfiles were lost, and it's OK to create the new controlfile with that agreed-upon SCN forced in to the controlfile as its new SCN. Therefore the entire database is consistent and the database can be opened without recovery.
    This sort of thing is what happens when you close your database down nicely and then delete all controlfiles as part of a recovery demo on a training course!
    If those numbers don't agree, then it doesn't really matter. Logically, the highest number found, whether that be in one or more of the datafiles or one of the online logs, must be the age the database had reached before disaster struck. Your server process then writes that highest number into the new controlfile as its new SCN, and therefore your new controlfile agrees with the age of the latest bit of your database. The bits which were found to have smaller SCNs than that are therefore obviously in need of recovery -and because your new controlfile knows the SCN at which recovery should stop, recovery can be performed without trouble.
    When the datafiles are inconsistent the control file has the latest SCN on it and it tries to bring the entrire database consisent with respective to its SCN..if something does not matches it says it is consisten
    SO the recovery is done mainly based on the Controlf file..but the term backup..assume we have binary backup or the created new controlfile will have the scn to bring the DB to consistent state
    Message was edited by:
    Maran Viswarayar

Maybe you are looking for