Skip Navigation Links | |
Exit Print View | |
![]() |
Oracle Solaris Cluster Data Service for Sybase ASE Guide Oracle Solaris Cluster |
1. Installing and Configuring Solaris Cluster HA for Sybase ASE
Solaris Cluster HA for Sybase ASE Overview
Overview of Installing and Configuring Solaris Cluster HA for Sybase ASE
Preparing to Install Solaris Cluster HA for Sybase ASE
Installing the Sybase ASE Software
How to Prepare the Nodes for the Installation of the Sybase ASE Software
How to Install the Sybase ASE Software
How to Verify the Sybase ASE Installation
Configuring Sybase ASE Database Access and Creating the Sybase ASE Database Environment
How to Configure Sybase ASE Database Access With Solaris Volume Manager
How to Configure Sybase ASE Database Access With Veritas Volume Manager
Installing the Solaris Cluster HA for Sybase ASE Packages
How to Install the Solaris Cluster HA for Sybase ASE Packages
Registering and Configuring Solaris Cluster HA for Sybase ASE
Setting Solaris Cluster HA for Sybase ASE Extension Properties
How to Register and Configure Solaris Cluster HA for Sybase ASE
Verifying the Solaris Cluster HA for Sybase ASE Installation and Configuration
How to Verify the Solaris Cluster HA for Sybase ASE Installation and Configuration
Location of Solaris Cluster HA for Sybase ASE Log Files
Solaris Cluster HA for Sybase ASE Logging and Security Issues
Solaris Cluster HA for Sybase ASE Logging Issues
Solaris Cluster HA for Sybase ASE Security Issues
Tuning the Solaris Cluster HA for Sybase ASE Fault Monitor
Obtaining Core Files for Troubleshooting
Customizing the Solaris Cluster HA for Sybase ASE Fault Monitor
Defining Custom Behavior for Errors
Changing the Response to a DBMS Error
Responding to an Error Whose Effects Are Major
Ignoring an Error Whose Effects Are Minor
Changing the Response to Logged Alerts
Changing the Maximum Number of Consecutive Timed-Out Probes
Propagating a Custom Action File to All Nodes in a Cluster
Specifying the Custom Action File That a Server Fault Monitor Should Use
How to Specify the Custom Action File That a Server Fault Monitor Should Use
A. Solaris Cluster HA for Sybase ASE Extension Properties
B. Preset Actions for DBMS Errors and Sybase ASE Logged Alerts
Configuring Sybase ASE database access and creating the Sybase ASE Database Environment involves the following tasks.
Configuring Sybase ASE database access with the volume manager that you are using:
If you are using Solaris Volume Manager, see How to Configure Sybase ASE Database Access With Solaris Volume Manager.
If you are using Veritas Volume Manager (VxVM), see How to Configure Sybase ASE Database Access With Veritas Volume Manager.
Creating the Sybase ASE database environment. See How to Create the Sybase ASE Database Environment.
For information about how to configure Solaris Volume Manager, see Oracle Solaris Cluster Software Installation Guide.
If you do not use raw devices, do not perform this step.
# chown sybase /dev/md/metaset/rdsk/dn # chgrp dba /dev/md/metaset/rdsk/dn # chmod 600 /dev/md/metaset/rdsk/dn
Specifies the name of the disk set
Specifies the name of the raw disk device within the metaset disk set
# ls -lL /dev/md/metaset/rdsk/dn
Next Steps
Go to How to Create the Sybase ASE Database Environment.
For information about how to configure Veritas Volume Manager, see Oracle Solaris Cluster Software Installation Guide.
If you do not use raw devices, do not perform this step.
# vxedit -g diskgroup set user=sybase group=dba mode=0600 volume
# ls -lL /dev/vx/rdsk/diskgroup/volume
# cldevicegroup create -t VxVM diskgroup
Next Steps
Go to How to Create the Sybase ASE Database Environment.
The Sybase ASE database environment consists of the following servers:
Data server
Backup server
Monitor server
Text server
XP server
Creating the Sybase ASE database environment involves configuring these servers.
Before You Begin
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.
Regular files
Raw devices
Files that the 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.
Solaris 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 Solaris 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.
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).
Run the ps(1) command to verify the operation of all of the servers. Sybase ASE server logs indicate any errors that have occurred.
For details about changing the sa login password, see Sybase Adaptive Server Enterprise System Administration Guide.
This account enables the fault monitor to perform the following tasks.
Supporting queries to system tables
Creating and updating user tables
Note - 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 Solaris Cluster HA for Sybase ASE Fault Monitor.
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 Solaris Cluster HA for Sybase ASE Security Issues.
Next Steps
After you create the Sybase ASE database environment, go to Installing the Solaris Cluster HA for Sybase ASE Packages.