IBM Support

SQL30081N due to lack of coordinate agent

Troubleshooting


Problem

The applications receives SQL30081N intermittently.

Symptom

Db2 client reports error messages as below:
AIX client: 
2020-04-03-02.43.21.116413+480 I3048483A366         LEVEL: Warning
PID     : 54133194             TID : 7197           PROC : myapp
INSTANCE: db2inst1             NODE : 000
HOSTNAME: hostname1
EDUID   : 7197
FUNCTION: DB2 UDB, DRDA Application Requester, sqljrIsSqlcodeGoodForCR, probe:40
DATA #1 : String, 47 bytes
Client timeout exceeded, can not go for retry. 

2020-04-03-02.43.21.116578+480 I3048850A840         LEVEL: Info
PID     : 54133194             TID : 3856           PROC : myapp
INSTANCE: db2inst1             NODE : 000
HOSTNAME: hostname1
EDUID   : 3856
FUNCTION: DB2 UDB, DRDA Application Requester, sqljrDrdaArConnect, probe:400
MESSAGE : ZRC=0x8136001A=-2127167462=SQLJC_ERROR_TIMEOUT "CONNECTION TIMED OUT"
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
 sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -30081   sqlerrml: 55
 sqlerrmc: 2 * * TCP/IP SOCKETS 144.14.20.11 selectForRecvTimeout 
 sqlerrp : SQLJCMN 
 sqlerrd : (1) 0x8136001A      (2) 0x0000001A      (3) 0x00000000
           (4) 0x00000000      (5) 0x00000000      (6) 0x00000000
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6)    
           (7)      (8)      (9)      (10)        (11)     
 sqlstate:
Linux client: 
2020-04-03-02.43.37.777232+480 I61581103E355         LEVEL: Warning
PID     : 4028                 TID : 46913701300864  PROC : db2bp
INSTANCE: db2inst2             NODE : 000
HOSTNAME: hostname2
FUNCTION: DB2 UDB, DRDA Application Requester, sqljrIsSqlcodeGoodForCR, probe:40
DATA #1 : String, 47 bytes
Client timeout exceeded, can not go for retry. 

2020-04-03-02.43.37.777591+480 I61581459E831         LEVEL: Info
PID     : 4028                 TID : 46913701300864  PROC : db2bp
INSTANCE: db2inst2             NODE : 000
HOSTNAME: hostname2
FUNCTION: DB2 UDB, DRDA Application Requester, sqljrDrdaArConnect, probe:400
MESSAGE : ZRC=0x8136001A=-2127167462=SQLJC_ERROR_TIMEOUT "CONNECTION TIMED OUT"
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
 sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -30081   sqlerrml: 57
 sqlerrmc: 115 * * TCP/IP SOCKETS 144.14.20.11 selectForRecvTimeout 
 sqlerrp : SQLJCMN 
 sqlerrd : (1) 0x8136001A      (2) 0x0000001A      (3) 0x00000000
           (4) 0x00000000      (5) 0x00000000      (6) 0x00000000
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6)    
           (7)      (8)      (9)      (10)        (11)     
 sqlstate:
Sometimes, a very simple SQL will take unexpected long time to complete: 

$ time db2 "SELECT CURRENT TIMESTAMP FROM SYSIBM.SYSDUMMY1"

real	0m10.399s
user	0m0.017s
sys	0m0.010s

Document Location

Worldwide

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"ARM Category":[{"code":"a8m500000008PkdAAE","label":"Connectivity"},{"code":"a8m500000008PkqAAE","label":"Performance"}],"ARM Case Number":"TS003501253","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Version(s)","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
01 May 2025

UID

ibm16206794

Page Feedback