DB2 - Problem description
Problem IT37490 | Status: Closed |
DB2_HANG_DETECT SCRIPT MAY DETECT HANG INCORRECTLY AND KILL THE INSTANCE WITH ACTION=TERMINATE | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
The db2_hang_detect script has a logic executing some monitor commands like "list applications" in background mode and waiting for its completion by checking the PID. If the command does not end in a certain period, the script thinks it can be hanging and kills the instance if ACTION=terminate. However, if the command ends normally and another unrelated process in the system starts with the same PID, db2_hang_detect thinks the command is still running. Thus it may detect the hang incorrectly and kill the instance. It can occur when the same PID is re-used within a second and the process does not complete within the timeout period. | |
Problem Summary: | |
It will be fixed on the next releases. | |
Local Fix: | |
Using ACTION=INFORM instead of TERMINATE can prevent the instance from being killed incorrectly | |
Solution | |
Workaround | |
It will be fixed on the next releases. | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 01.07.2021 11.05.2022 11.05.2022 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |