Caution - Perform all of the steps in this procedure on all of the nodes. If you do not perform all of the steps on all of the nodes, the Sybase ASE installation will be incomplete, and HA for Sybase ASE will fail during startup. |
On each node that can master the logical host that runs HA for Sybase ASE, include the following entries in the /etc/nsswitch.conf file.
passwd: files dns publickey: files dns project: files dns group: files dns
HA for Sybase ASE uses the su user command to start and stop the database node.
The network information name service might become unavailable when a cluster node's public network fails. Adding the preceding entries ensures that the su (1M) command does not refer to the NIS/NIS+ name services if the network information name service is unavailable.
If raw devices contain the databases, configure the global devices for raw-device access. For information about how to configure global devices, see Oracle Solaris Cluster Software Installation Guide .
If you use the Solaris Volume Manager software, configure the Sybase ASE software to use UNIX file system (UFS) logging on mirrored metadevices or raw-mirrored metadevices. For information about how to configure raw-mirrored metadevices, see Solaris Volume Manager Administration Guide .
Verify that the root and sybase users are members of the dba group, and add entries as necessary for other DBA users. Ensure that group IDs are the same on all of the nodes or zones that run HA for Sybase ASE, as the following example illustrates.
dba:*:520:root,sybase
You can create group entries in a network name service. If you create entries this way, also add your entries to the local /etc/group file to eliminate dependency on the network name service.
The following command updates the /etc/passwd and /etc/shadow files with an entry for the Sybase system administrator.
# useradd -u 120 -g dba -d /Sybase-home sybase
Ensure that the sybase user entry is the same on all of the nodes that run HA for Sybase ASE.