DB2 FOR LUW / DB2FORLUW / A10 - DB2

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.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB version 10.1 fixpack 4.                   * 
****************************************************************

Increase semume

DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 

Problem was first fixed in DB2 UDB Version 10.1 fix pack 4.

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

21.11.2013
02.06.2014
02.06.2014