home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC66254 Status: Geschlossen

WHEN A GPFS CONTAINING THE INSTANCE DIRECTORY (SQLLIB) IS LOST O NA SYSTEM,
IT RESULTS IN HIGH CPU USAGE BY DB2SYSC

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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).
verfügbare FixPacks:
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

Lösung
WHEN A GPFS CONTAINING THE INSTANCE DIRECTORY (SQLLIB) IS LOST 
ON A SYSTEM, IT RESULTS IN HIGH CPU USAGE BY DB2SYSC
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC67180 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
11.02.2010
13.09.2010
13.09.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP2
Problem behoben lt. FixList in der Version
9.7.0.2 FixList
9.7.0.3 FixList
9.7.0.3 FixList