Skip to content

How to Identify Key SQL Statements In Trace Files

  • by
The most important information in an Oracle trace file during debug-time is the root SQL statements that caused the dump, once you have identified the SQL, you can analyze the pattern of problems. That is, it's very useful for debugging. But the question is where can I find the SQL in a long and large trace file?

The first possible place that you might find is under the following keywords:
Current SQL Statement for this session:
SELECT ...
...

The second possible place that you might find is under the following keywords:
********************   Cursor Dump   ************************
Current cursor: 4,...
...
Cursor 1 ...
  cursor name:
SELECT ...
...
Cursor 2 ...
  cursor name:
SELECT ...
...

Furthermore, you can trace the calling stacks from "Cursor Dump" and may identify the problematic objects.

Leave a Reply

Your email address will not be published.