Standby recovery after open Resetlogs

Can someone explain the case more clearly?

If the database pending...	Then...	Perform these steps...
Not asked to redo data beyond the new resetlogs SCN (after the start of the new branch of data recovery)	Redo apply automatically takes the new branch of the roll forward.	No manual intervention is required. The MRP automatically resynchronizes the database pending with the new branch of data recovery.

I can't understand the following case:

"No data applied not repeat past the new resetlogs SCN (after the start of the new branch of data recovery).

then your current journal seq is 124, when stop you this seq is archived, shipped in standby mode and applied, so now your Eve is also at 124.

Meanwhile at the elementary level, like you did resetlogs, it will open the db with seq 1 and this too will be propagated to the wait and apply.

so your wait will remain synchronized in the resetlogs operation.

Tags: Database

Similar Questions

Reporter the read-only TBS restore/recovery and open resetlogs
Hello
our database has got some read only tablespaces on slow disk space (separate mount point).
During the disaster, we want to make DB as soon as possible and there is no need to open it with read only tablespaces in place (they can be restored later).
This scenario works when we complete the recovery, but in the case of incomplete recovery when we open with reset logs.
There is no way to restore/recovery of tablespaces only reading after change of the incarnation.
We must put CAMILLE on the kind of to THE and then recover/restore TBS to the current incarnation (opening after resetlogs).
Is there a way to deal with this?
Main goal is to show DB as soon as POSSIBLE with no read-only tablespace in the two scénarion (complete, recovery, incomplete recovery).
DB 9.2.0.8 AIX, backups on the tape library.
Regars.
G
I see that you have a patched 9.2.0.8 version and so I guess that you have metalink, maybe this can help:

Recovery of backups tablespace READONLY before an Open RESETLOGS [266991.1 ID]

Werner

ALTER database open resetlog with ora-01666: controlfile is in standby
I have a problem after I have restore / recovered a backup of the source.

On the target, restoration/recovery all finished successfully, but change open resetlog of database with the following errors:

ORA-01666.

My steps are:

(1) make a backup as follows on the source (which is a prod before) complete
Configure controlfile autobackup on;
Configure snapshot controlfile name to ' / oracle_backup/rman/snapf.f'
BACKUP OF DATABASE TAG 'FULL '.
(2) CPC backupsets above the target
(3) in rman, set the dbid as the dbid of source, restored the snapf.f and then added the location.
(4) then restore, recover (everything is fine).
(5) when I alter database open resetlogs, it gives me error ora-01666.
(6) change the database open worked, but the PB is now in sleep mode and readonly.

I checked the settings, the dbname points to the dbname in source and db_unique_name point test on the target name. These two parameters have been reset by RMAN Duplicate.

We do not want a standby db, we need a test copied from the sourc.e environment

How should I proceed from here?

Thank you
Hello again;

And there is the problem, the only file of control is a watch. Compare your this example of mine:
```
BS Key Type LV Size Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
4170117 Full 9.70M DISK 00:00:03 29-NOV-12
        BP Key: 4170119 Status: AVAILABLE Compressed: NO Tag: TAG20121129T125327
        Piece Name: /u01/oradata/RECOVER2_cold/control_RECOVER2_2821_20121129.bak
Control File Included: Ckp SCN: 1307992402301 Ckp time: 29-NOV-12

BS Key Type LV Size Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
4170127 Full 9.73M DISK 00:00:01 29-NOV-12
        BP Key: 4170129 Status: AVAILABLE Compressed: NO Tag: TAG20121129T125332
        Piece Name: /u01/app/oracle/flash_recovery_area/RECOVER2/autobackup/2012_11_29/o1_mf_s_800628756_8chcsf10_.bkp
Control File Included: Ckp SCN: 1307992402301 Ckp time: 29-NOV-12
```
Note the version of ".bak" auto backup and y.

I think you need to take another backup. If you use Oracle 11 I have even more options.

For example, I update my test system using this:

http://www.Visi.com/~mseberg/RMAN/diff_database_duplicating.html

Sometimes I save on users, roles etc and replace later to hide.

Subsequently

You may be able to save what you have by creating a trace on the source file and then use it to re-create a control on the copy file.
```
If you run a backup trace command daily you can probably pull some SQL from your daily trace file like this.

CREATE CONTROLFILE REUSE DATABASE "RECOVER2" NORESETLOGS  NOARCHIVELOG
    MAXLOGFILES 16
    MAXLOGMEMBERS 3
    MAXDATAFILES 100
    MAXINSTANCES 8
    MAXLOGHISTORY 292
LOGFILE
...
...
```
You can save as say cf.sql, then:
```
SQL> startup nomount 

Run the SQL as shown above

SQL> @cf.sql

Control file created.

SQL>

Check the status of the database

SQL> select status from v$instance;

-- should be mounted

If the database is mounted, can it be opened?

Open the database

SQL> alter database open;

Database altered.
```
Best regards

mseberg

Published by: mseberg on November 29, 2012 19:10

After the recovery cannot open database

Source database version: 11.2.0.2 - where, we had done a backup
Target database Version: 11.2.0.1 - where we are restored from the backup.
Restoration and recovery completed successfully, when I tried to open the database with open reset logs I encountered the error below
SQL > alter database open resetlogs;
ALTER database open resetlogs
*
ERROR on line 1:
ORA-01092: ORACLE instance is complete. Disconnection forced
ORA-00704: bootstrap failure process
ORA-39700: database must be opened with the UPGRADE option
Process ID: 18089
Session ID: serial number 43: 29
I tried to upgrade to start and run the region and catproc scripts but no use.
Can someone help me on this, and also, if I am downloading the binary 11202 and their installation on new home and can I try to start the database.
or
I have to completely restore and recover again, to provide as soon as possible, your thoughts!
Thank you, Sai

It seems to me that you would need to downgrade your DB to do this, since you move of 11.2.0.2 to 11.2.0.1.

If possible, you should update your 11.2.0.1 11.2.0.2, re-attempt to restore server.

Date backwards or forward basic restoration after issued resetlogs

Please find my contact details of the environment,
OS: Windows xp
VERSION: Oracle 11.2.0.1.0
Server: Test
Please find my scenario,
Date: June 11
I created a table named table_level0 and then take 0 backup survey
Date: June 12
I created a table named L1_JUNE12 and then took up 1 backup
Date: June 13
I created a table named L1_JUNE13 and then taking backup at level 1.
Date: 14 June
I created a table named L1_JUNE14 and then taken backup of level 1
Date: 14 June
I created a table called L1_JUNE14
and dropped to a table called L1_JUNE14 , then resumed level 1 backup
Restore scenario and my Question based on the error I encountered
I did the restore until 13 June, end of the day, using script, more

Run {}
until ' to_date (13 June 15 23:55 "," mm/dd/yy hh24:mi:ss') ";
restore the database;
recover the database;
}
and restore completed successfully with the prompt message following RMAN
After that, I opened database with the command of "alter database open resetlogs ' (data base has been set based restored time and Redo log also)
media recovery complete, duration: 00:00:06
Finished recover at 15 June 15
RMAN > "exit";

Here's my Question,
Question 1
I assumed that I restored a day in advance, so I want to save my database until June 12, as below.

Run {}
until ' to_date (12 June 15 23:55 "," mm/dd/yy hh24:mi:ss') ";
restore the database;
recover the database;
}
And I am facing the following error,
RMAN > run {}
2 > set up to that time ' to_date (12 June 15 23:55 "," mm/dd/yy hh24:mi:ss') ";
3 > restore database;
4 > restore database;
{5 >}
* Output of RMAN with error
executing command: SET until clause
new incarnation of the registered in the recovery catalog database
from full resynchronization of the recovery catalog
full complete Resync
From restoration to 15 June 15
RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-03002: failure of the restore command to 2015/06/15 18:12:08
RMAN-06004: error ORACLE recovery catalog database: RMAN-20207: until
or WINDOW of RECOVERY, which was before the RESETLOGS
RMAN >
and
Question 2
I decided that I restored and recover the database one day back (13 June) and the need to restore and recover after June 14 and use a script like below,
Run {}
until ' to_date (June 14, 15, 23:55 "," mm/dd/yy hh24:mi:ss') ";
restore the database;
recover the database;
}
* Exit RMAN error *.
RMAN > run {}
2 > set up to that time ' to_date (June 14, 15, 23:55 "," mm/dd/yy hh24:mi:ss') ";
3 > restore database;
4 > restore database;
{5 >}
executing command: SET until clause
From restoration to 15 June 15
RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-03002: failure of the restore command to 2015/06/15 18:17:39
RMAN-06004: error ORACLE recovery catalog database: RMAN-20207: until
or WINDOW of RECOVERY, which was before the RESETLOGS
RMAN >
It is time real work scenario, I was maybe faced with this situation,
So, is it possible to restore and recover based on backdate / date after once performed before restoring.
If it is possible then please give some idea or web link or a script to do this or tell me if it is not possible.

When you open a database with resetlogs, the sequence of newspapers is reset to 1 and online redo logs are given a new time stamp and the SNA. This is done to avoid confusion when two redo different streams have the same SNA, but occurred at different times.

You can restore an old controlfile, before your last resetlog or reset the database to a previous incarnation:

RMAN > list database incarnation

RMAN > reset database to incarnation

Then use your RMAN, run the command "set up time" and restore and recover the database. This will only work well if you have a full backup of the previous incarnation of the database and all archived redo logs until wherever you need to recover.

Open resetlogs

I don't do MFIs: why do I need to open the database after restore with resetlogs option?
According to oracle documentation: RESETLOGS is required after incomplete recovery and recovery using a backup control file.
Backup of the database which I have restored was done in MONTAGE mode, with:
Run {}
bootable media;
backup database;
backup current controlfile;
}
and now, I restored from the backupSet on another server of d.b.:
startup nomount;
RMAN:
Restore controlfile from "C-1072137799-20140214-00';
change the editing of the database;
restore the database;
and now:
ALTER DATABASE OPEN;
ORA-01610: recovery using the BACKUP CONTROLFILE option maust be made.
Why the recovery, if the backup was performed in MOUNT open not mode?
Thank you to

Assuming that you did a full backup (cold) a horse of database on 01 - Feb.

Assuming that you have the database in ArchiveLog mode and have generated some ArchiveLogs 01 - Feb 12 - Feb.

OR that he had transactions from the backup 01 - Feb and all transactions are always in newspapers in line again, even if the database is in NOARCHIVELOG mode. (It could have been a single transaction update of a single line in a tablespace user or in the data dictionary, OR there could be 1 million transactions).

Assuming that you RESTORE the backup 01 - Feb 13 - Feb.

Now, how Oracle knows that you want to apply redo generated since 01 - Feb? Your subsequent recovery can be online Redo Logs, it might be in ArchiveLogs.

Oracle would be happy to see a command 'RECOVER the NOREDO DATABASE' of the DBA to confirm that no. redo must be applied.

Newspapers to online that you may or may not present MUST be initialized before opening the database because they do not conform to the image of the database that you have restored and recovered. Therefore, an OPEN RESETLOGS must be issued.

If you have no online Redo Logs, an OPEN RESETLOGS is required to recreate.

Hemant K Collette

Backup recovery cold - open alter datbase omitting - going in circles
Well, I have the following situation
* Virtual Linux opensuse server using Oracle VM
* Oracle 11 g

From a customer in Singapore, I am in Belgium, we received a cold backup of one of their databases to be transformed in MS SQL Server

After a bit of research and in communicating with our customer, I know that the database is named orcl and the user's Oracle

Suite [how to and recover from a cold backup | http://thetendjee.wordpress.com/2007/08/29/how-to-perform-and-recover-from-a-cold-backup/].
I did the following steps
I created the following folders
/Home/Oracle/product/10.1.0/oradata/ORCL/
and put the files into it.

I have 3 (control01, control02, control03), controlfiles 3 redo files (redo01, redo02, redo03), sysaux01, system01, temp01, temp02, undotbs01, users01.
I created an initorcl.ora file and put it in /opt/oracle/product/10.2/db_1/dbs/
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
* .db_name = "orcl".
* full = '11.2.0.0.0'
* .control_files = ('/ home/oracle/produit/10.1.0/oradata/orcl/control01.ctl ',)
Home/Oracle/product/10.1.0/oradata/ORCL/control02.ctl','/home/Oracle/product/10.1.0/oradata/ORCL/control03.CTL ')
* .undo_tablespace = "UNDOTBS1.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

I then open terminal and use the sqlplus / as sysdba command
Bootable media;

The database is correctly mounted and then proceed to the opening of the database
ALTER database open;
ORA-01589: must use RESETLOGS or NORESETLOGS option of database open
ORA-1589 marked during: alter database open...

ALTER database open resetlogs; (noresetlogs resulted in the previous error saying resetlogs must be used)
ERROR on line 1:
ORA-01113: file 1 needs media recovery
ORA-01110: datafile 1:'/home/oracle/product/10.1.0/oradata/orcl/SYSTEM01.dbf'

Recover datafile ' / home/oracle/product/10.1.0/oradata/orcl/SYSTEM01.dbf'
What resulted
ORA-00283: cool cancelled due to errors
ORA-01610: recovery using BACKUP CONTROLFILE option must be

Select * v log$
show me journal 1 is underway

recover database using backup controlfile
Specify the log: {< RET > = suggested |} Filename | AUTO | CANCEL}
/Home/Oracle/10.1.0/oradata/ORCL/redo01.log
Application log.
Complete media recovery.

ALTER database open resetlogs;

Error resulting
ALTER database open resetlogs
*
ERROR on line 1:
ORA-01092: ORACLE instance is complete. Disconnection forced
ORA-00704: bootstrap failure process
ORA-39700: database must be opened with the UPGRADE option
Process ID: 23420
Series ID:16 series number: 3

I'm always looking in, but any help to refine the problem/solution would be useful.

Edited by: Resender on 26-mei-2011 01:50
SLES is Novell

Open resetlogs duplicate

Hello world

Under manual oracle, duplicate command must make 'open resetlogs' implicitly.
I just issued "backup database more archivelog ' and copied across all backupsets. However, oracle is not open database with resetlogs open and always awaiting archivelogs.
No 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

A day later, I ran the same command using the 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

When you duplicate the database its looking for the last archivelog generated, its not get it and failing. recover your database using the until the command until you have available archives journal. After that, open your database in the mode resetlog.

"alter database open resetlogs ' not reset one of the data files
I spent the last few weeks and a half, three years recovery of an oracle database (linux 64-bit of 11g) due to a block corrupted in a newspaper online redo (I thought was written at multiple locations). I have restored the files, some of them around displacement in the process; recovered on the last possible point; files moved to their location; has ran "alter database open resetlogs; and one of the files of data (from a bigfile tablespace) does not reset itself. I checked afterwards, and it has been marked offline. I do not remember placing the file in offline mode and can not find such a statement in my last orders 300 sqlplus, that includes orders while I renamed this file and the controls surrounding rename it.

Restore/recovery of the new database will take too long and is a remarkably low option. Even if the database was opened correctly, the affected tablespace not would have been addressed in two or three minutes, that the database has been opened. Is it possible to force the oracle again reset newspapers or the difficulty, otherwise this one file to mark with the same date? Allowing only to the resetlogs option after incomplete recovery seems a poor restriction, in particular, if files gliding through like that. I suspect there is a way to simply set the values of control point for the tablespace, but I don't know where to start. This particular file is < 5% of the database, so if I do a sort of backup/restore with all this, it's probably doable.
Thank you for the necessary information, the image would have been much clearer if you would have posted this initially. There was nothing wrong in procedures that you applied.

Unfortunately, it seems you hit a bug, the command to reset everything... is alter database open resetlogs, and there is no other command.
So, Yes, you must go to this door that says more
'Ogni speranza, voi che entrate leave fare' (leave all hope behind you, you happening. It is the inscription of Hades, the underworld, the Monteverdi's Opera "Orfeo"). This gate is called "My Oracle Support" and if your problem will be solved, who knows.
I don't think that this is a generic problem however, or we would have known, so it's probably still a few 64-bit partner. These days at Oracle quality assurance procedures seems to leave much to be desired.
If all goes well, they will be able to reproduce your problem.
Good luck on your trip across the river Styx!
Although they will probably want to upgrade you to 11.1.0.7
------------
Sybrand Bakker
Senior Oracle DBA

use the old backup RMAN after OPEN RESTLOGS
Hello
in 10g R2, we can use the backups made before one:
```
ALTER DATABASE OPEN RESETLOGS 
```
Thank you.
Salvation;
In 10g, yes you can, click on the link:
http://emrebaransel.blogspot.com/2009/01/performing-recovery-after-RESETLOGS.html

Protection of data error: no active Managed Standby recovery
Hi all
I have a strange problem. Right now I have 2 primary node RAC on Windows and another 2 RAC standby node (physical standby) also on Windows 2003 (R2). I've done a few time to spend waiting for redo apply read-only with no problems. Today, I tried the switch and he kept giving me the error as follows:

SQL > alter database recover managed standby database disconnect;

Database altered.

SQL > alter database recover managed standby database cancel;
ALTER database recover managed standby database cancel
*
ERROR on line 1:
ORA-16136: Managed Standby Recovery non-active

I also check the logs broker and archiving of guard data and all seems fine. All recovery logs are applied to standby mode. At the same time, the recovery of database alter managed declaration, standby database cancel works, but the open next alter database statement crashed to the instance.

Any suggestions?
Another instance is resumed by chance?

This will automatically launch after restart of the mount if you activate dataguard broker configuration and instance to apply may not be one where you connect to with sqlplus.

Try to look at the alert logs of bodies and gv$ managed_standby

ORA-01547: WARNING: RECOVER succeeded but OPEN RESETLOGS would get below error

Dear all,
While making RMAN cloning we get the error in the trace as file
Trace file E:\ORACLE\TESTDB\11.2.0\ADMIN\TEST_TESTDB\diag\rdbms\hrdev\test\trace\test_pr00_3980.trc
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - Production
With partitioning, OLAP, Data Mining and Real Application Testing options
Windows Server 2003 V5.2 Service Pack 2 Version
CPU: 2 - type 586, 2 physical cores
Process affinity: 0 x 0 x 00000000
Memory (success/Total): Ph: 15587 M / 16383 M, Ph + FCP: 32981 M / 34549 M, GOES: 708 M / 2047 M
Instance name: hrdev
Redo thread mounted by this instance: 1
Oracle process number: 20
Windows thread ID: 3980, image: ORACLE. EXE (PR00)
2015-07-03 18:30:47.577
Has started the recovery of parallel media
2015-07-03 18:30:47.983
Dumping table incarnation of database:
RESETLOGS 0 Yvert and time: 0x0003.660c2a42 01/09/2014 19:37:43
Incarnation of recovery target = 2, = 0 activation ID
The flow buffer limit = 37200 min (50% x 74400, 100000)
Start the recovery to the thread 1 ckpt SNA 15900955092 logseq 2726 block 469796
Initial size of the buffers: read 1024K, 832K overflow, change 805K
2015-07-03 18:30:48.030
Add a Media Recovery redo thread 1
2015-07-03 18:30:48.827
Fall of Media Recovery redo thread 1
DDE: Key problem "ORA 1110' was the controlled flood (0 x 1) (incident)
ORA-01110: data file 1: ' F:\ORACLE\TESTDATA\SYSTEM01. DBF'
2015-07-03 18:30:49.405
Completed media recovery
ORA-01547: WARNING: RECOVER succeeded but OPEN RESETLOGS would get below error
ORA-01194: file 1 needs a recovery more match
ORA-01110: data file 1: ' F:\ORACLE\TESTDATA\SYSTEM01. DBF'
Concerning
Villi Kumar

Dear all,

We have fixed this problem.

Solution:

E:\oracle\testdb\11.2.0>sqlplus sys as sysdba

SQL * more: Production of liberation 11.2.0.3.0 Fri Jul 3 19:00:20 2015

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

Enter the password:

Connected to:

Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - Production

With partitioning, OLAP, Data Mining and Real Application Testing options

SQL >

SQL > RECOVER DATABASE UNTIL CANCEL USING BACKUP CONTROLFILE;

ORA-00279: change 15900955092 generated at 02/07/2015 17:30:06 to

thread 1

ORA-00289: suggestion:

E:\ORACLE\TESTDB\11.2.0\RDBMS\ARC0000002726_0836422663.0001

ORA-00280: change 15900955092 thread 1 is in sequence #2726

Specify the log: {= suggested |} Filename | AUTO | CANCEL}

F:\oracle\arch\TEST\ARC0000002726_0836422663.0001

ORA-00279: change 15900962042 generated at 02/07/2015 18:30:06 to

thread 1

ORA-00289: suggestion:

E:\ORACLE\TESTDB\11.2.0\RDBMS\ARC0000002727_0836422663.0001

ORA-00280: change 15900962042 thread 1 is in sequence #2727

ORA-00278: save the file 'F:\oracle\arch\TEST\ARC0000002726_0836422663.0001' not

longer needed for recovery

Specify the log: {= suggested |} Filename | AUTO | CANCEL}

F:\oracle\arch\TEST\ARC0000002727_0836422663.0001

ORA-00279: change 15900962052 generated at 02/07/2015 18:30:16 needed to

thread 1

ORA-00289: suggestion:

E:\ORACLE\TESTDB\11.2.0\RDBMS\ARC0000002728_0836422663.0001

ORA-00280: change 15900962052 thread 1 is in sequence #2728

ORA-00278: save the file 'F:\oracle\arch\TEST\ARC0000002727_0836422663.0001' not

longer needed for recovery

Specify the log: {= suggested |} Filename | AUTO | CANCEL}

F:\oracle\arch\TEST\ARC0000002728_0836422663.0001

ORA-00279: change 15901106577 generated at 03/07/2015 06:23:19 needed to

thread 1

ORA-00289: suggestion:

E:\ORACLE\TESTDB\11.2.0\RDBMS\ARC0000002729_0836422663.0001

ORA-00280: change 15901106577 thread 1 is in sequence #2729

ORA-00278: save the file 'F:\oracle\arch\TEST\ARC0000002728_0836422663.0001' not

longer needed for recovery

Specify the log: {= suggested |} Filename | AUTO | CANCEL}

F:\oracle\arch\TEST\ARC0000002729_0836422663.0001

ORA-00279: change 15901247230 generated at 03/07/2015 06:33:53 required for

thread 1

ORA-00289: suggestion:

E:\ORACLE\TESTDB\11.2.0\RDBMS\ARC0000002730_0836422663.0001

ORA-00280: change 15901247230 thread 1 is in sequence #2730

ORA-00278: save the file 'F:\oracle\arch\TEST\ARC0000002729_0836422663.0001' not

longer needed for recovery

Specify the log: {= suggested |} Filename | AUTO | CANCEL}

F:\oracle\arch\TEST\ARC0000002730_0836422663.0001

ORA-00279: change 15901413113 generated at 03/07/2015 06:45:53 required for

thread 1

ORA-00289: suggestion:

E:\ORACLE\TESTDB\11.2.0\RDBMS\ARC0000002731_0836422663.0001

ORA-00280: change 15901413113 thread 1 is in sequence #2731

ORA-00278: save the file 'F:\oracle\arch\TEST\ARC0000002730_0836422663.0001' not

longer needed for recovery

Specify the log: {= suggested |} Filename | AUTO | CANCEL}

F:\oracle\arch\TEST\ARC0000002731_0836422663.0001

ORA-00279: change 15901578404 generated at 03/07/2015 06:56:49 to

thread 1

ORA-00289: suggestion:

E:\ORACLE\TESTDB\11.2.0\RDBMS\ARC0000002732_0836422663.0001

ORA-00280: change 15901578404 thread 1 is in sequence #2732

ORA-00278: save the file 'F:\oracle\arch\TEST\ARC0000002731_0836422663.0001' not

longer needed for recovery

Specify the log: {= suggested |} Filename | AUTO | CANCEL}

F:\oracle\arch\TEST\ARC0000002732_0836422663.0001

ORA-00279: change 15901715991 generated at 03/07/2015 07:05:32 needed to

thread 1

ORA-00289: suggestion:

E:\ORACLE\TESTDB\11.2.0\RDBMS\ARC0000002733_0836422663.0001

ORA-00280: change 15901715991 thread 1 is in sequence #2733

ORA-00278: save the file 'F:\oracle\arch\TEST\ARC0000002732_0836422663.0001' not

longer needed for recovery

Specify the log: {= suggested |} Filename | AUTO | CANCEL}

Cancel

SQL > alter database open resetlogs;

Concerning

Villi Kumar

Open resetlogs does not work when creating clone db with online backup
Hi all

I am trying to create a clone database using a database hot backup.

STEPS I FOLLOWED
------------------------------------

LET-> CURRENT_DB NAME = DEV
DATABASE NAME = DEVCLONE CLONE

FORM DEV DB steps
-----------------------------------------------
-put the database in backup mode using 'alter database begin backup'
-Copy all data files to a different folder
-for the copy, I carried a few operations on the DB (creating users, tables, LMD etc...)
-between the copy, I did also order journal
-at the end of the copy, "alter database end backup.
-created a backup control file in a human-readable format (alter database backup controlfile to trace under...)

steps to clone side DB ((DEVCLONE)
-------------------------------------------------------------------
-created a setting for the database file.
-changed the backup control file, so that it indicates the location of the datafiles copied destination
-set the ORACLE_SID
- then "sqlplus / as sysdba"
-starup nomount
-Run the file updated control (created a control file for database clone)
-recover the database using 'recover database using backup controlfile'
I have provided the files to archive that he was asking for (the archive that has been generated in DEV DB logs)
then I cancelled the recovery by typing 'Cancel '.
-recover database using backup controlfile until cancel;
then typed "Cancel".
-then try to open the database with resetlogs open but it showed error below

ALTER database open resetlogs
*
ERROR on line 1:
ORA-01195: online backup of file 1 needs a recovery more match
ORA-01110: data file 1: ' D:\DATA_GUARD\DEVHOT\SYSTEM01. DBF'

Please help me on this...

Thank you
When the database is in BACKUP mode, it is still actively updated, only the data file headers are frozen.
The data files are all "blurred".
To resynchronize the, you can all do it again that was generated during the BACKUP mode - so the generated archivelogs while in BACKUP mode at least the first captured archivelog BACKUP of the END (and release of the datafile headers) is required.

Hemant K Collette

Issue of OPEN RESETLOGS
So I have a database that is replicated (via the stream) which seems to have go haywire in terms of amount of recovery archive, that he was creating. We ran out of space FRA, so I have everything we had left then canceled the affected waterways. The database is then consumed about 10 GB of recovery archived per hour until I've performed a SHUTDOWN ABORT. At the start, he continued to use FRA space for several hours. All has calmed down now, but now I don't have enough space to run the RMAN backup.

Really well, this database is a replica of the master. So I would like to do away with the existing archived redo, take a gentle RMAN backup and starts with a new incarnation of the database. I thought about stopping the database, removing all backupsets and archived redo in the FRA, then opening the database with resetlogs. But it seems that you can only make without recovering the database first. I've seen some articles that I can use RECOVER until CANCEL and will take me by a current state (which anyway, it must be current because the stream is disabled), then ALTER DATABASE OPEN RESETLOGS will work.

Is this the best approach? 10 gr 2.
Thank you
-= Chuck
You need not open RESETLOGS. You only remove the archivelogs and old backupsets and run REMOVE EXPIRES and OVERLAP in RMAN so that the database is aware that they are deleted.

Hemant K Collette

Restore, recover the backup hot inevitably will be OPEN RESETLOGS
DB version: 11.2
Platform: Solaris / AIX

Cold backup is performed when the DB is in editing mode, and when no recovery is generated during the backup.
So when you restore this backup, you can open the database with
```
alter database open;
```
But when we take the backup hot of a DB, we will never be able to redo backup generated in restoration online logs when the hot backup. Thus, during recovery, we can apply only archived redo logs from the source DB and we are obliged to skip applying entries online to the DB of the Source again.
Thus, hot backup recovery will inevitably end up by in OPEN RESETLOGS.
```
alter database open resetlogs
```
These assumptions are good?
If you restore and recover to the same server with the current controlfile and remake online still present newspapers, you would be able to make a full recovery. In such a case it is not necessary to OPEN RESETLOGS.
All other cases of hot backup are incomplete recoveries and require an OPEN RESETLOGS.

In the case of a cold backup taken by RMAN, you should always an OPEN RESETLOGS because RMAN does not include online of Redo Log files.
http://hemantoracledba.blogspot.com/2008/05/RMAN-cold-consistent-backup-and-restore.html

Hemant K Collette

Standby recovery after open Resetlogs

Similar Questions

Maybe you are looking for