Hi All,
I am having a report that needs to be burst. We are bursting report based on a Region. When set to burst, It is giving the report cut for few values only.
And then it throws the error as follows:
DPR-ERR-2056 The Report Server is not responding. Handler trace back: [the_dispatcher] com.cognos.pogo.handlers.performance.PerformanceIndicationHandler [the_dispatcher] com.cognos.pogo.handlers.logic.ChainHandler [service_lookup] com.cognos.pogo.handlers.engine.ServiceLookupHandler [load_balancer] com.cognos.pogo.handlers.logic.ChainHandler [lb_forwarder] com.cognos.p2plb.clerver.LoadBalanceHandler [batchreportservicechain] com.cognos.pogo.handlers.logic.ChainHandler [warptask_with_authenticate] com.cognos.pogo.handlers.logic.ChainHandler [do_batch_warp] com.cognos.pogo.handlers.logic.ChainHandler [warptaskmtaChain] com.cognos.pogo.handlers.logic.ChainHandler [warptaskmta] com.cognos.pogo.reportservice.BatchReportServerHandler
To solve this, I removed the unwanted query items from the queries,
The report contains 3 queries and 3 charts.
Cognos version 10.2.1
Unable to find the exact cause of this failure.
Regards
saumil287
That's your report server crashing (defect within Cognos). If you look in the /bin or /bin64 folders on your dispatcher servers you should see dump files (*.dmp). If you monitor your BI Bus process, you'll see it crash and regenerate a new process ID.
You'll need to open a case with support. They'll forward it to the DEV team, who will inspect the dump file and tell you if it's fixed in an existing FP.
In the meantime, monitor memory and check the logs for error messages happening around the time it crashed.
If you want to trouble shoot this yourself a little more, you can enable IPF RSVP tracing, although that requires some experience in inspecting these types of logs.
Hi,
CognoidJay, Thanks for quick reply,
Is it because the BIBUS process cannot handle the data or is it the memory leak issue?
The report is running fine when we set the burst properties 1. Run in parallel and query prefetch to true.
Thanks
Hi,
There are so many reasons why this could happen. The only way to really know what caused it is to inspect the dump file using a utility. This is usually something Cognos Support will ask of from the Cognos development team.
It's interesting that it runs fine with query prefetching. Have you monitored the BI BUS process? Are you hitting memory limits when the crash occurs?
Create a test and hard code a filter on two regions in your report so you only burst out two copies. Does the issue still occur? This can help you narrow down the issue further (memory capacity issue vs some sort of product defect).