IBM Books

Quick Beginnings for DB2 Extended Enterprise Edition for UNIX

Setting up Solstice HA on DB2 for Solaris

To set up Solstice HA 1.3, perform the following steps:

Step 1. Choose an HA Configuration

To choose an HA configuration, perform the following steps:

  1. Set up the two machines to use either a hot standby or mutual takeover configuration. For a hot standby configuration, use one logical host. For a mutual takeover, use two logical hosts, (which is the maximum for Solstice HA 1.3).

  2. Decide on the amount of disk space that is required for each logical host and its resources, such as raw devices or SMS table space containers. Whether you use SMS or DMS (raw devices) table spaces, any disks belonging to a logical host must be included in its disk sets.

  3. Decide on the location of the database partition servers on each logical host. For example, you may choose to locate all the database partition servers on one logical host or separate them over the two logical hosts.

Step 2. Select a Logical Host for Use as the HA-NFS Server for the HA Instance Home Directory

In an HA configuration, you can have one or two logical hosts. One logical host should contain the HA instance owner's physical directory. To choose a logical host to contain the HA instance owner's directory, create a directory under the logical host's filesystem, for example: 

   /logical_host/home/db2inst

where db2inst is the instance owner. Then use HA-NFS (which comes with Solstice HA 1.3) to export that directory to make it highly available.

Step 3. Mount the Logical Host's Home Directory



Figure hint not displayed.

Do not use the automounter command for this step. The automounter utility uses loopback virtual file system (LOFS) to mount the directories if they are local. Solstice HA 1.3 does not support LOFS.

On both machines, NFS-mount the highly available directory /logical_host/home/db2inst from the HA-NFS server for use as the HA instance owner's home directory.

For example, a line in the /etc/vfstab file for the logical host snap and the instance db2inst should look like the following: 

   snap:/snap/home/db2inst - /export/home/db2inst  nfs - yes hard,rw,bg

Step 4. Create a DB2 Instance

Create a DB2 instance using the NFS-mounted home directory as the instance owner's home directory. To create the instance, use the db2icrt command, which is located in the DB2DIR/instance directory, where DB2DIR is /opt/IBMdb2/V5.0.

note

Run the db2icrt command from the machine where the home directory of the instance (INSTHOME) physically resides. Because the INSTHOME directory is NFS-mounted on all machines, you only have to run the db2icrt command on one machine.

The syntax of the db2icrt command is:
Creating an instance
 where:

-h | -?
Display a help menu for this command.

-d
Sets the debug mode that you can use for problem determination.

-a AuthType
Is an optional parameter that specifies the authentication type for the instance. Valid authentication types are SERVER, CLIENT, and DCS. If the -a parameter is not specified, the authentication type defaults to SERVER, if a DB2 server is installed. Otherwise, the AuthType is set to CLIENT.

Notes:

  1. All databases in the instance have the same authentication type.

  2. DCE authentication is not valid for this command; however, you can enable DCE authentication for an instance. For more information, refer to the Administration Guide.

-u FencedID
Is the user under which the fenced UDFs and stored procedures will execute. This is not required if you install the DB2 Client Application Enabler or the DB2 Software Developer's Kit. For other products, this is a required parameter.
Note:FencedID may not be root or bin.

InstName
Is the login name of the instance owner.

When you create an instance, ensure that its primary and secondary groups are different from the Administration Server's primary (SYSADM) group. When you create an instance on the same machine as the Administration Server, its SYSADM group is automatically added to the secondary group list of the Administration Server so that you can use the Control Center to perform administration tasks on that instance.

Examples:

When an instance is created, its name is also added to the list of instances on the system.

The db2icrt command creates the INSTHOME/sqllib directory, where INSTHOME is the home directory of the instance owner.

Figure hint not displayed.

To avoid a potential loss of data if an instance is deleted, you should not create user files or directories under the INSTHOME/sqllib directory, other than those created by DB2. Exceptions are:

  1. If your system supports fenced user defined functions and fenced stored procedures, put the fenced applications in the INSTHOME/sqllib/function directory.

  2. The location of the db2nodes.cfg file. This file should be put in the INSTHOME/sqllib directory, where INSTHOME is the home directory of the instance owner.

Step 5. Run the HA-DB2 Extended Enterprise Edition Setup Program

To setup the HA instance with Solstice HA, run the hadb2eee.setup program. The program will prompt you for the following information:

When the setup program completes successfully, it does the following:

A sample hadb2-mpp.cfg file might look like this: 

   HA-INSTANCE: db2inst1 ON
   HA-MAINNODE: snap
   NODE:whirl  0
   NODE:whirl  1
   NODE:whirl  2
   NODE:whirl  3
   NODE:snap 4
   NODE:snap 5
   NODE:snap 6
   NODE:snap 7

where HA-INSTANCE is the username of the instance owner, HA-MAINNODE is the name of the logical host which contains the home directory of the instance owner, and NODE binds a database partition server (node) number with a logical host.

You can now start up DB2 by entering the following command: 

   hareg -y hadb2


note

After completing the setup of Solstice HA 1.3, go to "Step 7. Create the Administration Server" to continue with the remaining installation steps.

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

[ DB2 List of Books | Search the DB2 Books ]