controlfile identification error

[sreddy]

Usually, we do these steps @ command mode interactively

*creating control file nomount mode
*mounting database
*recovering the database if its production/development and has backup,archivelog,wanted transactions in redolog .
*opening database

If you want to include these, the way trace file gives it can be done thru script.

Assuming,thinking there might be any problem while bringing back database from loss of cotrol file, in general people does stepwise interactively rather driven by a script.

ASA you bring db up do

SVRMGR> ALTER DATABASR BACKUP CONTROLFILE TO TRACE ;

And mirror controlfiles atleast 2 locations.

NORESETLOGS and SCN sync makes difference if you have turned on archivelog mode and you are doing recovery otherwise, no difference, as your logs will be recycled anyway as you are not moveing 'em to archivedlog. So,RESETLOGS resets your logs and starts logging with beginig SCN.

Hope you got what Jeff steps meant now. You said no archivelog, no backup. So, Jeff gave you the steps to match your situation.


[Edited by sreddy on 01-11-2001 at 12:29 AM]

[sreddy]

consolidate the concept of recreating controlfile....

[url]http://www.dbasupport.com/forums/showthread.php?threadid=5619[/url]

[Edited by sreddy on 01-11-2001 at 12:21 AM]

[st2000]

Thanks a lot sreddy and jeff..
Now everything is back in form..
creating the control file and recovery got done successfully.
except that i had some db links and they failed.. i am working on it now.. (listener was shut down)..