Db2 Error Detected Client Termination
Contents |
(troubleshooting) Problem(Abstract) db2diag.log file may get filled with "Detected client termination" error messages. db2checkclientinterval Symptom Following errors may be seen in db2diag.log file. 2012-10-07-03.31.44.562773+480
Function: Db2 Udb, Base Sys Utilities, Sqeagent::agentbreathingpoint, Probe:16
I559988E520 LEVEL: Error PID : 2160 TID : 140574011156224PROC : db2sysc INSTANCE: db2inst1 NODE : 000
Zrc=0xfffffb95=-1131
DB : SAMPLE APPHDL : 0-4470 APPID: 202.27.30.1.2101.121006192554 AUTHID : PSOGALAG EDUID : 568 EDUNAME: db2agent (SAMPLE) FUNCTION: DB2 UDB, common communicati on, sqlcctest, probe:50
Sqlcode
MESSAGE : sqlcctest RC DATA #1 : Hexdump, 2 bytes 0x00007FD9EFFF6780 : 3600 2012-10-07-03.31.44.543149+480 I560509E538 LEVEL: Error PID : 2160 TID : 140574002767616PROC : db2sysc INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-4510 APPID: 202.27.30.1.2286.121006192634 AUTHID : PSOGALAD EDUID : 570 EDUNAME: db2agent (SAMPLE) FUNCTION: DB2 UDB, common communication, sqlcctcptest, probe:11 MESSAGE : Detected client termination DATA #1 : Hexdump, 2 bytes 0x00007FD9EF7F6748 : 3600 Resolving the problem Function sqlcctcptest() tests if the client connection is active and function sqlcctest() tests whether the connection is still valid. If you don't want such messages to be logged into db2diag.log file, you can set DB2CHECKCLIENTINTERVAL to zero. For Example : Issue following: 1) db2set DB2CHECKCLIENTINTERVAL=0 2) db2stop 3) db2start Note : This variable specifies the frequency of TCP/IP client connection verifications during an active transaction. It permits early detection of client termination, instead of waiting until after the completion of the query. If this variable is set to 0, no verification is performed. Related information APAR IC73909 Communications variables Document information More support for: DB2 for Linux, UNIX and Windows Database Objects/Config - Instance Software version: 9.1, 9.5, 9.7, 10.1 Operating system(s): AIX, HP-UX, Linux, Solaris, Windows Reference #: 1613530 Modified date: 2
SQL1042; SQL0443; unstable; DB2_MAX_THREADS_PER_FMP; IZ08425; -1042; -4304; SQL4304; Power7; ENOMEM; DIA8003C; interrupt; -952; -1224 Technote (FAQ) Question What do these messages from the db2fmp process mean? Cause This technote provides some FAQs regarding messages in the db2diag.log in regards to db2fmp processes used to run non-SQL routines such as Java and C. In some cases the fenced userid may not have permission to write errors to db2diag.log file. For example there is a db2fmp related error such as SQL1131 or SQL4304, but the db2diag.log does not contain any entries. This may be caused by incorrect permission settings http://www-01.ibm.com/support/docview.wss?uid=swg21613530 by the last process which wrote to the db2diag.log. On UNIX/Linux these would be the umask settings. $ ls -la ~/sqllib/db2dump/db2diag.log -rw-rw-rw- 1 db2inst1 system 26827 Apr 24 20:51 /home/db2inst1/sqllib/db2dump/db2diag.log The temporary work-around is to modify the permission of db2diag.log so everyone can write to it. chmod 777 db2diag.log Scenario #1: SQL1042 / -1042 This could be caused by many different causes. 1 (a) Threads in db2fmp process http://www-01.ibm.com/support/docview.wss?uid=swg21470035 When the DB2 registry variable DB2_MAX_THREADS_PER_FMP is set you may see the messages below which can be safely ignored. This registry variable was introduced as an enhancement to DB2 via IZ08425. In some cases the SQL1042 is a legitimate error so its important to note that in this scenario "Max number of thread in fmp reached; no thread created" is the cause of the SQL1042. The SQL1042 can be safely ignored. Please note that the SQL1042 is transparent to the application, so no errors will be returned to the application. DB2 automatically starts a new db2fmp process to service the existing or subsequent requests. 2011-01-10-11.31.12.480063-300 I34781A381 LEVEL: Warning PID : 1200 TID : 1 PROC : db2fmp (Java) 0 INSTANCE: db2inst1 NODE : 000 EDUID : 1 EDUNAME: db2fmp (Java) 0 FUNCTION: DB2 UDB, routine_infrastructure, sqlerMasterThreadListener, probe:200 MESSAGE : Max number of thread in fmp reached; no thread created 2011-01-10-12.10.13.923352-300 I74680A573 LEVEL: Warning PID : 1234 TID : 100 PROC : db2sysc INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-33648 APPID: 192.168.1.1.50234.11022217100 AUTHID : DB2INST1 EDUID : 608 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, routine_infrastructure, sqlerMasterThreadReq, probe:89 MESSAGE : FMP reported it could not create a new thread DATA #
on DB2 for Linux, UNIX, and WindowsWhere is this place located?All Places SAP on DB2 for Linux, UNIX, and Windows 3 Replies Latest reply: Jan 31, 2014 6:31 AM by Deepak Kori Tweet Error in db2diag.log https://scn.sap.com/thread/3493602 in DB HADR configured systems bsreddy571 c Jan 30, 2014 6:55 PM Currently Being Moderated Hello Experts,I have noticed a work process got terminated unexpectedly and made entry in sm21 and on further investigation i found following entries in db2diag.logand also noticed that this occurred during Z tcode execution as belowLEVEL: ErrorPID : 4716 TID : 5556 PROC : db2syscs.exeINSTANCE: db2tnt NODE : 000 DB db2 error : PRDAPPHDL : 0-17 APPID: 192.168.1.20.11968.140126060745AUTHID : SAPTNT FUNCTION: DB2 UDB, common communication, sqlcctcptest, probe:11MESSAGE : Detected client terminationDATA #1 : Hexdump, 2 bytes0x00000000F88A8D90 : 3600 6.2014-01-30-14.09.16.368000+330 I1220271F470 LEVEL: ErrorPID : 4716 TID : 5556 PROC : db2syscs.exeINSTANCE: db2tnt NODE : 000 DB : PRDAPPHDL : 0-17 APPID: 192.168.1.20.11968.140126060745AUTHID : SAPTNT FUNCTION: DB2 UDB, common communication, sqlcctest, probe:50MESSAGE : sqlcctest RCDATA #1 : Hexdump, db2 error detected 2 bytes0x00000000F88A8DF0 : 3600 6.2014-01-30-14.09.16.368000+330 I1220743F470 LEVEL: ErrorPID : 4716 TID : 5556 PROC : db2syscs.exeINSTANCE: db2tnt NODE : 000 DB : PRDAPPHDL : 0-17 APPID: 192.168.1.20.11968.140126060745AUTHID : SAPTNT FUNCTION: DB2 UDB, base sys utilities, sqleqint, probe:10MESSAGE : sqleqint2 iRCDATA #1 : Hexdump, 4 bytes0x00000000F88A8F70 : 3600 0000 Kindly suggest on the effects of this error on HADR and Database. Thanks,Bharath. 1038Views Re: Error in db2diag.log in DB HADR configured systems Hugo Amo Jan 30, 2014 7:12 PM (in response to bsreddy571 c) Currently Being Moderated Hi Bharath,The error message in db2diag.log file is related to function sqlcctcptest:FUNCTION: DB2 UDB, common communication, sqlcctcptest, probe:11MESSAGE : Detected client terminationThe function sqlcctcptest() is used by db2 agents to check if a TCP/IP connection is still valid. Because there are not reported any SQL30081N errors, this looks like the connection was idle when it got disconnected. The disconnection occured on the client or any router/firewall on the way. It is possible that the disconnection was due to TCP/IP timeouts. There is AIX setting tcp_keepidle which sets how long a connection can be idle before it gets closed. It can be the case that the idl