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

SORT SHARED MEMORY COUNTER UNDERFLOW MAY CAUSE SEVERE MESSAGE IN THE
DB2DIAG.LOG

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
You may see following severe message in the db2diag.log : 
 
2012-08-22-14.11.47.121000+120 I6229343F540       LEVEL: Severe 
PID     : 10364                TID  : 11768       PROC : 
db2syscs.exe 
INSTANCE: DB2                  NODE : 000         DB   : DBNAME 
APPHDL  : 0-31650              APPID: 
10.11.110.210.4934.120822120652 
AUTHID  : DB2INST1 
EDUID   : 11768                EDUNAME: db2agntp 0 
FUNCTION: DB2 UDB, Self tuning memory manager, 
stmmReleaseUnthrottledSharedSortSpace, probe:2615 
MESSAGE : Trying to release more pages than were held -  2 - 
786556 - 
         4294705272 - 
 
Message is related to some other warnings of type: 
 
2012-08-22-15.25.17.207000+120 I6242572F1073      LEVEL: Warning 
PID     : 10364                TID  : 2224        PROC : 
db2syscs.exe 
INSTANCE: DB2                  NODE : 000         DB   : DBNAME 
APPHDL  : 0-32116              APPID: 
10.11.110.210.1724.120822131417 
AUTHID  : DB2INST1 
EDUID   : 2224                 EDUNAME: db2agent (DBNAME) 0 
FUNCTION: DB2 UDB, sort/list services, 
sqlsReleaseSharedSortSpace, probe:10 
DATA #1 : String, 46 bytes 
Sort shared memory counter underflow detected 
DATA #2 : unsigned integer, 4 bytes 
260642 
DATA #3 : unsigned integer, 4 bytes 
260640 
CALLSTCK: 
  [0] 0x000000018010B885 pdLog + 0x353 
  [1] 0x0000000003A349D6 sqlsfshp + 0x9FE 
  [2] 0x0000000003A2C753 sqlsopen + 0xC57 
  [3] 0x00000000034FDF35 sqlrsopen + 0xCD 
  [4] 0x000000000361AFDE sqlrisrt + 0x2D0 
  [5] 0x00000000034D6BFF sqlriSectInvoke + 0x139 
  [6] 0x0000000003219314 sqlrr_process_fetch_request + 0x1A8 
  [7] 0x0000000003214D47 sqlrr_open + 0x531 
  [8] 0x00000000023D92EB sqljs_ddm_opnqry + 0x447 
  [9] 0x00000000023B8021 sqljsParse + 0x2B85 
 
 
and: 
 
2012-08-23-23.44.03.058000+120 I6566317F1115      LEVEL: Warning 
PID     : 10364                TID  : 6988        PROC : 
db2syscs.exe 
INSTANCE: DB2                  NODE : 000         DB   : DBNAME 
APPHDL  : 0-6810               APPID: *LOCAL.DB2.120823213457 
AUTHID  : DB2INST1 
EDUID   : 6988                 EDUNAME: db2agntp (DBNAME) 0 
FUNCTION: DB2 UDB, sort/list services, 
sqlsReleaseSharedSortSpace, probe:10 
DATA #1 : String, 46 bytes 
Sort shared memory counter underflow detected 
DATA #2 : unsigned integer, 4 bytes 
94440 
DATA #3 : unsigned integer, 4 bytes 
91830 
CALLSTCK: 
  [0] 0x000000018010B885 pdLog + 0x353 
  [1] 0x0000000003A2F8A2 sqlsReleaseSharedSortSpace + 0x1E4 
  [2] 0x0000000003516F09 sqlriReleaseSortSpace + 0x1D 
  [3] 0x000000000350935A sqlri_hsjnClose + 0xCA0 
  [4] 0x000000000362DB31 sqlrihsjn + 0x329 
  [5] 0x00000000034D6BFF sqlriSectInvoke + 0x139 
  [6] 0x00000000032DFFF4 sqlrr_smp_router + 0x184 
  [7] 0x00000000032E2C8B sqlrr_subagent_router + 0xE6F 
  [8] 0x000000000220A77E sqleSubRequestRouter + 0xA32 
  [9] 0x000000000220962A sqleProcessSubRequest + 0x200 
 
 
Warnings are recorded with different stacks (and stack might be 
different than the ones above). 
Severe message is informational (no other symptoms of problem 
except mentioned severe message).
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.1 fixpack 3                        * 
****************************************************************
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
Problem was first fixed in DB2 version 10.1 fixpack 3
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
22.04.2013
02.10.2013
02.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