Email: service@parnassusdata.com 7 x 24 online support!

    You are here

    • You are here:
    • Home > Blogs > PDSERVICE's blog > Oracle ORA-600 [kcbgcur_3] "current buffer has same class but wrong object id"

Oracle ORA-600 [kcbgcur_3] "current buffer has same class but wrong object id"

Oracle ORA-600 [kcbgcur_3] "current buffer has same class but wrong object id"

Format: ORA-600 [kcbgcur_3] [a] [b] [c] [d] [e] [f]

VERSIONS:

versions 8.0 to 10.1

DESCRIPTION:

This error is raised because a cache buffer in state "current"

was holding a database block with the same address

(tablespace#, relative dba) as the one expected but belonging

to a different object (indicated by a different object id).

ARGUMENTS:

The number of arguments and their meaning vary depending on the Oracle

Server release and the object type relating to the error.

4 Argument format

=================

This format relates to Oracle Server version 10gR2 and above

Arg [a] Object Id passed to the cache by the layer accessing the cache.

Arg [b] Class of the block.

Arg [c] Flags which define characteristics of buffer usage

Arg [d] 1 for a temporary object.

3 Argument format

=================

This format relates to Oracle Server version 10gR1

Arg [a] Object Id passed to the cache by the layer accessing the cache.

Arg [b] Class of the block.

Arg [c] 1 for a temporary object.

2 Argument format

 

 

=================

This format relates to Oracle Server version 9.X

Arg [a] Object Id passed to the cache by the layer accessing the cache.

Arg [b] 1 for a temporary object.

6 Argument format

=================

This format relates to Oracle Server versions 8.0.4 to 8.1.7

Arg [a] Class of the block.

Arg [b] Tablespace number.

Arg [c] Relative DBA.

Arg [d] Object Id in the cache buffer at the time of the error.

Arg [e] Object Id passed to the cache by the layer accessing the cache.

Arg [f] Indicates if this is a temporary or a permanent object.

In version 8.0.4 to 8.1.5, this is 1 for a permanent object.

In version 8.1.6 and 8.1.7, this is 1 for a temporary object.

5 Argument format

=================

This format relates to Oracle Server 8.0.3

Arg [a] Class of the block.

Arg [b] Tablespace number.

Arg [c] Relative DBA.

Arg [d] Object Id in the cache buffer at the time of the error.

Arg [e] Object Id passed to the cache by the layer accessing the cache.

FUNCTIONALITY:

Cache Buffer management Implementation

IMPACT:

PROCESS FAILURE

POSSIBLE PHYSICAL CORRUPTION

 

 

NB Bug Fixed Description

 

+ 13467683

11.2.0.2.BP15,

11.2.0.3.3,

11.2.0.3.BP04, 12.1.0.0

Join of temp and permanent tables in RAC might cause

corruption of permanent table. Regression by bug

10352368

11902008 12.1.0.0 SMON may crash with ORA-00600 [kcbgcur_3] or ORA-

600 [kcbnew_3] during Transaction recovery

7227645 11.1.0.7, 11.2.0.1 OERI[kcbgcur_3]/OERI[kcb_check_objd_typ] during

INSERT on freelist-managed segment

6444339 10.2.0.5, 11.2.0.1 Truncate/purge does not clean AQ dependencies

properly

6337376 11.1.0.7 OERI:kcbgcur_3 / ORA-8103 after truncating a partition

table with LOBs

5909305 11.1.0.6 Change to DML (TM) lock modes for foreign key

constraints

5303237 11.1.0.6 ORA-600 [kcbgtcr_5] during create queue table

8778379 10.2.0.5 Fix event 10227 in 10.2 ORA-600[kcbgcur_3] or ORA-

600[kcbgcur_9]

3963135 10.1.0.5, 10.2.0.1 OERI[kcbgcur_3] / OERI:25027 during bitmap index

updates

2784201 9.2.0.5, 10.1.0.2 OERI:[ktspfupdst-1] on INSERT into LOB after TRUNCATE

with ASSM

3693283 9.0.1.0 TRUNCATE can cause SMON to crash the instance with

OERI:[KTSF_RSP2]

1148416 8.1.6.1, 8.1.7.0 Buffer cache corruption can occur using GLOBAL

TEMPORARY TABLES

689973 8.0.4.4, 8.0.5.1, 8.0.6.0 OERI:KCBGCUR_3 during DROP/CREATE table with

concurrent queries.