ORA-600 RAISED WHEN CALLING DBMS_UTILITY.DB_VERSION VIA DBLINK
(Doc ID 784824.1)
Last updated on NOVEMBER 28, 2016
Applies to:Oracle Server Enterprise Edition - Version: 18.104.22.168 to 10.2.0.4
This problem can occur on any platform.
a) ORA-00600 error is reported in alert log :-
ORA-00600: internal error code, arguments: , [0x698BF258]   ----> address will vary
b) V92x and V102x databases are communicating via DBLINK [issue might apply to other RDBMS
versions but has not been tested]
c) 600 errors are seen when trying to create new or existing MVIEWS over
d) Error will also be reproduced when using the PLSQL :-
Where 'testlink' is an appropriately created or already existing dblink
d) Stack trace will be similar to the following :-
Function List (to Full stack) (to Summary stack)
VInfreq__kglgob <- kgldpo <- kgldon <- pkldon <- pkloud <- phnnrl_name_resolve_by_loading
<- phngdl_get_defining_libunit <- phnrpls_resolve_prefix_libscope <- phnrp_resolve_pref
<- phnr_resolve <- ph2ogc <- ph2orc <- ph2osc <- ph2op1 <- ph2stm <- ph2sms <- ph2blo <- ph2stm <- ph2uni <- ph2dr2 <- ph2drv <- phpsem <- phpcmp <- pcisem2 <- kkxsem <- opitca <- kksctca
<- rpiswu2 <- kkslod <- kglobld <- kglobpn <- kglpin <- kksfbc <- kkspsc0 <- opiosq0 <- kpooprx
<- kpoal8 <- opiodr <- ttcpip <- opitsk <- opiino <- opiodr <- opidrv <- sou2o <- opimai
The stack itself for this ORA-00600 is quite generic and does not easily narrow the bug
search, on this basis the next symptom is very important for this article to be considered appropriate.
e) EVENT 10336 is present on at least one of the databases
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
|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.|