Error while execution of Report Definition in one environment while it works fine on another
I have a report definition rule in two environments the Dev3 region and the Dev8 region.
The rules executes fine (both while running standalone as well as from the Report Browser) on Dev3 environment but it throws up the error "Retrieving the report data exceeded the limit of 30 seconds. Please try making the report more specific by further limiting which rows to include." on Dev8 on most occasions. It runs on Dev8 a few times and other times it fails while it NEVER fails on Dev3 the other environment. Both the environments have similar data volume,same JVM params and same Hotfixes etc
The rule is in same ruleset version for both environments and are exactly in sync.
Already tried Revalidate and Save on the problematic env but to no avail.
Any suggestions on the next steps??
Accepted Solution
LTIMindtree
CA
Hi Joe,
Thanks for the inputs! However, in our case both the environments had absolutely same level of data (both were refreshed from PROD) and we tried that approach at first.
Finally, truncating cache tables in the database resolved the issue.
Pegasystems
IN
There are multiple reasons why a query might timeout in one environment and not in another
1) Indices might need rebuild
2) Statistics are out of date
3) Tables are more fragmented
4) The database configuration is different for both environment including memory and hardware
5) Query plans are different in both environments.
I suggest you involve your DBA to see why there is a difference in the query execution assuming the query is exactly the same in both environments (please compare the queries for sure).
Murex
LB
Hello Bidyun,
We had a similar case with a certain report. The issue turned out to be that on the Dev environment on which the error was happening, the number of records being processed by the report was extremely large due to the addition of dummy data for testing. As such, the report timed out after trying for more than 30 seconds to retrieve all of the results.
To make sure this is the case, you can add another filter to the report, to limit the number of results returned. If this works, then you know what your problem is. If it doesn't, then we'll have to take a closer look at what's going on.
Let us know if this helps.
Thanks,
Joe
Accepted Solution
LTIMindtree
CA
Hi Joe,
Thanks for the inputs! However, in our case both the environments had absolutely same level of data (both were refreshed from PROD) and we tried that approach at first.
Finally, truncating cache tables in the database resolved the issue.