Skip to Main Content
Forums

Oracle Database Discussions

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

resmgr:cpu quantum

530393Aug 6 2007 — edited Aug 7 2007
A one time set of conditions caused every connected session to show a wait event of resmgr:cpu quantum. This resulted in all new session requests timing out in the listener and all existing sessions to list resmgr:cpu quantum. This occurred to all sessions, even ones which were not in the same resource consumer group.

The trigger for this observed behavior was none of the causes listed in note 392037.1.

I've investigated sys.dba_hist_active_sess_history, but I can't seem to find a good _hist table which shows which resource group or plan which was being applied when the resmgr:cpu quantum event was being observed on the session.

Is there a historical location to find out which consumer group was being applied to a session?

Is there a problem with a consumer group being on multiple plans?

Thank You.

Comments

Processing
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Sep 4 2007
Added on Aug 6 2007
#general-database-discussions
4 comments
1,014 views