Transhipment-Fix beschädigtes, vom System verwaltetes Rückgängigmachen von Segmenten

Weitere Informationen zum Umgang mit Korruption, see the BC expert notes on corruption und

see MOSC Note 1088018.1 – Umgang mit Oracle-Datenbankbeschädigungsproblemen.

Also see how to fix undo log corruption (JETZT-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. Jedoch,

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:

JETZT-00600: internal error code, arguments: [6006], [1], [], [], [], [], [], []

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.

Damit, 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.

Damit, here is what you need to do:

Create a new system management undo tablespace:

connect / als sysdba

create undo tablespace undotbs2 datafile “/u02/oracle/oradata/test/undotbs2.dbf”

size 500m;

Determine the problem undo segment:

select segment_name, status from dba_rollback_segs;

 

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 it:

connect / als sysdba

create pfile=”/u01/oracle/admin/test/pfile/inittest.ora” from spfile;

Edit the inittest.ora pfile and add (using the undo segment from our example error):

*._offline_rollback_segments=? _SYSSMU29$?

*._corrupt_rollback_segments=?_SYSSMU29$?

Now shutdown your instance, this may require a shutdown abort, but try a shutdown immediate first.

Startup using the manual startup command:

startup pfile=”/u01/oacle/admin/test/pfile=inittest.ora”

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 underscore parameters.

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. Jedoch, 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.