Skip to end of metadata
Go to start of metadata

x_cons <database_name> show suspends

Shows the reasons why tasks have been suspended.

List of suspend reasons:
========================

total suspends:  832920

Vwait          :      20 (   0.00% ) k53wait
TableRootShare :       1 (   0.00% ) bd13GetNode
InvRootExcl    :       7 (   0.00% ) bd13GetNode
InvRootShare   :      11 (   0.00% ) bd13GetNode
InvNodeExcl    :    2019 (   0.24% ) bd13GetNode
InvNodeShare   :     353 (   0.04% ) bd13GetNode
ObjRootExcl    :  615967 (  73.95% ) bd13GetNode
ObjRootShare   :     631 (   0.08% ) bd13GetNode
ObjNodeExcl    :   41672 (   5.00% ) bd13GetNode
ObjNodeShare   :   50187 (   6.03% ) bd13GetNode
HistRootExcl   :      57 (   0.01% ) bd13GetNode
IOWait(R)(041) :       2 (   0.00% ) b13get_node: await read              :-(
IOWait(W)(044) :      27 (   0.00% ) b13pfree_pno                         :-(
PagerWaitWritr :       6 (   0.00% ) Pager_Controller::WaitForPagerWritReply
SVP-LogW (211) :       2 (   0.00% ) Log_Savepoint::WaitForLogQueueFlush
SVP-End  (230) :      24 (   0.00% ) Log_SavepointSync::LockSVPSyncEntry
LogIOwait(234) :   33628 (   4.04% ) Log_Queue::UserTaskEOTReady
SVP-wait (243) :       1 (   0.00% ) Log_Savepoint::StartSavepointAndWait
No-Work  (255) :   88305 (  10.60% ) Task is waiting for work


There are special Vsuspend wait situations that are displayed under their own names. The following list shows the most important of these states.

  • TableRootExcl: TableRootExcl can occur while accessing B* trees that represent permanent data. A task is trying to set an exclusive lock on the root page of a B* tree but has to wait due to a lock collision. Tasks request exclusive locks on B* trees for structure-changing operations such as tree balancing, among other operations.
  • TableRootShare: TableRootShare can occur while accessing B* trees that represent permanent data. A task is trying to set a shared lock on the root page of a B* tree but has to wait due to a lock collision. As a rule, all operations on a B* tree begin with a shared lock, which is refined as the operation descends into the B* tree, that is it is extended to become an exclusive or shared lock on the leaf level.
  • TableNodeExcl: TableNodeExcl can occur while accessing a node in a B* tree that represent permanent data. A task is trying to set an exclusive lock on the leaf node of a B* tree but has to wait due to a lock collision.
  • TableNodeShare: TableNodeShare can occur while accessing a node in a B* tree that represent permanent data. A task is trying to set a shared lock on the leaf node of a B* tree but has to wait due to a lock collision.
  • InvRootExcl: InvRootExcl can occur while accessing B* trees that represent an index. A task is trying to set an exclusive lock on the root page of a B* tree but has to wait due to a lock collision. The task is waiting for an exclusive lock on the index root page.
  • InvRootShare: InvRootShare can occur while accessing B* trees that represent an index. A task is trying to set a shared lock on the root page of a B* tree but has to wait due to a lock collision. It is waiting for a shared lock on the index root page.
  • InvNodeExcl: InvNodeExcl can occur while accessing B* tree that represent an index. A task is trying to set an exclusive lock on a leaf page of a B* tree but has to wait due to a lock collision. It is waiting for the exclusive lock on an index node.
  • InvNodeShare: InvNodeShare can occur while accessing B* tree that represent an index. A task is trying to set a shared lock on a leaf page of a B* tree but has to wait due to a lock collision. It is waiting for the shared lock on an index node.
  • TempRootExcl: TempRootExcl can occur while accessing B* tree that represent temporary data. It is waiting for an exclusive lock on the root page of a B* tree.
  • TempRootShare: TempRootShare can occur while accessing B* tree that represent temporary data. It is waiting for a shared lock on the root page of a B* tree.
  • ObjRootExcl: Waiting for the exclusive lock on an object root ( for page chains in SAP liveCache)
  • ObjRootShare: Waiting for the shared lock on an object root ( for page chains in SAP liveCache)
  • ObjNodeExcl: Waiting for the exclusive lock on an object node ( for page chains in SAP liveCache)
  • ObjNodeShare: Waiting for the shared lock on an object node ( for page chains in SAP liveCache)
  • HistRootExcl:Exclusive lock on the root of history page
  • IOWait(R) (041) : Waiting for a page that is currently read from disk by another session
  • IOWait(R) : Waiting for own I/O to be done
  • PagerWaitWriter: Waiting for pager write
  • SVP_LogW (211): Waiting for log queue flush
  • SVP-End (230): Waiting for savepoint to be finished
  • LogIOwait (234): Waiting for log I/O
  • SVP-wait(243): Start savepoint and wait
  • DC OvFlow: Data cache is operating at capacity and cannot accept any new data. Only when pages have been written from the data cache to the volumes, the data cache can accept new pages. If you frequently observe DC OvFlow states, check whether your data cache is large enough or the I/O system is too slow.
  • LogQ FULL: Log queues are operating at capacity and cannot accept any new redo log entries. Only when the log writer has written data from the log queues to the log area, the log queues can accept the log entries again. If you frequently observe LogQ FULL states, check whether your log queues are too small or the I/O system is too slow.
  • DB FULL: Data area is full and cannot accept any more pages. Add a new data volume.
  • NO-Work: Task is waiting for work

back to top