Home » RDBMS Server » Backup & Recovery » cold backup recovery fails for database in noarchivelog mode (Oralce 11gr2, RHEL)
cold backup recovery fails for database in noarchivelog mode [message #461133] Wed, 16 June 2010 13:00 Go to next message
learn_ora
Messages: 3
Registered: June 2010
Junior Member
Hi,

I am trying to recover a database on a different machine from a backup of a cold copy of a database. I have the original control file, datafiles, online redo log files in the backup taken. The original database is running in NOARCHIVELOG mode; hence no archive logs backed up.

On the other machine, the steps to bring up the DB performed are:
1. startup mount
2. using RMAN, run the below:
run {
allocate channel rep_auto type disk;
recover database;
}
sql 'alter database open';

The error I get is:
sql statement: alter database open
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of sql command on default channel at 06/16/2010 17:46:49
RMAN-11003: failure during parse/execution of SQL statement: alter database open
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open

My questions:
1. I am using the original control file(not backup control file), so why is Oracle complaining to use resetlogs?
2. Before taking a cold backup, the database was shutdown "clean". As such, we should not need any recovery on the backup when trying to recover it on the other machine. If we attempt to do a recovery, it says "No media recovery required". Later, when we try to open the DB, it errors. Why does a simple "alter database open" fail?
3. We had taken a cold backup, so the database should be consistent with complete recovery. resetlogs should be used in case of incomplete recovery. So, is the only way out to use noresetlogs?

Im trying to find answers to the above..
Any help will be appreciated Smile

Thanks in advance!
Re: cold backup recovery fails for database in noarchivelog mode [message #461135 is a reply to message #461133] Wed, 16 June 2010 13:03 Go to previous messageGo to next message
BlackSwan
Messages: 26766
Registered: January 2009
Location: SoCal
Senior Member
what clues exist within alert_SID.log file?

Re: cold backup recovery fails for database in noarchivelog mode [message #461140 is a reply to message #461133] Wed, 16 June 2010 13:16 Go to previous messageGo to next message
Mahesh Rajendran
Messages: 10707
Registered: March 2002
Location: oracleDocoVille
Senior Member
Account Moderator
>> recover database;

Not sure why you are recovering a database that is noarchivelog mode.

All you need is

nomount the database.
Restore control file (you already have it). So just mount the database.
set new name for datafiles/log files if the path is different from source.
Restore database.

Re: cold backup recovery fails for database in noarchivelog mode [message #461200 is a reply to message #461135] Thu, 17 June 2010 01:08 Go to previous messageGo to next message
learn_ora
Messages: 3
Registered: June 2010
Junior Member
The alert log doesnt have any additional info. It only has the ORA-01589 error.

File: alert log
alter database open
Errors in file /u01/app/oracle/product/11.2.0/dbhome_1/admin/SUP/diag/diag/rdbms/sup/SUP/trace/SUP_ora_5927.trc:
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
ORA-1589 signalled during: alter database open...

File: trace file
Redo thread mounted by this instance: 1
Oracle process number: 23
Unix process pid: 5927, image: oracle@RDDAC022 (TNS V1-V3)

*** 2010-06-16 11:52:30.190
*** SESSION ID:(191.11) 2010-06-16 11:52:30.190
*** CLIENT ID:() 2010-06-16 11:52:30.190
*** SERVICE NAME:() 2010-06-16 11:52:30.190
*** MODULE NAME:(sqlplus@RDDAC022 (TNS V1-V3)) 2010-06-16 11:52:30.190
*** ACTION NAME:() 2010-06-16 11:52:30.190

ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
Re: cold backup recovery fails for database in noarchivelog mode [message #461203 is a reply to message #461140] Thu, 17 June 2010 01:15 Go to previous message
learn_ora
Messages: 3
Registered: June 2010
Junior Member
Right Mahesh, I agree we do not need to do a recovery (as if I attempt to run recover, Oracle clearly says recovery is not needed). The real issue is in "alter database open". I have the online redo logs. Why does Oracle expect us to use resetlogs or noresetlogs option?
Previous Topic: Restore database Error when restoring database to a new server
Next Topic: Datafile recovery not repairing corrupted block
Goto Forum:
  


Current Time: Thu Mar 28 07:52:56 CDT 2024