The Sybase ASE database environment consists of the following servers:
Creating the Sybase ASE database environment involves configuring these servers.
Ensure that you have completed the following tasks.
Establish a highly available IP address and name, that is, a network resource that operates at installation time.
Locate device paths for all of the Sybase ASE devices—including the master device and system devices—in the highly available local file system or cluster file system. Configure device paths as one of the following file types.
Files that the Solstice DiskSuite/Solaris Volume Manager software or the VxVM software manages
Locate the Sybase ASE server logs in either the cluster file system or the local file system.
Ensure that the password for the Sybase ASE system administrator account is correctly specified.
Sun Cluster HA for Sybase ASE must be able to start and monitor the monitor server. To meet this requirement, ensure that the password for the Sybase ASE system administrator account (sa) is specified in the file RUN_monitor-server, where monitor-server is the name of the Sybase ASE monitor server. This name is defined during the Sybase ASE installation. For more information, see your Sybase ASE documentation.
If you do not set the required password in the RUN_monitor-server file, the Sun Cluster HA for Sybase ASE data service cannot start the monitor service. If no password is set for the sa account, you do not need to modify the RUN_monitor-server file.
Create an interfaces file for the cluster.
The entire cluster must contain only one copy of the interfaces file. The $SYBASE directory contains the interfaces file. If you plan to maintain per-node file copies, ensure the file contents are identical.
All of the clients that connect to Sybase ASE servers connect with Sybase OpenClient libraries and utilities. When you configure the Sybase ASE software, in the interfaces file, enter information about the network resource and various ports. All of the clients use this connection information to connect to the Sybase ASE servers.
Run the GUI-based utility srvbuild to create the Sybase ASE database.
This utility is contained in the $SYBASE/ASE_major-version/bin directory, where major-version is the major version of Sybase ASE that you are using. For example, if you are using Sybase ASE version 12.5.1, major-version is 12-5.
For information about the srvbuildutility, see the Sybase ASE document Installing Sybase Adaptive Server Enterprise on Sun Solaris 2.x (SPARC).
To verify successful database installation, ensure that all of the servers start correctly.
Run the ps(1) command to verify the operation of all of the servers. Sybase ASE server logs indicate any errors that have occurred.
Set the password for the Sybase ASE system administrator account.
For details about changing the sa login password, see Sybase Adaptive Server Enterprise System Administration Guide.
Create a new Sybase ASE account for fault monitoring.
This account enables the fault monitor to perform the following tasks.
Supporting queries to system tables
Creating and updating user tables
Do not use the sa account for these purposes.
The following example shows how to create a new Sybase ASE account for fault monitoring.
# isql -Usa -Psybase -Sasedb 1> use master 2> go 1> create database sc3xdb 2>go 1> sp_addlogin dbmon, dbmonp, sc3xdb 2> go 1> use sc3xdb 2> go 1> sp_changedbowner dbmon 2> go 1> sp_modifylogin dbmon, defdb, sc3xdb 2> go 1> exit
For more information, see Tuning the Sun Cluster HA for Sybase ASE Fault Monitor.
Update the stop file with the sa password.
Because the stop file contains the sa password, protect the file with the appropriate permissions, and place the file in a directory that the system administrator chooses. Enable only the sybase user to read, write, and execute the stop file.
For more information about the stop file, see Sun Cluster HA for Sybase ASE Security Issues.
After you create the Sybase ASE database environment, go to Installing the Sun Cluster HA for Sybase ASE Packages.