|
|
|
|
|
The following examples describe a typical service group configured to monitor the state of a DB2 instance configured in a Solaris zone.
If the root file system of a zone is on the local disk of each node, the file system mounts when you boot the system. Hence, the service group does not need to have separate DiskGroup and Volume resources for the zone.
DB2 UDB instance configured in a Solaris zone
Click the thumbnail above to view full-sized image.
The shared disk groups and volumes in the cluster are configured as resources of type DiskGroup and Volume respectively. The volumes are mounted using the Mount agent. The Solaris zone is monitored through a zone resource, which is dependent on the Mount and NIC resources. The DB2 server can be started after each of these resources is brought online.
The DB2 instance's home directory is mounted in the global zone. In order to make this file system available to the non-global zone, you must execute the following command on the global zone.
The lines in the following example specify that you mount /zones/db2data in the global zone as /db2inst1 in the non-global zone named zone1. The file system type to use is LOFS. The /db2inst1 directory in this example is the home directory for the DB2 instance.
zonecfg:zone1:fs> set dir=/db2inst1
zonecfg:zone1:fs> set type=lofs
zonecfg:zone1:fs> set special=/zones/db2data