Setting SEMMNU and SEMMNS

bohrmann

Member
Hi,
Though I saw some threads earlier, but I cannot resolve similar issue in our case.
First of all I'm not a Unix administrator, but the Unix guys ask me for advice... So we should set the SEMMNU and SEMMNS parameters properly, because after a server reboot only 1 appl can be launched out of 8, we encountered the usual error:
Semaphore limit exceeded

First we increased SEMMNU (I don't know from which value) like this:
set semsys:seminfo_semmns=30000

Then 4 apps were launched, but some of them gives this error message:
Too many users requested semaphore undo, increase SEMMNU

Is it enough to increase these two values? Approximately to what extent?
Any idea why these parameters have changed after the reboot?

OS: Sun Solaris
Progress 9.1E

Thanks,
Peter
 
You need to adjust several Unix kernel parameters ( you'll find information about that kernel parameters and how to set them in the database administration guide in the section managing performance ):
Table 13–3: UNIX kernel parameters that affect semaphores
Parameter Description Recommended setting
SEMMNI The maximum number of
semaphore identifiers
allowed for the system.
One per active multi-user database.
If you set this value too low, the
database engine might generate error
1131.
SEMMSL The maximum number of
semaphores allowed per
semaphore identifier
(semaphore set).
(Max-local-users-on-any-databases +
Max-#servers-on-any-databases + 4).
If you set this value too low, the
database engine might generate error
1093 or 1130.
SEMMNS Total number of
semaphores allowed for
the system.
SEMMSL * number of active databases.
If you set this value too low, the
database engine might generate error
1093, 1131, or 1195.
SEMMNU Maximum number of
semaphore undo structures
allowed for the system.
Same value as SEMMNS.
If you set this value too low, the
database engine might generate error
1081.
HTH, RealHeavyDude.
 
Back
Top