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.

Similar Messages

  • Open resetlogs is not  working when creating clone db with online backup

    Hi All,
    I am trying to create a clone database using hot backup of a database .
    STEPS THAT I FOLLOWED
    LET ----- >CURRENT_DB NAME=DEV
    CLONE DATABASE NAME=DEVCLONE
    steps PERFORMED FORM DEV DB
    - put the database in backup mode using 'alter database begin backup'
    - copy all the data files to a different folder
    - during copy i have performed some operations on the DB (creating users, tables, dmls etc...)
    - in between copying i also performed log switch
    - after completion of copy , "alter database end backup"
    - created a backup control file in a human readable format (alter database backup controlfile to trace as ........)
    steps performed for clone DB side ((DEVCLONE)
    - created a parameter file for the database .
    - modified the backup control file so that it will point to the location of copied destination of datafiles
    - set the ORACLE_SID
    - then 'sqlplus / as sysdba
    - starup nomount
    - run the modified control file ( created a control file for the clone database)
    - recover the database using "recover database using backup controlfile"
    I have provided the archive files that it was asking for (archive logs that has been generated in DEV DB)
    then i canceled the recovery by typing "cancel"
    - recover database using backup controlfile until cancel;
    then typed "cancel"
    - then try to open the database with open resetlogs but it showed below error
    alter database open resetlogs
    ERROR at line 1:
    ORA-01195: online backup of file 1 needs more recovery to be consistent
    ORA-01110: data file 1: 'D:\DATA_GUARD\DEVHOT\SYSTEM01.DBF'
    please help me on this ......
    Thanks

    Thanks , now i am able to open the DB in open reset logs mode .
    Previously , when i had not taken the archive log after "alter database end backup" , i was not able to open the db with open resetlogs because the
    fuzzy status of all the datafile headers were YES .
    But after taking the archive log that got generated after "alter database end backup" and applying it on the clone db(Created with HOT backup ) the datafile_header status got changed from YES to NO .
    So for that i am able to open the clone db with open resetlogs .
    Can you please help me with a small description why this is happening ?
    Thanks.......

  • Error during restore/recovery and 'open resetlogs'

    Hello forum. I'm attempting to restore a database to a new host and have run into an error during the opening of the database (with resetlogs). The renaming of the datafiles, restore, switching of datafiles, and recovery are all done by an rman script, the contents of which are below:
    # Restore production database to DR site using file system
    # instead of ASM
    run {
    set newname for datafile 1 to '/opt/oracle/product/10gR2/oradata/DB01/system.dbf';
    set newname for datafile 2 to '/opt/oracle/product/10gR2/oradata/DB01/undotbs1.dbf';
    set newname for datafile 3 to '/opt/oracle/product/10gR2/oradata/DB01/sysaux.dbf';
    set newname for datafile 4 to '/opt/oracle/product/10gR2/oradata/DB01/users.dbf';
    set newname for datafile 5 to '/opt/oracle/product/10gR2/oradata/DB01/undotbs2.dbf';
    set newname for datafile 6 to '/opt/oracle/product/10gR2/oradata/DB01/file1.dbf';
    set newname for datafile 7 to '/opt/oracle/product/10gR2/oradata/DB01/file2.dbf';
    restore database;
    switch datafile all;
    recover database;
    I get the following output:
    RMAN> @/home/oracle/scripts/rman_dr.rman
    RMAN> # Restore production database to DR site using file system
    2> # instead of ASM
    3> #
    4> run {
    5> set newname for datafile 1 to '/opt/oracle/product/10gR2/oradata/DB01/system.dbf';
    6> set newname for datafile 2 to '/opt/oracle/product/10gR2/oradata/DB01/undotbs1.dbf';
    7> set newname for datafile 3 to '/opt/oracle/product/10gR2/oradata/DB01/sysaux.dbf';
    8> set newname for datafile 4 to '/opt/oracle/product/10gR2/oradata/DB01/users.dbf';
    9> set newname for datafile 5 to '/opt/oracle/product/10gR2/oradata/DB01/undotbs2.dbf';
    10> set newname for datafile 6 to '/opt/oracle/product/10gR2/oradata/DB01/file1.dbf';
    11> set newname for datafile 7 to '/opt/oracle/product/10gR2/oradata/DB01/file2.dbf';
    12>
    13> restore database;
    14> switch datafile all;
    15> recover database;
    16> }
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    Starting restore at 03-JAN-08
    Starting implicit crosscheck backup at 03-JAN-08
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=156 devtype=DISK
    Crosschecked 651 objects
    Finished implicit crosscheck backup at 03-JAN-08
    Starting implicit crosscheck copy at 03-JAN-08
    using channel ORA_DISK_1
    Crosschecked 1 objects
    Finished implicit crosscheck copy at 03-JAN-08
    searching for all files in the recovery area
    cataloging files...
    no files cataloged
    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/product/10gR2/oradata/DB01/system.dbf
    restoring datafile 00002 to /opt/oracle/product/10gR2/oradata/DB01/undotbs1.dbf
    restoring datafile 00003 to /opt/oracle/product/10gR2/oradata/DB01/sysaux.dbf
    restoring datafile 00004 to /opt/oracle/product/10gR2/oradata/DB01/users.dbf
    restoring datafile 00005 to /opt/oracle/product/10gR2/oradata/DB01/undotbs2.dbf
    restoring datafile 00006 to /opt/oracle/product/10gR2/oradata/DB01/file1.dbf
    restoring datafile 00007 to /opt/oracle/product/10gR2/oradata/DB01/file2.dbfchannel ORA_DISK_1: reading from backup piece /ocfs2/remitpro/oracleBackups/tmp/rman_LV0_DB01.642899284.1.1.bus
    channel ORA_DISK_1: restored backup piece 1
    piece handle=/ocfs2/remitpro/oracleBackups/tmp/rman_LV0_DB01.642899284.1.1.bus tag=20080101_LV0_DB
    channel ORA_DISK_1: restore complete, elapsed time: 01:22:28
    Finished restore at 03-JAN-08
    datafile 1 switched to datafile copy
    input datafile copy recid=14 stamp=643049225 filename=/opt/oracle/product/10gR2/oradata/DB01/system.dbf
    datafile 2 switched to datafile copy
    input datafile copy recid=15 stamp=643049225 filename=/opt/oracle/product/10gR2/oradata/DB01/undotbs1.dbf
    datafile 3 switched to datafile copy
    input datafile copy recid=16 stamp=643049225 filename=/opt/oracle/product/10gR2/oradata/DB01/sysaux.dbf
    datafile 4 switched to datafile copy
    input datafile copy recid=17 stamp=643049225 filename=/opt/oracle/product/10gR2/oradata/DB01/users.dbf
    datafile 5 switched to datafile copy
    input datafile copy recid=18 stamp=643049225 filename=/opt/oracle/product/10gR2/oradata/DB01/undotbs2.dbf
    datafile 6 switched to datafile copy
    input datafile copy recid=19 stamp=643049225 filename=/opt/oracle/product/10gR2/oradata/DB01/file1.dbf
    datafile 7 switched to datafile copy
    input datafile copy recid=20 stamp=643049225 filename=/opt/oracle/product/10gR2/oradata/DB01/file2.dbf
    Starting recover at 03-JAN-08
    using channel ORA_DISK_1
    starting media recovery
    channel ORA_DISK_1: starting archive log restore to default destination
    channel ORA_DISK_1: restoring archive log
    archive log thread=2 sequence=1005
    channel ORA_DISK_1: restoring archive log
    archive log thread=1 sequence=1365
    channel ORA_DISK_1: reading from backup piece /ocfs2/remitpro/oracleBackups/tmp/rman_LV0_DB01.642900444.1.1.bus
    channel ORA_DISK_1: restored backup piece 1
    piece handle=/ocfs2/remitpro/oracleBackups/tmp/rman_LV0_DB01.642900444.1.1.bus tag=20080101_LV0_DB
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:05
    archive log filename=/opt/oracle/product/10gR2/db/flash_recovery_area/DB01/archivelog/2008_01_03/o1_mf_1_1365_3qtshnfv_.arc thread=1 sequence=1365
    archive log filename=/opt/oracle/product/10gR2/db/flash_recovery_area/DB01/archivelog/2008_01_03/o1_mf_2_1005_3qtshncz_.arc thread=2 sequence=1005
    channel default: deleting archive log(s)
    archive log filename=/opt/oracle/product/10gR2/db/flash_recovery_area/DB01/archivelog/2008_01_03/o1_mf_1_1365_3qtshnfv_.arc recid=2418 stamp=643049236
    unable to find archive log
    archive log thread=1 sequence=1366
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 01/03/2008 16:47:22
    RMAN-06054: media recovery requesting unknown log: thread 1 seq 1366 lowscn 181804603
    RMAN> **end-of-file**
    I searched for a decription of the 06054 error, and found that if the archive logs weren't available, then to run "alter database open resetlogs;", which I did. Here's the output:
    RMAN> alter database open resetlogs;
    database opened
    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
    ORACLE error from target database:
    ORA-06553: PLS-801: internal error [56319]
    I've done all of this twice now, with the same result. I've googled PLS-801 and found more than a few instances of people getting this code, but not during a database open after a restore. Can anyone shed some light on what might have gone wrong? In the interest of brevity, I left out the rest of the restore process prior to running the database restore, but other than setting "compatible" and "db_recovery_file_dest_size", it was all by the book.
    Thanks in advance.

    Thanks for the reply Pierre.
    I am not using RMAN Duplicate. Yes, the source of the backup is an RAC. The destination is a single server, with the DB on the filesystem. Here's an overview of of the commands I ran and the procedure.
    Copied tar'd backup controlfile and datafiles to destination machine. Untar'd. Install 10.2.0.1.0 on destination machine, patch to 10.2.0.2.0.
    OS> sqlplus /nologin
    SQL> alter system set compatible = '10.2.0.2.0' scope=spfile;
    SQL> alter system set db_recovery_dest_file_size = '8g'; scope spfile;
    SQL> shutdown immediate;
    SQL> startup; (to verify changes took...)
    SQL> shutdown immediate;
    OS> Copy control file from untar'd dir and place in $ORACLE_HOME/dbs/, truncate name to c-DBID-date-00.
    OS> rman target /
    RMAN> startup nomount;
    RMAN> set dbid <dbid from control file>;
    RMAN> restore controlfile from autobackup; (finds control file with no problem...)
    RMAN> alter database mount;
    RMAN> @/home/oracle/rman_dr.rman (script cited in first post, to rename datafiles from ASM to filesystem, restore, switch files, and recover...)
    RMAN> alter database open resetlogs; (as cited before...)
    If I'm not using Duplicate and not specifying dates, the UNTIL/SET UNTIL commands aren't necessary, correct?

  • 'alter database open resetlogs' didn't reset one of the datafiles

    I've spent the last three and a half weeks recovering an oracle database (11g 64-bit linux) because of a corrupt block in an online redo log (which I thought was being written to multiple locations). I restored the files, moving some of them around in the process; recovered to the latest possible point; moved files back to their proper location; ran 'alter database open resetlogs'; and one of the datafiles (from a bigfile tablespace) didn't get reset. I checked afterward, and it was marked offline. I do not remember placing the file offline, and cannot find such a statement in my last 300 sqlplus commands, which includes commands well before I renamed this file and the commands surrounding the rename.
    Restoring/recovering the database again will take too long, and is a remarkably poor option. Even if the database had opened correctly, the affected tablespace would not have been touched in the two or three minutes the database was open. Is there any way to force oracle to reset the logs again or otherwise fix this one file to mark it with the same date? Only allowing the resetlogs option after an incomplete recovery seems a poor restriction, especially, if files can slip through like this. I'm suspecting there is someway to just fix the checkpoint values for the tablespace, but I don't know where to begin. This particular file is <5% of the database, so if I have to do some sort of backup/restore with just it, that is probably doable.

    0: 11.1.0.6.0 on SUSE Linux Enterprise Server 10 SP2
    1: rman
    backup format '/opt/oracle/backup/mydatabase_%Y-%M-%D_%s_datafiles_%p' (database);
    backup format '/opt/oracle/backup/mydatabase_%Y-%M-%D_%s_archivelogs_%p' archivelog all delete input;
    backup format '/opt/oracle/backup/mydatabase_%Y-%M-%D_%s_control_%p' current controlfile spfile;
    2:
    restore database; --not sure what datafiles were restored with this
    restore datafile X; --several files were restored individually
    recover database until scn 1137554504; -- I verified that all datafiles were on the same checkpoint after this finished. Not having placed any files offline, I didn't bother checking that.
    3:
    SQL> alter database open resetlogs;
    Database altered.
    Elapsed: 00:04:20.34
    SQL> quit
    Disconnected from Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - 64bit Production
    With the Partitioning, OLAP and Data Mining options
    4: Nothing in the tablespace has been touched since I ran 'alter database open resetlogs;'. It also appears that oracle placed the file offline (without me telling it to do so) and left it that way through the resetlogs, leaving the tablespace unusable during the time it was opened. The only things that would be out of date are the 'RESETLOGS_CHANGE#', the 'CHECKPOINT_CHANGE#', and associated values. It's still at the last scn before the resetlogs, and the system has been in archivelog mode the entire time. This is all information that Oracle could be tracking, and from a program logic standpoint there is no reason why Oracle cannot tie together the changes before the resetlogs, the resetlogs command and the changes after the resetlogs into a new, continuous string of changes. I assume there is some such feature in a high-caliber program because I'm actually a programmer (who would have included such advanced tracking features), and I've become a DBA out of necessity. I admit to not knowing all of the oracle DBA commands, hence me posting here before doing the work of submitting a request to metalink.
    5: I consider it a poor restriction because it doesn't always reset the logs on all files, and as far as my knowledge goes it has rendered my 3.5 week recovery process WORTHLESS. I suppose it could cause numerous errors, especially if the database wasn't cleanly shut down, but having the ability to do something equivalent to datafiles that oracle skipped the process on seems quite useful in my situation. I guess the more fundamental problem to complain about is that it would apply such changes to only some of the files, while leaving others unusable, instead of just giving me an error that some files weren't going to be reset, but I think I'm done venting my Oracle frustrations for now.
    Am I stuck with a tablespace that I cannot bring online with the database open, or is there some sort of 'alter database datafile' command (or anything else) that I know nothing of that will fix the straggling file?
    Edited by: jbo5112 on Oct 5, 2009 3:33 PM -- obfuscated some file names to secure identity.

  • Queries on DATABASE OPEN RESETLOGS and lost Control Files

    Hi I have some queries on RESETLOGS I would be keen to hear some answers on
    Q1. If I am doing a PITR and I end in ALTER DATABASE OPEN RESETLOGS, what happens about any Archived Redo Log files ( still in situ ) that were from the original source database but were at a future point in time ? Are they just ignored by any future restore ( since their log sequence number will be different ? ) and eventually over written or purged out ?
    Q2. When you create a new incarnation using RESETLOGS can you Flashback Database to before this ?
    Q3. If I have lost all my Control Files and have not created a backup control file or done a backup to trace of the control file, can I simply restore one of the actual control files from my last backup and use RECOVER DATABASE USING BACKUP CONTROLFILE AUTO; or will this only work with a bonafide backup control file ( i.e. one created via ALTER DATABASE BACKUP CONTROLFILE TO ‘<file spec>’; )
    Q4. When I issue RECOVER DATABASE USING BACKUP CONTROLFILE AUTO;
    Do I have to ALTER DATABASE OPEN RESETLOGS at the end of the recovery ? I have seen this documented but I am not sure why I would need to reset the redo logs and instead simply open the database ?
    Q5. If I am running the CREATE CONTROL FILE command from an ALTER DATABASE BACKUP CONTROLFILE TO TRACE;
    Do I need to use the NORESETLOGS or RESETLOGS ? How do I know which to use ?
    thanks,
    Jim

    Jimbo wrote:
    Hi I have some queries on RESETLOGS I would be keen to hear some answers on
    Q1. If I am doing a PITR and I end in ALTER DATABASE OPEN RESETLOGS, what happens about any Archived Redo Log files ( still in situ ) that were from the original source database but were at a future point in time ? Are they just ignored by any future restore ( since their log sequence number will be different ? ) and eventually over written or purged out ?
    what happens when you try it?
    Q2. When you create a new incarnation using RESETLOGS can you Flashback Database to before this ?
    what happens when you try it?
    Q3. If I have lost all my Control Files and have not created a backup control file or done a backup to trace of the control file, can I simply restore one of the actual control files from my last backup and use RECOVER DATABASE USING BACKUP CONTROLFILE AUTO; or will this only work with a bonafide backup control file ( i.e. one created via ALTER DATABASE BACKUP CONTROLFILE TO ‘<file spec>’; )
    what happens when you try it?
    Q4. When I issue RECOVER DATABASE USING BACKUP CONTROLFILE AUTO;
    Do I have to ALTER DATABASE OPEN RESETLOGS at the end of the recovery ? I have seen this documented but I am not sure why I would need to reset the redo logs and instead simply open the database ?
    what happens when you try it?
    Q5. If I am running the CREATE CONTROL FILE command from an ALTER DATABASE BACKUP CONTROLFILE TO TRACE;
    Do I need to use the NORESETLOGS or RESETLOGS ? How do I know which to use ?
    what happens when you try it?

  • What are all scenarios we will open the database in open resetlog mode

    what are all scenarios we will open the database in open resetlog mode..please advise

    Another situation I could think of is that when the active/current online redo logs are lost.
    Regards,
    Jaffar

  • DataGuard / effect of open resetlogs on Primary

    Hi,
    We've a primary RAC with corresponding dataguard physical standby database (running as 1 node when acting as disaster recover site).
    In the event of a major upgrade, we typically stop the apply of redo to the standby site and run the upgrade (say to the application tables), thus we have the standby in the event of catastrophe (call this T1, where we stop the apply / sending of redo to the DR site).
    Where we have to restore the primary database to a point in time during the upgrade, so POST T1, and open with an "alter database open resetlogs" (so point in time recovery) - does this mean we'd have to rebuild our primary.
    I believe we would not - per DataGuard Concepts and Administration for Oracle 10GR2 (B14239-05), chapter 8 section 4 -
    "Data Guard allows recovery on a physical standby database to continue after the primary database has been opened with the RESETLOGS option. When an ALTER DATABASE OPEN RESETLOGS statement is issued on the primary database, the incarnation of the database changes, creating a new branch of redo data."
    has anyone tried this - is it OK!?
    Thanks,
    Truman.
    Btw - appreciate we could use flashback, however this is not currently being considered - db is 10.2.0.3 on hp-ux 11.23.

    Truman...we have done sort of what you are talking about and it did work. We did a test where we created restore points on both primary and standby, ran some testing on primary and then at the end of the test flashed both primary and standby back to resrtore points and opned primary with open resetlogs.....this did work but had some issues where it would apply/catch up some an then would start asking for ancient sequences that didn't exist so the fix was to rebuild the standby control and recovery picked back up. I will say that we use dgbroker, RAC database and we used flashback with restore points, so there are differences from your setup but for the idea of it working so we didn't have to rebuild the standby..yes it did. Oracle said that a reason this could have happened was that the broker stops and starts recovery several times when enabling on startup and it had trouble going across the resetlogs.
    Edited to fix testing scenerio...was thinking of a different test we also did without open resetlogs.
    Edited by: DBA_Mike on Mar 27, 2009 7:22 AM

  • 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..

  • OPEN RESETLOGS and incarnation....

    Hi ,
    I try to understand the use/function of OPEN RESETLOGS but the extensive use of the word 'incarnation' sets obstacles....
    The following lines are from :
    Oracle® Database Backup and Recovery Advanced User's Guide
    10g Release 2 (10.2)
    Part Number B14191-02
    Paragraph:
    Resetting the Database Incarnation in the Recovery Catalog
    When you run either the RMAN command or the SQL statement ALTER
    DATABASE OPEN RESETLOGS, you create a new incarnation of the database.
    You can access a record of the new incarnation in the
    V$DATABASE_INCARNATION view of the target database.
    If you run the RMAN command or the SQL statement ALTER DATABASE OPEN
    RESETLOGS, then a new database incarnation record is automatically created in
    the recovery catalog. The database also implicitly and automatically issues a
    RESET DATABASE command, which specifies that this new incarnation of the
    database is the current incarnation. All subsequent backups and log archiving
    done by the target database is associated with the new database incarnation.Can anybody explain ....????
    Thanks....a lot
    Sim

    Incarnation here has the same meaning here that you would find in dictionary.
    What it means is that now after "incarnation" this database is as good as a new database since all the redolog sequence, archive log sequence etc will be reset to start which they were during the time of creation (or last incarnation) of the database.
    Lets assume u create a database. Lets call this as Life1 of the database.
    Now a year later because of some reason you have to do an incomplete recovery and you open you database using resetlogs. Lets say this is Life2 of the database
    Now after some time you do that again. This is Life3 of the database.
    But there are times when you might want to bring the database back to Life1 and Life2. It is possible but because Oracle maintains all the Lives i.e INCARNATION of the database.
    The concept of incarnation is important due to many reasons but for you understanding you can take it as life cycle of a database.
    Thanks,
    Ankit.

  • 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.

  • 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

  • Alter database open resetlogs upgrade ;         throwing error

    Recently i have cloned a database from 11.2.0.2 to 11.2.0.3 on a new server.... I got the error as fowwos,
    contents of Memory Script:
    Alter clone database open resetlogs;
    executing Memory Script
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00601: fatal error in recovery manager
    RMAN-03004: fatal error during execution of command
    RMAN-10041: Could not re-create polling channel context following failure.
    RMAN-10024: error setting up for rpc polling
    RMAN-10005: error opening cursor
    RMAN-10002: ORACLE error: ORA-03114: not connected to ORACLE
    RMAN-03002: failure of Duplicate Db command at 07/12/2012 16:19:24
    RMAN-05501: aborting duplication of target database
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-06136: ORACLE error from auxiliary database: ORA-01092: ORACLE instance terminated. Disconnection forced
    ORA-00704: bootstrap process failure
    ORA-39700: database must be opened with UPGRADE option
    Process ID: 29247
    Session ID: 200 Serial number: 5
    So i have tried
    SQL> alter database open resetlogs upgrade;
    alter database open resetlogs upgrade
    ERROR at line 1:
    ORA-01139: RESETLOGS option only valid after an incomplete database recovery
    SQL> alter database open upgrade;
    alter database open upgrade
    ERROR at line 1:
    ORA-01113: file 1 needs media recovery
    ORA-01110: data file 1: '+DATA_CMX/cmx/datafile/system.270.788451975'
    Any help ?

    Hi,
    Duplicate is not supported using different version of database, so I recommend you don't use duplicate.
    Because RMAN "duplicate" attempts to automatically rename (rename required recover) and open the database you may not use RMAN duplicate for this case, only RMAN restore.
    Perform this work using normal restore database.
    See this example.
    On prod database with db_name/db_unique_name dbupg:
    Recovery Manager: Release 11.2.0.2.0 - Production on Fri Jul 13 15:15:59 2012
    RMAN> backup database plus archivelog delete input;
    Starting backup at 13-JUL-12
    current log archived
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=52 device type=DISK
    channel ORA_DISK_1: starting archived log backup set
    channel ORA_DISK_1: specifying archived log(s) in backup set
    input archived log thread=1 sequence=17 RECID=1 STAMP=788540852
    input archived log thread=1 sequence=18 RECID=2 STAMP=788541371
    channel ORA_DISK_1: starting piece 1 at 13-JUL-12
    channel ORA_DISK_1: finished piece 1 at 13-JUL-12
    piece handle=/u01/app/oracle/flash_recovery_area01/DBUPG/backupset/2012_07_13/o1_mf_annnn_TAG20120713T151612_800shf7w_.bkp tag=TAG20120713T151612 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
    channel ORA_DISK_1: deleting archived log(s)
    archived log file name=/u01/app/oracle/flash_recovery_area01/DBUPG/archivelog/2012_07_13/o1_mf_1_17_800rz40y_.arc RECID=1 STAMP=788540852
    archived log file name=/u01/app/oracle/flash_recovery_area01/DBUPG/archivelog/2012_07_13/o1_mf_1_18_800shcsd_.arc RECID=2 STAMP=788541371
    Finished backup at 13-JUL-12
    Starting backup at 13-JUL-12
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    input datafile file number=00001 name=+DS8000_DG/dbupg/datafile/system.271.788537119
    input datafile file number=00002 name=+DS8000_DG/dbupg/datafile/sysaux.272.788537167
    input datafile file number=00003 name=+DS8000_DG/dbupg/datafile/undotbs1.273.788537199
    input datafile file number=00004 name=+DS8000_DG/dbupg/datafile/users.275.788537229
    channel ORA_DISK_1: starting piece 1 at 13-JUL-12
    channel ORA_DISK_1: finished piece 1 at 13-JUL-12
    piece handle=/u01/app/oracle/flash_recovery_area01/DBUPG/backupset/2012_07_13/o1_mf_nnndf_TAG20120713T151614_800shgw5_.bkp tag=TAG20120713T151614 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:35
    channel ORA_DISK_1: starting full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    including current control file in backup set
    including current SPFILE in backup set
    channel ORA_DISK_1: starting piece 1 at 13-JUL-12
    channel ORA_DISK_1: finished piece 1 at 13-JUL-12
    piece handle=/u01/app/oracle/flash_recovery_area01/DBUPG/backupset/2012_07_13/o1_mf_ncsnf_TAG20120713T151614_800sjm29_.bkp tag=TAG20120713T151614 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
    Finished backup at 13-JUL-12
    Starting backup at 13-JUL-12
    current log archived
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting archived log backup set
    channel ORA_DISK_1: specifying archived log(s) in backup set
    input archived log thread=1 sequence=19 RECID=3 STAMP=788541412
    channel ORA_DISK_1: starting piece 1 at 13-JUL-12
    channel ORA_DISK_1: finished piece 1 at 13-JUL-12
    piece handle=/u01/app/oracle/flash_recovery_area01/DBUPG/backupset/2012_07_13/o1_mf_annnn_TAG20120713T151652_800sjnf7_.bkp tag=TAG20120713T151652 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
    channel ORA_DISK_1: deleting archived log(s)
    archived log file name=/u01/app/oracle/flash_recovery_area01/DBUPG/archivelog/2012_07_13/o1_mf_1_19_800sjn5q_.arc RECID=3 STAMP=788541412
    Finished backup at 13-JUL-12
    RMAN> backup current controlfile;
    Starting backup at 13-JUL-12
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    including current control file in backup set
    channel ORA_DISK_1: starting piece 1 at 13-JUL-12
    channel ORA_DISK_1: finished piece 1 at 13-JUL-12
    piece handle=/u01/app/oracle/flash_recovery_area01/DBUPG/backupset/2012_07_13/o1_mf_ncnnf_TAG20120713T153435_800tkwl2_.bkp tag=TAG20120713T153435 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
    Finished backup at 13-JUL-12I used same server to do this work... I really dont recommend that, if yes you must be aware about location of restore... you should use new server:
    Create a spfile:
    *.control_files='+DS8000_DG/dbclone/controlfile/Current.277.788541913'
    *.db_name='dbupg'
    *.db_unique_name='dbclone'
    *.audit_file_dest='/u01/app/oracle/admin/dbclone/adump'
    *.audit_trail='db'
    *.compatible='11.2.0.0.0'
    *.db_block_size=8192
    *.db_create_file_dest='+MMC'
    *.db_domain=''
    *.db_recovery_file_dest_size=107374182400
    *.db_recovery_file_dest='/u01/app/oracle/flash_recovery_area01'
    *.diagnostic_dest='/u01/app/oracle'
    *.log_file_name_convert='+DS8000_DG','+MMC'
    *.memory_target=1031798784
    *.open_cursors=300Make backup available on new server:
    and:
    SQL*Plus: Release 11.2.0.3.0 Production on Fri Jul 13 15:33:24 2012
    Copyright (c) 1982, 2011, Oracle.  All rights reserved.
    Connected to an idle instance.
    SQL> startup nomount
    ORACLE instance started.
    Total System Global Area 1027182592 bytes
    Fixed Size                  2227936 bytes
    Variable Size             599785760 bytes
    Database Buffers          419430400 bytes
    Redo Buffers                5738496 bytes
    SQL> show parameter db_n
    NAME                                 TYPE        VALUE
    db_name                              string      dbupg
    SQL> show parameter db_un
    NAME                                 TYPE        VALUE
    db_unique_name                       string      dbclone
    RMAN> restore controlfile from '/u01/app/oracle/flash_recovery_area01/DBUPG/backupset/2012_07_13/o1_mf_ncnnf_TAG20120713T153435_800tkwl2_.bkp';
    Starting restore at 13-JUL-12
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=290 device type=DISK
    channel ORA_DISK_1: restoring control file
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:02
    output file name=+DS8000_DG/dbclone/controlfile/current.277.788541913
    Finished restore at 13-JUL-12
    RMAN> startup mount
    database is already started
    database mounted
    released channel: ORA_DISK_1
    RMAN> run {
    2> SET NEWNAME FOR DATABASE TO '+MMC';
    3> restore database  ;
    4> }
    executing command: SET NEWNAME
    Starting restore at 13-JUL-12
    Starting implicit crosscheck backup at 13-JUL-12
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=290 device type=DISK
    Crosschecked 4 objects
    Finished implicit crosscheck backup at 13-JUL-12
    Starting implicit crosscheck copy at 13-JUL-12
    using channel ORA_DISK_1
    Crosschecked 2 objects
    Finished implicit crosscheck copy at 13-JUL-12
    searching for all files in the recovery area
    cataloging files...
    no files cataloged
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting datafile backup set restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    channel ORA_DISK_1: restoring datafile 00001 to +MMC
    channel ORA_DISK_1: restoring datafile 00002 to +MMC
    channel ORA_DISK_1: restoring datafile 00003 to +MMC
    channel ORA_DISK_1: restoring datafile 00004 to +MMC
    channel ORA_DISK_1: reading from backup piece /u01/app/oracle/flash_recovery_area01/DBUPG/backupset/2012_07_13/o1_mf_nnndf_TAG20120713T151614_800shgw5_.bkp
    channel ORA_DISK_1: piece handle=/u01/app/oracle/flash_recovery_area01/DBUPG/backupset/2012_07_13/o1_mf_nnndf_TAG20120713T151614_800shgw5_.bkp tag=TAG20120713T151614
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:46
    Finished restore at 13-JUL-12
    RMAN> recover database;
    Starting recover at 13-JUL-12
    using channel ORA_DISK_1
    starting media recovery
    media recovery complete, elapsed time: 00:00:01
    Finished recover at 13-JUL-12So, just startup with upgrade option.
    SQL*Plus: Release 11.2.0.3.0 Production on Fri Jul 13 15:39:31 2012
    SQL>  alter database open resetlogs upgrade; Now you can upgrade your database.
    After upgrade database you can change the database name using NID:
    $ nid
    DBNEWID: Release 11.2.0.3.0 - Production on Fri Jul 13 15:50:23 2012
    Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.
    Keyword     Description                    (Default)
    TARGET      Username/Password              (NONE)
    DBNAME      New database name              (NONE)
    LOGFILE     Output Log                     (NONE)
    REVERT      Revert failed change           NO
    SETNAME     Set a new database name only   NO
    APPEND      Append to output log           NO
    HELP        Displays these messages        NOHTH,
    Levi Pereira
    Edited by: Levi Pereira on Jul 13, 2012 4:04 PM

  • Alter database open resetlogs

    Hi,
    when I try to duplicate my database by RMAN I have :
    RMAN-06053: unable to perform media recovery because of missing log
    RMAN-06025: no backup of log thread 1 seq 1452 scn 252730 found to restore
    I connect to duplicate database in sqlplus , it is not open.
    Than I do :
    alter database open resetlogs;
    And the database would be open.
    Is it bad ? Will we lose the data ? If yes what solution do you propose ?
    Effectively I do not know how to use this informations :
    log thread 1 seq 1452 scn 252730 found to restore
    Please help me to use this informations if helplfull.
    Many thanks.

    From Oracle Error documentation:
    RMAN-06025: no backup of log thread number seq number lowscn string found to restore
    Cause: An archive log restore restore could not proceed because no backup of the indicated archived log was found. It may be the case that a backup of this file exists but does not satisfy the criteria specified in the user"s restore operands.
    Action: None - this is an informational message. See message 6026 for further details.
    RMAN-06026: some targets not found - aborting restore
    Cause: Some of the files specified for restore could not be found. Message 6023, 6024, or 6025 is also issued to indicate which files could not be found. Some common reasons why a file can not be restored are that there is no backup or copy of the file that is known to recovery manager, or there are no backups or copies that fall within the criteria specified on the RESTORE command, or some datafile copies have been made but not cataloged.
    Action: The Recovery Manager LIST command can be used to display the backups and copies that Recovery Manager knows about. Select the files to be restored from that list.
    It seems you do not have some of the files required for recover operation. Could you post how this database is backed up using RMAN?

  • ORA-01547 :warning recover succeeded but open resetlogs......

    Hai All,
    In a standby database I put a command
    sql> recover standby database
    auto
    then error comes...
    ORA-01547 :warning recover succeeded but open resetlogs......
    ora-01152 : file1 was not restored from a sufficiently old bcakup
    ora-01110 : datafile 1: d:\sfms\system01.dbf'
    when the database open read only .. also this error comes...
    How can I resolve....
    Shiju

    See Note:1070049.6

  • 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.

  • Alter database open resetlog?

    Hi all,
    I am trying the Database cloning(new database name) in my development environment(Oracle 11g r1 Windows 2003 Server). While Creating a new controlfile we need pass command like this "CREATE CONTROLFILE REUSE SET DATABASE "ORCL2" RESETLOGS FORCE LOGGING NOARCHIVELOG"
    1.i just wants to know why we need to use resetlogs, when i pass this command what is internally happening in the oracle?
    2.when the new database name is updated in all datafile during controlfile creation or while opening the database?
    3.Alter database open resetlogs what is internally happening in the oracle when i pass this command?
    Please advice me
    Thanks & Regards,
    Shan

    this will help
    http://web.njit.edu/info/limpid/DOC/backup.102/b14191/osrecov009.htm

Maybe you are looking for