ORA-600: [QESMMCVALSTAT4], [3], [1] ON 10GR2 GRID AGENT STARTUP (Doc ID 456929.1)

Last updated on NOVEMBER 28, 2016

Applies to:

Oracle Database - Enterprise Edition - Version to [Release 9.2 to 10.2]
Information in this document applies to any platform.
This problem can occur on any platform.
***Checked for relevance on 04-Apr-2013***


Whilst this article is specifically written for ORA-00600 errors seen in conjunction with starting
the 10GR2 Grid Agent the bug identified is very general. If the following symptoms are seen
and in particular symptom (x) then this article may be applicable but if still unresolved after
following the advised actions further research should be made or a new SR should be raised to Support.

a) 10GR2 Grid Agent is being started
b) ORA-00600[qesmmCValStat4], [3], [1] is reported in the alert log
c) The ORA-00600 trace reports the SQL :-

/* OracleOEM */
substr(SYS_CONNECT_BY_PATH(c, '->'),3,512) path, c, 'CREATE_PRIVILEGE'
null p,
name c
name like '%CREATE%'
granted_role p,
grantee c
privilege p,
grantee c
where ((c = 'PUBLIC') or (exists (select 'w' from dba_users where username=c))
) and rownum < 200
start with p is null
connect by p = prior c

CONNECT BY must be present in the SQL

d) Identifying the state object information (In the trace search for the string <session)> [the angled
brackets should not be used in the search] will show something similar to :-

SO: c000000119962580, type: 4, owner: c000000134a60b90, flag: INIT/-/-/0x00
(session) trans: 0000000000000000, creator: c000000134a60b90, flag:
(1000e5) USR/- BSY/-/-/-/-/-
DID: 0001-000F-0000078E, short-term DID: 0000-0000-00000000
txn branch: 0000000000000000
oct: 3, prv: 0, sql: c0000001399b0598, psql: c0000001399b0598, user: 19/DBSNMP
O/S info: user: oracle, term: , ospid: 16434, machine: xxxx
program: emagent@xxxx (TNS V1-V3)
application name: emagent@xxxx (TNS V1-V3), hash value=0
last wait for 'direct path read' blocking sess=0x0 seq=881 wait_time=1

So we are seeing the emagent executable and the DBSNMP user

e) The stack in the trace file will be similar to

ksedmp ksfdmp kgerinv kgeasnmierr qesmmCValidateStatus qesmmCStartWorkArea
qerhjInitializeManagementComponents qerhjFetch qerjoFetch
qergsFetch rwsfcd qeruaFetch qersoFetch qervwFetch qercoFetch
qerflFetchOutside qercbiFilterData qercbiFetch qerflFetchOutside qercoFetch kpofr
ws opifch2 opiall0 kpoal8 opiodr ttcpip opitsk opiino opiodr opirip opidrv
sou2o main $START$

Symptoms (B)/(C) [and C does not have to be from OEM] and (E) are sufficient for this article to be considered valid for the known bug that we are reporting.


Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms