DB2 Connect Quick Beginnings for UNIX**

Manually Installing DB2 Connect for NUMA-Q

We recommend that you use the db2setup utility to install DB2 Connect for NUMA-Q. If you prefer not to use this utility, you can install DB2 products and filesets manually using the db2_install and pkgadd commands.

Before you install DB2 Connect you should update your system's kernel configuration parameters. For more information see Updating NUMA-Q/PTX Kernel Configuration Parameters.

To install your DB2 Connect for NUMA-Q product using the db2_install command:

  1. Log in as a user with root authority.
  2. Insert and mount the appropriate CD-ROM.
  3. Run the db2_install command as follows: 
       /cdrom/unnamed_cdrom/db2_install

    The db2_install command prompts for one or more of the following to be installed, and for the base directory where the product files are to be installed. The products are listed by keyword and product description:

    DB2.CENT
    DB2 Connect Enterprise Edition for NUMA-Q

    DB2.RCAE
    DB2 Universal Database Run-Time Client NUMA-Q

    DB2.SDK
    DB2 Application Development Client NUMA-Q

    The command displays the following prompt: Specify one or more of the keywords separated by spaces.

  4. Type the keyword of the products to be installed when prompted.
  5. Type the name of the base directory when prompted. The default base directory is /opt.

    If the default base directory is used, all files will be installed in the /opt/IBMdb2/V7.1 directory.

  6. Enter Yes to start the DB2 Connect product installation.

Installing DB2 Connect for NUMA-Q Product Messages

A separate package exists for every locale in which DB2 Product Messages are translated. Packages for DB2 Product Messages are given names such as db2ms%L71, where %L represents two letters for the language name. For example, the package name for the DB2 Product Messages in the de (German) locale is db2msde71. For a complete list of DB2 Product Messages, see Contents of the DB2 Products for UNIX platforms.

To install DB2 Product Message packages using the pkgadd command:

  1. Log in as a user with root authority.
  2. Insert and mount the appropriate CD-ROM.
  3. Run the pkgadd command as follows: 
       pkgadd -d cdrom-dir/db2 pkgname

    where cdrom-dir represents the CD-ROM mount directory and pkgname is the package name.

    For example, to install the DB2 Product Messages in the de (German) locale, enter the following command: 

        pkgadd -d /cdrom/unnamed_cdrom/db2 db2msde71

DB2 Connect for NUMA-Q Post-installation tasks

After manually installing your DB2 Connect product, you should create a group and user IDs for the instance owner, Administration Server, and fenced user defined functions (UDFs) and stored procedures. Once you set up these IDs you can create an instance, create the Administration Server, install the license key, and create links for your DB2 files.

You do not have to perform these tasks if you used the db2setup utility to install DB2.

Creating group and user IDs for the instance owner, Administration Server, and UDFs

You should create group and user IDs for the instance owner, Administration Server, and UDFs and stored procedures. If you want to use existing user or group IDs, you can skip this section and proceed to creating an instance.

In addition to the rules imposed by the operating system for user names and groups, you must also adhere to the rules described in Appendix D, Naming Rules.

To create a group and user ID for the instance owner:

  1. Log in as a user with root authority.
  2. Enter the following command to make a new group: 
       groupadd -g 999 dbadmin1

    where 999 represents the group ID and dbadmin1 represents the group name. This new group is the SYSADM group for the instance.

  3. Enter the following command to make a new user: 
       useradd -g dbadmin1 -u 1004 -d /export/home/db2inst1 -m db2inst1
     passwd db2inst1

    where dbadmin1 represents the group you created in the previous step, 1004 represents the user ID, /export/home/db2inst1 represents the user's home directory, and db2inst1 represents the username and instance name.

You should use a unique user ID for each instance you create. This allows for easier error recovery if a system error occurs.

To create group and user IDs for the Administration Server follow the same steps you used to create IDs for the instance owner. You must use different user IDs for the Administration Server and instance owner. For security reasons, we recommend you use a different group ID for the Administration Server and instance owner.

To create group and user IDs for UDFs and stored procedures, follow the same steps you used to create IDs for the instance owner. For security reasons, we recommend that you use different user IDs for UDFs and the instance owner. You will be asked to supply a UDF user ID when you create a DB2 instance.

Creating an instance

A DB2 instance is an environment in which you store data and run applications. Use the db2icrt command to create an instance. You must have root authority to enter this command. For more information about database instances, refer to the Administration Guide.

The db2icrt command is run with the following parameters: 

   DB2DIR/instance/db2icrt -a AuthType -u FencedID InstName

where:

Creating the Administration Server

The Administration Server provides services to support tools that automate the configuration of connections to DB2 databases. The Administration Server also supports tools that administer DB2 from your server system or a remote client using the Control Center. For more information on the Administration Server, refer to the Administration Guide.

To create the Administration Server use the DB2DIR/instance/dasicrt ASName command

where DB2DIR = /usr/lpp/db2_07_01 on AIX


= /opt/IBMdb2/V7.1 HP-UX, PTX, SGI IRIX, or Solaris


= /usr/IBMdb2/V7.1 on Linux

and ASName represents the name of the Administration Server you want to create.

Updating the License Key

Your Proof of Entitlement and the License Information booklet identify the products for which you are licensed.

To update your DB2 product license key:

  1. Log in as a user with root authority.
  2. Update your DB2 product license with the following command: 
       /opt/IBMdb2/V7.1/adm/db2licm -a filename

    where filename represents the full pathname and filename for the license file that corresponds to the product you have purchased.

    The DB2 Connect product license key is added to the /var/ifor/nodelock file.

    The names of the license files for these products are:

    db2conee.lic
    DB2 Connect Enterprise Edition

    db2relc.lic
    DB2 Relational Connect

    For example, if the CD-ROM is mounted in the /cdrom directory and the name of the license file is db2udbee.lic, the command should be as follows: 

       /opt/IBMdb2/V7.1/adm/db2licm -a /unnamed_cdrom/db2/license/db2udbee.lic

Creating links for DB2 Connect files

You can create links for the DB2 files to the /usr/lib directory, and for the include files to the /usr/include directory for a particular version and release level of the product.

You may want to create these links if you are developing or running applications and want to avoid having to specify the full path to the product libraries and include files.

To create links for DB2 Connect files, log in as a user with root authority and run the /opt/IBMdb2/V7.1/cfg/db2ln command.

If there are existing links to the /usr/lib and /usr/include directories from previous versions of DB2, they will automatically be removed by entering the db2ln command to create links for this version of DB2. If you want to re-establish the links to the libraries of previous versions, then you must execute the db2rmln command from your previous version of DB2 before you execute the db2ln command from the previous versions of DB2. Links can be established for only one version of DB2 on a given system.

[ Top of Page | Previous Page | Next Page ]