I have posted the same few days back but due to somereason it was not showing so posting again. Please ignore if this is duplicate.
Some of our stored procedures started timing out with reason code 00D3003B on z/OS. I have looked at the IDTHTOIN is set to 1800 seconds. We are using DB2 version V10NF. Recently we have changed the stored procedures to use temporary tables. Returning result sets from a temporary table but still getting deadlock. Can any one suggest a fix to this problem? These procedures are being called from Java.
I googled it but did not find the solution. Please someone help to resolve this.
Below is issue details from DB2 master log:
09.48.35 STC12001 DSNI031I #XTD1 DSNILKES - LOCK ESCALATION HAS 571
571 OCCURRED FOR
571 RESOURCE NAME =<Table Name>
571 LOCK STATE = S
571 PLAN NAME : PACKAGE NAME = DISTSERV : SYSLN300
571 COLLECTION-ID = NULLID
571 STATEMENT NUMBER = 00000003
571 CORRELATION-ID = db2jcc_appli
571 CONNECTION-ID = SERVER
571 LUW-ID = GA812A2F.C0E8.D333BC43A1BC
571 THREAD-INFO = X0AVDPTP : gvx0lwasa01q.ahold : x0avdptp :
571 db2jcc_application : DYNAMIC : 944 :
09.55.19 STC12001 DSNL027I #XTD1 SERVER DISTRIBUTED AGENT WITH 900
900 RECEIVED ABEND=04E
900 FOR REASON=00D3003B
09.55.19 STC12001 DSNL028I #XTD1 GA812A30.O69E.D333BC446DC0=55151 901
901 ACCESSING DATA FOR
901 LOCATION ::<IP address>
901 IPADDR ::<IP address>
10.07.19 STC12001 DSNL027I #XTD1 SERVER DISTRIBUTED AGENT WITH 616