Re: Database recovery problem

almost correct
startup mount;
alter database datafile 'D:\DB\ORADATA\BODEV\NMSANDBOX_DATA.ORA' offline drop;
alter database open;
if the database still wants to recover more files you need to drop them also, if it wants to recover system it's time to learn irish say
WHALE
OIL
BEEF
HOOKED
faster and faster with an bit of an irish lilt. back to the problem at hand.
drop tablespace tablespace_of_the_above_datafile; then reload your data because you were in noarchivelog mode so you must be able to reload your data.

then take this opportunity to crank up your buffer cache to as big as possible -- this is a joke, no flames please.

• Original Message ----- From: Mercadante, Thomas F (LABOR) To: onkarnath.tiwary_at_gmail.com ; oracle-l_at_freelists.org Sent: Tuesday, September 20, 2005 8:26 AM Subject: RE: Database recovery problem

Onkar,

It is asking for an archive file because the dummy file that you created is not an Oracle database file. So it is trying to bring it up to date. Even though you are not running in archivelog mode, Oracle still acts the same way - that is, it is keeping track of what would be the correct archivelog file even though it did not write them out to disk.

You have one option:

Startup mount;
Alter datafile 'D:\DB\ORADATA\BODEV\NMSANDBOX_DATA.ORA' offline. Alter database open.

You will be able to export all of the data in the database except what was stored in this data file. This will allow you to import it into another database.

So all of your data is not gone - just the stuff in this file/tablespace. Everything else has been lost.

Good Luck!

Tom

• Original Message ----- From: Mercadante, Thomas F (LABOR) To: onkarnath.tiwary_at_gmail.com ; oracle-l_at_freelists.org Sent: Tuesday, September 20, 2005 8:26 AM Subject: RE: Database recovery problem

Onkar,

It is asking for an archive file because the dummy file that you created is not an Oracle database file. So it is trying to bring it up to date. Even though you are not running in archivelog mode, Oracle still acts the same way - that is, it is keeping track of what would be the correct archivelog file even though it did not write them out to disk.

You have one option:

Startup mount;
Alter datafile 'D:\DB\ORADATA\BODEV\NMSANDBOX_DATA.ORA' offline. Alter database open.

You will be able to export all of the data in the database except what was stored in this data file. This will allow you to import it into another database.

So all of your data is not gone - just the stuff in this file/tablespace. Everything else has been lost.

Good Luck!

Tom

--
http://www.freelists.org/webpage/oracle-l