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

DB2OSCONF DOES NOT SHOW SEMUME IN HP-UX.

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
db2osconf does not show semume. 
 
$ db2osconf | grep -c semume 
0 
 
If semume is specified default value, semop may fail with 
EINVAL. 
 
Here is a part of db2daig.log. 
2013-02-06-18.52.43.440012+540 E680250A473        LEVEL: Error 
(OS) 
... snip ... 
FUNCTION: DB2 UDB, oper system services, sqloOpenMLNQue, probe:3 
MESSAGE : ZRC=0x870F003E=-2029060034=SQLO_QUE_BAD_HANDLE "Bad 
Queue Handle" 
          DIA8555C An invalid message queue handle was 
encountered. 
CALLED  : OS, -, semop 
OSERR   : EINVAL (22) "Invalid argument" 
 
 
From man of HP-UX. 
man semume 
 NAME 
      semume - maximum number of System V IPC undo entries per 
process 
... snip ... 
DESCRIPTION 
      The semume tunable specifies the maximum number of System 
V IPC 
      semaphores upon which a single process can have 
outstanding (non-zero) 
      "undo" operations. 
 
      If an application exhausts this limit, it will receive an 
[EINVAL] 
      error from semop(). 
 
man semop 
 NAME 
      semop, semtimedop - semaphore operations 
... snip ... 
 RETURN VALUE 
           [EINVAL]  The number of individual semaphores for 
which the 
                          calling process requests a SEM_UNDO 
would exceed 
                          the limit.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* HP-UX                                                        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB version 10.5 fixpack 4.                   * 
****************************************************************
Local-Fix:
Increase semume
verfügbare FixPacks:
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Lösung
Problem was first fixed in DB2 UDB Version 10.5 FixPack 4.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
27.08.2013
15.09.2014
15.09.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.4 FixList