Publishing Reports to the Web - Downloads - Oracle

20.1.1 Performance Analysis Tools
Methodology
The first step towards tuning your report is determining where your report spends
most of its execution time. Does it spend a large portion of the time retrieving the data,
formatting the retrieved data, or waiting for run time resources/distribution? Even if
your report has the most streamlined and tuned layout possible, it may be of little
consequence if most of the time is spent in retrieving data, due to inefficient SQL.
20.1.1.1 Report Trace
Setting the report tracing option produces a text file that describes the series of steps
completed during the execution of the report. Tracing can be set to capture all events
or just specific types of events. For example, you can trace just the SQL execution or
just the layout and formatting. The trace file provides abundant information, which is
useful not only for performance tuning but also for debugging reports.
Tracing can be set for various methods of report execution, such as, both .rdf and
.jsp report definitions containing SQL and/or non-SQL data sources (for example,
XML and Text pluggable data sources).
Generating a reports trace file
To turn tracing on, do one of the following:
■ In Reports Builder:
1. Choose Program >Tracing.
2. Select the Trace Mode.
3. Select appropriate Trace Options. The trace file now logs information for the
entire Reports Builder session. Refer to Chapter 3, "Configuring OracleAS
Reports Services", for more information on Trace Options.
Figure 20–1 Reports Builder
■ In the rwbuilder.conf configuration file, specify:
Tuning Oracle Reports 20-3