23   Diagnosing and Tuning Oracle Reports

As your reporting requests grow in size and complexity and your user base increases, you will need to consider streamlining your report's performance (or your report's execution time) as much as possible. This maximizes its reach and minimizes its delivery time. Consider the following essentials before you tune the performance of your reports:

Investigating some of these areas can result in significant performance improvements. Some may result in minor performance improvements and others may have no affect on the actual report performance but can improve the perceived performance. Perceived performance refers to events that contribute to the end result (measured in terms of the final output). See Section 23.7.1, "Fetching Ahead" for an example of perceived performance.

This chapter provides a number of guidelines and suggestions for good performance practices in building, implementing, and tuning individual reports. The suggestions given are general in nature and not all suggestions might apply to all cases. However, implementing some or all of the points in a given application environment should improve the performance of report execution (real and perceived).


This chapter does not address Oracle Reports deployment or scalability issues. Refer to the Oracle Reports Services Scalability white paper on OTN (http://www.oracle.com/technology/products/reports/index.html) for more information.

This chapter will help you look at your report in the broader context of:

After identifying the context of your report, you can gear the tuning process towards optimizing and minimizing:

To achieve these objectives, you should focus your tuning on the following distinct aspects of your report:

This chapter addresses these aspects in the following sections: