Recover database cancel using controlfile
Hi,
I want to know what means and what will do this command
RECOVER DATABASE UNTIL CANCEL USING BACKUP CONTROLFILE
and what means the option
Specify log: {=suggested | filename | AUTO | CANCEL}
thanks for you help
I want to know what means and what will do this command
RECOVER DATABASE UNTIL CANCEL USING BACKUP CONTROLFILE
and what means the option
Specify log: {=suggested | filename | AUTO | CANCEL}You can perform recovery by providing logs how you wish.
suggested - you can give enter, so that which thread & Sequence it wants it will apply one archive.
filename - if you want to mention filename(in case actual file name is different) ,ofcourse you can give one by one up to what archives you want to apply
Auto - If you want to perform recovery with all the available archvies, you can prefer option too
Cancel - if you apply any of the archives, when you want to cancel, If you perform this recovery will be cancelled.
Also read documentation from Oracle http://docs.oracle.com/cd/B12037_01/server.101/b10734/rcmrecov.htm
Edited by: CKPT on Jun 4, 2012 10:38 AM
Similar Messages
-
How to recover database without controlfile and redo files?
Hi all,
If I just have datafiles using hot backup saving in another machine, and all files in current database were lost including data files,control files and redo log files .
How can I recover database just using hot backup datafiles? without control file, without redo files.
Your help is greatly appreciated.alter database backup control file to trace
SQL> alter database backup controlfile to trace;
Go to udump folder in oracle home folder check the trace file copy these lines
CREATE CONTROLFILE REUSE DATABASE "O10G1 NORESETLOGS NOARCHIVELOG
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 8
MAXLOGHISTORY 454
LOGFILE
GROUP 1 'E:\ORACLE2\PRODUCT\10.1.0\ORADATA\O10G1\REDO01.LOG' SIZE 10M,
GROUP 2 'E:\ORACLE2\PRODUCT\10.1.0\ORADATA\O10G1\REDO02.LOG' SIZE 10M,
GROUP 3 'E:\ORACLE2\PRODUCT\10.1.0\ORADATA\O10G1\REDO03.LOG' SIZE 10M
-- STANDBY LOGFILE
DATAFILE
'E:\ORACLE2\PRODUCT\10.1.0\ORADATA\O10G1\SYSTEM01.DBF',
'E:\ORACLE2\PRODUCT\10.1.0\ORADATA\O10G1\UNDOTBS01.DBF',
'E:\ORACLE2\PRODUCT\10.1.0\ORADATA\O10G1\SYSAUX01.DBF',
'E:\ORACLE2\PRODUCT\10.1.0\ORADATA\O10G1\USERS01.DBF'
CHARACTER SET WE8MSWIN1252
Change the new database name abc
and REUSE replaced by SET and NORESTLOGS replaced by RESTLOGS above lines.
Save as C1.sql
C:\ set oracle_sid=instance name
C:\>sqlplus /nolog
SQL*Plus: Release 10.1.0.2.0 - Production on Tue Apr
11 06:44:28 2006
Copyright (c) 1982, 2004, Oracle. All rights reserved.
SQL> connect / as sysdba;
Connected to an idle instance.
SQL> startup nomount
pfile='C:\oracle\product\10.1.0\admin\jeeno\pfile\jeenoinit.ora'
ORACLE instance started.
Total System Global Area 171966464 bytes
Fixed Size 787988 bytes
Variable Size 145750508 bytes
Database Buffers 25165824 bytes
Redo Buffers 262144 bytes
SQL> @c1.sql
Control file created.
SQL> alter database open resetlogs;
Database altered -
Recover database until cancel using backup controlfile Fails with ORA-01547
Hi
First of all, I'm sorry for posting in this community as my issue doesn't have any thing to do with Rman, but I couldn't find any more relative Community to post in
our System is Oracle EBS 11i and the OS on the production is AIX 5.2 / and the DR is 5.3 / DB version is 9i
we have our Oracle ERP scheduled using crontab to take a database COLD backup daily using gtar -cvzf .
yesterday I needed to clone the database only, so I used my usual method witch is
1) on the source SQL> alter database backup controlfile to trace as '<dest>/makecntrlfil.sql'
then you can delete the Commented header and change the first command from
"CREATE CONTROLFILE REUSE DATABASE <SOURCE> NORESETLOGS ..."
TO
CREATE CONTROLFILE SET DATABASE <TARGET> RESETLOGS <NO>ARCHIVELOG
2) de-compress the tgz files
3) on the target edit the $ORACLE_HOME/dbs/init<source>.ora, $ORACLE_HOME/environment file
4)run /ORACLE_HOME/appsutils/clone/bin/adcfgclone.prl
5) delete old controlfiles
6) on the database run the script you created on firs t step to create a new control fole
7)recover database until cancel using backup controlfile
8) alter database open resetlogs
add new temp file system
this way I used to do it
but yesterday when trying to execute recover database it didn't work, and gave this error
ORA-00279: change 6450277404 generated at 02/28/2013 02:47:56 needed for thread
1
ORA-00289: suggestion : /ERPDEV/DBASE/devdb/9.2.0/dbs/arch1_188462.dbf
ORA-00280: change 6450277404 for thread 1 is in sequence #188462
Specify log: {<RET>=suggested | filename | AUTO | CANCEL} >> I gave cancel >> so >>
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: '/ERPDEV/DBASE/SYS/devdata/system01.dbf'
nothing strange in the original alert log file in the time of taking the backup
So can You please tell me what maybe wrong and why it used to work before and now it's not
take in consideration that we are on archive log mode, but not using Rman or the archived Logs for backup and the sequence it needed ( 188462 ) is too old and already deleted on Production.the output of the sript
Please Do not Forgot to run /usr/bin/runmwm as root Please Do not Forgot to run /usr/bin/runmwm as root Please Do not Forgot to run /usr/bin/runmwm as root Please Do not Forgot to run /usr/bin/runmwm as root ConcMgr will not work ConcMgr will not work ConcMgr will not work #####################################################
172.16.10.10:1.0
access control disabled, clients can connect from any host
You are running adstpall.sh version 115.19
Executing service control script:
/ERPABP/APPL/abpcomn/admin/scripts/ABP_babtain-erp/adapcctl.sh stop script returned:
adapcctl.sh version 115.54
Apache Web Server Listener :httpd ( pid 765998 ) is running.
Stopping Apache Web Server Listener (dedicated HTTP) ...
Apache Web Server Listener (PLSQL) :httpd ( pid 2830390 ) is running.
Stopping Apache Web Server Listener (dedicated PLSQL) ...
adapcctl.sh: exiting with status 0
.end std out.
.end err out.
Executing service control script:
/ERPABP/APPL/abpcomn/admin/scripts/ABP_babtain-erp/adalnctl.sh stop script returned:
adalnctl.sh version
Shutting down listener process APPS_ABP.
adalnctl.sh: exiting with status 0
.end std out.
.end err out.
Executing service control script:
/ERPABP/APPL/abpcomn/admin/scripts/ABP_babtain-erp/adtcfctl.sh stop script returned:
You are running adtcfctl.sh version 115.14
Shutting down TCF SocketServer for ABP on port -1.
adtcfctl.sh: exiting with status 0
.end std out.
.end err out.
Executing service control script:
/ERPABP/APPL/abpcomn/admin/scripts/ABP_babtain-erp/adcmctl.sh stop script returned:
You are running adcmctl.sh version 115.28
Shutting down concurrent managers for ABP ...
Submitted request 7481224 for CONCURRENT FND SHUTDOWN
adcmctl.sh: exiting with status 0
.end std out.
.end err out.
Executing service control script:
/ERPABP/APPL/abpcomn/admin/scripts/ABP_babtain-erp/adfrmctl.sh stop script returned:
You are running adfrmctl.sh version 115.37
Stopping forms server for ABP on port 9003.
adfrmctl.sh: exiting with status 0
.end std out.
.end err out.
Executing service control script:
/ERPABP/APPL/abpcomn/admin/scripts/ABP_babtain-erp/adrepctl.sh stop script returned:
You are running adrepctl.sh version 115.32
stopping Reports Server for ABP on port 7003.
kill -9 827420
Reports Server for ABP successfully stopped.
adrepctl.sh: exiting with status 0
.end std out.
.end err out.
Executing service control script:
/ERPABP/APPL/abpcomn/admin/scripts/ABP_babtain-erp/adfmcctl.sh stop script returned:
You are running adfmcctl.sh version 115.19
Stopping forms load balancing client for ABP.
adfmcctl.sh: exiting with status 0
.end std out.
.end err out.
Executing service control script:
/ERPABP/APPL/abpcomn/admin/scripts/ABP_babtain-erp/adfmsctl.sh stop script returned:
You are running adfmsctl.sh version 115.15
Stopping forms metrics server for ABP on port 9203.
adfmsctl.sh: exiting with status 0
.end std out.
.end err out.
Executing service control script:
/ERPABP/APPL/abpcomn/admin/scripts/ABP_babtain-erp/jtffmctl.sh stop script returned:
You are running jtffmctl.sh version 115.16
Shutting down Fulfillment Server for ABP on port 9303 ...
jtffmctl.sh: exiting with status 0
.end std out.
.end err out.
All enabled services on this node are stopped.
Check logfile /ERPABP/APPL/abpcomn/admin/log/ABP_babtain-erp/04010130.log for details
Exiting with status 0
You are running addlnctl.sh version 115.7
Logfile: /ERPABP/DBASE/abpdb/9.2.0/appsutil/log/ABP_babtain-erp/addlnctl.txt
Shutting down listener process ABP ...
addlnctl.sh: exiting with status 0
You are running addbctl.sh version 115.10
Shutting down database ABP ...
SQL*Plus: Release 9.2.0.8.0 - Production on Mon Apr 1 01:36:25 2013
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected.
Database closed.
Database dismounted.
ORACLE instance shut down.
Disconnected from Oracle9i Enterprise Edition Release 9.2.0.8.0 - 64bit Production With the Partitioning, OLAP and Oracle Data Mining options JServer Release 9.2.0.8.0 - Production
addbctl.sh: exiting with status 0
You are running addbctl.sh version 115.10
Starting the database ABP ...
SQL*Plus: Release 9.2.0.8.0 - Production on Mon Apr 1 01:38:48 2013
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to an idle instance.
ORACLE instance started.
Total System Global Area 6829474752 bytes
Fixed Size 742336 bytes
Variable Size 1493172224 bytes
Database Buffers 5324800000 bytes
Redo Buffers 10760192 bytes
Database mounted.
Database opened.
Disconnected from Oracle9i Enterprise Edition Release 9.2.0.8.0 - 64bit Production With the Partitioning, OLAP and Oracle Data Mining options JServer Release 9.2.0.8.0 - Production
addbctl.sh: exiting with status 0
You are running addbctl.sh version 115.10
Shutting down database ABP ...
SQL*Plus: Release 9.2.0.8.0 - Production on Mon Apr 1 01:39:08 2013
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected.
Database closed.
Database dismounted.
ORACLE instance shut down.
Disconnected from Oracle9i Enterprise Edition Release 9.2.0.8.0 - 64bit Production With the Partitioning, OLAP and Oracle Data Mining options JServer Release 9.2.0.8.0 - Production
addbctl.sh: exiting with status 0
root 2883784 2097278 0 01:39:54 - 0:00 grep abpappl
root 1425530 2097278 1 01:39:54 - 0:00 grep abpora
Taring /ERPABP/DBASE/SYS/abpdata
Mon Apr 1 01:39:54 SAUST 2013
Mon Apr 1 03:00:16 SAUST 2013
Taring /ERPDEV/DBASE/SYS/abpdata
Mon Apr 1 03:00:16 SAUST 2013
Mon Apr 1 03:10:18 SAUST 2013
Taring /ERPABP/DBASE/DATA/abpdata
Mon Apr 1 03:10:18 SAUST 2013
Mon Apr 1 04:51:04 SAUST 2013
Taring /ERPDEV/APPL/DATA/abpdata
Mon Apr 1 04:51:04 SAUST 2013
Mon Apr 1 05:02:58 SAUST 2013
You are running addbctl.sh version 115.10
Starting the database ABP ...
SQL*Plus: Release 9.2.0.8.0 - Production on Mon Apr 1 05:04:46 2013
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to an idle instance.
ORACLE instance started.
Total System Global Area 6829474752 bytes
Fixed Size 742336 bytes
Variable Size 1493172224 bytes
Database Buffers 5324800000 bytes
Redo Buffers 10760192 bytes
Database mounted.
Database opened.
Disconnected from Oracle9i Enterprise Edition Release 9.2.0.8.0 - 64bit Production With the Partitioning, OLAP and Oracle Data Mining options JServer Release 9.2.0.8.0 - Production
addbctl.sh: exiting with status 0
You are running addlnctl.sh version 115.7
Logfile: /ERPABP/DBASE/abpdb/9.2.0/appsutil/log/ABP_babtain-erp/addlnctl.txt
Starting listener process ABP ...
addlnctl.sh: exiting with status 0
Please Do not Forgot to run /usr/bin/runmwm as root Please Do not Forgot to run /usr/bin/runmwm as root Please Do not Forgot to run /usr/bin/runmwm as root Please Do not Forgot to run /usr/bin/runmwm as root ConcMgr will not work ConcMgr will not work ConcMgr will not work #####################################################
172.16.10.10:1.0
access control disabled, clients can connect from any host
You are running adstrtal.sh version 115.16
Executing service control script:
/ERPABP/APPL/abpcomn/admin/scripts/ABP_babtain-erp/adapcctl.sh start script returned:
adapcctl.sh version 115.54
Apache Web Server Listener is not running.
Starting Apache Web Server Listener (dedicated HTTP) ...
Apache Web Server Listener (PLSQL) is not running.
Starting Apache Web Server Listener (dedicated PLSQL) ...
adapcctl.sh: exiting with status 0
.end std out.
.end err out.
Executing service control script:
/ERPABP/APPL/abpcomn/admin/scripts/ABP_babtain-erp/adalnctl.sh start script returned:
adalnctl.sh version
Checking for FNDFS executable.
Starting listener process APPS_ABP.
adalnctl.sh: exiting with status 0
.end std out.
.end err out.
Executing service control script:
/ERPABP/APPL/abpcomn/admin/scripts/ABP_babtain-erp/adtcfctl.sh start script returned:
You are running adtcfctl.sh version 115.14
TCF SocketServer for ABP on port -1 is already started.
adtcfctl.sh: exiting with status 2
.end std out.
.end err out.
Executing service control script:
/ERPABP/APPL/abpcomn/admin/scripts/ABP_babtain-erp/adcmctl.sh start script returned:
You are running adcmctl.sh version 115.28
Starting concurrent manager for ABP ...
Starting ABP_0401@ABP Internal Concurrent Manager Default printer is noprint
adcmctl.sh: exiting with status 0
.end std out.
.end err out.
Executing service control script:
/ERPABP/APPL/abpcomn/admin/scripts/ABP_babtain-erp/adfrmctl.sh start script returned:
You are running adfrmctl.sh version 115.37
Starting forms server for ABP on port 9003.
adfrmctl.sh: exiting with status 0
.end std out.
.end err out.
Executing service control script:
/ERPABP/APPL/abpcomn/admin/scripts/ABP_babtain-erp/adrepctl.sh start script returned:
You are running adrepctl.sh version 115.32
starting Reports Server for ABP on port 7003.
adrepctl.sh: exiting with status 0
.end std out.
.end err out.
Executing service control script:
/ERPABP/APPL/abpcomn/admin/scripts/ABP_babtain-erp/adfmcctl.sh start script returned:
You are running adfmcctl.sh version 115.19
Starting forms load balancing client for ABP.
adfmcctl.sh: exiting with status 0
.end std out.
.end err out.
Executing service control script:
/ERPABP/APPL/abpcomn/admin/scripts/ABP_babtain-erp/adfmsctl.sh start script returned:
You are running adfmsctl.sh version 115.15
starting forms metrics server for ABP.
adfmsctl.sh: exiting with status 0
.end std out.
.end err out.
Executing service control script:
/ERPABP/APPL/abpcomn/admin/scripts/ABP_babtain-erp/jtffmctl.sh start script returned:
You are running jtffmctl.sh version 115.16
Validating Fulfillment patch level via /ERPABP/APPL/abpcomn/java Fulfillment patch level validated.
Starting Fulfillment Server for ABP on port 9303 ...
jtffmctl.sh: exiting with status 0
.end std out.
.end err out.
All enabled services for this node are started.
Check logfile /ERPABP/APPL/abpcomn/admin/log/ABP_babtain-erp/04010505.log for details
Exiting with status 0
MWA Telnet Server Release: 1.0.8.4 [December 12th 2002] Mon Apr 1 05:06:01 SAUST 2013
9653.50 /store/abp/data/data_abpdata_010413.tgz
1089.50 /store/abp/data/datadev_abpdata_010413.tgz
0.04 /store/abp/data/mkctrl.sql
13309.38 /store/abp/data/sys_abpdata_010413.tgz
1000.25 /store/abp/data/sysdev_abpdata_010413.tgz
Mon Apr 1 05:06:01 SAUST 2013
####################################################################################################################### -
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 -
"recover database until cancel" asks for archive log file that do not exist
Hello,
Oracle Release : Oracle 10.2.0.2.0
Last week we performed, a restore and then an Oracle recovery using the recover database until cancel command. (we didn't use backup control files) .It worked fine and we able to restart the SAP instances. However, I still have questions about Oracle behaviour using this command.
First we restored, an online backup.
We tried to restart the database, but got ORA-01113,ORA-01110 errors :
sr3usr.data1 needed media recovery.
Then we performed the recovery :
According Oracel documentation, "recover database until cancel recovery" proceeds by prompting you with the suggested filenames of archived redo log files.
The probleme is it prompts for archive log file that do not exist.
As you can see below, it asked for SMAarch1_10420_610186861.dbf that has never been created. Therefore, I cancelled manually the recovery, and restarted the database. We never got the message "media recovery complete"
ORA-279 signalled during: ALTER DATABASE RECOVER LOGFILE '/oracle/SMA/oraarch/SMAarch1_10417_61018686
Fri Sep 7 14:09:45 2007
ALTER DATABASE RECOVER LOGFILE '/oracle/SMA/oraarch/SMAarch1_10418_610186861.dbf'
Fri Sep 7 14:09:45 2007
Media Recovery Log /oracle/SMA/oraarch/SMAarch1_10418_610186861.dbf
ORA-279 signalled during: ALTER DATABASE RECOVER LOGFILE '/oracle/SMA/oraarch/SMAarch1_10418_61018686
Fri Sep 7 14:10:03 2007
ALTER DATABASE RECOVER LOGFILE '/oracle/SMA/oraarch/SMAarch1_10419_610186861.dbf'
Fri Sep 7 14:10:03 2007
Media Recovery Log /oracle/SMA/oraarch/SMAarch1_10419_610186861.dbf
ORA-279 signalled during: ALTER DATABASE RECOVER LOGFILE '/oracle/SMA/oraarch/SMAarch1_10419_61018686
Fri Sep 7 14:10:13 2007
ALTER DATABASE RECOVER LOGFILE '/oracle/SMA/oraarch/SMAarch1_10420_610186861.dbf'
Fri Sep 7 14:10:13 2007
Media Recovery Log /oracle/SMA/oraarch/SMAarch1_10420_610186861.dbf
Errors with log /oracle/SMA/oraarch/SMAarch1_10420_610186861.dbf
ORA-308 signalled during: ALTER DATABASE RECOVER LOGFILE '/oracle/SMA/oraarch/SMAarch1_10420_61018686
Fri Sep 7 14:15:19 2007
ALTER DATABASE RECOVER CANCEL
Fri Sep 7 14:15:20 2007
ORA-1013 signalled during: ALTER DATABASE RECOVER CANCEL ...
Fri Sep 7 14:15:40 2007
Shutting down instance: further logons disabled
When restaring the database we could see that, a recovery of online redo log has been performed automatically, is it the normal behaviour of a recovery using "recover database until cancel" command ?
Started redo application at
Thread 1: logseq 10416, block 482
Fri Sep 7 14:24:55 2007
Recovery of Online Redo Log: Thread 1 Group 4 Seq 10416 Reading mem 0
Mem# 0 errs 0: /oracle/SMA/origlogB/log_g14m1.dbf
Mem# 1 errs 0: /oracle/SMA/mirrlogB/log_g14m2.dbf
Fri Sep 7 14:24:55 2007
Completed redo application
Fri Sep 7 14:24:55 2007
Completed crash recovery at
Thread 1: logseq 10416, block 525, scn 105140074
0 data blocks read, 0 data blocks written, 43 redo blocks read
Thank you very much for your help.
Frod.Hi,
Let me answer your query.
=======================
Your question: While performing the recovery, is it possible to locate which online redolog is needed, and then to apply the changes in these logs
1. When you have current controlfile and need complete data (no data loss),
then do not go for until cancel recovery.
2. Oracle will apply all the redologs (including current redolog) while recovery
process is on.
3. During the recovery you need to have all the redologs which are listed in the view V$RECOVERY_LOG and all the unarchived and current redolog. By querying V$RECOVERY_LOG you can find out about the redologs required.
4. If the required sequence is not there in the archive destination, and if recovery process asks for that sequence you can query V$LOG to see whether requested sequence is part of the online redologs. If yes you can mention the path of the online redolog to complete the recovery.
Hope this information helps.
Regards,
Madhukar -
Doubt in Recover database until cancel
Hi experts,
One query, I want to try out recover database until cancel. But my archivelog files are in tape drive. How do i do it as it ask for archiver destination directory for the archivelog file.
Or can any please explain how should i do it.
Thanks in advance
shaanHi Satist,
when i apply the other archivelog file, it again shows the error
SQL> recover database until cancel using backup controlfile;
ORA-00279: change 1740044 generated at 06/18/2007 21:20:18 needed for thread 1
ORA-00289: suggestion : /oracle/NEWDB/admin/arch/1_5.dbf
ORA-00280: change 1740044 for thread 1 is in sequence #5
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
/oracle/NEWDB/admin/arch/1_30.dbf
ORA-00310: archived log contains sequence 30; sequence 5 required
ORA-00334: archived log: '/oracle/NEWDB/admin/arch/1_30.dbf'
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/oracle/NEWDB/oradata/NEWDB/system.dbf'
Please tell me why this happening or any solution for this. Moreover i have archivelog file
from 1_1 to 1_14 .
Thanks in advance
shaan -
Recover database using cold backup
Hi All,
One of the table is delete by one of our DBA from PROD accidentally. We have a cold backup on one day before.
Now we are trying to restore it from the cold backup. PROD DB is in archivelog and all the archive is in tact.
The table got truncated today at 8 PM. Can we apply the database till 8 PM so that we can restore the truncated table using cold backup.
Please find the below steps which we are using to restore.
creating controlfile
starting the db in mount state
recover database;
Will it ask for latest archive log when we try to recover it.
ENV details -
DB - 11.2.0.1
Please suggest.
ThanksHi,
If you have doubts about the procedure to use to restore a backup to a point in time, then please take a look at the documentation first: Performing Flashback and Database Point-in-Time Recovery - 11g Release 2 (11.2)
After you specify the time when the recovery must end (UNTIL clause in rman), then the RECOVER command will try to use the archivelogs needed.
Before starting with this PITR operation, you should check if your database has flashback active, because it will be much easier to recover using it.
This is also explained on the same document linked above.
Regards.
Nelson -
RMAN-06067: RECOVER DATABASE required with a backup or created controlfile
Hi,
DB:9.2.0.8
OS: AIX 5.3
I am restoring DB with until time(12/06/2012) for needed tablespaces.
I restored the 12th date controlfile ,which is backed up with archivedlogs. I also have one more controlfile which backed up with full DB..
Restore of tablespaces are completed..
When recovery is going , failed with following error..
allocated channel: c7
channel c7: sid=22 devtype=SBT_TAPE
channel c7: VERITAS NetBackup for Oracle - Release 5.1 (2006040520)
allocated channel: c8
channel c8: sid=21 devtype=SBT_TAPE
channel c8: VERITAS NetBackup for Oracle - Release 5.1 (2006040520)
executing command: SET until clause
Starting recover at 23-06-2012 02:00:15
released channel: c1
released channel: c2
released channel: c3
released channel: c4
released channel: c5
released channel: c6
released channel: c7
released channel: c8
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 06/23/2012 03:36:57
RMAN-06067: RECOVER DATABASE required with a backup or created controlfile
RMAN>
Restore Script:
connect target /
connect catalog rmanc/recom@lgn_rmanc
run {
allocate channel c1 type 'SBT_TAPE';
allocate channel c2 type 'SBT_TAPE';
allocate channel c3 type 'SBT_TAPE';
allocate channel c4 type 'SBT_TAPE';
allocate channel c5 type 'SBT_TAPE';
allocate channel c6 type 'SBT_TAPE';
allocate channel c7 type 'SBT_TAPE';
allocate channel c8 type 'SBT_TAPE';
allocate channel c9 type 'SBT_TAPE';
allocate channel c10 type 'SBT_TAPE';
allocate channel c11 type 'SBT_TAPE';
allocate channel c12 type 'SBT_TAPE';
set until time '12-06-2012 00:01:26';
restore tablespace SYSTEM,UNDO_GEN01,UNDO_GEN02,TAB_80K_GENCON,TAB_25M_GENCON;
release channel c1;
release channel c2;
release channel c3;
release channel c4;
release channel c5;
release channel c6;
release channel c7;
release channel c8;
release channel c9;
release channel c10;
release channel c11;
release channel c12;
Recover Script:
connect catalog rmanc/recom@lgn_rmanc
connect target /
run {
allocate channel c1 type 'SBT_TAPE';
allocate channel c2 type 'SBT_TAPE';
allocate channel c3 type 'SBT_TAPE';
allocate channel c4 type 'SBT_TAPE';
allocate channel c5 type 'SBT_TAPE';
allocate channel c6 type 'SBT_TAPE';
allocate channel c7 type 'SBT_TAPE';
allocate channel c8 type 'SBT_TAPE';
set until time '12-06-2012 00:01:26';
recover tablespace SYSTEM,UNDO_GEN01,UNDO_GEN02,TAB_80K_GENCON,TAB_25M_GENCON;
release channel c1;
release channel c2;
release channel c3;
release channel c4;
release channel c5;
release channel c6;
release channel c7;
release channel c8;
Any suggestion in this is helpful to me..
Thanks in advance,Hello;
I read your post and here's the thoughts that came to mind : ( my largest concern is you might restore something that damages your current system )
1. So you want to restore the whole DB back to 12/06/2012 to get some tablespaces from then right?
2. Are you restoring to a different system?
3. How did you start the database ( NOMOUNT, MOUNT )
4. If you are restoring the whole DB back to 12/06/2012 how did you restore the control file?
5. Your command shows :
restore tablespace SYSTEM,UNDO_GEN01,UNDO_GEN02,TAB_80K_GENCON,TAB_25M_GENCON;
COMMENT : Generally I use recover tablespace for point in time recovery and use an auxilary destination.
Meaning I don't use restore at all, in fact using restore may cause an issue.
SUMMARY : I don't see how this will work as is.
It seems you want data from five tablespaces from about six months ago including the SYSTEM tablespace.
This is an Incomplete Recovery. I believe I would rethink this completely.
Give the time that has past I would consider restoring the whole database to a different server where cannot damage anything.
Once this is done I would decide how to get the data I need.
Or I would check for a daily export file and recover the tablespace data that way.
So you have some good details on your question but it seems the plan is either missing something or you need to add a few more details.
Example
I'm recovering old tablespaces into a test system.
Here's how I'm not damaging my current production system.
I don't have an export from that date.
So take a step back and either rethink or give a few more details on how this is safe.
Best Regards
mseberg -
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 -
Can I use RECOVER database command evenif there is no MEDIA FAILURE? [b]Urg
I need an urgent help from all the big guns out there?
My database is up and running, but still I want to recover the deletion of data that has been done on FRIDAY/SATURDAY/SUNDAY/MONDAY/TUESDAY/WEDNESDAY in other words I want the FRIDAY's state of the database.
Can I do it using the
"RECOVER DATABASE UNTIL TIME '2005-28-06-00:00:00' command?
Please guide me.
Thanks in advanceHi,
i assume you running your database in archive log mode and using rman to accomplish you task.i would say that you can recover your database even if there is no media faliur occurs,no doubt you can use this.i think you want to recover your database to the fridays state prior to the table deletion,so you get the tables back in your database.so what's a problem execut following.
run {
SET UNTIL TIME "TO_DATE('apr 03 2005 01:17:13','MON DD YYYY HH24:MI:SS')";
restore database ;
recover database ;
asuume in this example that you want to recover your database up to date aprail 3 and prior to 01pm time.
change the code according to your requirement.
thanks. -
Problem in performing multiple Point-In-Time Database Recovery using RMAN
Hello Experts,
I am getting an error while performing database point in time recovery multiple times using RMAN. Details are as follows :-
Environment:
Oracle 11g, ASM,
Database DiskGroups : DG_DATA (Data files), DG_ARCH(Archive logs), DG_REDO(Redo logs Control file).
Snapshot DiskGroups :
Snapshot1 (taken at 9 am): SNAP1_DATA, SNAP1_ARCH, +SNAP1_REDO
Snapshot2 (taken at 10 am): SNAP2_DATA, SNAP2_ARCH, +SNAP2_REDO
Steps performed for point in time recovery:
1. Restore control file from snapshot 2.
RMAN> RESTORE CONTROLFILE from '+SNAP2_REDO/orcl/CONTROLFILE/Current.256.777398261';
2. For 2nd recovery, reset incarnation of database to snapshot 2 incarnation (Say 2).
3. Catalog data files from snapshot 1.
4. Catalog archive logs from snapshot 2.
5. Perform point in time recovery till given time.
STARTUP MOUNT;
RUN {
SQL "ALTER SESSION SET NLS_DATE_FORMAT = ''dd-mon-yyyy hh24:mi:ss''";
SET UNTIL TIME "06-mar-2013 09:30:00";
RESTORE DATABASE;
RECOVER DATABASE;
ALTER DATABASE OPEN RESETLOGS;
Results:
Recovery 1: At 10.30 am, I performed first point in time recovery till 9:30 am, it was successful. Database incarnation was raised from *2* to *3*.
Recovery 2: At 11:10 am, I performed another point in time recovery till 9:45 am, while doing it I reset the incarnation of DB to *2*, it failed with following error :-
Starting recover at 28-FEB-13
using channel ORA_DISK_1
starting media recovery
media recovery failed
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 03/06/2013 11:10:57
ORA-00283: recovery session canceled due to errors
RMAN-11003: failure during parse/execution of SQL statement: alter database recover if needed
start until time 'MAR 06 2013 09:45:00'
ORA-00283: recovery session canceled due to errors
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '+DG_REDO/orcl/onlinelog/group_1.257.807150859'
ORA-17503: ksfdopn:2 Failed to open file +DG_REDO/orcl/onlinelog/group_1.257.807150859
ORA-15012: ASM file '+DG_REDO/orcl/onlinelog/group_1.257.807150859' does not exist
Doubts:
1. Why did recovery failed 2nd time, but not 1st time and why is RMAN looking for online redo log group_1.257.807150859 in 2nd recovery ?
3. I tried restoring control file from AutoBackup, in that case both 1st and 2nd recovery succeeded.
However for this to work, I always need to keep the AutoBackup feature enabled.
How reliable is control file AutoBackup ? Is there any alternative to using AutoBackup, can I restore control file from snapshot backup only ?
4. If I restore control file from AutoBackup, then from what point of time/SCN does RMAN restores the control file ?
Please help me out in this issue.
Thanks.992748 wrote:
Hello experts,
I'm little newbie to RMAN recovery. Please help me in these doubts:
1. If I have datafiles, archive logs & control files backup, but current online REDO logs are lost, then can I perform incomplete database recovery ?yes, if you have backups of everything else
2. Till what maximum time/scn can incomplete database recovery be performed ??Assuming the only thing lost is the redo logs, you can recover to the last scn in the last archivelog.
3. What is role of online REDO logs in incomplete database recovery ? They provide the final redo changes - the ones that have not been written to archivelogs
Are they required for incomplete recovery ?It depends on how much incomplete recovery you need to do.
Think of all of your changes as a constant stream of redo information. As a redolog fills, it is copied to archive, then (eventually) reused. over time, your redo stream is in archivelog_1, continuing into archvivelog_2, then to 3, and eventually, when you get to the last archivelog, into the online redo. A recovery will start with the oldest necessary point in the redo stream and continue forward. Whether or not you need the online redo for a PIT recovery depends on how far forward you need to recover.
But you should take every precaution to prevent loss of online redo logs .. starting with having multiple members in each redo group ... and keeping those multiple members on physically separate disks. -
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. -
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 to new server problem
Hi all,
I'm running a production 10.2.0.4 DB in archivelog mode on Solaris 10.8. I used RMAN with a recovery catalog to execute the stored script:
run{sql 'alter system archive log current';
backup incremental level 0
database archivelog all delete input;}
I copied the rman files and spfile to a test server with the same directory structres. No Problem.
Using "rman target /" I started the database in nomount and restored the controlfile from backup and mounted the database. No Problem.
Still within the RMAN session, I restored the 1TB worth of datafiles. The restore completed, no problem.
I then issued the command, "recover database;" PROBLEM, RMAN said datafile1 "System.dbf" needs more recovery to be in a consistent state.
WHY? I issued the commands, "alter system archive log current;" and "archivelog all delete input" in my script.
Why does it need the next archivelog to be consistent?
I was under the impression that all I need to recover a database with rman was the output files from RMAN.
I copied the next archivelog over and in SQLPLUS as SYS I issued the command, " recover database using backup controlfile until cancel;"
I canceled the recovery when it asked for the next archivelog and opened database reset logs.
If I didn't have access to the next archive log how would I solve this problem?Your BACKUP should be executed as BACKUP DATABASE PLUS ARCHIVELOG. The "PLUS ARCHIVELOG" causes Oracle to issue an ALTER SYSTEM SWITCH LOGFILE at the end of the database backup so that the ArchiveLog generated gets picked up by the subsequent Backup of the ArchiveLog as well.
Your first RECOVER DATABASE command was attempting a Complete recovery. Had you specified an UNTIL clause, Oracle would know that you wanted an Incomplete recovery upto the last available archivelog. Your second RECOVER DATABASE with the UNTIL CANCEL was an Incomplete Recovery.
Hemant K Chitale -
Recover database until time - doesn't recover as expected
Hi,
We've got an Oracle 9i db (9208) running on AIX.
We've had a problem and that has meant restoring all the dbf's and control files from the over night backup onto the server replacing the currently corrupted system.
Once this was done we then opened the DB in order to check some things.
Once this was done we then closed and mounted it and issued the "recover database until time .... " command.
The archive logs we need are in the default archive location. They cover the time period just prior to the restored files up until the time we need the DB recovered to.
However, when running the recover the alert log just shows
"ALTER DATABASE RECOVER database until time '2010-08-11:16:30:00'
Mon Aug 16 14:33:57 2010
Media Recovery Start
Media Recovery Not Required"
Can anyone tell us why the recover command isn't recovering the archive log files up until the time we are specifying. It doesn't look like its even looking at them.
The command executes in less than a second.
Is this because we opened the DB between restoring and recovering so its already written a newer archive log file, so the DB thinks its already up to date???Got it - thanks
Basically cause we were also restoring the control file so when adding the "using backup controlfile" it then started to work.
SQL> recover database until time '2010-08-11:16:30:00' using backup controlfile
ORA-00279: change 276395529 generated at 08/10/2010 21:59:38 needed for thread
1
ORA-00289: suggestion : /archive_logs/tprod/arch0000070260.arc
ORA-00280: change 276395529 for thread 1 is in sequence #70260
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
This was the first message we got once we put the "using backup controlfile" part into the command.
We selected AUTO and its now slowly working through all the archive log files going up the numbers therefore i assume applying the archive logs correctly.
Once this is done i believe we just "alter database open resetlogs"
Maybe you are looking for
-
Logistics Invoice Verification - Error in MIRO Transaction
While posting the invoice in MIRO we get an error - " Maximum permitted number of internal tax items reached". What is the solution?
-
Hi, Has someone done some tests with ramjournal? What I found is that the performance of versionedPutAll gets worse when the cache size grows. Is this the case for anyone? I am using 2 nodes storage enabled and a cache in distributed-scheme. I am usi
-
Show only those key words in the slide show that are marked for export
Hi, I just learned that I can hide some keywords for export. I find it useful to look at the keywords at the bottom of the hierarchy in the slideshow. I found a way to display all keywords in a text field in the slide show, but I did not find a way t
-
Hi, I'm have just downloaded FLASH PROFESSIONAL 8. I want to import a quick time file into flash.Please can someone walk me through this. THANKS
-
TS1543 reset Mac OS X 10.5 password at the
Overnight my Mac OS X won't accept the password. Can't get into system to reset. Tried typing at command promtp after restarting with Command S. System did not recognize the LS users directory. How can I get in by accessing a partition to reset or