Expert Oracle Exadata - Parent Directory

CHAPTER 10 EXADATA WAIT EVENTSPARSING IN CURSOR #47046073104400 len=34 dep=0 uid=85 oct=3 lid=85 tim=1301275393323414hv=3308960238 ad='b3c9faf8' sqlid='c4js15z2mpfgf'select count(*)from kso.skewEND OF STMTPARSE #470460:c=0,e=77,p=0,cr=0,cu=0,mis=0,r=0,dep=0,og=1,plh=937687140,tim=130EXEC #470460:c=0,e=49,p=0,cr=0,cu=0,mis=0,r=0,dep=0,og=1,plh=937687140,tim=130WAIT #470460: nam='SQL*Net message to client' ela= 4 driver id=1650815232 #bytes=1 ...WAIT #470460: nam='resmgr:cpu quantum' ela= 3457 location=3 consumer group id=75525 ...WAIT #470460: nam='resmgr:cpu quantum' ela= 68126 location=3 consumer group id=75525 ...WAIT #470460: nam='resmgr:cpu quantum' ela= 68046 location=3 consumer group id=75525 ...WAIT #470460: nam='resmgr:cpu quantum' ela= 108941 location=3 consumer group id=75525 ...WAIT #470460: nam='resmgr:cpu quantum' ela= 38234 location=3 consumer group id=75525 ...WAIT #470460: nam='resmgr:cpu quantum' ela= 103282 location=3 consumer group id=75525 ...ParametersHere are the parameters for this event. Note that the obj# parameter exists but is not used.P1 - LocationP2 - Consumer group idP3 - Not usedobj# - NAThe location parameter is a numeric value that most likely refers to a location (function) in the Oraclecode. There are at least 5 distinct locations that we have observed. Unfortunately, Oracle does notpublicly document where in the Oracle kernel these checks are performed.The consumer group number in the P2 parameter is pretty self-explanatory. It maps to theCONSUMER_GROUP_ID column in the DBA_RSRC_CONSUMER_GROUPS view. This parameter allowsyou to tell what consumer group a process was assigned to when its CPU usage was curtailed.resmgr:pq queuedThis event is used to record time spent waiting in the parallel query queue.Event MeaningThe parallel statement queuing feature comes with its own wait event. Statements that are queued dueto insufficient parallel server processes or other directives clock time to this event. Here’s an excerpt of a10046 trace file showing the resmgr:pq queued event:PARSING IN CURSOR #47898436021000 len=73 dep=0 uid=0 oct=3 lid=0 tim=1301966072332694hv=3186480617 ad='2cd2d1cb8' sqlid='bgcmmcyyyvpg9'select /*+ parallel (a 16) */ avg(pk_col) from kso.skew3 a where col1 > 0END OF STMTPARSE #478:c=2000,e=1572,p=0,cr=0,cu=0,mis=1,r=0,dep=0,og=1,plh=1404581711,tim=130WAIT #478: nam='resmgr:pq queued' ela= 65102047 location=1 =0 =0 obj#=523 tim=130WAIT #478: nam='enq: KO - fast object checkpoint' ela= 258 ... obj#=523342