Database Administration (MOSC)

MOSC Banner

Database Control / DBSNMP Parse Errors

edited Jan 29, 2015 3:21AM in Database Administration (MOSC) 2 commentsAnswered ✓

I've been investigating the cause of some high "parse failure" counts in an AWR report and found that the culprit seems to be DB Control.

StatisticTotalper Secondper Trans
parse count (failures)45,82850.824.69
parse count (hard)47,58652.774.87

Looking at V$SESS_TIME_MODEL, the sessions with the highest stat_name = 'failed parse elapsed time' are DBSNMP and SYSMAN.

I read through 1353015.1 (How to Identify Hard Parse Failures) and turned on the 10035 trace, and have found it appears to be caused by this query:

Tue Jan 27 10:44:25 2015
PARSE ERROR: ospid=65521, error=936 for statement:
select  msgid from  WMSYS.AQ$_WM$EVENT_QUEUE_TABLE_I where SUBSCRIBER# =  and rownum <=1

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

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

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center