Database - RAC/Scalability (MOSC)

MOSC Banner

enq: TM - contention

edited Dec 10, 2015 10:02AM in Database - RAC/Scalability (MOSC) 2 commentsAnswered

"Drill down into individual sessions showing high waits to understand which application code , which objects, and which SQL/s are involved in the waits. ASH reports for sessions showing high "enq: TM - contention" wait time may help."


From "Top Event P1/P2/P3 Values" section in the ASH report (for a particular session) : I got SQL_ID, Lock_mode.

Question:

1. Should I run ASH for each individual sessions and compare the %event values - to get high "enq: TM - contention" session? (Let's say, I have ~20 sessions affected with that wait event)

2. How to identify which session caused this event in the first place?

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

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center