I am writing this on the chance that someone out there has come across this issue. It's a little hard to reproduce because the problem seems to be happening intermittently.

We have an internal customer who has some users writing their own queries using Report Assistant. Often when they run a query, the result set will be truncated. They can run it once and get a certain number of rows, and run it immediately again and get a completely different number of rows returned, without changing anything at all about the query.

In every example they have been targeting the output to Excel (EXL2k). The data source is not changing (it's not a transactional d/b, it's a datamart that is updated overnight).

I reproduced this myself in their QA environment. I created their query. The first time I ran it, I received 35,819 rows back. The second time I ran it, I received 589 rows back. 3rd & 4th time each produced 35,819 rows again. One thing I DID notice on the second run was that Excel seemed to hang a bit before opening the file. The user said that he had experienced the hanging before with Excel, but could not say with certainty that it always coincided with a truncated results set.

I'm just wondering if there is anyone in the user community who has experienced similar quirkiness when writing and running queries with Report Assistant?

Our customer is on WF 7.6.4 on an AIX platform.

Regards,

Deborah Sullivan
deborah.a.sullivan@fmr.com
Fidelity Investments

This message has been edited. Last edited by: Kerry,

I would try running the report in HTML format first. If you see inconsistencies, view the source - there may be a WebFOCUS or DB error message that might point to the problem.

Thanks for your reponse. I just ran my QA version and targeted a HTML output. Ran it with an ECHO and there were no errors under the covers.

Regards,

Deborah Sullivan
deborah.a.sullivan@fmr.com
Fidelity Investments

But you should run the report repeatedly to see if you get the same inconsistencies as when running as Excel 2000 format. If there are no inconsistencies when running as HTML, perhaps something on the server causing WebFOCUS to not all the rows.

you might want to invoke an ON TABLE HOLD FORMAT EXL2K and re-direct the output with an APP FI command and determine if the problem is on the reporting server side or with a caching type of issue on the App Server.