My Oracle Support Banner

ORA-600 [ktspgetmyb-1] From Insert into a Particular Table (Doc ID 1604092.1)

Last updated on FEBRUARY 07, 2014

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.3 and later
Information in this document applies to any platform.

Symptoms

ORA-00600: internal error code, arguments: [ktspgetmyb-1], [], [], [], [], [], [], [], [], [], [], [] reported on an insert into a particular table.

 

The call stack in the trace file written by the error contains the following functions:

ktspgetmyb <- ktspbhwm <- ktspbmphwm <- ktspmvhwm
          <- ktsp_bump_hwm <- ktspgsp_main <- kdtgsp <- kdtgrs <- kdtSimpleInsRow
           <- qerltcSimpleSingleI <- nsRowCBK <- qerltcSingleRowLoad <- qerltcFetch <- insexe
            <- opiexe <- opipls <- opiodr <- rpidrus <- skgmstack
             <- rpiswu2 <- rpidrv <- psddr0 <- psdnal <- pevm_EXECC
              <- pfrinstr_EXECC <- pfrrun_no_tool <- pfrrun <- plsql_run <- peicnt
               <- kkxexe <- opiexe <- kpoal8 <- opiodr <- ttcpip
                <- opitsk <- opiino <- opiodr <- opidrv <- sou2o

Analyze table <tablename> validate structure cascade, run against the table being inserted into returns no errors.

exec dbms_space_admin.assm_segment_verify(
segment_owner=>'<owner>', -
segment_name => '<tablename>', -
segment_type => 'TABLE', -
partition_name => null, -
verify_option => dbms_space_admin.segment_verify_deep);


Writes a trace file containing entries similar to:

Verifying extent map and  auxilliary extent map   consistency in   the segment
Verifying extent map and L1 bitmap blocks consistency in the segment

*** 2013-11-26 04:59:09.938
The L1 BMB range [start dba: 0x001c43560, length: 8, offset: 16]
is inconsistent with the extent map
The correct start dba: 0x0018b7df0
The L1 BMB range [start dba: 0x001c43560, length: 8, offset: 16]
is inconsistent with the extent map
The end dba: 0x001c43568 not contained in an extent
The L1 BMB range [start dba: 0x0018b7e28, length: 8, offset: 24]
is inconsistent with the extent map
The correct start dba: 0x0018b7e00
The L1 BMB range [start dba: 0x0018b7e28, length: 8, offset: 24]
is inconsistent with the extent map
The end dba: 0x0018b7e30 not contained in an extent
The L1 BMB range [start dba: 0x001c43568, length: 8, offset: 32]
is inconsistent with the extent map
The correct start dba: 0x001c43548
The L1 BMB range [start dba: 0x001c43568, length: 8, offset: 32]
is inconsistent with the extent map
The end dba: 0x001c43570 not contained in an extent


 

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Cause
Solution


This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.