'Configuration' wait class in AWR report [message #639296] |
Sun, 05 July 2015 07:22 |
karthik4u
Messages: 36 Registered: September 2006 Location: CHENNAI
|
Member |
|
|
In AWR report I could find this 'Configuration' wait class leads in Foreground Wait Class.
There it has Avg wait(ms) as 1414.63 and %DB time as 37.29.
Please explain what does it mean? How to reduce this ?
|
|
|
Re: 'Configuration' wait class in AWR report [message #639297 is a reply to message #639296] |
Sun, 05 July 2015 07:25 |
John Watson
Messages: 8951 Registered: January 2010 Location: Global Village
|
Senior Member |
|
|
If you upload the entire report, I'm sure I can spot the problem. It is usually pretty obvious. You do need to fix it, 37% of your DB Time is a lot to be losing.
I can't remember the limitations for file upload, you may have to zip it (and perhaps rename the .zip suffix to something else).
|
|
|
|
|
Re: 'Configuration' wait class in AWR report [message #639300 is a reply to message #639298] |
Sun, 05 July 2015 08:29 |
John Watson
Messages: 8951 Registered: January 2010 Location: Global Village
|
Senior Member |
|
|
Not as obvious as I had hoped - but I think one can make a few observations.
Most of the Enq: HW events appear to be inserting or updating LOBs. Is your tablespace TESTDISTDATA using ASSM, or freelists? Are your LOBs, particularly those in FBNK_RC_DETAIL, basicfile or securefile LOBs?
You are getting a lot waits on commit. If you set COMMIT_WAIT=NOWAIT and COMMIT_LOGGING=BATCH, you may get an immediate performance boost. Though you would need to be aware of yhe implications for recoverability.
But before any of this, do you actually have a performance problem? Can you identify the statement, or business process, that is in trouble?
|
|
|