How can you analyze an existing trace file to list the almost resource-intensive statements, aggregation of statistics, and to either exclude recursive call details?

Question

Options

• ABy using the DBMS_TRACE package
• BBy using the EXPLAIN PLAN command
• CBy enabling the SQL_TRACE parameter for the session
• DBy using the TKPROF utility
• EBy using the TRCSESS utility

• A
  12% (7)
• B
  5% (3)
• C
  2% (1)
• D
  78% (45)
• E
  3% (2)

Explanation

D: You can run the TKPROF program to format the contents of the trace file and place the output into a readable output file. TKPROF can also: * Create a SQL script that stores the statistics in the database * Determine the execution plans of SQL statements TKPROF reports each statement executed with the resources it has consumed, the number of times it was called, and the number of rows which it processed. This information lets you easily locate those statements that are using the greatest resource. With experience or with baselines available, you can assess whether the resources used are reasonable given the work done. A: DBMS_TRACE provides subprograms to start and stop PL/SQL tracing in a session. Oracle collects the trace data as the program executes and writes it to database tables. A typical session involves: Starting PL/SQL tracing in session (DBMS_TRACE.SET_PLSQL_TRACE). Running an application to be traced. Stopping PL/SQL tracing in session (DBMS_TRACE.CLEAR_PLSQL_TRACE). E: The trcsess utility consolidates trace output from selected trace files based on several criteria: After trcsess merges the trace information into a single output file, the output file could be processed by TKPROF

No community discussion yet for this question.