|
Problem IC77150
|
Status: Closed |
ON AIX ONLY, DB2WDOG PROCESS CONSUMES 100% CPU AND STUCK AT SIGNAL HANDLING CODE. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
If there is general performance issues and
DB2_MEMORY_PROTECT=YES, and you collect db2pd -stacks or db2fodc
data, this can cause db2wdog process to get stuck at signal
handling code and to spin on CPU, causing db2 hang.
This issue happens on AIX only.
ps -ef output will also show a lot of defunc db2fmp processes. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users using DB2_MEMORY_PROTECT db2 registry. *
****************************************************************
* PROBLEM DESCRIPTION: *
* ON AIX ONLY, DB2WDOG PROCESS CONSUMES 100% CPU AND STUCK AT *
* SIGNAL HANDLING CODE. *
****************************************************************
* RECOMMENDATION: *
* Apply DB2 V97 FP5 *
**************************************************************** |
| Local Fix: |
As a temporary workaround, disable db2 memory protect registry:
db2set DB2_MEMORY_PROTECT=NO |
| available fix packs: |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
First Fixed in DB2 V9.7 Fix Pack 5 |
| Workaround |
As a temporary workaround, disable db2 memory protect registry:
db2set DB2_MEMORY_PROTECT=NO |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 28.06.2011
19.12.2011
19.12.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP5
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.5
|
 |
