reports take a long time to come up

[ArunBhatia]

I am a new developer of Business Objects reports. The person I am replacing has written some horrendous reports. Many do not come up. They have error messages like 'Internal memory error during SQL generation. (QP0002)' ; 'Connection or SQL sentence error. (DA0005)'; all of them take atleast 1/2 to 3 hours to come up. Some of course end up giving error messages. Others that do report back with data take too long to come.

Any suggestions how I can improve performance ? Most of users do have 1/2 MB of cache only (RAM) ? However, the CMS, servers, and Oracle dbs are on 1 TB of storage areas with huge 10 - 100 GB of RAM.

For each report there are many, many classes and objects, I am guessing unnecessary for that particular report.

Thanks a bunch, Arun

 

[skrandel]

If the reports take that long to open, then they are set to refresh on open. I don't know how you're going to get around this. If you can't open them, you can't edit them in order to fix them.

Steve Krandel
Intuit

 

[ArunBhatia]

Sorry, the word 'open' was incorrectly used. I am able to open it, edit it, make changes to SQL, fonts, slice and dice, look at the cube etc.

That is no problem. After I click Run then the Report takes a long time to bring back data. It keeps churning, churning, churning... I don't ever see think I saw so much time it took to get the report back in Discoverer which I have used extensively.

Thanks.

 

[skrandel]

How much data is returned by the report?

You should look at the SQL that is being generated and see if it's right.

My guess is that you're reports are generating SQL that is very inefficient.

Steve Krandel
Intuit