Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

The database is hanging randomly (with some leniency I would say almost each hour). Top session is:

select privilege#
from sysauth$
where (grantee#=:1 or grantee#=1) and privilege#>0
select /*+ connect_by_filtering */ privilege#, level
from sysauth$ connect by grantee#=prior privilege# and privilege#>0 
start with grantee#=:1 and privilege#>0

In ash I saw these top wait events:high concurrency on event library cache: mutex X and latch: shared pool

This problem occurred after upgrading from to

These queries are almost always in top sessions but the wait event when the database is not hanging is CPU. In they didn't appear. We are using DRCP.

share|improve this question

migrated from Jan 6 '12 at 15:40

This question came from our site for professional and enthusiast programmers.

going to post it also in serverfault, but it should apply in both, might be something the code is generating against the new version, or the new version by itself – capi Jan 6 '12 at 13:26
@capi Please don't cross post, you can flag for migration – Sathya Jan 6 '12 at 14:56
select privilege#
from sysauth$
where (grantee#=:1 or grantee#=1) and privilege#>0

That SQL is executed as a user authenticates to the database upon login. This is mentioned in support doc 730066.1

Is there a storm of logins happening periodically?

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.