We have some trouble with timeout situations like this:
an application program (using static sql) terminated because of a DB2 timeout (SQLCODE -911, reason code 68) when trying to open this cursor:
DECLARE WHTR016T-CUR CURSOR WITH HOLD FOR
ORDER BY BUCHG_ID,
When this error occured, no other process accessed the table.
Does anybody have an idea, why timeouts like this occur?
Are there other resources (apart from the table) which could have been locked, so that this timeout occured?
For future timeouts: how do we collect some detailed information about these situations?
Edit 29.06.2010, 15.09h: I just found out that an automatic rebind of the package took place right after we (successfully) restarted the process. If this rebind was also tried after we started the program the first time, could a non-successful rebind be the reason for this error?