Database Tuning (MOSC)

MOSC Banner

WAITED TOO LONG FOR A ROW CACHE ENQUEUE LOCK!

edited May 24, 2009 8:31PM in Database Tuning (MOSC) 3 commentsAnswered
Hello,

To Summarize:

I received an alert from my Production Server where the scheduled DBMS JOB was stuck and with the error on alert log " WAITED TOO LONG FOR A ROW CACHE ENQUEUE LOCK! pid=21".

I have checked the corresponding "jobxxx" trace file and found the error on dc_sequence.

Searched metalink and also googled, my bad luck i could not get a clue apart from "increasing the cache of the sequence" that the job uses.

But then the alter command also was stuck with no progress(hung). Since to let the way for the forthcoming scheduled jobs, i had happened to kill the session.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center