|
Problem IC66254
|
Status: Closed |
WHEN A GPFS CONTAINING THE INSTANCE DIRECTORY (SQLLIB) IS LOST O NA SYSTEM, IT RESULTS IN HIGH CPU USAGE BY DB2SYSC |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
When a GPFS filesystem containing the instance directory
(sqllib, where DB2 binaries and libraries reside) is lost on a
system, both db2sysc and db2fmp processes go into a defunct
state and start consuming high CPU, the result of which is due
to the process being stuck in infinite recursion with a signal
handler. Even a kill with a signal 9 against these defunct DB2
processes would not cleanup.
Callstack for db2sysc via a debugger would show the following
stack recursively:
#0 0x00002adf7d8fa634 in do_lookup_x ()
from /lib64/ld-linux-x86-64.so.2
#1 0x00002adf7d8faa87 in _dl_lookup_symbol_x ()
from /lib64/ld-linux-x86-64.so.2
#2 0x00002adf7d8fe0b5 in _dl_fixup ()
from /lib64/ld-linux-x86-64.so.2
#3 0x00002adf7d9034d2 in _dl_runtime_resolve ()
from /lib64/ld-linux-x86-64.so.2
#4 0x00002adf7ef45d04 in pdlogNestedTrapHandler ()
from /opt/tivoli/tsm/db2/lib64/libdb2e.so.1
#5 <signal handler called>
#6 0x00002adf7d8fa634 in do_lookup_x ()
from /lib64/ld-linux-x86-64.so.2
#7 0x00002adf7d8faa87 in _dl_lookup_symbol_x ()
from /lib64/ld-linux-x86-64.so.2
#8 0x00002adf7d8fe0b5 in _dl_fixup () from
/lib64/ld-linux-x86-64.so.2
#9 0x00002adf7d9034d2 in _dl_runtime_resolve ()
from /lib64/ld-linux-x86-64.so.2
#10 0x00002adf7ef45d04 in pdlogNestedTrapHandler ()
from /opt/tivoli/tsm/db2/lib64/libdb2e.so.1
#11 <signal handler called> |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* WHEN A GPFS CONTAINING THE INSTANCE DIRECTORY (SQLLIB) IS *
* LOST ON A SYSTEM, IT RESULTS IN HIGH CPU USAGE BY DB2SYSC *
****************************************************************
* RECOMMENDATION: *
* Upgrade to 9.7 FP2 *
**************************************************************** |
| Local Fix: |
To workaround, either reboot the system or kill db2wdog process
with a signal 9 (this will clean up defunct DB2 processes). |
| available fix packs: |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
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 |
WHEN A GPFS CONTAINING THE INSTANCE DIRECTORY (SQLLIB) IS LOST
ON A SYSTEM, IT RESULTS IN HIGH CPU USAGE BY DB2SYSC |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC67180
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 11.02.2010
13.09.2010
13.09.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP2
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
| 9.7.0.3
|
|
| 9.7.0.3
|
|
