For additional information on handling corruption, see the
BC expert notes on corruption and see MOSC Note 1088018.1 -
Handling Oracle Database Corruption Issues.
Also see how to fix
log corruption (ORA-00375) with _undo_log_corruption
In Oracleand greater releases of
Oracle the old rollback segment has been replaced with undo segments
and for the most part, have become automatically sized and managed.
However, what happens when one of these system created and managed
undo segments becomes corrupt? Well, for one thing you will get
errors in your alert log similar to the following:
Errors in file /oracle/admin/test/bdump/test2_smon_21466.trc:
ORA-00600: internal error code, arguments: , , , , ,
, , 
SMON: mark undo segment 29 as needs recovery
ORACLE Instance test2 (pid = 11) -
Error 600 encountered while recovering
transaction (29, 42) on object 36.
(Note that this will show the same
undo segment, transaction, and object number each time it occurs, if
the undo segment and transaction number vary, then the problem is
with the object number displayed)
In fact, you may get many of these
over and over again.
So, what can you do about this?
If you attempt to alter the undo
segment with the ALTER ROLLBACK SEGMENT command you will be told in
no uncertain terms that this is system managed and can?t be altered.
So, here is what you need to
Create a new system management undo tablespace:
connect / as sysdba
create undo tablespace
Determine the problem undo segment:
The problem segment will show
a ?Needs Recovery? status.
Alter the system to use the new undo tablespace:
alter system set undo_tablespace=undotbs2 scope=both; (Note if you are not
using an spfile, omit the scope command)
If you are using an spfile, create a pfile from
connect / as sysdba
Edit the inittest.ora pfile and add (using the
undo segment from our example error):
Now shutdown your instance, this may require a
shutdown abort, but try a shutdown immediate first.
Startup using the manual startup command:
Alter the old undo tablespace offline:
alter tablespace undotbs1 offline;
Drop the offending tablespace:
drop tablespace undotbs1 including contents and datafiles;
Shut down immediate.
Edit the inittest.ora file to eliminate the
Restart the instance using the pfile option.
Create an spfile from the pfile:
create spfile from pfile=?/u01/oracle/admin/test/pfile/inittest.ora?;
Once step 13 is accomplished the
database should be up normally. However, it might be wise to do a
full backup and then rebuild using an export and import. Since we
had to drop a undo segment that had some possibly active
transactions un-applied the database may not be fully consistent.
Get the Complete
Oracle SQL Tuning Information
The landmark book
SQL Tuning The Definitive Reference" is
filled with valuable information on Oracle SQL Tuning.
This book includes scripts and tools to hypercharge Oracle 11g
performance and you can
for 30% off directly from the publisher.