Quick Beginnings

Before You Begin



Figure 00002674 not displayed.
The instructions in this section assume that you are installing DB2 Enterprise - Extended Edition (DB2 EEE) for HP-UX on one system and running Multiple Logical Nodes (MLNs) to create your partitioned database system. If you are installing DB2 EEE on a cluster, you will have to run the DB2 Installer program on each physical machine that you want to participate in 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/fstab file so that this file system is mounted each time the system is rebooted.

    Figure 00002674 not displayed.
    		If you are installing DB2 EEE on a cluster of HP-UX systems, you must add an entry to the /etc/exports 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:

    The usernames you create must conform to both your operating system's naming rules, and those of DB2. You can have the DB2 Installer create these usernames, or you can create them manually. 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 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


    Figure 00002674 not displayed.
    		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 /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:

    Figure 00002674 not displayed.
    		The HP-UX operating system automatically reboots after changing the kernel configuration parameter values.

    Step  a.

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

    Step  b.

    Update the kernel configuration parameters as follows:

    Table 5. HP-UX Kernel Configuration Parameters (Recommended Values)
    Kernel Parameter Physical Memory
    64MB - 128MB 128MB - 256MB 256MB - 512MB 512MB+ 
    maxuprc
maxfiles
 
nproc
nflocks
ninode
nfile
 
msgseg
msgmnb
msgmax
msgtql
msgmap
msgmni
msgssz
 
semmni
semmap
semmns
semmnu
 
shmmax
shmseg
shmmni
 


    256
256
 
512
2048
512
(4 * ninode)
 
8192
65535  (2)
65535  (2)
256
130
128
16
 
128
130
256
256
 
67108864
16
300


    384
256
 
768
4096
1024
(4 * ninode)
 
16384
65535  (2)
65535  (2)
512
258
256
16
 
256
258
512
512
 
134217728  (3)
16
300


    512
256
 
1024
8192
2048
(4 * ninode)
 
32767(1)
65535  (2)
65535  (2)
1024
258
256
16
 
512
514
1024
1024
 
268435456 (3)
16
300


    1500
256
 
2048
8192
2048
(4 * ninode)
 
32767(1)
65535  (2)
65535  (2)
2048
2050
1024
16
 
2048
2050
4096
1024
 
268435456 (3)
16
1000

    Notes:

    1. The msgseg parameter must be set no higher than 32767.

    2. The msgmnb and msgmax parameters must be set to at least 65 535.

    3. The shmmax parameter should be set to 134 217 728 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 shmmax to 184968806 (196*1024*1024*0.9).

    4. To maintain the interdependency among kernel parameters, change parameters in the same sequence in which they appear in the preceding table.

To change a value, perform the following steps:

Step  1.

Enter the SAM command to start the System Administration Manager (SAM) program.

Step  2.

Double-click on the Kernel Configuration icon.

Step  3.

Double-click on the Configurable Parameters icon.

Step  4.

Double-click on the parameter that you want to change and enter the new value in the Formula/Value field.

Step  5.

Click on OK.

Step  6.

Repeat these steps for all of the kernel configuration parameters that you want to change.

Step  7.

When you are finished setting all of the kernel configuration parameters, select Action --> Process New Kernel from the action menu bar.

[ Top of Page | Previous Page | Next Page ]