This is what you have to do:


. Shutdown your instance
. Make sure that there is no background processing running for this instance
(run ps -ef | grep -i oracle, kill if required or do a shutdown abort)
. Its good idea to move the existing redologs to a new location
sometimes you might need it for recovery purposes.
. move or rename your control files (you can also use the reuse clause)
. Verify that your create control file is something like this :

STARTUP NOMOUNT
CREATE CONTROLFILE REUSE DATABASE "PM1" NORESETLOGS NOARCHIVELOG
MAXLOGFILES 16
MAXLOGMEMBERS 2
MAXDATAFILES 30
MAXINSTANCES 1
MAXLOGHISTORY 226
LOGFILE
GROUP 1 '/oradata/pm1/vg01_01/redo_01.log' SIZE 126M,
GROUP 2 '/oradata/pm1/vg01_01/redo_02.log' SIZE 126M,
GROUP 3 '/oradata/pm1/vg01_01/redo_03.log' SIZE 126M
DATAFILE
'/oradata/pm1/vg01_01/system_01.dbf',
'/oradata/pm1/vg01_01/rbs1_01.dbf',
'/oradata/pm1/vg01_01/rbs2_01.dbf',
'/oradata/pm1/vg01_01/users_01.dbf',
'/oradata/pm1/vg01_01/tools_01.dbf',
'/oradata/pm1/vg01_01/pm1_med01.dbf'
;

I am assuming you have a script that does the above eg :makecontrol.sql
. you may have to use resetlogs (its been a while since I did this)
. make sure your sid is set accordingly (. oraenv)
. start a server mamager session :
. svrmgrl
. connect internal
. @makecontrol.sql
. you can now try an alter database open command to see if the database will come up
. if it says it needs recovery, do the recovery (recover database or
recover database until cancel).
. you should not have any problems bringing your database back up!.