Applicable versions and levels
Solaris versions: 5.0 or later
Action
Points to check
Has the shared memory of the system parameters been tuned to an appropriate value?
Cause
If jobs that use shared memory are started from Systemwalker Operation Manager, the shared memory size must be tuned taking the size of the shared memory used by the job process into consideration. If the shared memory is not tuned, or an application that consumes a large amount of shared memory exists, the shared memory may be insufficient.
Action method
The Solaris shared memory tuning is as follows:
[Solaris 7/8/9]
Jobscheduler uses shared memory for each subsystem individually. If shminfo_shmmni is set in the etc/system file, add the amount needed for the number of subsystems (subsystem x 1). If this value is insufficient, the Jobscheduler daemon cannot start.
If shminfo_shmmax is set in the etc/system file, set a value of 50000 bytes or more. If this value is not set correctly, the Jobscheduler daemon cannot start.
[Solaris 10]
Jobscheduler uses shared memory. Set the values shown below for "project.max-shm-memory" of the system and user.root entries in the etc/project file. If these values are not set correctly, the Jobscheduler daemon cannot start.
project.max-shm-memory = Value equal to or greater than operating system physical memory size (bytes)/4 + 50000 x number of subsystems used (*1) |
*1: In EE versions. In SE versions, set the number of subsystems used as "1".
