Publishing Reports to the Web - Downloads - Oracle

Methodology
20.1.6 Running the Report
Reports and Oracle Application Server Forms Services allows you to pass blocks of
data between the associated products and removes the need for subsequent queries.
This technique referred to as query partitioning ensures that Oracle Reports is
responsible for formatting data and ignores dynamic alteration of queries via triggers
and lexical parameters.
Passing data between Oracle Application Server Forms Services and Oracle Reports is
achieved using record groups and data parameters, in conjunction with the Run_
Report_Object built-in (for calling Oracle Reports from OracleAS Forms Services).
This is the only supported way to call Oracle Reports from OracleAS Forms Services.
Refer to the Integrating Oracle9iAS Reports in Oracle9iAS Forms white paper on OTN,
(http://otn.oracle.com), for more information on calling a report from an Oracle
Application Server Forms Services application.
Note: Unless data parameters are unreasonably large or the
queries particularly complicated, the perceived performance
improvements should be negligible. Additionally, only top level
groups in a report can accept data parameters passed from forms.
You can further affect the overall performance by setting specific runtime options:
■ Reports Builder automatically runs an error check on paper layout definitions and
bind variables. Set the runtime parameter RUNDEBUG=NO to turn off this extra
error checking at runtime.
■ For JSP report definitions, Reports Builder performs tag validation and checks for
items such as duplicate field identification or malformed attributes. This feature is
useful only during the design phase, but not in the production environment. By
default, Tag validation in OracleAS Reports Services is off. To turn this option on,
use the VALIDATETAG=YES option in your http request.
■ By default, the RECURSIVE_LOAD command line option used by both rwrun and
rwservlet commands is set to yes causing invalid external references of PL/SQL
program units to automatically recompile. Set the RECURSIVE_LOAD option to no
in a production environment, because this is useful only in a development
environment.
■ For SQL queries, Oracle Reports takes advantage of the Oracle database’s array
processing capabilities for data fetching. This allows records to be fetched from the
database in batches instead of one at a time, resulting in fewer calls to the
database. However, array processing requires more memory on the execution
platform to store the arrays of records returned. To reduce the network load
(number of network trips) in a production environment, set the value of the
ARRAYSIZE command line parameter (defined in kilobytes) to a large value.
■ Set the LONGCHUNK parameter to as large a value as possible, if your report uses
the LONG, CLOB, or BLOB data types to retrieve large amounts of data. This
reduces the number of increments taken by Oracle Reports to retrieve long values.
On an Oracle8i or Oracle9i server, use the more efficient CLOB or BLOB data
types, instead of LONG or LONG RAW.
■ If the paper layout Parameter Form is not required, set the PARAMFORM option to
NO.
Use the COPIES parameter carefully when printing to PostScript. Setting COPIES to a
value greater than 1 requires that Oracle Reports save the pages in a temporary
20-16 Oracle Application Server Reports Services Publishing Reports to the Web