Recover Database vrs Recover Tablespace & Datafile
Traditionally when I have been recovering a database either to point of failure or point in time I have issued
RECOVER DATABASE AUTO;
(or I have specified the point in time I wish to recover to ).
I see now in 11gR2 there is also a RECOVER TABLESPACE and a RECOVER DATAFILE command
Why would you use those instead of the RECOVER DATABASE ? You would have to be pretty sure it is only that tablespace or data file you wanted to apply archive logs to, otherwise would your recovery not risk putting the contents of that tablespace or datafile out of logical sync with the data in other tablespaces ( eg potentially viloating referential integrity etc ) ?
I am presuming these commands also only apply the contents of archive logs that effect the specified tablespace or datafile ?
thanks,
Jim
If I issue a RECOVER TABLESPACE or RECOVER DATAFILE for a Tablespace or Datafile that is current and does not need recovery, Oracle does nothing to the Tablespace / Datafile. It won't be out of logical sync with the rest of the database.
>>>
Can you recover the data file or the tablespace to a point in time before the current time ? If that is the case then surely it is possible that the recovered tablespace could have a table in it that has referential integrity to another table in a different ( unrecovered ) tablespace and that the referential integrity could then be compromised ?
Jim
Similar Messages
-
Recover Database in RMAN vs SQL*PLUS
Hello,
Oracle 11.2.0.1, Oracle Linux 5.5 UEK.
I recently did a "recover database" in sql*plus, but an attempt to open the database gave ORA-01113, complaining the system tablespace requried more recovery. Then I used RMAN (nocatalog) and after the same "recover database" command I was able to open the database.
It seems there are differences between SQL*PLUS and RMAN "recover database" command. I have not been able to locate the chapter in the Oracle documentation that explains the difference. I have some ideas, but...
Thanks.
h3. Solution Summary:
The recover command in RMAN compared to SQL*Plus implements a more user friendly processing logic based on the current detected scenario. For instance, a RMAN recover database command may actually perform a "recover database using backup controlfile until cancel" and automatically apply all archived and online redo logs if available. The same can be achieved with the recover command in SQL*plus, but will have to be done manually.
Edited by: Dude on Jan 7, 2011 12:30 PMDude wrote:
I did not remove any datafiles or redo logs. it is the same restore operation as before, and again RMAN "recovery database" succeeds, whereas SQL recover has trouble. This tells me something is different between the two methods. For one, RMAN does not requrie to specify "using backup controlfile".
Maybe someting about "resetlogs" that that RMAN recover can handle and SQL recover not?No,problem is there.If you using rman execute RECOVER DATABASE it also will apply online logs(if available) also and as result you will get complete recovery however you must open database with resetlogs option due to you recovered database using backup controlfile.So also you can recover and open database applying this online logs.After executing RECOVER DATABASE USING BACKUP CONTROLFILE you have to pass full path of online log then press ENTER so log will apply and you can open database with RESETLOGS.See below
C:\Documents and Settings\chinar>rman target sys/sm
Recovery Manager: Release 10.2.0.1.0 - Production on Fri Jan 7 17:47:49 2011
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database (not started)
RMAN> startup nomount;
Oracle instance started
Total System Global Area 138412032 bytes
Fixed Size 1247708 bytes
Variable Size 71304740 bytes
Database Buffers 58720256 bytes
Redo Buffers 7139328 bytes
RMAN> restore controlfile from 'D:\oracle\product\10.2.0\flash_recovery_area\T\B
ACKUPSET\2011_01_07\O1_MF_NCSNF_TAG20110107T171001_6LG48JR5_.BKP'
2> ;
Starting restore at 07-JAN-11
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=157 devtype=DISK
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:03
output filename=D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\CONTROL01.CTL
output filename=D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\CONTROL02.CTL
output filename=D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\CONTROL03.CTL
Finished restore at 07-JAN-11
RMAN> alter database mount;
database mounted
released channel: ORA_DISK_1
RMAN> restore database;
Starting restore at 07-JAN-11
Starting implicit crosscheck backup at 07-JAN-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
Crosschecked 1 objects
Finished implicit crosscheck backup at 07-JAN-11
Starting implicit crosscheck copy at 07-JAN-11
using channel ORA_DISK_1
Finished implicit crosscheck copy at 07-JAN-11
searching for all files in the recovery area
cataloging files...
cataloging done
List of Cataloged Files
=======================
File Name: D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\T\BACKUPSET\2011_01_07\O
1_MF_NCSNF_TAG20110107T171001_6LG48JR5_.BKP
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 D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\SYSTEM01.DBF
restoring datafile 00002 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\UNDOTBS01.DBF
restoring datafile 00003 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\SYSAUX01.DBF
restoring datafile 00004 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\USERS01.DBF
channel ORA_DISK_1: reading from backup piece D:\ORACLE\PRODUCT\10.2.0\FLASH_REC
OVERY_AREA\T\BACKUPSET\2011_01_07\O1_MF_NNNDF_TAG20110107T171001_6LG45BXS_.BKP
channel ORA_DISK_1: restored backup piece 1
piece handle=D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\T\BACKUPSET\2011_01_07
\O1_MF_NNNDF_TAG20110107T171001_6LG45BXS_.BKP tag=TAG20110107T171001
channel ORA_DISK_1: restore complete, elapsed time: 00:01:04
Finished restore at 07-JAN-11
RMAN> recover database;
Starting recover at 07-JAN-11
using channel ORA_DISK_1
starting media recovery
archive log thread 1 sequence 7 is already on disk as file D:\ORACLE\PRODUCT\10.
2.0\ORADATA\T\REDO02.LOG
archive log filename=D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\REDO02.LOG thread=1 sequ
ence=7
media recovery complete, elapsed time: 00:00:03
Finished recover at 07-JAN-11
RMAN> exit
Recovery Manager complete.
C:\Documents and Settings\chinar>sqlplus sys/sm as sysdba
SQL*Plus: Release 10.2.0.1.0 - Production on Fri Jan 7 17:51:31 2011
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
SQL> alter database open;
alter database open
ERROR at line 1:
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
SQL> alter database open resetlogs;
Database altered.
SQL> And above you see lines as
archive log thread 1 sequence 7 is already on disk as file D:\ORACLE\PRODUCT\10.
*2.0\ORADATA\T\REDO02.LOG*
archive log filename=D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\REDO02.LOG thread=1 sequ
ence=7
It means RMAN apply these.So you can apply these using SQLPLUS ALSO.In additionally you can see that from alert log as
alter database recover if needed
start until cancel using backup controlfile
Media Recovery Start
parallel recovery started with 2 processes
ORA-279 signalled during: alter database recover if needed
start until cancel using backup controlfile
Fri Jan 07 17:50:34 2011
alter database recover logfile 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\REDO02.LOG'
Fri Jan 07 17:50:34 2011
Media Recovery Log D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\REDO02.LOG
Fri Jan 07 17:50:34 2011
Incomplete recovery applied all redo ever generated.
Recovery completed through change 665263
Completed: alter database recover logfile 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\REDO02.LOG'And finally you see clearly that even if you execute RECOVER DATABASE from RMAN it actually execute RECOVER DATABASE UNTIL CANCEL USING BACKUP CONTROLFILE (from alert.log start until cancel using backup controlfile)
And these is not any difference.
Hope that help you and you got answer. -
Hi,
I am trying to recover my Oracle 9i v9.2.0.4 database running on Solaris 9 (sparc). Database is in archived log mode and RMAN is also used to perform incremental and full backups.
My database died with an internal error and so far I can restore it from within RMAN with no problem. When I execute "Recover database", I see the following:
RMAN> recover database;
Starting recover at 12-APR-04
using channel ORA_DISK_1
using channel ORA_DISK_2
channel ORA_DISK_1: starting incremental datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
destination for restore of datafile 00003: /ora02/app/oracle/oradata/sunesdb/cwmlite01.dbf
destination for restore of datafile 00005: /ora02/app/oracle/oradata/sunesdb/example01.dbf
destination for restore of datafile 00006: /ora02/app/oracle/oradata/sunesdb/indx01.dbf
destination for restore of datafile 00010: /ora02/app/oracle/oradata/sunesdb/xdb01.dbf
channel ORA_DISK_2: starting incremental datafile backupset restore
channel ORA_DISK_2: specifying datafile(s) to restore from backup set destination for restore of datafile 00001: /ora02/app/oracle/oradata/sunesdb/system01.dbf
destination for restore of datafile 00008: /ora02/app/oracle/oradata/sunesdb/tools01.dbf
channel ORA_DISK_1: restored backup piece 1
piece handle=/ora_backup/ora_df522977420_s309_s1 tag=TAG20040408T233019 params=NULL
channel ORA_DISK_1: restore complete
channel ORA_DISK_2: restored backup piece 1
piece handle=/ora_backup/ora_df522977515_s311_s1 tag=TAG20040408T233019 params=NULL
channel ORA_DISK_2: restore complete
channel ORA_DISK_1: starting incremental datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
destination for restore of datafile 00002: /ora02/app/oracle/oradata/sunesdb/undotbs01.dbf
destination for restore of datafile 00004: /ora02/app/oracle/oradata/sunesdb/drsys01.dbf
destination for restore of datafile 00007: /ora02/app/oracle/oradata/sunesdb/odm01.dbf
destination for restore of datafile 00009: /ora02/app/oracle/oradata/sunesdb/users01.dbf
channel ORA_DISK_1: restored backup piece 1
piece handle=/ora_backup/ora_df522977420_s310_s1 tag=TAG20040408T233019 params=NULL
channel ORA_DISK_1: restore complete
starting media recovery
media recovery failed
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 04/12/2004 17:10:44
ORA-00283: recovery session canceled due to errors
RMAN-11003: failure during parse/execution of SQL statement: alter database recover if needed start
ORA-00283: recovery session canceled due to errors
ORA-00600: internal error code, arguments: [3020], [8388729], [1], [154], [167160], [16
ORA-10567: Redo is inconsistent with data block (file# 2, block# 121)
ORA-10564: tablespace UNDOTBS1
ORA-01110: data file 2: '/ora02/app/oracle/oradata/sunesdb/undotbs01.dbf'
ORA-10560: block type 'KTU SMU HEADER BLOCK'
RMAN>
I also tried to restore and recover to 08-Apr-04, the day before it crashed. This can be done successfully but I still cannot open the database.
The error says I need to used RESETLOGS or NORESETLOGS. I followed but the database still refused to open.
What should I do to get the database back online? I am not DBA trained and hence kindly list me the steps to follow.
Is it possible to start without the undotsb01.dbf and then rebuild it? What would I lose by doing this? Any alternatives?
Thank you very much!Bad news.. I forgot to turn off my cron jobs last night and it seems that my backups were overwritten. I cannot restore back to 08-APR-04 as it reported RMAN-06023: no backup or copy of datafile found to restore.
Any way to resolve the undotsb01.dbf problem so that I can startup my database again? -
Unable to recover database after rman recovery and database open resetlogs
I am running Oracle 10.2.0.5 on OpenSUSE 9. I have been trying to upgrade the database to 11g, through dbua. I was getting stuck at one point during the Oracle Server install and the upgrade failed and I was forced to restore the database to an earlier backup.
Below is the current place that I am stuck. As you can see I opened the database multiple times and reset the logs. Now I am afraid that my controlfile and redo log backups are out of sync and i can't get them back on track. Before when I actually got the database recovered RMAN would immediately throw:
RMAN-06900: WARNING: unable to generate V$RMAN_STATUS or V$RMAN_OUTPUT row
RMAN-06901: WARNING: disabling update of the V$RMAN_STATUS and V$RMAN_OUTPUT rows
OPA-00600: ORA-00600: internal error code, arguments: ...
The database would open with ALTER DATABASE RESETLOGS but any query on non-system tables would fail and throw:
ORA-04045: errors during recompilation/revalidation of LCRS_DEV1.FACILITY_REF
ORA-00600: internal error code, arguments: [17069], [0x1158ED180], [], [], [],
I hope I have not dug myself into too deep of a hole here.
Here is the trace from my most recent attempt.
RMAN> startup nomount;
connected to target database (not started)
Oracle instance started
Total System Global Area 3070230528 bytes
Fixed Size 2099424 bytes
Variable Size 301991712 bytes
Database Buffers 2751463424 bytes
Redo Buffers 14675968 bytes
RMAN> list incarnation of database;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of list command at 08/02/2011 15:49:04
ORA-01507: database not mounted
RMAN> restore controlfile from autobackup;
Starting restore at 02-AUG-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
recovery area destination: /opt/oracle/flash_recovery_area
database name (or database unique name) used for search: LCRSDEV
channel ORA_DISK_1: autobackup found in the recovery area
channel ORA_DISK_1: autobackup found: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758129928_73jr2s7p_.bkp
channel ORA_DISK_1: control file restore from autobackup complete
output filename=/opt/oracle/oradata/LCRSDEV/control01.ctl
output filename=/opt/oracle/oradata/LCRSDEV/control02.ctl
output filename=/opt/oracle/oradata/LCRSDEV/control03.ctl
Finished restore at 02-AUG-11
RMAN> alter database mount;
database mounted
released channel: ORA_DISK_1
RMAN> list incarnation of database;
List of Database Incarnations
DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
1 1 LCRSDEV 756543625 PARENT 1 22-OCT-05
2 2 LCRSDEV 756543625 PARENT 525876 20-JAN-11
3 3 LCRSDEV 756543625 PARENT 92348137 18-JUL-11
4 4 LCRSDEV 756543625 PARENT 95654931 01-AUG-11
5 5 LCRSDEV 756543625 PARENT 95675699 01-AUG-11
6 6 LCRSDEV 756543625 PARENT 95676699 02-AUG-11
7 7 LCRSDEV 756543625 PARENT 95676700 02-AUG-11
8 8 LCRSDEV 756543625 CURRENT 95676701 02-AUG-11
RMAN> restore database until scn 95676700;
Starting restore at 02-AUG-11
Starting implicit crosscheck backup at 02-AUG-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
Crosschecked 6 objects
Finished implicit crosscheck backup at 02-AUG-11
Starting implicit crosscheck copy at 02-AUG-11
using channel ORA_DISK_1
Finished implicit crosscheck copy at 02-AUG-11
searching for all files in the recovery area
cataloging files...
cataloging done
List of Cataloged Files
=======================
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758129928_73jr2s7p_.bkp
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 08/02/2011 15:52:04
RMAN-20208: UNTIL CHANGE is before RESETLOGS change
RMAN> restore database;
Starting restore at 02-AUG-11
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to /opt/oracle/oradata/LCRSDEV/system01.dbf
restoring datafile 00002 to /opt/oracle/oradata/LCRSDEV/undotbs01.dbf
restoring datafile 00003 to /opt/oracle/oradata/LCRSDEV/sysaux01.dbf
restoring datafile 00004 to /opt/oracle/oradata/LCRSDEV/users01.dbf
restoring datafile 00005 to /opt/oracle/oradata/LCRSDEV/LCRS_TBS.dbf
channel ORA_DISK_1: reading from backup piece /opt/oracle/flash_recovery_area/LCRSDEV/backupset/2011_07_22/o1_mf_nnndf_TAG20110722T111922_72m8rc5x_.bkp
channel ORA_DISK_1: restored backup piece 1
piece handle=/opt/oracle/flash_recovery_area/LCRSDEV/backupset/2011_07_22/o1_mf_nnndf_TAG20110722T111922_72m8rc5x_.bkp tag=TAG20110722T111922
channel ORA_DISK_1: restore complete, elapsed time: 00:23:36
Finished restore at 02-AUG-11
RMAN> recover database until scn 95676700;
Starting recover at 02-AUG-11
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 08/02/2011 16:16:28
RMAN-20208: UNTIL CHANGE is before RESETLOGS change
RMAN> recover database;
Starting recover at 02-AUG-11
using channel ORA_DISK_1
starting media recovery
archive log thread 1 sequence 90 is already on disk as file /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_90_72ml85v3_.arc
archive log filename=/opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73jr20qc_.arc thread=1 sequence=1
unable to find archive log
archive log thread=1 sequence=1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 08/02/2011 16:25:04
RMAN-06054: media recovery requesting unknown log: thread 1 seq 1 lowscn 95676701Thanks for the reply Hemant. I have reset the database for the controlfile that I am using as backup and now I am not able to recover until the correct SCN. I am thinking that my recovery catalog is bad. If I mount with the current controlfile I have this list of incarnations:
List of Database Incarnations
DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
*1 1 LCRSDEV 756543625 PARENT 1 22-OCT-05*
*2 2 LCRSDEV 756543625 PARENT 525876 20-JAN-11*
*3 3 LCRSDEV 756543625 PARENT 92348137 18-JUL-11*
*4 4 LCRSDEV 756543625 PARENT 95654931 01-AUG-11*
*5 5 LCRSDEV 756543625 PARENT 95675699 01-AUG-11*
*6 6 LCRSDEV 756543625 PARENT 95676699 02-AUG-11*
*7 7 LCRSDEV 756543625 PARENT 95676700 02-AUG-11*
*8 8 LCRSDEV 756543625 PARENT 95676701 02-AUG-11*
*9 9 LCRSDEV 756543625 CURRENT 95676702 02-AUG-11*
However if I restore the controlfile to the earlier version I am getting the following output from the process:
RMAN> startup nomount;
connected to target database (not started)
Oracle instance started
Total System Global Area 3070230528 bytes
Fixed Size 2099424 bytes
Variable Size 301991712 bytes
Database Buffers 2751463424 bytes
Redo Buffers 14675968 bytes
RMAN> restore controlfile from '/opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_07_22/o1_mf_s_757164997_72m9rqw3_.bkp';
Starting restore at 03-AUG-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:03
output filename=/opt/oracle/oradata/LCRSDEV/control01.ctl
output filename=/opt/oracle/oradata/LCRSDEV/control02.ctl
output filename=/opt/oracle/oradata/LCRSDEV/control03.ctl
Finished restore at 03-AUG-11
RMAN> alter database mount;
database mounted
released channel: ORA_DISK_1
RMAN> list incarnation of database;
List of Database Incarnations
DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
1 1 LCRSDEV 756543625 PARENT 1 22-OCT-05
2 2 LCRSDEV 756543625 PARENT 525876 20-JAN-11
3 3 LCRSDEV 756543625 CURRENT 92348137 18-JUL-11
RMAN> restore database until scn 92348137;
Starting restore at 03-AUG-11
Starting implicit crosscheck backup at 03-AUG-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
Crosschecked 1 objects
Finished implicit crosscheck backup at 03-AUG-11
Starting implicit crosscheck copy at 03-AUG-11
using channel ORA_DISK_1
Finished implicit crosscheck copy at 03-AUG-11
searching for all files in the recovery area
cataloging files...
cataloging done
List of Cataloged Files
=======================
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_01/o1_mf_1_1_73g3hn6o_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_01/o1_mf_1_2_73g3hnxq_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_01/o1_mf_1_1_73g0rts6_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_134_72v9gv4s_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_138_72v9p4b4_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_120_72v8wwg0_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_121_72v8x5ty_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_131_72v9cnrv_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_139_72v9q5ok_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_137_72v9n4t5_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_136_72v9l88q_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_123_72v8ytm8_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_132_72v9dcxd_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_124_72v8zkg0_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_128_72v96qm1_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_135_72v9jqmx_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_129_72v98q3r_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_125_72v91g3b_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_118_72v8v8r4_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_127_72v9626w_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_130_72v9bqtb_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_141_72vncy6g_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_122_72v8ycd4_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_126_72v94cns_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_133_72v9fb17_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_140_72vn6wgo_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_119_72v8v9hf_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73j3wo01_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_2_73josgf1_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73jr20qc_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_2_73jh223h_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73josflf_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73jvqdqs_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_3_73josh91_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73j91rh9_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_91_72mqlnx9_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_111_72mrdr5m_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_96_72mqx958_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_114_72mrgsf9_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_94_72mqs6gj_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_102_72mr3893_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_99_72mr2h6c_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_104_72mr5hfm_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_109_72mrc83z_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_98_72mr080w_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_93_72mqq36m_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_97_72mqz0mm_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_116_72mrk268_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_101_72mr31yv_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_110_72mrddhg_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_95_72mqv3hp_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_105_72mr5vq4_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_115_72mrjd2s_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_106_72mr7hnt_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_100_72mr2qfc_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_112_72mrfc5j_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_107_72mr909t_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_103_72mr4pol_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_113_72mrfsb9_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_117_72mrl5mf_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_108_72mrb13l_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_90_72ml85v3_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_92_72mqnxz1_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_26/o1_mf_1_143_72y6ww71_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_26/o1_mf_1_144_72ybybps_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_26/o1_mf_1_142_72xt10j7_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_26/o1_mf_1_145_72yccy5z_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_01/o1_mf_s_758043324_73g3jfxx_.bkp
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_01/o1_mf_s_758035850_73fw6vrc_.bkp
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758133684_73jvr5px_.bkp
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758127608_73jot9x0_.bkp
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758109276_73j3xfom_.bkp
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758129928_73jr2s7p_.bkp
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_07_22/o1_mf_s_757164997_72m9rqw3_.bkp
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 08/03/2011 12:53:19
RMAN-20208: UNTIL CHANGE is before RESETLOGS change
Edited by: K Doyle on Aug 3, 2011 10:22 AM -
Hi All,
We were trying to restore and recover one of our databases. The restore went well but the recover is erroring out. Can someone please let us know what we should do to remedy this and carry on with the recovery.
We got an error when we were trying to restore the controlfile at the begining (details below), but as you can see, it did manage to restore a copy of the controlfile successfully..
Details below.
C:\Users\oracle>rman target system/XXXX catalog rman/XXXX@rmancat
Recovery Manager: Release 11.1.0.7.0 - Production on Thu Dec 2 08:31:03 2010
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: CODP (not mounted)
connected to recovery catalog database
RMAN> set dbid=2399577932
executing command: SET DBID
database name is CODP and DBID is 2399577932
RMAN> RESTORE CONTROLFILE;
Starting restore at 02-DEC-10
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=152 device type=DISK
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\CONTROLFILE_BKUP_CODP_C-2399577932-20101201-00
channel ORA_DISK_1: "ORA-19870: error while restoring backup piece D:\RMAN\CODP\CONTROLFILE_BKUP_CODP_C-2399577932-20101201-00"
"ORA-19505: failed to identify file D:\RMAN\CODP\CONTROLFILE_BKUP_CODP_C-2399577932-20101201-00"
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
failover to previous backup
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_DULUG8H9_1_1
channel ORA_DISK_1: "ORA-19870: error while restoring backup piece D:\RMAN\CODP\BKUP_CODP_DULUG8H9_1_1"
"ORA-19505: failed to identify file D:\RMAN\CODP\BKUP_CODP_DULUG8H9_1_1"
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
failover to previous backup
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\CONTROLFILE_BKUP_CODP_C-2399577932-20101130-01
channel ORA_DISK_1: piece handle=D:\RMAN\CODP\CONTROLFILE_BKUP_CODP_C-2399577932-20101130-01 tag=TAG20101130T204059
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:01
output file name=C:\ORACLE\ORADATA\CONTROLFILE\CODP\CONTROL01.CTL
output file name=D:\ORACLE\ORADATA\CONTROLFILE\CODP\CONTROL02.CTL
output file name=D:\ORACLE\ORADATA\CODP\CONTROL03.CTL
Finished restore at 02-DEC-10
RMAN> RESTORE SPFILE FROM AUTOBACKUP;
Starting restore at 02-DEC-10
using channel ORA_DISK_1
recovery area destination: D:\oracle\flash_recovery_area\
database name (or database unique name) used for search: CODP
channel ORA_DISK_1: no AUTOBACKUPS found in the recovery area
channel ORA_DISK_1: looking for AUTOBACKUP on day: 20101202
channel ORA_DISK_1: looking for AUTOBACKUP on day: 20101201
channel ORA_DISK_1: looking for AUTOBACKUP on day: 20101130
channel ORA_DISK_1: AUTOBACKUP found: D:\RMAN\CODP\controlfile_bkup_CODP_c-2399577932-20101130-01
channel ORA_DISK_1: restoring spfile from AUTOBACKUP D:\RMAN\CODP\controlfile_bkup_CODP_c-2399577932-20101130-01
channel ORA_DISK_1: SPFILE restore from AUTOBACKUP complete
Finished restore at 02-DEC-10
RMAN> restore database;
Starting restore at 02-DEC-10
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 00020 to D:\ORACLE\ORADATA\CODP\VCLLOAD_T1.DBF
channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_56LU9C9M_1_1
channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_56LU9C9M_1_1 tag=LEVEL0_TUE
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:02:45
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 00002 to D:\ORACLE\ORADATA\CODP\UNDOTBS01.DBF
channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_57LU9CFQ_1_1
channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_57LU9CFQ_1_1 tag=LEVEL0_TUE
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:03:25
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 00009 to D:\ORACLE\ORADATA\CODP\PROD_T3_NEW_02.DBF
channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_58LU9CMS_1_1
channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_58LU9CMS_1_1 tag=LEVEL0_TUE
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:01:55
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 00010 to D:\ORACLE\ORADATA\CODP\PROD_T3_NEW_03.DBF
channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_59LU9CR4_1_1
channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_59LU9CR4_1_1 tag=LEVEL0_TUE
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:01:55
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 D:\ORACLE\ORADATA\CODP\SYSTEM01.DBF
channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5ALU9CV2_1_1
channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5ALU9CV2_1_1 tag=LEVEL0_TUE
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:45
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 00005 to D:\ORACLE\ORADATA\CODP\PROD_T1_NEW_01.DBF
channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5BLU9D0P_1_1
channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5BLU9D0P_1_1 tag=LEVEL0_TUE
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:15
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 00006 to D:\ORACLE\ORADATA\CODP\PROD_T2_NEW_01.DBF
channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5CLU9D1J_1_1
channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5CLU9D1J_1_1 tag=LEVEL0_TUE
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:01:45
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 00007 to D:\ORACLE\ORADATA\CODP\PROD_T3_NEW_01.DBF
channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5DLU9D4T_1_1
channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5DLU9D4T_1_1 tag=LEVEL0_TUE
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:55
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 00025 to D:\ORACLE\ORADATA\CODP\PREV_PR_CODP_02.DBF
channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5ELU9D79_1_1
channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5ELU9D79_1_1 tag=LEVEL0_TUE
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:01:36
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 00024 to D:\ORACLE\ORADATA\CODP\PREV_PR_CODP_01.DBF
channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5FLU9DAI_1_1
channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5FLU9DAI_1_1 tag=LEVEL0_TUE
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:01:35
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 00026 to D:\ORACLE\ORADATA\CODP\PREV_PR_CODP_03.DBF
channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5GLU9DDI_1_1
channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5GLU9DDI_1_1 tag=LEVEL0_TUE
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:01:35
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 00027 to D:\ORACLE\ORADATA\CODP\PREV_PR_CODP_04.DBF
channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5HLU9DGU_1_1
channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5HLU9DGU_1_1 tag=LEVEL0_TUE
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:01:35
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 00011 to D:\ORACLE\ORADATA\CODP\PROD_I3_16K_02.DBF
channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5ILU9DJT_1_1
channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5ILU9DJT_1_1 tag=LEVEL0_TUE
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:01:35
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 00030 to D:\ORACLE\ORADATA\CODP\PREV_PR_CODP_07.DBF
channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5JLU9DN8_1_1
channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5JLU9DN8_1_1 tag=LEVEL0_TUE
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:46
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 00028 to D:\ORACLE\ORADATA\CODP\PREV_PR_CODP_05.DBF
channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5KLU9DOV_1_1
channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5KLU9DOV_1_1 tag=LEVEL0_TUE
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:45
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 00029 to D:\ORACLE\ORADATA\CODP\PREV_PR_CODP_06.DBF
channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5LLU9DQO_1_1
channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5LLU9DQO_1_1 tag=LEVEL0_TUE
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:45
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 00003 to D:\ORACLE\ORADATA\CODP\SYSAUX01.DBF
channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5MLU9DSF_1_1
channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5MLU9DSF_1_1 tag=LEVEL0_TUE
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:25
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 00008 to D:\ORACLE\ORADATA\CODP\PROD_I2_16K_03.DBF
channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5NLU9DT9_1_1
channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5NLU9DT9_1_1 tag=LEVEL0_TUE
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:35
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 00032 to D:\ORACLE\ORADATA\CODP\PROD_I2_16K_01.DBF
channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5OLU9DUN_1_1
channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5OLU9DUN_1_1 tag=LEVEL0_TUE
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:55
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 00033 to D:\ORACLE\ORADATA\CODP\PROD_I2_16K_02.DBF
channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5PLU9E0P_1_1
channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5PLU9E0P_1_1 tag=LEVEL0_TUE
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:01:05
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 00034 to D:\ORACLE\ORADATA\CODP\PROD_I3_16K_01.DBF
channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5QLU9E3F_1_1
channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5QLU9E3F_1_1 tag=LEVEL0_TUE
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:01:45
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 00031 to D:\ORACLE\ORADATA\CODP\PROD_I1_16K_01.DBF
channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_8QLU9ES2_1_1
channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_8QLU9ES2_1_1 tag=LEVEL0_TUE
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:35
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 00004 to D:\ORACLE\ORADATA\CODP\USERS01.DBF
channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_8SLU9ET9_1_1
channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_8SLU9ET9_1_1 tag=LEVEL0_TUE
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:01
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 00021 to D:\ORACLE\ORADATA\CODP\VCLLOAD_T2.DBF
channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_8ULU9ETF_1_1
channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_8ULU9ETF_1_1 tag=LEVEL0_TUE
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:01
Finished restore at 02-DEC-10
RMAN> recover database;
Starting recover at 02-DEC-10
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 12/02/2010 09:08:05
ORA-00210: cannot open the specified control file
RMAN>ThanksSorry everyone.. My bad.. I forgot to MOUNT the instance before trying to use the RECOVER DATABASE command.
Thanks -
Problem in recovering database
I Have Oracle Database 10g (10.2.0.1.0) on Windows Server 2003
I have taken full hot RMAN backup of database.
I have copied the backup files from flash recovery area.
I have one other Machine having windows server 2003 And Oracle 10g Same version. I have copied the backup files from first machine to Flash Recovery Area folder on second machine.
Now i am trying to restore the database of first machine to second machine.
1. I have created a new instance on second machice with same name as in fiirst machine.
2. I have created one ORA password file as well.
3. SET ORACLE_SID=<name of DB as it was in first machine>
4. RMAN TARGET sys/<password given in newly ORA pwd file>@<DB name> nocatalog
5. SET DBID=<dbid of old database>
6. STARTUP NOMOUNT FORCE
7. RESTORE SPFILE TO PFILE '<path of new pfile>' from '<path where backup files are there>';
8. CREATE UDUMP,BDUMP,CDUMP,PFILE,ORADATA FOLDERS where required;
9. SHUTDOWN IMMEDIATE;
10. STARTUP NOMOUNT PFILE='<path of newly created pfile>';
11 RESTORE CONTROLFILE FROM '<path of backup files>';
12. ALTER DATABASE MOUNT;
Everything work fine till here
Now my next step was
13. RESTORE DATABASE;
Then it gives error like:-
RMAN> restore database;
Starting restore at 20-NOV-08
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=375 devtype=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 11/20/2008 21:00:54
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 4 found to restore
RMAN-06023: no backup or copy of datafile 3 found to restore
RMAN-06023: no backup or copy of datafile 2 found to restore
RMAN-06023: no backup or copy of datafile 1 found to restore
Firstly i copied backup files to flash recovery area, then i copied files to 'D:\oracle\product\10.2.0\db_1\database' as well. Because i have done it in 9i, in 9i i copied the backup files to this backup folder then while doing restore RMAN succesfully takes file from this folder & restores the database. but in 10g RMAN is not recognising the path of backup. How this problem can be solved? Or is this some different problem which i am not getting?
Waiting for reply..Hi ORADBA,
Thanks for your response. Your solution worked. Actually there was a difference the Oracle installation on server from which i was taking backup is on E drive.
And the server on which i am trying to restore that database has Oracle installation files on D drive. That's why this confusion occurred.
But i have one query again. I am not able to recover my database fully.
Firstly i typed restore database command that worked. Thereafter i tried recover database command. that commant resulted in an error as given below. Than i typed command archive log list on SQL promt, from there i found the information of latest archive log. then i tried recover database until logseq 484 thread 1. That also didn't work. In the same situation i tried to open database i was able to open database using command alter database open resetlogs. I suppose i was not able to recover the database fully. Hi can i recover my database fully?
waiting for reply. Thanks in advance.
RMAN> recover database;
Starting recover at 24-NOV-08
using channel ORA_DISK_1
channel ORA_DISK_1: starting incremental datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
destination for restore of datafile 00001: E:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTDB\SYSTEM01.DBF
destination for restore of datafile 00002: E:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTDB\UNDOTBS01.DBF
destination for restore of datafile 00003: E:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTDB\SYSAUX01.DBF
destination for restore of datafile 00004: E:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTDB\USERS01.DBF
channel ORA_DISK_1: reading from backup piece E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\TESTDB\BACKUPSET\2008_11_20\O1
MFNNND1_BACKUP_TESTDB_L_1_4LB0PZXS_.BKP*
channel ORA_DISK_1: restored backup piece 1
piece handle=E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\TESTDB\BACKUPSET\2008_11_20\O1_MF_NNND1_BACKUP_TESTDB_L_1_4L
B0PZXS_.BKP tag=BACKUP_TESTDB_L_112008115509
channel ORA_DISK_1: restore complete, elapsed time: 00:00:15
starting media recovery
unable to find archive log
archive log thread=1 sequence=484
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 11/24/2008 19:47:07
RMAN-06054: media recovery requesting unknown log: thread 1 seq 484 lowscn 11013224
RMAN> recover database until logseq 484;
Starting recover at 24-NOV-08
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 11/24/2008 19:48:07
RMAN-06556: datafile 1 must be restored from backup older than scn 11009149
RMAN> recover database until logseq 484 thread 1;
Starting recover at 24-NOV-08
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 11/24/2008 19:48:20
RMAN-06556: datafile 1 must be restored from backup older than scn 11009149
RMAN> recover database until logseq 483 thread 1;
Starting recover at 24-NOV-08
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 11/24/2008 19:48:58
RMAN-06556: datafile 1 must be restored from backup older than scn 10973094
RMAN> recover database until logseq 482 thread 1;
Starting recover at 24-NOV-08
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 11/24/2008 19:49:06
RMAN-06556: datafile 1 must be restored from backup older than scn 10952975
RMAN> alter database open;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of alter db command at 11/24/2008 19:49:21
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
RMAN> alter database open resetlogs
*2> ;*
Edited by: user648257 on Nov 24, 2008 6:48 AM -
Recover database but don't have archive log file
Hi
I use old backup set in tape and restore all datafile completed but I cannot recover that show below errror in RMAN
RMAN> recover database;
Starting recover at 08-SEP-09
using channel ORA_DISK_1
starting media recovery
unable to find archive log
archive log thread=1 sequence=29166
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 09/08/2009 21:49:36
RMAN-06054: media recovery requesting unknown log: thread 1 seq 29166 lowscn 1648727512
But in backup set and include archive log already that don't have seq 29166 that have last seg is 29165 when I tyr recover in sqlplus that show below error
SQL> recover database using backup controlfile;
ORA-00279: change 1648727512 generated at 09/05/2009 00:02:07 needed for thread
1
ORA-00289: suggestion : /oradata/archive/hrprd/1_29166_671345511.arc
ORA-00280: change 1648727512 for thread 1 is in sequence #29166
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00308: cannot open archived log
'/oradata/archive/hrprd/1_29166_671345511.arc'
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: No such file or directory
Additional information: 3
And I tried to open with reset log that show below error
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01113: file 1 needs media recovery
ORA-01110: data file 1: '/oradata/data/hrprd/system01.dbf'
How can I do to open database?
Taohiko.taohiko wrote:
Hi Werner
I tried and show below error
SQL> recover database using backup controlfile until cancel;
ORA-00279: change 1648727512 generated at 09/05/2009 00:02:07 needed for thread
1
ORA-00289: suggestion : /oradata/archive/hrprd/1_29166_671345511.arc
ORA-00280: change 1648727512 for thread 1 is in sequence #29166
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
CANCEL
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/oradata/data/hrprd/system01.dbf'
ORA-01112: media recovery not started
How to do next step?
TaohikoHi Taohiko
Have you made backup of all archived redo log files? If so, why this one was disappeared?
Have you applied all archived redo log files before that required archived redo log file?
Please try to recover the database using the following command:
RMAN> RESTORE DATABASE;
RMAN> RECOVER DATABASE UNTIL SEQUENCE 29166;
RMAN>ALTER DATABASE OPEN RESETLOGS; -
Error returns when "Recover database"?
Hi all experts,
I am doing recover the database and get the following errors, I don't know what I have done wrong?
recover database;
Starting recover at 05-MAR-08
using channel ORA_DISK_1
starting media recovery
unable to find archive log
archive log thread=1 sequence=9
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 03/05/2008 17:19:37
RMAN-06054: media recovery requesting unknown log: thread 1 scn 1254920
Any ideas,
FanI have done what you said and get the followings:
ORA-00279: change 1254920 generated at 03/05/2008 14:11:26 needed for thread 1
ORA-00289: suggestion : /home/oracle/OraHome1/dbs/arch/1_9.dbf
ORA-00280: change 1254920 for thread 1 is in sequence #9
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00308: cannot open archived log '/home/oracle/OraHome1/dbs/arch/1_9.dbf'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
It seems to be SCN 1254920 for thread 1 is in sequence #9 and the 1_9.dbf not found. I didn't delete any files in redo log arch directory. What if this possible happen?
I am really tired. Any ideas?
Fan -
How to recover database SYSTEM datafile get corrupt ?
Database is in ARCHIVELOG mode, and the datafile belonging to SYSTEM tablespace gets corrupted. Up to what point can I recover the database ?
A. Until last commit.
B. Until the time you perform recovery.
C. Until the time the datafile got corrupted.
D. You cannot recover the SYSTEM tablespace and you must be re-create the database.
and 1 more doubt :
If redologfiles are not multiplexed and redolog blocks get corrupt in group 2, and archiving stops. All redolog files are filled and database activity is halted.
DBWR has written everything to disk. What command can be used to proceed further ?
A. recover logfile block group 2;
B. alter database drop logfile group 2;
C. alter database clear logfile group 2;
D. alter database recover logfile group 2;
E. alter database clear unarchived lofile group 2;
Edited by: user642367 on Sep 18, 2008 8:45 PM1. A. Since the DB is in archivelog mode, so you can always restore and recover the whole DB including system tablespace datafile till last SCN generated provided the redo record is available in archive/online logfiles.
2. E. Since only redolog is corrupted so archiver won't proceed and hence a db hang is obvious, So, in order to proceed further you need to clear online (un archived log file) and then db will work as usual. Care should be taken that you must take a full backkup of DB(cold backup wherever feasible) as soon as possible after issuing this command. As now you don't have redo info in archivelog files to recover the db in case of a crash.
Please go through Oracle 10g DB Administrators guide (available on OTN) for more details.
Thanks -
How to recover database in this situation?
My os is windows 2000 server, the oracle database version is 9.2.0.1
And the database is in archivelog mode.
first: I backup the controlfile to trace
second: I added a new tablespace
third: I shutdown immediate the database
forth: I delete the controlfile and datafile of the new added database
then: I tried to recover my database.
But I meet troubles.
I am a user from China. Appreciate your help!
C:\>sqlplus
SQL*Plus: Release 9.2.0.1.0 - Production on 星期一 10月 24 21:05:24 2005
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
请输入用户名: sys/nolog as sysdba
连接到:
Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.1.0 - Production
SQL> archive log list
数据库日志模式 存档模式
自动存档 启用
存档终点 D:\oracle\ora92\RDBMS
最早的概要日志序列 0
下一个存档日志序列 1
当前日志序列 1
SQL> select group#, sequence#, archived, status from v$log;
GROUP# SEQUENCE# ARC STATUS
1 0 YES UNUSED
2 0 YES UNUSED
3 1 NO CURRENT
SQL> create tablespace user_data datafile
2 'd:\oracle\oradata\wwfdb\user_data01.dbf' size 50m;
表空间已创建。
SQL> create table t(a number) tablespace user_data;
表已创建。
SQL> insert into t values(10);
已创建 1 行。
SQL> commit;
SQL> shutdown immediate
数据库已经关闭。
已经卸载数据库。
ORACLE 例程已经关闭。
SQL> host del d:\oracle\oradata\wwfdb\*.CTL
SQL> host del d:\oracle\oradata\wwfdb\user_data01.dbf
SQL> startup nomount
ORACLE 例程已经启动。
Total System Global Area 135338868 bytes
Fixed Size 453492 bytes
Variable Size 109051904 bytes
Database Buffers 25165824 bytes
Redo Buffers 667648 bytes
SQL> CREATE CONTROLFILE REUSE DATABASE "WWFDB" NORESETLOGS ARCHIVELOG
2 MAXLOGFILES 50
3 MAXLOGMEMBERS 5
4 MAXDATAFILES 100
5 MAXINSTANCES 1
6 MAXLOGHISTORY 226
7 LOGFILE
8 GROUP 1 'D:\ORACLE\ORADATA\WWFDB\REDO01.LOG' SIZE 100M,
9 GROUP 2 'D:\ORACLE\ORADATA\WWFDB\REDO02.LOG' SIZE 100M,
10 GROUP 3 'D:\ORACLE\ORADATA\WWFDB\REDO03.LOG' SIZE 100M
11 DATAFILE
12 'D:\ORACLE\ORADATA\WWFDB\SYSTEM01.DBF',
13 'D:\ORACLE\ORADATA\WWFDB\UNDOTBS01.DBF',
14 'D:\ORACLE\ORADATA\WWFDB\CWMLITE01.DBF',
15 'D:\ORACLE\ORADATA\WWFDB\DRSYS01.DBF',
16 'D:\ORACLE\ORADATA\WWFDB\EXAMPLE01.DBF',
17 'D:\ORACLE\ORADATA\WWFDB\INDX01.DBF',
18 'D:\ORACLE\ORADATA\WWFDB\ODM01.DBF',
19 'D:\ORACLE\ORADATA\WWFDB\TOOLS01.DBF',
20 'D:\ORACLE\ORADATA\WWFDB\USERS01.DBF',
21 'D:\ORACLE\ORADATA\WWFDB\XDB01.DBF'
22 CHARACTER SET ZHS16GBK;
控制文件已创建
SQL> recover database until time '2005-10-24 21:10:33';
完成介质恢复。
SQL> alter database open;
alter database open
ERROR 位于第 1 行:
ORA-01589: ??????????? RESETLOGS ? NORESETLOGS ??
SQL> alter database open noresetlogs;
数据库已更改。
SQL> select * from t;
select * from t
ERROR 位于第 1 行:
ORA-00376: ???????? 11
ORA-01111: ???? 11 ???? - ?????????
ORA-01110: ???? 11: 'D:\ORACLE\ORA92\DATABASE\MISSING00011'
the above sql statement:
recover database until time '2005-10-24 21:10:33'，the reason I choosed the time '2005-10-24 21:10:33'
is based the contents of alert.log file:
Mon Oct 24 21:10:20 2005
create tablespace user_data datafile
'd:\oracle\oradata\wwfdb\user_data01.dbf' size 50m
Mon Oct 24 21:10:32 2005
Completed: create tablespace user_data datafile
'd:\oracle\orHi,
why you create trace file ? and if you did that then you must have trace your ctl file after adding the tablespace for your db.so your ctl file will have registered the name of newly created tablespace.and if you do not have backup of ctl file which dosent contain the name of newly created tablespace then how would you recover your tablespace ? if you want to achieve your disered thoughts then add the tablespace and then backup of your full db then shutdown your db and delete your ctl file and data file.now open your db in nomount mode then restore your ctl file and datafile.
thanks
Alok -
Hi,
In our environment we sometimes copy "live" database from one disk volume to other. We use NetApp Snapmirror technology, but that is not important. That way, on the second volume we get a snapshot of that "live" database. What's obvious, the snapshot is inconsistent and before the copy database can be opened, needs recovery. We recover it using the "recover database" command. That solution we have been using for ages.
The copied database usually performs recovery using redolog files. But yesterday, during recovery, the database asked us for archived redolog files (archived one day before). That was not a problem, we restored what was needed, but we couldn't deliver the "copy" database to users on time.
I was asked to explain why the database needed the archived log files. My first explanation was "because the copy database was inconsistent as a result of long running transactions on the source database". But in my opinion undo data, to undo all uncommitted transactions is taken from undo tablespace. Nothing must have been redone. Can you explain me what the database had to redo? What could be the reason? Would you be so kind and give me advice how may I investigate the reason? In the future we have to deliver copied databases on time so there is a pressure put on me.
Any help will be appreciated.
Regards,
TimYou don't mention a database version, but I presume you either do 'alter database begin backup' (if 10g) or 'alter tablespace ... begin backup' (if not 10g) before taking your mirror snapshot?
If not, you're lucky to have had this thing working at all.
If you issue those sorts of 'begin backup' commands, then there will be a database/tablespace checkpoint and the header blocks of the files involved will be updated with the latest checkpoint change number. During the recovery of your mirror, you will only need to roll those files forward from that point. The contents of the buffer cache for those files will be flushed to disk, and the copied files are therefore guaranteed to have contents no earlier than the header block's checkpoint change number.
If you don't issue those sorts of commands, then Lord knows what state your datafile headers are in, and stuff in the buffer cache isn't necessarily flushed to disk in time. The copied file can therefore contain blocks from any checkpoint change number you care to think of onwards, and it's all pure chance what you get asked to supply by way of redo to rectify the situation.
Recovery means rolling things forward as well as rolling them back: your comment about undo is a bit misguided therefore. You need undo and redo to be able to complete a recovery. -
Error in Recover Database - ORA-01547 , ORA-01194 and ORA-01110
Hello folks,
I am facing a problem when recovering a database..
I made each tablespace in backup mode, then copied the datafile. I revert back the tablespace status to normal status.Once all datafiles are copied to target location, i created the control file from the source db.
I started the target db by
sqlplus "/ as sysdba"
then i executed the control file
SQL>@ctrlfile.sql
Control file got created.
SQL>recover database until cancel using backup controlfile;
it asked for archives. I gave the path one by one until everything was done.Now i gave 'cancel' as below.
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
cancel
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 377 needs more recovery to be consistent
ORA-01110: data file 377: '<path>/xxfndx01.dbf'
ORA-01112: media recovery not started
Could anyone please tell me where I went wrong and how can I move ahead from this stage???
Later on, when I gave open resetlogs, it gave the same error(as below)
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01194: file 377 needs more recovery to be consistent
ORA-01110: data file 377: '<path>/xxfndx01.dbf'
Please let me know the mistake I made, how to avoid that and how to proceed now ???
Thanks,
Cherrish Vaidiyan
[email protected]Hello Cherrish,
A very good question you have asked. I hope you realize that you're doing an incomplete recovery. There is some amount of information that is still there in the online redo-log, that would not be applied on your target db. Moreover when you're using backup controlfile, you do not know till which point you need to apply archive logs.
For incomplete recovery, Oracle for some reason has been very strict about the recover database command. i.e.
recover database using backup controlfile
recover database using backup controlfile until cancel
Is not same. It also applies to the command that you had given. By giving the command 'recover database using backup controlfile until cancel', you're telling Oracle that incomplete recovery is in process, and you would do resetelogs, to make sure all files are in sync. This is required when you have lost the redo-logs
In case you have just lost the control file. All latest redo-logs, archive-logs and datafiles are okay (or have been restored), then recover database using backup controlfile; would work perfectly okay. and resetlogs would not be required.. and that would be a complete recovery
I hope this all makes sense to you
Regards
Sudhanshu -
Recover database without controlfile and redo logs
Hi guys,
I am doing a testing with an Oracle Database 11.1.0.7.0, I want recover a database in this scenario without using RMAN:
-All controlfiles are missing
-All redo logs are missing
-I have a Backup Controlfile To Trace Resetlogs (bkp_controlfile.sql)
-The database is in archivelog mode
-The database was created with OMF (Oracle Managed Files)
So I have done this steps:
1) When the database was opened I rename all controlfiles and all redo logs
2) Shutdown Abort
3) I run the bkp_controlfile.sql, here I have a problem...
The database put in NOMOUNT, the controlfile was created and started the RECOVER DATABASE USING BACKUP CONTROLFILE, but when run ALTER DATABASE OPEN RESETLOGS; appear this:
ERROR at line 1:
ORA-01113: file 1 needs media recovery
ORA-01110: data file 1:
'/u02/app/oracle/oradata/OMF/datafile/o1_mf_system_68hzcb2z_.dbf'I wasn´t expect this because I don´t want recover a datafile, I only want open with resetlogs.
Any suggestion to help me?
Thanks a lot.Excelent! Thanks for your answers Markus and Hemant.
In conclusion...
- If we have all redo logs availables we can recreate the control file and recover the database without any problems using backup controlfile to trace noresetlogs*.
- if we haven´t all redo logs availables, there are 2 situations:
1) If the database shutdown properly:_ We will be able to open the database using recover database using backup controlfile until cancel*.
2) If the database doesn´t shutdown properly:_ We won´t be able to open the database with only a backup controlfile to trace.
With all this I close this thread. Was very good experience.
If anyone would add something will be welcome.
Thanks for all
I wish add the results of one of my tests: if I did all the steps in only one session of sqlplus I can shutdown properly the database, but if do the shutdown immediate* in a new session I can´t shutdown properly the database. Here I post the output:
ALL IN ONE SESSION*
[oracle@prueba ~]$ $ORACLE_HOME/bin/sqlplus / as sysdba
SQL*Plus: Release 11.1.0.7.0 - Production on Wed Sep 22 13:58:10 2010
Copyright (c) 1982, 2008, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> ALTER SYSTEM SWITCH LOGFILE;
System altered.
SQL> SHUTDOWN IMMEDIATE
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> STARTUP
ORACLE instance started.
Total System Global Area 631914496 bytes
Fixed Size 1315224 bytes
Variable Size 377491048 bytes
Database Buffers 247463936 bytes
Redo Buffers 5644288 bytes
Database mounted.
Database opened.
SQL> SHUTDOWN IMMEDIATE
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> @/home/oracle/bkp_controlfile.sql
ORACLE instance started.
Total System Global Area 631914496 bytes
Fixed Size 1315224 bytes
Variable Size 377491048 bytes
Database Buffers 247463936 bytes
Redo Buffers 5644288 bytes
Control file created.
SQL> RECOVER DATABASE USING BACKUP CONTROLFILE UNTIL CANCEL;
ORA-00279: change 398764 generated at 09/22/2010 14:09:49 needed for thread 1
ORA-00289: suggestion :
/u02/app/oracle/flash_recovery_area/OMF/archivelog/2010_09_22/o1_mf_1_40_%u_.arc
ORA-00280: change 398764 for thread 1 is in sequence #40
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
CANCEL
Media recovery cancelled.
SQL> ALTER DATABASE OPEN RESETLOGS;
Database altered.
SQL> ALTER TABLESPACE TEMP ADD TEMPFILE '/u02/app/oracle/oradata/OMF/datafile/o1_mf_temp_69n3z3vv_.tmp' SIZE 50331648 REUSE AUTOEXTEND ON NEXT 655360 MAXSIZE 32767M;
Tablespace altered.
SQL>
ALL IN DIFERENT SESSIONS*
[oracle@prueba ~]$ $ORACLE_HOME/bin/sqlplus / as sysdba
SQL*Plus: Release 11.1.0.7.0 - Production on Wed Sep 22 13:55:47 2010
Copyright (c) 1982, 2008, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> ALTER DATABASE BACKUP CONTROLFILE TO TRACE AS '/home/oracle/bkp_controlfile.sql' RESETLOGS;
Database altered.
SQL> SHUTDOWN IMMEDIATE
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> STARTUP MOUNT
ORACLE instance started.
Total System Global Area 631914496 bytes
Fixed Size 1315224 bytes
Variable Size 377491048 bytes
Database Buffers 247463936 bytes
Redo Buffers 5644288 bytes
Database mounted.
SQL> ALTER DATABASE ARCHIVELOG;
Database altered.
SQL> ALTER DATABASE OPEN;
Database altered.
SQL> ALTER SYSTEM SWITCH LOGFILE;
System altered.
SQL> ALTER SYSTEM SWITCH LOGFILE;
System altered.
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
[oracle@prueba ~]$ $ORACLE_HOME/bin/sqlplus / as sysdba
SQL*Plus: Release 11.1.0.7.0 - Production on Wed Sep 22 13:58:10 2010
Copyright (c) 1982, 2008, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> SHUTDOWN IMMEDIATE
ORA-00210: cannot open the specified control file
ORA-00202: control file: '/u02/app/oracle/oradata/OMF/controlfile/o1_mf_69n3x6n5_.ctl'
ORA-27041: unable to open file
Linux Error: 2: No such file or directory
Additional information: 3 -
Hi, I hope someone can explain to me what happened with my recovery process. I am running Oracle 8i.
I dropped a tablespace on 11/22 @ 09:11. I first tried to do a full restore without restoring the control file (I was told that I should keep the current control file in order to apply any logs).
RMAN> run {
2> allocate channel d1 type disk;
3> set limit channel d1 kbytes 100000;
4> allocate channel d2 type disk;
5> set limit channel d2 kbytes 100000;
6> allocate channel d3 type disk;
7> set limit channel d3 kbytes 100000;
8> restore database;
9> alter database mount;
10> recover database;
11> alter database open resetlogs;
12> release channel d1;
13> release channel d2;
14> release channel d3;
15> }
I received the following error:
RMAN-03002: failure during compilation of command
RMAN-03013: command type: recover
RMAN-03006: non-retryable error occurred during execution of command: recover(1)
RMAN-07004: unhandled exception during command execution on channel default
RMAN-10035: exception raised in RPC: ORA-19654: must use backup controlfile to switch file incarnations
RMAN-10031: ORA-19654 occurred during call to DBMS_BACKUP_RESTORE.SWITCHTOCOPY
I could not open the database, next I did a point in time restore with the control file:
RMAN> run {
2> allocate channel d1 type disk;
3> set limit channel d1 kbytes 100000;
4> allocate channel d2 type disk;
5> set limit channel d2 kbytes 100000;
6> allocate channel d3 type disk;
7> set limit channel d3 kbytes 100000;
8> restore controlfile;
9> alter database mount;
10> set until time = '2004-11-22:09:00:00';
11> restore database;
12> recover database;
13> release channel d1;
14> release channel d2;
15> release channel d3;
16> }
I received the following error:
RMAN-03002: failure during compilation of command
RMAN-03013: command type: recover
RMAN-03002: failure during compilation of command
RMAN-03013: command type: recover(4)
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of log thread 1 seq 8 scn 263762 found to restore
I could not open the database, I received the following error when I tried to open with resetlogs:
RMAN-06003 .....:ORA-01113 file 1 needs media recovery
'/d01/oradata/dr_cms/system01.dbf'
I was done for the day and the system was shutdown, including the AIX server. When I started everything this morning, I did an 'alter database open resetlogs' and the database opened and the tablespace that I dropped was back!!!
Does this make sense? Can anyone tell me what happened?!
Why should a reboot of the system cause the database to open?No, you do not have to reboot the OS to get start the database. To know what exactly passed it was needed to see at the OS level the datafiles found in disk during the several intents you did for recover the database.
Joel Pérez
http://www.oracle.com/technology/experts -
How to recover database without archive files
Hello,
I've a test database without archive files and I need to know how to recover it without using archive files.
What is SQL command to recover database wthout archives?
Thanks in advance for your help.
Regards,
CarlesThere are serveral information missing in this posting and as a support personnel, I would like to find out more when I see postings like this.
1. This person wants to "Test" his backup and recovery in NOARCHIVELOG mode.
2. He/She did not say his database had already crashed or had a problem.
3. He/She did not give any indication the kind of scenario he wants to recover from.
4. He/She did not mention the state of his database at the time of he posting.
5. He/She did not mention the Release of his Oracle Server or Platform.
6. He/She did not mention the type of backup he already has in place (although provided later as Full COLD Backup). How "genuine" is the back?
7. What actions has already been taken to attempt recovery.
In my support experience, I normally would go through a list of questions witht he use/client to get the full picture of the current status of the database before I give answers that would worsen situations, especially in a Disaster Recovery sitaution.
Personaly, I would suggest you have a look at the list above. One of the most important is number 3 (The Recovery Scenario), then number 4, number 6 and 7. Number 7 will determine the situation of your database. So, when you ask for SQL commands to use, there are different commands for different kind of recovery depending on what has gone wrong or what kind of file is damaged (Datafiles, Logfiles, Control Files, one tablespace, one table, entire database gone, etc).
Maybe you are looking for
-
HI, I try to open my Iphoto but a message (topic) appears and won`t let me in.
-
Is there a way to block inappropiate search terms in Safari on an iphone or ipad?
I want to block certain search terms on the iphone and ipad that my son uses. Is it possible to do this in Safari on these devices?
-
How to handle the error ORA-04052
We have two Oracle database servers Primary and Secondary, and a DBLINK from Primary to Secondary. We have a table EmployeeDetails in both the database. we have written a query to retreive data from both the database using DBLINK without any problem.
-
Simulating input to a PXI-6624
Hello, I am tring to figure out how to simulate an input to a 6624 so I can work on my program. I created a simluated PXI-6624 board on my computer but I can't figure out how to stimulate the input? Thanks Scott
-
Ipad/Iphone camera switches photos when they are taken. How do I stop this?
When photos are being taken, at first they look fine. When clicked to take the photo it flips it and it looks different. How do I stop this?