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

CONNIDLETIME THRESHOLD EVALUATION MAY HIT SIGSEGV DUE TO A STACK CORRUPTION

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
CONNIDLETIME threshold evaluation may hit SIGSEGV due to a stack 
corruption. 
 
Signal #11 (SIGSEGV): si_addr is 0x4F4C444944203130, si_code is 
0x00000032 (SEGV_MAPERR:Address not mapped to object.) 
 
The failing stack may look like the following. 
 
sqlrrSqlCode 
sqlrwProcessThresholdExceeded 
sqlrwProcessConnectionIdleTimeExceeded 
sqljsSqlam 
sqljsDriveRequests 
 
The same agent hit the trap may also log -4712 in db2diag.log 
like the following: 
 
 sqlcaid :   sqlcabc: 167772160   sqlcode: -4712   sqlerrml: 16 
 sqlerrmc: THRESHOLDID 12 ? 
 sqlerrp : SQLRW082
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10 fixpak 1                           * 
****************************************************************
Local-Fix:
NA
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
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 DB2 Version 10, fixpak 1
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
13.06.2012
03.12.2012
03.12.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.1 FixList
10.5.0.1 FixList