My Oracle Support Banner

Setting 10046/10053 Events = ORA-600[dbgdrebuildScope_Scope_Missing] (Doc ID 2505037.1)

Last updated on MARCH 03, 2020

Applies to:

Oracle Database - Enterprise Edition - Version 12.2.0.1 to 12.2.0.1 [Release 12.2]
Oracle Database - Standard Edition - Version 12.2.0.1 to 12.2.0.1 [Release 12.2]
Information in this document applies to any platform.

Symptoms

When setting 10046/10053 events for specific SQL statements in multiple sessions, for example:

alter system set events 'sql_trace[sql:<SQL_ID>] level=12';

the following error occurs:

ORA-00600: internal error code, arguments: [dbgdrebuildScope_Scope_Missing], [0x12ED5B130], [], [], [], [], [], [], [], [], [], []

 

Test case:

[...]$ sqlplus / as sysdba
...

SQL> create tablespace t1 datafile 't1.dbf' size 500M segment space management auto;

Tablespace created.

SQL> connect t1/t1
Connected.
SQL> create table t1 (c1 number);

Table created.

SQL> insert into t1 values (1);

1 row created.

SQL> commit;

Commit complete.

SQL> select /* user1 */ * from t1;

        C1
----------
         1

SQL> select sql_id from v$sql where sql_text like '%user1%';

SQL_ID
-------------
1zbtxw8wr1ft1
b22b2yh1xabbj
cj738u935gtyw

SQL> connect / as sysdba
Connected.
SQL> alter system set events 'sql_trace[sql:b22b2yh1xabbj] level=12';

System altered.

SQL> exit

...
[...]$ sqlplus / as sysdba
...

SQL> alter system set events 'sql_trace[sql:b22b2yh1xabbj] level=12';

System altered.

SQL> exit

...
[...]$ sqlplus / as sysdba
...

SQL> alter system set events 'sql_trace[sql:b22b2yh1xabbj] level=12';

System altered.

SQL> alter system set events 'sql_trace[sql:cj738u935gtyw] level=12';

System altered.

SQL> exit

...
[...]$ sqlplus / as sysdba
...

SQL> alter system set events 'sql_trace[sql:cj738u935gtyw] level=12';
alter system set events 'sql_trace[sql:cj738u935gtyw] level=12'
*
ERROR at line 1:
ORA-00600: internal error code, arguments: [dbgdrebuildScope_Scope_Missing],
[0x067CC01E0], [], [], [], [], [], [], [], [], [], []

SQL>

Note: This test case is one of steps for reproducing. It may also occur with other steps.

The Call Stack Trace in the associated incident trace file shows:

ksedst <- dbkedDefDump <- ksedmp <- dbgexPhaseII <- dbgexProcessError
 <- dbgePostErrorKGE <- 1767 <- dbkePostKGE_kgsf <- kgeadse <- kgerinv_internal
  <- kgerinv <- kgeasnmierr <- dbgdRebuildScope <- 827 <- dbgdParseCmd
   <- dbkdParseCmd <- kkyasy_options <- 896 <- kkyasy <- kksExecuteCommand
    <- opiexe <- kpoal8 <- opiodr <- ttcpip <- opitsk
     <- opiino <- opiodr <- opidrv <- sou2o <- opimai_real
      <- ssthrdmain <- main <- libc_start_main <- start

 

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
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.