DB2 FOR LUW / DB2FORLUW / B50 - DB2

db2cluster -verify potential failure due to late server startup


Look at the logs generated by the db2cluster command to see
which pair of netnames failed

Sample:
Performing Verbs ping test from  to 
status: FAILED


Find the corresponding logs under tmp, it will have the same
timestamp suffix as the logs generated by the db2cluster
command,
ie /tmp/ibm.db2.cluster_int-



Take a look at when the server (netname 2) starts listening
               LEVEL: Event
PID     : 11773                TID : 139708297951040
FUNCTION: DB2 Common, OSSe, ossClusterPingVerbsServer,
probe:4591
DATA #1 : String, 27 bytes
The server starts listening


Next take a look at when the client (netname 1) starts
connecting
.             LEVEL: Event
PID     : 9992                 TID : 140624281339712
FUNCTION: DB2 Common, OSSe, ossClusterPingVerbsClient,
probe:4028
DATA #1 : String, 28 bytes
The client starts connecting


If timestamp 2 appears before timestamp 1, then the failure is
due to the late server startup



This would cause this pair of pings to fail

****************************************************************
* USERS AFFECTED:                                              *
* Db2_v115m5fp0                                                *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to 11.5.6 or later                                   *
****************************************************************

Increase the duration before the client tries to connect to the
server through this env var to 10 seconds

export DB2_RDMA_PING_WAIT_FOR_SRVR_STARTUP_IN_SEC=10

****************************************************************
* USERS AFFECTED:                                              *
* Db2_v115m5fp0                                                *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to 11.5.6 or later                                   *
****************************************************************

Upgrade to 11.5.6 or later

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

31.03.2021
21.06.2021
21.06.2021