IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1
Kernel settings for Solaris on DB2
See the following Web site for instructions on modifying kernel settings to support IBM DB2 on Solaris:
http://publib.boulder.ibm.com/infocenter/db2luw/v8/index.jsp?topic=/com.ibm.db2.udb.doc/start/t0006476.htmTo install IBM DB2 v8.x on Solaris, you need to add the following kernel settings in /etc/system file and reboot your system:
For systems with 2GB - 4GB of physical memory:
set msgsys:msginfo_msgmnb = 65535 set msgsys:msginfo_msgssz = 32 set msgsys:msginfo_msgseg = 32767 set msgsys:msginfo_msgmni = 2560 set msgsys:msginfo_msgtql = 2560 set semsys:seminfo_semmni = 3072 set shmsys:shminfo_shmmax = 1932735283 set shmsys:shminfo_shmmni = 3072For systems with 4GB - 16GB of physical memory:
set msgsys:msginfo_msgmnb = 65535 set msgsys:msginfo_msgssz = 32 set msgsys:msginfo_msgseg = 32767 set msgsys:msginfo_msgmni = 3584 set msgsys:msginfo_msgtql = 3584 set semsys:seminfo_semmni = 4096 set shmsys:shminfo_shmmax = 3865470566 set shmsys:shminfo_shmmni = 4096All the other kernel tunable parameters that the installation and configuration Guide recommends to adjust are in the System V Interprocess Communication (IPC) tunables. In Solaris 10 all System V IPC facilities are either automatically configured or can be controlled by resource controls.
The following parameters are still operational but use of the corresponding resource controls is recommended.
msgsys:msginfo_msgmnb - process.max-msg-qbytes msgsys:msginfo_msgtql - process.max-msg-messages semsys:seminfo_semopm - process.max-sem-ops semsys:seminfo_semmsl - process.max-sem-nsems shmsys:shminfo_shmmax - project.max-shm-memory shmsys:shminfo_shmmni - project.max-shm-ids msgsys:msginfo_msgmni - project.max-msg-ids semsys:seminfo_semmni - project.max-sem-idsObsolete parameters can still be included in the /etc/system file on a Solaris 10 system. If this is the case the parameters are used to initialize the default resource control values used in previous Solaris releases. You can override these by setting the corresponding resource controls. An important distinction between the obsolete IPC tunables and resource controls is that the IPC tunables were set on a system-wide basis and the resource controls are set on a per-project or per-process basis allowing for a more flexible tuning of different workloads in the system.
Parent topic:
HP-UX and Solaris: kernel settings for IBM DB2 8.x