From our Statspack report, approx 30% of DB time accounts to "connection management call elapsed".
From our Statspack report, approx 30% of DB time accounts to "connection management call elapsed".
What is Connection Management Call Elapsed Wait and How to Improve It (Doc ID 1936329.1)
The solution is not very helpful.
"Review the application code and discuss with developers or application team to see if connection caching can be used. This is usually done through the middle tier of the application. Application coding is beyond the scope of database performance team."
In E-Business 12.2, Weblogic has a connection pool.
Has anybody tuned the parameters?
Should I be increasing initial and minimum capacity?
Statement cache size is 0 which means not being used. Should we set this?
0