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 IC77523 Status: Geschlossen

ON LINUX, SETTING NOFILES ULIMIT TO A VALUE, HIGHER THEN 64K CAN CAUSE A
STACK CORRUPTION

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
On Linux systems , setting NOFILEs ulimit higher then 64K might 
cause a stack corruption. 
 
This stack corruption could potentially lead to an instance 
trap. 
 
 
The following messages are examples on how the error would look 
like on db2diag.log. 
 
 
2010-09-01-20.10.16.639154-240 E3414811E517        LEVEL: Error 
 
(OS) 
 
PID    : 17263                TID  : 47815921232192PROC : 
 
db2sysc 0 
 
INSTANCE: db2inst1            NODE : 000 
 
APPHDL  : 0-9799 
 
EDUID  : 2208                EDUNAME: db2agent () 0 
 
FUNCTION: DB2 UDB, oper system services, sqloPdbSelectSocket, 
 
probe:20 
 
MESSAGE : ZRC=0x870F0025=-2029060059=SQLO_INVH "invalid file 
 
handle" 
 
          DIA8534C An invalid file handle was encountered. 
 
CALLED  : OS, -, select                          OSERR: EBADF 
 
(9) 
 
 
 
2010-09-01-20.10.16.982814-240 I3415329E11559      LEVEL: Severe 
 
PID    : 17263                TID  : 47811676596544PROC : 
 
db2sysc 0 
 
INSTANCE: db2inst1            NODE : 000 
 
APPHDL  : 0-28624 
 
EDUID  : 1997                EDUNAME: db2agent () 0 
 
FUNCTION: DB2 UDB, base sys utilities, sqlePeekRequest, probe:10 
 
MESSAGE : Possible stack corruption detected! 
 
DATA #1 : Hexdump, 2200 bytes 
 
 
 
 
 
This is an example of how the PROCESS STACK may look: 
 
 
 
 
 
        ossDumpStackTraceEx 
 
1        OSSTrapFile::dumpEx 
 
2        OSSTrapFile::dump 
 
3        sqlo_trce 
 
4        sqloEDUCodeTrapHandler 
 
5        __invoke_dynamic_linker 
 
6        sqlcctest 
 
7        sqeAgent::AgentBreathingPoint 
 
8        sqldFetchDirect 
 
9        sqldDataFetch 
 
10      sqli_proc_leaf
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Linux                                                        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* On Linux systems , setting NOFILEs ulimit higher then 64K    * 
* might                                                        * 
* cause a stack corruption.                                    * 
*                                                              * 
*                                                              * 
*                                                              * 
* This stack corruption could potentially lead to an instance  * 
*                                                              * 
* trap.                                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* The NOFILE ulimit to less or equal of 64K                    * 
****************************************************************
Local-Fix:
Set NOFILE ulimit to less then 64K on the affected platforms
verfügbare FixPacks:
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
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
14.07.2011
22.12.2011
22.12.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
9.7.0.5 FixList