Changes to Sun Cluster Data Service for MaxDB Support on Non-Global Zones on SPARC and x86 Based System

The Sun Cluster Data Service for MaxDB supports non-global zones on SPARC and x86 based systems. The following changes should be made to the Sun Cluster Data Service MaxDB Guide for this support. The following steps can be performed on a cluster that has been configured to run in global zones. If you are installing your cluster to run in non-global zones, a few of these steps might not be necessary as indicated below.

• On each zone, ensure that all of the network resources are present in the /etc/hosts file to avoid any failures because of name service lookup.

• On each zone, create an entry for the MaxDB group in the /etc/group file, and add potential users to the group.

• On each zone, create an entry for the MaxDB user ID.

  Use the following command to update the /etc/passwd and /etc/shadow files with an entry for the user ID.

  # useradd -u uid -g group -d /sap-home maxdb user

• Create mount point directories in the zones where MaxDB could potentially run.

• Configure the /etc/nsswitch.conf file so that Sun Cluster HA for MaxDB starts and stops correctly in the event of a switchover or a failover.

• On each zone update /etc/services file with all necessary MaxDB ports obtained from the global zones /etc/services. This step might not be necessary for Max DB that is installed in non-global zones.

• Copy /etc/opt/sdb from the global zone to all local zone nodes. This step might not be necessary for MaxDB that is being installed in non-global zones.

• Copy /var/spool/sql from the global zone to all local zone nodes. This step might not be necessary for MaxDB that is being installed in non-global zones.

• On x86 based systems only, execute crle -64 -u -l /sapmnt/MaxDBSystemName/exe on all local zones that will run MaxDB.