Quick Beginnings

Before You Begin

If you are installing DB2 EEE on a cluster, and you are not running cluster software, you will have to run the DB2 Installer program on each physical machine that you want to participate in your partitioned database system. If you are running SunCluster 2.2, you can use ctelnet or cconsole to perform your installation. For more information, see your product documentation.

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. Ensure that you have a file system that is available to all machines that will participate in your partitioned database system. This file system will be used as the instance home directory.

   For configurations that use more than one machine for a single database instance, NFS (Network File System) is used to share this file system. Typically, one machine in a cluster will be used to export the file system via NFS, and the remaining machines in the cluster will mount the NFS file system from this machine. The machine that exports the file system will have the file system mounted locally. To create this file system, perform the following steps:
   

   There are a number of ways to create a local file system on a Solaris system. If you want to use a product such as Veritas to create the file system, refer to the product's documentation.

   Step  a.	On one machine, select a disk partition or configure one using the format command. When using the format command, ensure that the disk partitions being used do not overlap. Overlapping partitions can cause data corruption or file system failures.
   Step  b.	Using a utility like newfs or mkfs, create a file system on this partition. The file system should be large enough to contain the necessary DB2 files as well as other non-DB2 files. A minimum of 300 MB is recommended.
   Step  c.	Locally mount the file system you have just created and add an entry to the /etc/vfstab file so that this file system is mounted each time the system is rebooted. For example: dev/dsk/c1t0d2s2 /dev/rdsk/c1t0d2s2 /nfshome ufs 2 yes - You should not mount this file system using the automounter utility. This utility can cause NFS mounting or locking problems in a partitioned database system.
   Step  d.	To automatically export an NFS file system on Solaris at boot time, add an entry to the /etc/dfs/dfstab file. Be sure to include all of the host names participating in the cluster as well as all of the names that a machine might be known as. Also, ensure that each machine in the cluster has root authority on the exported file system by using the "root" option. In the following example, an entry for a two machine cluster is added to the /etc/dfs/dfstab file. The system called plasma is given permission to mount the file system /nfshome, which will be used as the file system for the instance home directory. share -F nfs -o \ rw=plasma.torolab.ibm.com:plasma-tr.torolab.ibm.com,\ root=plasma.torolab.ibm.com:plasma-tr.torolab.ibm.com \ -d "homes" /nfshome Note: -tr indicates that the system is using a token ring interface. The /etc/dfs/dfstab file contains share commands which can also be run manually. The /etc/dfs/dfstab file can be run with any shell. For example: sh /etc/dfs/dfstab This command will export all file systems listed in the /etc/dfs/dfstab file.
   Step  e.	On each of the remaining machines in the cluster, add an entry to the /etc/vfstab file to NFS mount the file system automatically at boot time. As in the following example, when you specify the mount point options, ensure that the file system is mounted at boot time, is read-write, is mounted hard, includes the bg (background) option, and that setuid programs can be run properly: fusion-en:/nfshome - /nfshome nfs - yes rw,hard,intr,bg
   Step  f.	Once you have added a similar entry to the /etc/vfstab file on each machine (except for the machine acting as the NFS server), NFS mount the exported file system on each of the remaining machines in the cluster by entering the following command: mount /nfshome If the mount command fails, use the showmount command to check the status of the NFS server. For example: showmount -e fusion-en This showmount command should list the file systems which are exported from the machine named fusion-en. If this command fails, the NFS server may not have been started. To start the server manually, run the following commands as root on the NFS server: /usr/lib/nfs/mountd /usr/lib/nfs/nfsd -a 16 These commands are run automatically at boot time if there are any entries in the /etc/dfs/dfstab file. After starting the NFS server, export the NFS file system again by running the following command: sh /etc/dfs/dfstab
   Step  g.	Ensure that you have completed the following steps: On a single machine in the cluster, you have created a file system to be used as the instance and home directory. If you have a configuration that uses more than one machine for a single database instance, you have exported this file system via NFS. You have mounted the exported file system on each of the remaining machines in the 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
   
   

   If you are using NIS or NIS+, groups and users must be created on the NIS server before running db2setup.

   You can have the DB2 Installer create these user names, or you can create them manually. The user names you create must conform to both your operating system's naming rules, and those of DB2. For more information on naming rules, see Appendix C, Naming Rules.

   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 primary 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 If you are using NIS or NIS+, secondary groups must be created for the DB2 instance owner and the Administration Server on the NIS server. You must then add the primary group of the instance owner to the secondary Administration Server group. Likewise, you must add the primary Administration Server group, to the secondary group for the instance owner.
   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 /nfshome/db2inst1 -m db2inst1 useradd -g db2fadm1 -u 1003 -d /nfshome/db2fenc1 -m db2fenc1 useradd -g db2asgrp -u 1002 -d /nfshome/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 parameters 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 semsys:seminfo_semume 65535(1) 65535(1) 130 128 16 256 8192 67108864 50 300 128 130 256 256 50 65535(1) 65535(1) 258 256 16 512 16384 134217728(2) 50 300 256 258 512 512 50 65535(1) 65535(1) 258 256 16 1024 32767(2) 268435456(3) 50 300 512 514 1024 1024 50 65535(1) 65535(1) 258 256 16 1024 32767(2) 536870912(3) 50 300 1024 1026 2048 2048 50 Notes: The msgsys:msginfo_msgmnb and msgsys:msginfo_msgmax parameters must be set to 65535 or larger. The msgsys:msgseg parameter must be set no higher than 32767. 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*1024*1024*0.9). 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/V7.1/cfg directory, or on your DB2 product CD-ROM in the /db2/install/samples directory. The names for these files are as follows: kernel.param.64MB for systems with 64MB-128MB 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 3 above. After updating the /etc/system file, reboot the system.