Migration from CRN to Cognos8 caused aggregation errors

[jimruddy]

To All Cognos gurus!
(This is my first post.)

When we migrated from ReportNet MR 2 to Cognos 8 MR1 several aggreation errors occured. Some fields were doubled and some summations just repeated the final number in a total column. Also, some reports, even though validated in Report Studio, were not able to be run and caused large handler errors, such as the following:
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

Have they things happened to any other upgraders?


Thanks for your response


Jim

[shaadi007]

Please can anyone suggest some solution even I am facing the same problem...Thnx

[COGNOiSe administrator]

Form my experience, bunch of reports had to be recreated from scratch as they did not upgrade well.

[goose]

When we upgraded from ReportNet to Cognos 8.1 a large portion of our reports bombed out. We even had Cognos support have a look but we ended up having to rewrite them. My advice to you is dont waste to much time trying to get them to upgrade rather just rewrite them.

[JGirl]

If you're lucky you might be able to alter the query properties (change it from auto group & summarise = yes to auto group & summarise = no) and fix some of the reports that have aggregation errors, but for the rest, I hope you like rewriting :)