ORADEBUG DOC EVENT

To list the event level internal documentation commands use ORADEBUG DOC EVENT:

ORADEBUG DOC EVENT NAME
ORADEBUG DOC EVENT SCOPE
ORADEBUG DOC EVENT FILTER
ORADEBUG DOC EVENT ACTION

In Oracle 12.1.0.2 output is:

SQL> ORADEBUG DOC EVENT

Event Help:
***********

  Formal Event Syntax
  --------------------
       ::= ' []
                                   []
                                   []
                                   []
                                   [off]'

         ::= []

      ::= [: scope_parameters]

     ::= {: filter_parameters}

           ::= (action_parameters)

     ::=  = [|][, ]

    <*_parameters> ::=  = [, ]


  Some Examples
  -------------
    * Set event 10235 level 1:
      alter session set events '10235';

    * Set events SQL_TRACE (a.k.a. 10046) level 1:
      alter session set events 'sql_trace';

    * Turn off event SQL_TRACE:
      alter session set events 'sql_trace off';

    * Set events SQL_TRACE with parameter  set to 'never'
      and parameter  set to 'true':
      alter session set events 'sql_trace wait=true, plan_stat=never';

    * Trace in-memory the SQL_MONITOR component (the target) and all its
      sub-components at level high. Get high resolution time for each
      trace:
      alter session set events 'trace[sql_mon.*] memory=high,
                                                 get_time=highres';

    * On-disk trace PX servers p000 and p005 for components 'sql_mon'
      and 'sql_optimizer' (including sub-components) at level highest:
      alter system set events 'trace[sql_mon | sql_optimizer.*]
                            {process: pname = p000 | process: pname=p005}';

    * Same as above but only when SQL id '7ujay4u33g337' is executed:
      alter system set events 'trace[sql_mon | sql_optimizer.*]
                                    [sql: 7ujay4u33g337]
                            {process: pname = p000 | process: pname=p005}';

    * Execute an action immediatly by using 'immediate' for the event
      name:
      alter session set events 'immediate eventdump(system)'

    * Create an incident labeled 'table_missing' when external error
      942 is signaled by process id 14534:
      alter session set events '942 {process: 14534}
                                    incident(table_missing)';


  Notes
  -----
    * Implicit parameter level is 1 by default
      e.g. '10053' is same as '10053 level 1'

    * Event target (see [] construct) is only
      supported by specific events like the TRACE[] event

    *  and/or  are constructs
      that can be used for any event

    * Same event can be set simultaneously for a different scope or
      target but not for different filters.

    * '|' character can be used to select multiple targets, scope or
      filters.

      E.g. 'sql_trace [sql: sql_id=g3yc1js3g2689 | sql_id=7ujay4u33g337]'

    * '=' sign is optional in <*_parameters>

      E.g. 'sql_trace level 12';

    * Like PL/SQL, no need to specify the parameter name for target,
      scope, filters and action. Resolution is done by position in
      that case:

      E.g. 'sql_trace [sql: g3yc1js3g2689 | 7ujay4u33g337]'


  Help sub-topics
  ---------------

    NAME    []      List all events or describe 
    SCOPE   []      List all scopes or describe 
    FILTER  []     List all filters or describe 
    ACTION  []     List all actions or describe