
Hang/Locking > Identify the Issue > Overview
To properly identify the issue we want to resolve, we must do three things:
● Recognize a query hang or locking issue
● Clarify the details surrounding the issue
● Verify that the issue is indeed the problem.
Recognize a Hang or Locking Issue
What is a Hang or Locking issue?
A "true" database hang issue can manifest itself as:
● A database that is no longer allowing users to connect
● A database that is no longer performing work
● Select 1 from dual does not produce output
● Create table does not complete
A locking issue can manifest itself as:
● One or more sessions that have completely stopped functioning
You might have identified the hang or lock from:
● benchmarking/testing
● user complaints
● systemstate or hanganalyze showing stuck sessions
● a query appearing to hang
● session consuming a large amount of CPU
● ORA-60 errors appearing in the alert log
These problems might appear after:
● schema changes
● changes in database parameters
● changes in application
● database upgrades
Clarify the Issue
A clear problem statement is critical. You need to be clear on exactly what the problem is. It may be that in
subsequent phases of working through the issue, the real problem becomes clearer and you have to
revisit and re-clarify the issue.
To clarify the issue, you must know as much as possible of the following:
● The affected users
● The sequence of events leading up to the problem
● Where/how it was noticed
● The significance of the problem
● What IS working
● What is the expected or acceptable result
● What have you done to try to resolve the problem
As an example:
● Many sessions do not appear to be completing the requests that were made
● It was noticed by end users.
Notes
● ODM Reference: Identify the Issue
How-To
● How to Identify Resource Intensive
SQL for Tuning
Case Studies
● Resolving High CPU usage in Oracle
Servers
Oracle Performance Diagnostic Guide (Version 3.20) - Hang/Locking 09/11/2012
评论