Schedule report time out after 2 hrs executing

Hi, we have a report that is timing out after 2 hours execution time. We are upgrading DB2 from V8 to V9.5. For some unknown reason yet, that 1 report is failing with this error:

A database error occured. The database error text is: [IBM][CLI Driver] SQL30081N A communication error has been detected. Communication protocol being used: “TCP/IP”. Communication API being used: “SOCKETS”. Location where the error was detected: “172.26.99.40”. Communication function detecting the error: “recv”. Protocol specific error code(s): “10054”, “*”, “0”. SQLSTATE=08001 . (WIS 10901)

We are sceduling this report with XIR3. It looks like we cannot execute a report longer that 2 hours. These queries are executing OK at DB2 level (more than 2 hours)
Any idea…

JR


Jean Robert99 :canada: (BOB member since 2009-09-09)

Check the time out settings for Web Intelligence Report Server(s) and Web Intelligence Job Server(s).

Else your query itself a issue.

Thanks…


JohnJustus :us: (BOB member since 2007-06-25)

Queries are executing more than 2 hrs when using the old DB2 V8. A 2 hours timeout exist somewhere at the connection level or after.


Jean Robert99 :canada: (BOB member since 2009-09-09)

Did you checked the “Limit execution time to:” in the Controls tab of the universe properies and see how many minutes it is set to?
Thanks…


JohnJustus :us: (BOB member since 2007-06-25)

Yes, we are using the same universe connecting to different DB using a different connection. The report execute OK (more than 2 hours) on the DB2 V8 but it is timing out after 2 hours using the connection for DB2 V9.

Everything is the same. It is timing out between the connection and DB2.


Jean Robert99 :canada: (BOB member since 2009-09-09)