The following examples describe a service group that monitors the state of a DB2 instance in a Solaris zone.

Figure: Db2udb resource that is configured in a Solaris zone illustrates the dependencies among the resources that are configured for a Db2udb resource that is configured in a Solaris zone.

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. 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 -z zone1
   zonecfg:zone1> add fs
   zonecfg:zone1:fs> set dir=/db2inst1
   zonecfg:zone1:fs> set type=lofs
   zonecfg:zone1:fs> set special=/zones/db2data
   zonecfg:zone1:fs> end

For more information on setting up VCS to work with Solaris 10 local zones, see the appendix in the:Veritas Cluster Server User's Guide.