What db-ressources are significant while runtime parsing queries in reports

Question

I have long idle time in running a report
what db-ressources are significant
while running Report
Report compiling / Query parsing ?
i have running the same report from a AS 10g
in identical schema's
on two different instances ( TEST and PROD )
on a R11_2 orcale-db
in TEST-Instance the report does run well in some seconds
in PROD-Instance the report need more then 10 min
to analyze it I have trace_all on AS
and taken outputs in all triggers in the report
I can see,
the idle-time in the long-time report is between
the AFTER_PARAM_FORM - Trigger
and
the BEFORE_REPORT - Trigger
trace detail:
[2011/6/22 0:9:25:115] State 56016 (JobManager:updateJobStatus): Job 76089 status is: Bericht Before-Report-Trigger wird ausgeführt wird
ausgeführt
[2011/6/22 0:9:25:115] Debug 50103 (JobManager:updateJobStatus): Finished updating job: 76089
idle Time
[2011/6/22 0:20:17:459] State 56016 (JobManager:updateJobStatus): Job 76089 status is: Bericht Seite 1 wird formatiert wird ausgeführt
[2011/6/22 0:20:17:459] Debug 50103 (JobManager:updateJobStatus): Finished updating job: 76089
this is while
Report is "compiled".
Queries are parsed.
because both the reports run on the same AS
and both schemas are identical
it maybe the differences come from different the instance-system-ressources
( in the TEST-Instance there is 1 or 2 users / sessions,
in the PROD-Instance there are > 100 users / sessions )
what db-ressources are significant for performance
while running Report
Report compiling / Query parsing ?
what other reason may be for the idle-time in this report ?

Answer 1

In your trace your idle time is between Before Report Trigger and the formatting of page 1. So, the activity is in the database.
Report compiling / Query parsing ?Compilation has already taken place when the report runs, so that's not it.
Parsing depends on the query. If the query exists in the SGA it shouldn't parse again. However, if you have lexical parameters the query may be different each time. Still, parsing is (never) a problem.
What remains: execution of the query. Trace the report session in the database.
I just use TOAD for monitoring a session and see which query is executing for a particular session.