In rate timing, connecting database could fail with connection
timeout when the value of ConnectionTimeout property for
CLI/ODBC or JDBC driver is set to 10 second or
less.
For this problem, the following kind of two records could be
observed at a 10-seconds interval in db2diag.log.
2018-07-10-10.29.48.993400+540 I67988A550 LEVEL: Event
PID : 33226888 TID : 9286 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : DATABASE
APPHDL : 0-41242 APPID: *LOCAL.DB2.180716103821
AUTHID : BRCORUSR HOSTNAME: hostname
EDUID : 9286 EDUNAME: db2stmm (DATABASE) 0
FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam,
probe:20
CHANGE : STMM CFG DB DATABASE: "Database_memory" From: "1400604"
To: "1475128"
2018-07-10-10.29.58.987781+540 I72498A663 LEVEL: Warning
PID : 33226888 TID : 13654 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : DATABASE
APPHDL : 0-45570 APPID: *LOCAL.db2inst1.180724002900
HOSTNAME: hostname
EDUID : 13654 EDUNAME: db2agent (DATABASE) 0
FUNCTION: DB2 UDB, config/install, sqlf_openfile, probe:3024
MESSAGE : File not found error was incorrectly detected as file
successfully
opened after multiple attempts.
DATA #1 : String, 65 bytes
/home/db2inst1/NODE0000/SQL00001/MEMBER0000/SQLDBCONF
DATA #2 : signed integer, 4 bytes
1 |
