Database Crash With ora-600 [2886] After Alter Tablespace <tablespace_name> Read Write (Doc ID 799556.1)

Last updated on NOVEMBER 28, 2016

Applies to:

Oracle Server - Enterprise Edition - Version: 11.1.0.6 to 11.1.0.7 - Release: 11.1 to 11.1
Information in this document applies to any platform.
***Checked for relevance on 06-Feb-2012***

Symptoms

DB crashes after altering a tablespace to be read write e.g.

alter tablespace <tablespace_name> read write;

The following is seen in the alert.log:

ORA-00600: internal error code, arguments: [2886], [18], [1], [], [], [], [], []
DBW0 (ospid: 29082): terminating the instance due to error 471
Thu Mar 26 04:30:05 2009
ORA-1092 : opiodr aborting process unknown ospid (18857_1)
Thu Mar 26 04:30:05 2009
ORA-1092 : opitsk aborting process
Thu Mar 26 04:30:06 2009
ORA-1092 : opitsk aborting process
Thu Mar 26 04:30:06 2009
ORA-1092 : opitsk aborting process
Instance terminated by DBW0, pid = 29082

 Trace File shows:

ORA-00600: internal error code, arguments: [2886], [18], [1], [], [], [], [], []

========= Dump for incident 8073 (ORA 600 [2886]) ========

*** 2009-03-26 04:29:59.889
----- SQL Statement (None) -----
Current SQL information unavailable - no cursor.

Function List
----------------------
ksedst1 <- ksedst <- dbkedDefDump <- dbgexPhaseII <- dbgexProcessError
<- dbgePostErrorKGE <- 1124 <- kgeade <- kgeriv_int <- kgesiv
<- ksesic2 <- kcfbsy <- kcfcsy <- ksbabs <- ksbrdp
<- opirip <- opidrv <- sou2o <- main <- start

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms