Re: Reports Tuning issues

kpram27 wrote:

> However right now I lack direct access to the Prod Database

Then how can they expect you to tune the database?

> There are very few optimizer hints being used and the reports are large
> but not using PQ etc.

Those were merely examples. However, it is a fact that execution plans can change for the _same_ query from day to day. Just as it is a fact the same execution plan can work fine one month and not work at all the next month, because of changes in data volumes.

> And the same report with the same values( or almost same) generates
> these widely varying results.

When matching performance from one process to another, we must make sure we're comparing like with like. The two having the same SQL does not mean that the two processes are indeed alike. The CBO may well just decide to using a hash join this time around (due to changes in the database) instead of a nested loop join.

> But the server Parameters seem OK and it would be better to go and check
> the Report Parsing etc.. (as you have indicated)

Lots of neat stuff in those V$ tables.. :-)

--
Billy