Friday, May 27, 2011
projadd for db2 in solaris - Configure Solaris systems with the resource limits required by IBM DB2
Configure Solaris systems with the resource limits required by IBM DB2
Here are suggestions:
The recommended way of setting IPC resource control limits is now through
With the aforementioned basic setup configurations, the Solaris 10 OS can be configured to allow DB2 to scale in terms of resource usage to more than 5000 connections in practice.
Various other types of fine-tuning can be done that are more workload specific than generic, and hence, not mentioned in this section.
Thanks to:http://developers.sun.com/solaris/articles/db2_t2000.html
Suggestions are always welcome...! Without signing also you can send your comments.
Here are suggestions:
# projadd -U db2inst1 user.db2inst1 # projmod -a -K "project.max-shm-ids=(priv,1288,deny)" user.db2inst1 # projmod -a -K "project.max-sem-ids=(priv,1288,deny)" user.db2inst1 # projmod -a -K "project.max-shm-memory =(priv,30813703372,deny)" user.db2inst1 # projmod -a -K "project.max-msg-ids =(priv,10240,deny)" user.db2inst1 |
The recommended way of setting IPC resource control limits is now through
projects
(4) instead of defining them in /etc/system
, which forces a reboot to enable the parameters. The command projadd
(4M) is used to add these types of tuning to /etc/project
for the DB2 instance owner ID (for example, db2inst1
). With the aforementioned basic setup configurations, the Solaris 10 OS can be configured to allow DB2 to scale in terms of resource usage to more than 5000 connections in practice.
Various other types of fine-tuning can be done that are more workload specific than generic, and hence, not mentioned in this section.
Thanks to:http://developers.sun.com/solaris/articles/db2_t2000.html
Suggestions are always welcome...! Without signing also you can send your comments.
Labels:
DBA,
Sun Solaris,
Unix
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment