Publishing Reports to the Web - Downloads - Oracle

Methodology
Viewing the generated the trace file helps you determine the actual time spent in
fetching data versus the time spent in formatting the report. This helps you to identify
performance bottlenecks.
The following command line example generates a trace file, containing performance
trace information, and replaces any previously existing trace file:
rwrun module=emp.rdf userid=scott/tiger@orcl destype=file desformat=pdf
desname=emp_pdf.pdf traceopts=trace_prf tracemode=trace_replace
tracefile=emp_tr.txt
Following is the outline of the information output to the emp_tr.txt trace file.
Example 20–1 Reports Builder
+------------------------------------------+
| Report Builder Profiler statistics |
+------------------------------------------+
Total Elapsed Time: 8.00 seconds
Reports Time: 7.00 seconds (87.50% of TOTAL)
ORACLE Time: 1.00 seconds (12.50% of TOTAL)
UPI: 0.00 seconds
SQL: 1.00 seconds
TOTAL CPU Time used by process: N/A
Table 20–1 Reports Builder
Field Description
Total Elapsed Time Time spent in executing the report.
Reports Time Time spent in formatting the retrieved data. Also displayed as
a percentage of Total Elapsed Time.
ORACLE Time Time spent in retrieving the data. Also displayed as a
percentage of Total Elapsed Time.
UPI SQL queries only. Time spent in establishing a database
connection, then parsing and executing the SQL.
SQL Time taken by the database server to fetch the data (percent of
time spent executing SRW.DO_SQL() statements, EXEC_SQL
statements, PL/SQL cursors, and so on.)
Note: If your data source is a non-SQL data source such as Text or
an XML pluggable data source, the values for ORACLE Time, UPI,
and SQL display as 0.
In Example 20–1, focus your tuning efforts on formatting (Reports Time) the data
rather than on querying and fetching it.
20.1.1.2 Efficient SQL
Oracle Reports uses SQL to retrieve data from the database.
Note: Oracle Reports uses SQL for non-PDS queries only.
Inefficient SQL can cripple performance especially in large reports. Thus, anyone
tuning Oracle Reports must have a good working knowledge of SQL and understand
Tuning Oracle Reports 20-5