Optimizing Reports That Include Thousands of Records

This topic describes how you can optimize performance for reports that include a lot of records, such as 10,000 records.

Caution: It is recommended that you do the work that this topic describes on a separate, named subsystem that only the XMLP Report server component uses. For example, reportsdatascr. If you do not do this, then the Application Object Manager (AOM) on the client might fail if it gets a large amount of data.

If a report includes a lot of records, then it is recommended that you schedule this report to run on the Oracle Publisher Server. It is also recommended that your run this report immediately. For more information, see Scheduling Reports.