Re: Reports Performance

Joanie,
  By any chance is there a 'for update' on the select?

  I occasionally have a report die during a run where the cursor definition has a 'for update' and the next run will hang waiting to get a lock.

joanie_at_raisovich.net (joanie) wrote in message news:<26173f0b.0209270621.47b36565_at_posting.google.com>...
> I'm using a rather complex SQL script (it includes 3 functions and
> some calculations). We're searching about 4000 records, and it runs
> fine under SQL.
>
> However, it won't run under Oracle Reports Builder. I'm using a
> Select statement with a Where and Order By, but the report is never
> produced (I've let it run for a LONG time, and nothing happens).
> However, if I limit the number of rows, then the report works, and I
> get the correct info. I just can't run the report on the whole set of
> data.
>
> Since I'm new to Reports, can anyone give me some troubleshooting
> advice? I've tried the Trace tool in Reports, but it doesn't seem to
> be returning meaningful results. If I limit the number of records to
> look at (rownum < whatever) and time the resulting report that's
> produced, the trace times don't even come close to matching.
>
> I know I'm missing something here.
Received on Wed Oct 09 2002 - 22:21:29 CEST