MON - Runaway Session

MON - Runaway Session

Identifying runaway sessions is one of the most important aspects of the 
database monitoring.  It will shed direct light on what's slowing your system 
down.

There are two types of metrics that can be used to identify runaway session:
  - time based metrics
  - resource based metrics

Time based metrics
-------------------
The simplest of the two - if a session remains active for X amount of time 
consider it a runaway process.

Resource based metrics
-----------------------
Here we look at the resource consumption statistics to determine if it's a 
runaway process:
   - consistent gets
   - db block gets
   - physical reads
   - db block changes


Detection Methods
------------------

   FusionCode Event
   ----------------
   Event      : RUNAWAY_PROC
   Name       : Runaway Session (IO)
   File       : SEEDMON/runprc.sh
   Agent      : Local
   Collection : No
    
      Checks for runaway processes using v$session can drill down to APPS
      request or APPS forms connection.
      
      Report only sessions with high resource consumption rate
      (consistent gets, db block gets, physical reads, db block changes)
      that ran for longer than predefined threshold (see parameters)
      
      REPORT ATTRIBUTES:
      -----------------------------
      sid
      serial#
      username
      program
      module||' '||action
      
      
      PARAMETER       DESCRIPTION                                         EXAMPLE
      --------------  --------------------------------------------------  --------
      RUN_THRES       < v$session.last_call_et (in minutes)               60
      
      APPS_TYPE       Set this parameter if APPS related session details  11i
                      are nessesary.  Allowable values are - "11i"
      

   FusionCode Event
   ----------------
   Event      : RUNAWAY_PROC2
   Name       : Runaway Session (TIME)
   File       : SEEDMON/runprc2.sh
   Agent      : Local
   Collection : No
    
      Checks for runaway processes using v$session can drill down to APPS
      request or APPS forms connection.
      
      Report ALL sessions that ran for longer than predefined threshold
      (see parameters)
      
      REPORT ATTRIBUTES:
      -----------------------------
      sid
      serial#
      username
      program
      module||' '||action
      
      
      PARAMETER       DESCRIPTION                                         EXAMPLE
      --------------  --------------------------------------------------  --------
      RUN_THRES       < v$session.last_call_et (in minutes)               60
      
      APPS_TYPE       Set this parameter if APPS related session details  11i
                      are nessesary.  Allowable values are - "11i"

Example of Event trigger output

.