Dropping undo tablespace after ORA-00376, 01110 [message #289419] |
Fri, 21 December 2007 09:36 |
jwayt@iobar.com
Messages: 3 Registered: December 2007 Location: Houston
|
Junior Member |
|
|
I have a client who has no DBA. After some backup glitch, they started getting 376 errors, complaining file 2 cannot be read at this time. data file 2: ...UNDOTSP01.DBF
I read that the back could lock this and oracle would then flag it unreadable. How do I clear that flag?
I tried to drop tabalespace undotsp1 and it told me
ORA-01548: Active rollback segment '_SYSSMU1$' found, terminate dropping tablespace.
Please help. Their server is down.
|
|
|
|
|
|
|
Re: Dropping undo tablespace after ORA-00376, 01110 [message #289428 is a reply to message #289419] |
Fri, 21 December 2007 11:14 |
jwayt@iobar.com
Messages: 3 Registered: December 2007 Location: Houston
|
Junior Member |
|
|
Their best backup via oracle agent was a week ago Wednesday.
I've exported the User/schema. It gets all the tables throu stored procedures, then stops with the 376 error. It's missing integ contraints and a few arcane items afterward. Does it have enough to recover with?
|
|
|
|
Re: Dropping undo tablespace after ORA-00376, 01110 [message #289455 is a reply to message #289419] |
Fri, 21 December 2007 16:01 |
halfydba
Messages: 20 Registered: November 2007 Location: Australia
|
Junior Member |
|
|
Did you try to online the undo tablespace datafile? The error that you are getting is not related to an undo corruption. It leads me to believe at some stage Oracle could not write to the datafile so it took it off line. This is quite normal for all datafiles. Try a startup mount and check the status in v$datafile next time.
O and you can't just drop and undo tablespace. You have to ensure there are no active transaction first. There are ways to do this, but you have to really know what you are doing or it's dangerous to your database.
|
|
|