V$HANG_INFO displays information about hangs found on the cluster. A hang can be an open wait chain or closed wait chain (cycle or deadlock). A wait chain is a series of sessions that are blocking one another. Each row represents a hang and describes how severe the hang is. This view also includes the victim or final blocker of the hang.
A number identifying the hang
Indicates how many sessions are in the main wait chain of the hang
Indicates how many total sessions are affected by the hang, including the main wait chain and any wait chains branching off of the main wait chain
Is set to Hang if this is an open wait chain, or Deadlock if this is a cycle or closed wait chain?
Date and time that the hang was detected
Time that the hang may be automatically resolved
Y - The hang was ignored and will not be automatically resolved at this time
N - The hang has not yet been verified
Y - An attempt was made to resolve the hang
N - No attempt was made to resolve the hang
Y - The hang spans multiple nodes in the cluster
N - All of the sessions in the hang reside on a single instance
Y - An attempt was made to resolve the hang but was unsuccessful, and the hang is becoming more severe. Another resolution attempt will be made.
N - The first resolution attempt was successful and it was not necessary to escalate the hang to a higher resolution level.
Contains the reason why the hang was resolved or ignored
Instance number of the instance on which the victim or final blocker session resides
Victim or final blocker's Oracle session ID
Victim or final blocker's Oracle session serial number
Victim or final blocker's operating system process ID
Y - Victim or final blocker is a critical background process
N - Victim or final blocker is not a critical background process
Resource or event for which the victim or final blocker is waiting; set to not in a wait if the session is not waiting on a resource