|Skip Navigation Links|
|Exit Print View|
|Oracle Solaris Cluster Data Service for Sybase ASE Guide Oracle Solaris Cluster|
Use the procedures in this section to complete the following tasks.
Preparing the nodes for the installation of the Sybase ASE Software
Installing the Sybase ASE software
Verifying the Sybase ASE installation
Note - Before you configure Solaris Cluster HA for Sybase ASE, use the procedures that the Oracle Solaris Cluster Software Installation Guide describes to configure the Oracle Solaris Cluster software on each node.
Note - The Solaris Cluster HA for Sybase ASE can be configured to run in a whole root or a sparse root non-global zone for x86/x64 and SPARC architectures.
Caution - Perform all of the steps in this procedure on all of the nodes or zones. If you do not perform all of the steps on all of the nodes or zones, the Sybase ASE installation will be incomplete, and Solaris Cluster HA for Sybase ASE will fail during startup.
Note - Consult the Sybase ASE documentation before you perform this procedure.
On each node or zone that can master the logical host that runs Solaris Cluster HA for Sybase ASE, include the following entries in the /etc/nsswitch.conf file.
passwd: files [NOTFOUND=return] nis [TRYAGAIN=0] publickey: files [NOTFOUND=return] nis [TRYAGAIN=0] project: files [NOTFOUND=return] nis [TRYAGAIN=0] group: files [NOTFOUND=return] nis [TRYAGAIN=0]
Solaris Cluster 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.
Note - Configuring raw devices on non-global zones is not supported on Oracle Solaris Cluster.
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 the Solaris Volume Manager documentation.
Note - If you install the Sybase ASE binaries on a local disk, use a separate disk if possible. Installing the Sybase ASE binaries on a separate disk prevents the binaries from being overwritten during reinstallation of the operating system.
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 Solaris Cluster HA for Sybase ASE, as the following example illustrates.
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 or zones that run Solaris Cluster HA for Sybase ASE.
If you plan to install the Sybase ASE software at another location, omit this step.
For more information about installation locations, see Preparing to Install Solaris Cluster HA for Sybase ASE.
# clresourcegroup create [-n node-zone-list] resource-group
Specifies an optional, comma-separated list of physical node names or zones or IDs that identify potential masters. The order here determines the order in which the Resource Group Manager (RGM) considers primary nodes or zones during failover.
Specifies the name of the resource group. This name can be your choice but must be unique for resource groups within the cluster.
Note - Use the -n option to specify the order of the node list. If all of the nodes in the cluster are potential masters, you do not need to use the -n option.
# clreslogicalhostname create -g resource-group -h host_list logical_host
Specifies a resource name of your choice.
Specifies a comma-separated list of host names that are to be made available by the logical host name resource.
Enabling the resource and fault monitoring
Moving the resource group into a managed state
Bringing the resource group online
# clresourcegroup online -M resource-group
The installation of the Sybase binaries must be performed on the node or zone where the corresponding logical host is running.
Regardless of where you install the Sybase ASE software, modify each node's /etc/system files as you would in standard Sybase ASE installation procedures. For instructions about how to install the Sybase ASE software, refer to the Sybase installation and configuration guides.
If you do not specify a host name that is associated with a network resource, Sybase ASE starts only on the node or zone where the Sybase ASE software was installed.
Some versions of Sybase ASE, such as 12.5, prompt you for the host name. Other versions of Sybase ASE, such as 12.5.1, use the physical host name. If your version of Sybase ASE uses the physical host name, you must change the physical host name to specify a network resource.
If the Sybase ASE installer prompts you for the host name, type the host name in response to the prompt.
Otherwise, modify the interfaces file to change the physical host name to a host name that is associated with a network resource.
After you install the Sybase ASE software, go to How to Verify the Sybase ASE Installation.
After you verify the Sybase ASE installation, go to Configuring Sybase ASE Database Access and Creating the Sybase ASE Database Environment.