IBM Books

Quick Beginnings EEE for UNIX**

Before you Begin



Figure hint not displayed.
The instructions in this section assume that you are installing DB2 Enterprise - Extended Edition (DB2 EEE) for Solaris on one workstation and running Multiple Logical Nodes (MLNs) to create your partitioned database system.

Before you begin the installation, be sure that you have the following items and information:

__  1.

Ensure that your system meets all of the memory, hardware, and software requirements to install your DB2 product. For more information, see Planning for Installation.

__  2.

Have a file system that is available to all of the systems that will participate in your partitioned database system. This file system will be the home file system for the instance owner and the Administration Server. To create a file system, perform the following steps:

Step  a.

Select a disk partition or logical volume and use a utility like newfs to create this file system. For more information, enter the man newfs command.

Step  b.

Mount this file system locally and add an entry to the /etc/ufstab file so that the this file system is mounted each time the system is rebooted.

Figure hint not displayed.
If you are installing DB2 EEE on a cluster of Solaris systems, you must add an entry to the /etc/dfs/dfstab file to export this file system via NFS. After you have exported this file system, you must mount this file system on each system in the DB2 EEE cluster.

__  3.

Create three separate groups and user accounts for the:

  • DB2 instance owner

  • user that will execute fenced UDFs (user defined functions) or stored procedures

  • Administration Server.

The usernames you create must conform to both your operating system's naming rules, and those of DB2. For more information on naming rules, see Appendix D, Naming Rules.

Figure hint not displayed.
You can have the DB2 Installer create these usernames, or you can create them manually.

To create all three of these users, perform the following steps:

Step  a.

Log on to the system as a user with root authority.

Step  b.

Create a group for the instance owner (for example, db2iadm1), the user that will execute UDFs or stored procedures (for example, db2fadm1), and the Administration Server (for example, db2asgrp) by entering the following commands: 

   groupadd -g 999 db2iadm1
   groupadd -g 998 db2fadm1
   groupadd -g 997 db2asgrp

Step  c.

Create a user that belongs to each group that you created in the previous step by entering the following commands: 

   useradd -g db2iadm1 -u 1004 -d /home2/db2inst1 -m db2inst1
   useradd -g db2fadm1 -u 1003 -d /home2/db2fenc1 -m db2fenc1
   useradd -g db2asgrp -u 1002 -d /home2/db2as    -m db2as

Step  d.

Set an initial password for each user that you created by entering the following commands: 

   passwd db2inst1
   passwd db2fenc1
   passwd db2as

Step  e.

Log out.

__  4.

Update the Kernel Configuration Parameters. In order to run DB2 EEE you should update your kernel configuration parameter by performing the following steps:

Step  a.

Log on to the system as a user with root authority.

Step  b.

Update the kernel configuration parameters as follows:

Table 7. Solaris Kernel Configuration Parameters (Recommended Values)
Kernel Parameter Physical Memory
64MB - 128MB 128MB - 256MB 256MB - 512MB 512MB+ 
msgsys:msginfo_msgmax
msgsys:msginfo_msgmnb
msgsys:msginfo_msgmap
msgsys:msginfo_msgmni
msgsys:msginfo_msgssz
msgsys:msginfo_msgtql
msgsys:msginfo_msgseg
 
shmsys:shminfo_shmmax
shmsys:shminfo_shmseg
shmsys:shminfo_shmmni
 
semsys:seminfo_semmni
semsys:seminfo_semmap
semsys:seminfo_semmns
semsys:seminfo_semmnu
 


65 535(1)
65 535(1)
130
128
16
256
8 192
 
67 108 864
16
300
 
128
130
256
256


65535(1)
65 535(1)
258
256
16
512
16 384
 
134 217 728(2)
16
300
 
256
258
512
512


65 535(1)
65 535(1)
258
256
16
1024
32 768
 
268 435 456(2)
16
300
 
512
514
1024
1024


65 535(1)
65 535(1)
258
256
16
1024
32 768
 
536 870 912(2)
16
300
 
1024
1026
2048
2048

Notes:

  1. The msgsys:msginfo_msgmnb and msgsys:msginfo_msgmax parameters must be set to 65535 or larger.

  2. The shmsys:shminfo_shmmax parameters should be set to the suggested value in the above table, or 90% of the physical memory (in bytes), whichever is higher. For example, if you have 196 MB of physical memory in your system, set the shmsys:shminfo_shmmax parameter to 184968806 (196*0.9*1024*1024).

To set a kernel parameter, add a line at the end of the /etc/system file as follows: 

   set parameter_name = value

For example, to set the value of the msgsys:msginfo_msgmax parameter, add the following line to the end of the /etc/system file: 

   set msgsys:msginfo_msgmax = 65535

Sample files for updating the kernel configuration parameters are provided in the /opt/IBMdb2/V6.1/cfg directory. The names for these files are as follows:

kernel.param.64MB

for systems with 64MB-124MB of physical memory

kernel.param.128MB

for systems with 128MB-256MB of physical memory

kernel.param.256MB

for systems with 256MB-512MB of physical memory

kernel.param.512MB

for systems with 512MB-1GB of physical memory

kernel.param.hints

for systems with more than 1GB of physical memory

Depending upon the amount of physical memory in your system, append the appropriate kernel configuration parameter file to the /etc/system file. If necessary, change the value of the shmsys:shminfo_shmmax parameter as described in Note 2 above.

After updating the /etc/system file, reboot the system.

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]

[ DB2 List of Books | Search the DB2 Books ]