Oracle diagnostic events Part 5

I know I already did four blogs on events but there is more to cover.

This short post will focus on some of the  trace option and it’s components.

trace[target ]<components>

In previous post I have used example something like:

alter session set events ‘trace[sql_mon] memory=high,get_time=highres’;

where sql_mon is target of interest

Just for reference here is list of targets that I have already posted:

bind_capture  -  capturing binds

dirpath_load  – direct load

explain       -  explain plan

sql_apa       – access path analysis

sql_analyze   -  sql analyze

sql_perf      -  performance analyzer

sql_tune      -  tuning advisor

sql_mon       -  sql monitor

sql_optimizer -  optimizer

sql_planmanagement – plan management

sql_costing        – cost based analysis

sql_transform     – sql transformation

sql_execution     – sql execution

Now let’s see what other options I can use in conjuction with target.

In my previous example I have used options memory and get_time :

alter session set events ‘trace[sql_mon] memory=high,get_time=highres’;

so this command will trace in memory sql monitor on high resolution.

Here is list of all combination:

[disk=DISABLE | LOW | LOWEST | MEDIUM | HIGH | HIGHEST]

[memory=DISABLE | LOW | LOWEST | MEDIUM | HIGH | HIGHEST]

[get_time=DISABLE | DEFAULT | SEQ | HIGHRES | SEQ_HIGHRES ]

[get_stack=DISABLE | DEFAULT | ENABLED ]

These options are self explanatory.

Just a few examples:

alter session set events ‘trace[sql_mon] memory=high,get_time=highres’;

alter session set events ‘trace[sql_mon] disk=highest,get_time=highres,get_stack=default’;