Wednesday, March 30, 2005
I have noticed a significant issue with the SimpleProfiler Utility, this issue is also likely to affect users of the Trace Analyzer Utility from Oracle. The issue is this, STAT lines that get emitted to the trace file after a new cursor has been parsed get associated with the new cursor rather than the cursor they refer to. This has the effect that some execution plans may be truncated whilst others may display incorrect information.
I will be working on this, but if you suspect that the execution plan that Simple profiler lists doesn't make sense or is truncated then the workaround is to run the trace file through tkprof (without the explain= option since that can also give incorrect results) and look for the plan recorded there.
0 Comments
I will be working on this, but if you suspect that the execution plan that Simple profiler lists doesn't make sense or is truncated then the workaround is to run the trace file through tkprof (without the explain= option since that can also give incorrect results) and look for the plan recorded there.
0 Comments:
Post a Comment
