ORA-600: [gwm_get_virtual_inst_num-1] During Startup Nomount
(Doc ID 3022964.1)
Last updated on MAY 15, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 19.11.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
Startup nomount generates:
ORA-00600: internal error code, arguments: [gwm_get_virtual_inst_num-1], [15], [10], [], [], [], [], [], [], [], [], []
The Call Stack Trace in the associated incident trace file is similar to:
gwm_init <- gwm_sga_notifier <- kscnfy <- ksmcsg
<- opistr_real <- opistr <- opiodr <- ttcpip <- opitsk
<- opiino <- opiodr <- opidrv <- sou2o <- opimai_real
<- ssthrdmain <- main <- libc_start_main <- start
Trace file shows following failing PL/SQL and packages:
BEGIN GSMADMIN_INTERNAL.DBMS_GSM_DBADMIN.sync(:dsc, :warn); END;
----- PL/SQL Stack -----
----- PL/SQL Call Stack -----
object line object
handle number name
0x84c91d88 1531 package body GSMADMIN_INTERNAL.DBMS_GSM_COMMON.SETDBPARAMETERINTERNAL
0x84c91d88 1570 package body GSMADMIN_INTERNAL.DBMS_GSM_COMMON.SETDBPARAMETER
0x84c91d88 1548 package body GSMADMIN_INTERNAL.DBMS_GSM_COMMON.SETDBPARAMETER
0x84c91d88 1021 package body GSMADMIN_INTERNAL.DBMS_GSM_COMMON.SETGSMPARAMETER
0xdc592d20 1543 package body GSMADMIN_INTERNAL.DBMS_GSM_DBADMIN.ADDGSM
0xdc592d20 3619 package body GSMADMIN_INTERNAL.DBMS_GSM_DBADMIN.SYNC
0x936a1610 1 anonymous block
In this incident when trying to register broker configuration with GDS keeps failing.
Changes
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 |
Changes |
Cause |
Solution |
References |