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

POSSIBLE CRASH (ABORT/SEGV) WHEN RUNNING OUT OF MEMORY BECAUSE OF RECURSION
CONSUMING UP THE STACK

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
The signature here will be that we will end up with segv when 
trying to allocate a new frame in the stack and the frame 
address will fall in the range of the guard page. Also, most of 
the stack will be filled up with functions from oss layer for 
analysing out of memory error. 
 
From the stack example below what should be common is the 
recursion seen in the last top frames: 
 
Frame for _ossMemAlloc() 
Frame for ossGetPhysSwapInfo() 
Frame for ossErrorGetMemoryStatistics() 
Frame for ossErrorAnalysis() returned on call to 
ossErrorMemoryAnalysis() 
Frame for ossSystemErrorHandler() 
Frame for _ossMemAlloc() 
Frame for ossGetPhysSwapInfo() 
Frame for ossErrorGetMemoryStatistics() 
Frame for ossErrorAnalysis() returned on call to 
ossErrorMemoryAnalysis() 
Frame for ossSystemErrorHandler() 
Frame for _ossMemAlloc() 
Frame for ossGetPhysSwapInfo() 
Frame for ossErrorGetMemoryStatistics() 
Frame for ossErrorAnalysis() returned on call to 
ossErrorMemoryAnalysis() 
Frame for ossSystemErrorHandler() 
Frame for _ossMemAlloc() 
Frame for ossGetPhysSwapInfo() 
Frame for ossErrorGetMemoryStatistics() 
Frame for ossErrorAnalysis() returned on call to 
ossErrorMemoryAnalysis() 
Frame for ossSystemErrorHandler() 
Frame for _ossMemAlloc() 
Frame for sqlnlsMessage() 
Frame for sqlnlsgmsg() 
Frame for sqlogmsg_noconv() 
Frame for pdGetMessage() returned on call to pdLoadMessage() 
Frame for pdLogInternal() 
Frame for pdLog() 
Frame for sqlt_logadmin() 
Frame for sqlexGetGroupsForUser() 
Frame for sqlexSlsSystemAccrdb() 
Frame for sqlexEngAuthenticate() 
Frame for sqleExecuteSecurityCheck() 
Frame for sqeApplication::AppLocalStart() 
Frame for sqlelostWrp() 
Frame for sqleUCengnInit() 
Frame for sqleUCagentConnect() 
Frame for sqljsConnectAttach() 
Frame for sqljs_ddm_accsec() 
Frame for sqljsParseConnect() 
Frame for sqljsParse() 
Frame for sqljsSqlam() 
Frame for sqljsDriveRequests() 
Frame for sqljsDrdaAsInnerDriver() 
Frame for sqljsDrdaAsDriver() 
Frame for sqeAgentGRunEDU() 
Frame for sqlzRunEDU() 
Frame for sqloEDUEntry() 
 
This issue can occur on Solaris due to the fact that function 
'ossGetPhysSwapInfo()' on Solaris attempts to allocate memory. 
And this probably may also happen in other platforms with other 
situations as in funtion 'ossSystemErrorHandler()' we do not 
detect that we are entering again for the same reason.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Systems running DB2 UDB on Solaris machines.                 * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrading to db2 version v101fp3 resolves this issue.        * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Lösung
First fixed in db2v101fp3.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
01.05.2013
18.10.2013
18.10.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.3 FixList
10.1.0.3 FixList