If you get an ORA-00600 or the following error message on your Oracle database:

ORA-00600: internal error code, arguments: [3020], [356515961], [1], [4606], [2], [16], [], []
ORA-10567: Redo is inconsistent with data block (file# 85, block# 121)
ORA-10564: tablespace UNDO

Please note, that the following rescue scenario resolves from corrupt rollback systems, the UNDO datafile still exists. If your UNDO datafile is corrupt or lost go to the next scenario:Rescue any Tablespace except SYSTEM.

Steps to rescue the UNDO Tablespace

1. Shutdown the Database if it is still running

sqlplus "/ as sysdba"
shutdown abort;

2. Verify the Rollback Segments in the UNDO Tablespace

The name of the Rollback Segments in the UNDO Tablespace are_SYSSMU1$, _SYSSMU2$,_SYSSMU3$, etc. One Rollback Segment in theSYSTEMT ablespace is called SYSTEM, we use exactly this Rollback Segment to rescue the UNDO Tablespace.

cd
strings .dbf | grep _SYSSMU | cut -d $ -f 1 | sort -u

Probably you get the following Rollback Segments:

   _SYSSMU1$,
   _SYSSMU2$,
   _SYSSMU3$,
   _SYSSMU4$,
   _SYSSMU5$,
   _SYSSMU6$,
   _SYSSMU7$,
   _SYSSMU8$,
   _SYSSMU9$,
   _SYSSMU10$

3. Uncomment and add the following lines to PFILE

   # undo_management = auto
   # undo_retention = 10800
   # undo_tablespace = undo

   undo_management = manual
   rollback_segments = (system)
   _corrupted_rollback_segments = ('_SYSSMU1$','_SYSSMU2$','_SYSSMU3$','_SYSSMU4$','_SYSSMU5$','_SYSSMU6$','_SYSSMU7$','_SYSSMU8$','_SYSSMU9$','_SYSSMU10$')

4. Startup in RESTRICT Mode with edited PFILE, then drop the Rollback Segments and UNDO Tablespace

sqlplus "/ as sysdba";
startup

restrict pfile='/home/oracle/oracle/initTEST.ora';
   drop rollback segment "_SYSSMU1$";
   drop rollback segment "_SYSSMU2$";
   drop rollback segment "_SYSSMU3$";
   drop rollback segment "_SYSSMU4$";
   drop rollback segment "_SYSSMU5$";
   drop rollback segment "_SYSSMU6$";
   drop rollback segment "_SYSSMU7$";
   drop rollback segment "_SYSSMU8$";
   drop rollback segment "_SYSSMU9$";
   drop rollback segment "_SYSSMU10$";
   drop tablespace undo including contents and datafiles;

select segment_name,status,tablespace_name from dba_rollback_segs;

   SEGMENT_NAME                   STATUS           TABLESPACE_NAME
   ------------------------------ ---------------- ------------------------------
   SYSTEM                         ONLINE           SYSTEM

At this point, no UNDO Tablespace exists anymore, and the SYSTEM Rollback Segment is the only active Rollback Segment.

5. Recreate the UNDO Tablespace and Restart the Database with original PFILE

   CREATE UNDO TABLESPACE undo DATAFILE '/home/oracle/undo.dbf' SIZE 1000M;

   undo_management = auto
   undo_retention = 10800
   undo_tablespace = undo

   #undo_management = manual
   #rollback_segments = (system)
   #_corrupted_rollback_segments = ('_SYSSMU1$','_SYSSMU2$','_SYSSMU3$','_SYSSMU4$','_SYSSMU5$','_SYSSMU6$','_SYSSMU7$','_SYSSMU8$','_SYSSMU9$','_SYSSMU10$')

shutdown immediate;
startup;

   select segment_name,status,tablespace_name from dba_rollback_segs;
   SEGMENT_NAME                   STATUS           TABLESPACE_NAME
   ------------------------------ ---------------- ------------------------------
   SYSTEM                             ONLINE           SYSTEM
   _SYSSMU11$                     ONLINE           UNDO
   _SYSSMU12$                     ONLINE           UNDO
   _SYSSMU13$                     ONLINE           UNDO
   _SYSSMU14$                     ONLINE           UNDO
   _SYSSMU15$                     ONLINE           UNDO
   _SYSSMU16$                     ONLINE       &nb

sp;   UNDO
   _SYSSMU17$                     ONLINE           UNDO
   _SYSSMU18$                     ONLINE           UNDO
   _SYSSMU19$                     ONLINE           UNDO
   _SYSSMU20$                     ONLINE           UNDO

ITPub博客

Rescue UNDO Tablespace

最新文章