Method R Discussion GroupMethod R helps developers, DBAs, and decision-makers optimize Oracle-based software in every phase of the software life cycle. |
||
Discuss Method R products, techniques, and events. Ask new questions or post your own responses. |
In the readme.txt
"The BEGIN_TASK call checks to see whether someone has expressed the intent to trace by calling HOTSOS_ILO_TASK.SET_TRACE(TRUE)." This doesn't work as the package specification for HOTSOS_ILO_TASK has a get_trace but no set_trace. How does one enable tracing for another session? Also, is the set_trace(true) required to turn on the setting of action, client_info and module via the HOTSOS_ILO_TASK.BEGIN_TASK calls?
Toby,
You are correct there is no SET_TRACE function. The intent to begin tracing is set by calling the SET_CONFIG() procedure, who's signature is: PROCEDURE set_config ( TRACE IN BOOLEAN, write_wall_time IN BOOLEAN ); The idea is that you call this procedure from your application when a "debug" flag is set by the user (or by some "higher authority"), causing the ILO package to begin emitting trace data. The BEGIN_TASK call *WILL* set the Module and Action using the DBMS_APPLICATION_INFO regardless of whether trace data is actually being emitted. Therefore you should be able to see the Module and Action of all instrumented tasks show up in the V$* tables. If you are wanting something outside of the application you are instrumenting to be able to influence whether a task is traced, then an easy way to do that might be to modify the BEGIN_TASK procedure code to look at a table for a flag. The table might look like CREATE TABLE TRACE_ME ( MODULE VARCHAR2(256), ACTION VARCHAR2(256), TRACE VARCHAR2(1) ); Then the BEGIN_TASK procedure could check to see if the MODULE/ACTION pair is "designated for trace" by checking the table. Hope this helps!! |
Powered by FogBugz