Cannot open db

[itwizzkid]

Cannot start db

Hi, I am getting the following message when i try to start my database:
ORA-00704: bootstrap process failure
ORA-00604: error occurred at recursive SQL level 2
ORA-08103: object no longer exists

Thu Oct 07 02:58:45 2004
Error 704 happened during db open, shutting down database
USER: terminating instance due to error 704
Instance terminated by USER, pid = 736

I moved the datafiles to a new location and had this problem:
SQL> alter database rename file 'C:\ORACLE\ORADATA\TRAIN1\UNDOTBS01.DBF' to 'E:\
ORACLE\ORADATA\TRAIN1\UNDOTBS011.DBF';

Database altered.

SQL> alter database open;
alter database open
*
ERROR at line 1:
ORA-01122: database file 2 failed verification check
ORA-01110: data file 2: 'E:\ORACLE\ORADATA\TRAIN1\UNDOTBS011.DBF'
ORA-01251: Unknown File Header Version read for file number 2
ORA-1092 signalled during: ALTER DATABASE OPEN...

I dropped the datafile and now have the problem above. I cannot restore the UNDOTBS011.DBF.
Is there anyway to get around this?

Thanks

Will

[stecal]

1) Create new UNDO tablespace, make it the default.
2) Say goodbye to anything you had in the previous UNDO tablespace. Then get rid of it.
3) Make sure you have a good backup & recovery plan/system. What do you think happens to a tablespace when you whack one of its datafiles? You're lucky you didn't do this to a relevant data type of datafile.
4) Read, study, learn. Which Oracle DBA reference book do you own?

[itwizzkid]

Stecal,

I can't create a new tablespace because (undo tablespace is auto) the database is mounted not opened.

[gandolf989]

Originally posted by itwizzkid
Stecal,

I can't create a new tablespace because (undo tablespace is auto) the database is mounted not opened.

change the UNDO_MANAGEMENT parameter to manual in the parameter file. So that you can open the database and recreate your undo tablespace. Then change it back to auto and bounce the database.

You may need to bounce the database after you change the parameter.

[itwizzkid]

gandolf989 tried this still cannot start the db. Do I need to specify any rollback_segements?

[gandolf989]

Originally posted by itwizzkid
gandolf989 tried this still cannot start the db. Do I need to specify any rollback_segements?

You should be able to start the database without rollback.
Here is an ask tom article that should walk you through everything you need to do to start your database.

Ask Tom

[itwizzkid]

gandolf989, Thank for your replies. I tried the suggestion in the article. When I open the database this what I get

SQL> alter database open;
alter database open
*
ERROR at line 1:
ORA-01092: ORACLE instance terminated. Disconnection forced

I looked in the alert log and this what I am seeing:

Errors in file c:\oracle\admin\train1\udump\train1_ora_2036.trc:
ORA-00704: bootstrap process failure
ORA-00604: error occurred at recursive SQL level 2
ORA-08103: object no longer exists
From udump:
** SESSION ID:(9.3) 2004-10-08 02:41:08.000
----- Redo read statistics for thread 1 -----
Read rate (ASYNC) = 0Kb/sec => 1 blocks in 4s
Read buffer = 8192Kb (16384 blocks)
Longest record = 0Kb
Record moves = 0/1 (0%)
----------------------------------------------
*** 2004-10-08 02:41:09.000
KCRA: start recovery claims for 0 data blocks
*** 2004-10-08 02:41:09.000
KCRA: buffers claimed = 0/0, eliminated = 0
ORA-00704: bootstrap process failure
ORA-00604: error occurred at recursive SQL level 2
ORA-08103: object no longer exists

Any other leads welcomed
will

[DaPi]

Since you start without an undo, you shouldn't have rollback_segments= in your initSID.ora file.

[itwizzkid]

Dapi,

I do not have rollback_segments= in initSID.ora file. I still can only mount the db not open.

Thanks

[gandolf989]

Have you tried recreating the control file? do an alter database backup controlfile to trace; Find the file that was created in you bdump folder and edit it. Take out all of the comments and references to your undo tablespace and then run that against the database as sys. But make sure that you set UNDO_MANAGEMENT = manual;

This should remove the missing tablespace from your database, you should then be able to open the database and recreate the undo tablespace and change UNDO_MANAGEMENT = auto;