Kbase 15411: Modification of SEMMNS and SEMMSL under SCO OpenServer 5.0.x
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/16/2008 |
|
Status: Verified
GOAL:
Modification of SEMMNS and SEMMSL under SCO OpenServer 5.0.x
GOAL:
How to tune Kernel parameters on SCO OpenServer
FACT(s) (Environment):
Progress 9.x
OpenEdge 10.x
SCO OpenServer 5
FIX:
The specific parameters, SEMMNS and SEMMNU control the number of semaphores provided by the system for use by the database servers.
The user interface, scoadmin, does not provide access to these parameters. Which means they need to be changed manually. This can be done via two methods:
Method 1
--------
Use idtune to modify the kernel parameter. The command (idtune) will change the value of a parameter as long as its new value is within the boundaries defined in the system file /etc/conf/cf.d/mtune. This file can be viewed with an editor (vi) for a list of the acceptable minimum and maximum values for each parameter. The /etc/conf/cf.d/stune is a file which is read each time the kernel is built to apply any user defined changes to the kernel parameters. It contains all of the parameters that have been modified with new values.
idtune command syntax:
/etc/conf/bin/idtune [ -f | -m ] name value
[ -min new_min ] [ -max new_max ]
where name = the name of the parameter, value = the new value
If there is already a value in the stune file, you will be prompted to confirm the change. The (-f) and (-m) options will suppress this prompt with these conditions:
-f Force the change to stune. Do not output any messages.
-m Do not change the value of the parameter in stune if it is greater than the new value entered. Do not output any messages.
Example: To change the value of SEMMNS to 80, enter this command at the UNIX prompt
# /etc/conf/bin/idtune -f SEMMNS 80
This creates an entry in the /etc/conf/cf.d/stune file for SEMMNS with a value of 80. The idtune command does not verify that the new value is within the minimum and maximum range defined in the mtune file.
Be careful not to invalidate a tunable parameter that was previously modified or set a value outside the allowable range unless absolutely necessary. Many add-on packages will use the idtune command during their setup process to set parameters at the proper values for their optimum operation. As always, the kernel must be re-linked after any changes.
Method 2
--------
Edit the stune file to add/change the parameter value. This method is obviously more dangerous and it should only be used by an experienced system administrator.
When the kernel is relinked, this new value in the stune file will be included in the kernel.