It's all about the answers!

Ask a question

[Reporting for QM2] Can't execute reports; no data in them


Luca Sangemi (2621) | asked Feb 25 '10, 1:02 p.m.
Hello! I hope I can find some help here.
This is the scenario:
- Quality Manager 2.0.0.1fix3 with an oracle 10g instance running on a redhat 5 box
- Custom Reporting for QM 2 with oracle 11g, RIDW instance and RICM instance up, on another RH5 box
- RCR can connect to RICM, RICM (ETL), RIDW and RIDW (ETL) from IBM Cognos Administration->Configuration (using access profiles - please note that I've removed the well-known RIDW (ETL) profile, that doesn't work with oracle, and replaced it with a brand-new that works).
- XDC was set up through XML Data Configuration Lite. rqm.xdc was configured (the one in configurations folder and the other in live data folder). Anyway, if I got the point, this is useless if you decide to use the datawarehouse; but I did it
- I've deployed the latest rqm reports (allrqm.zip import done): I can see the QM folder with all the reports.

Now, the issues:
- launching the task RQMAll, it doesn't seem to finish the job... it keeps running forever
- executing any report in the quality manager folder, cognos shows the arguments page of the report, but all the boxes where one should select the arguments (e.g. project, test plan, ...) for the report are empty. No choice is allowed.
- importing a report in quality manager from cognos works, but when I execute it, the same issue occurs.

I think cognos can't populate the datawarehouse with the data, but I can't figure out how to get it working.

Any help would be appreciated.
Thank you
Luca

5 answers



permanent link
Luca Sangemi (2621) | answered Feb 26 '10, 3:38 a.m.
Today, looking for some error, I've found this in a pogo log in cognos/logs:


2010-02-26 09:10:51.761 INFO [ogo.contentmanager.coordinator.CMBootstrap] Thread-52: Dispatcher was successfully registered in Content Manager.
2010-02-26 09:15:00.225 FATAL [ com.cognos.pogo.http.ServerConnection] asyncDMSThread-1: Failed to parse multipart data java.io.IOException: Bad chunk size: DM-DBM-0724 The CM Data Source 'RIDW (ETL)'
at org.apache.commons.httpclient.ChunkedInputStream.getChunkSizeFromInputStream(ChunkedInputStream.java:288)
at org.apache.commons.httpclient.ChunkedInputStream.nextChunk(ChunkedInputStream.java:205)
at org.apache.commons.httpclient.ChunkedInputStream.read(ChunkedInputStream.java:130)
at java.io.FilterInputStream.read(FilterInputStream.java:89)
at org.apache.commons.httpclient.AutoCloseInputStream.read(AutoCloseInputStream.java:90)
at com.cognos.pogo.http.mime.MimeParseInputStream.readFromUpstream(MimeParseInputStream.java:414)
at com.cognos.pogo.http.mime.MimeParseInputStream.fillBuffer(MimeParseInputStream.java:140)
at com.cognos.pogo.http.mime.MimeParseInputStream.<init>(MimeParseInputStream.java:83)
at com.cognos.pogo.http.mime.MIMEPartParser.<init>(MIMEPartParser.java:39)
at com.cognos.pogo.http.ServerConnection.iterator(ServerConnection.java:636)
at com.cognos.pogo.bibus.BIBusCommand.execute(BIBusCommand.java:249)
at com.cognos.pogo.reportservice.ReportServerRequest.sendRequest(ReportServerRequest.java:340)
at com.cognos.pogo.reportservice.RequestInvoker.sendRequest(RequestInvoker.java:248)
at com.cognos.pogo.reportservice.RequestInvoker.invoke(RequestInvoker.java:95)
at com.cognos.pogo.dms.DMSHandler.processRequestRun(DMSHandler.java:1059)
at com.cognos.pogo.dms.DMSHandler.processRequest(DMSHandler.java:1292)
at com.cognos.pogo.dms.DMSHandler.asyncInvoke(DMSHandler.java:1864)
at com.cognos.pogo.dms.DMSAsyncService.invoke(DMSAsyncService.java:1146)
at com.cognos.pogo.async.impl.AsyncContextImpl.runRequest(AsyncContextImpl.java:180)
at com.cognos.pogo.async.impl.AsyncRequestThread.run(AsyncRequestThread.java:45)



It seems related to a "bad chunk size" of some packet sent to RIDW, I think. The task hangs up, altough cognos tells it's still running.
Any idea?

Thanks

permanent link
Luca Sangemi (2621) | answered Feb 26 '10, 5:32 a.m.
The error is changed... I've fixed the RIDW (ETL) profile, and now i get the following error:

Data Manager v8.4.27.78 -- Copyright (C) 2008 Cognos ULC, an IBM Company. All rights reserved.
COGNOS INTERNAL USE ONLY
jobstream -- start run on localhost.(none) (25-Feb-2010 10:31:11)

DM-DBM-0402 UDA driver reported the following:

UDA-SQL-0031 Unable to access the "Rational Data Warehouse" database.

UDA-SQL-0129 Invalid login information was detected by the underlying database.

ORA-01017: invalid username/password; logon denied


DM-DBM-0306 UDA driver error connecting to 'Rational Data Warehouse'.

DM-LIB-0300 Error initializing variable 'ETL_DATEID' to:
GetETLDateID( $ETL_STARTTIME ).

DM-BLD-0004 JobStream 'RQMAll' is not a valid specification.

jobstream -- failed (25-Feb-2010 12:28:02)

permanent link
Luca Sangemi (2621) | answered Mar 03 '10, 6:41 a.m.
Ok, the problem was in the Redhat/Oracle setup. Setting it up on a win2003 server with db2 made the work. Probably one can fix all the issues arising with the redhat/oracle couple, but it should take a lot of days...

permanent link
Dang En Ren (31) | answered Mar 03 '10, 9:04 a.m.
JAZZ DEVELOPER
Hello,

We had the similar issue recently on Oracle, there's a ETL fix, please refer to https://jazz.net/jazz02/resource/itemName/com.ibm.team.workitem.WorkItem/28874

Ok, the problem was in the Redhat/Oracle setup. Setting it up on a win2003 server with db2 made the work. Probably one can fix all the issues arising with the redhat/oracle couple, but it should take a lot of days...

permanent link
Luca Sangemi (2621) | answered Mar 09 '10, 9:37 a.m.
Ok, thank you, now we're using DB2, but it's very likely we'll need to get back to Oracle, so we'll take it into account.

Hello,

We had the similar issue recently on Oracle, there's a ETL fix, please refer to https://jazz.net/jazz02/resource/itemName/com.ibm.team.workitem.WorkItem/28874

Ok, the problem was in the Redhat/Oracle setup. Setting it up on a win2003 server with db2 made the work. Probably one can fix all the issues arising with the redhat/oracle couple, but it should take a lot of days...

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.