Re: High Concurrency Wait

From: Sanjay Mishra <"Sanjay>
Date: Thu, 30 Nov 2017 20:59:00 +0000 (UTC)
Message-ID: <>

Thanks to all. After going all advice, it was found that someone has move the data into this database using parallel which caused degree changed and so environment comes to normal after bringing the degree to 1. Thanks again for all advices which helped in troubleshooting the details Sanjay

    On Wednesday, November 29, 2017 12:26 AM, Stefan Knecht <> wrote:  

 If you're seeing that event in such high amounts, this is most likely a bug. If you are running parallel queries and those queries are using bind variables, the most likely candidate is "Bug 21834574 - Mutex contention and increased hard parse time due to ILM (segment-access tracking) checking with partitioned objects (Doc ID 21834574.8)". We actually discovered this initially and Oracle filed the initial bug on behalf of us. What you're gonna want to do is take consecutive hanganalyze and systemstate dumps. Oracle will need that to fully prove if you're hitting this bug.

If you have a test environment where you can reproduce it, you can apply patch Patch 21834574: MUTEX CONTENTION FOR PARALLEL QUERY WITH BIND VARIABLES and see if the problem goes away. Do not however, that you will always see this event to some degree. It's quite normal to see it appear in an AWR report, but it should be nowhere near the top.  Stefan

//zztat - The Next-Gen Oracle Performance Monitoring and Reaction Framework!Visit us at | Support our Indiegogo campaign at | _at_zztat_oracle

Received on Thu Nov 30 2017 - 21:59:00 CET

Original text of this message