|
Problem IT36086
|
Status: Closed |
DB2CLUSTER -VERIFY POTENTIAL HANG
|
| product: |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 |
| Problem description: |
While stress testing the db2rocmc rdma ping test for Db2 adapter
liveliness monitor, a
hang was found.
Log shows that the server was waiting for the client to send
over data. We currently have a infinite loop checking for the
data. If the client happens to die unexpectedly before sending
over the data, the server will be struck indefinitely.
The db2rocmc ping logs will show a pair ( client / server ) not
completing. Follow the PID/TID of both the client and server,
one of the two will have a missing db2rocmc exit message. That
is the one that is hanging.
Sample exit message
2021-02-23-17.07.23.392812 LEVEL: Event
PID : 6672 TID : 140458484983616
FUNCTION: DB2 UDB, high avail services, main, probe:2758
MESSAGE : ECF=0x0 OK
DATA #1 : String, 12 bytes
Command exit
DATA #2 : Uint32, 4 bytes
0 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* all *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 11.5.5.1 or higher *
**************************************************************** |
| Local Fix: |
Kill the db2rocmc ping process and re-try the ping test |
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* all *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 11.5.5.1 or higher *
**************************************************************** |
| Comment |
Upgrade to Db2 11.5.5.1 or higher |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 02.03.2021
09.04.2021
09.04.2021 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
