4

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
or 
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 11.2.0.1 to 11.2.0.3.

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

0

2 Answers 2

1
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?

0

It is a bug, please refer

Bug 14283239 - High CPU/IO for dictionary SQL against SYSAUTH$ (Doc ID 14283239.8)

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.