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
How to Create the Sybase ASE Database Environment
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
Register and configure Solaris Cluster HA for Sybase ASE as a failover data service.
The section that follows contains instructions for registering and configuring resources. These instructions explain how to set only extension properties that Solaris Cluster HA for Sybase ASE requires you to set. For information about all Solaris Cluster HA for Sybase ASE extension properties, see Appendix A, Solaris Cluster HA for Sybase ASE Extension Properties. You can update some extension properties dynamically. You can update other properties, however, only when you create or disable a resource. The Tunable entry indicates when you can update a property.
To set an extension property of a resource, include the following option in the clresource(1CL) command that creates or modifies the resource:
-p property=value
Identifies the extension property that you are setting
Specifies the value to which you are setting the extension property
You can also use the procedures in Chapter 2, Administering Data Service Resources, in Oracle Solaris Cluster Data Services Planning and Administration Guide to configure resources after the resources are created.
This procedure describes how to use the Oracle Solaris Cluster maintenance commands to register and configure Solaris Cluster HA for Sybase ASE.
This procedure includes creating the SUNW.HAStoragePlus resource type. This resource type synchronizes actions between HAStorage and Solaris Cluster HA for Sybase ASE and enables you to use a highly available local file system. Solaris Cluster HA for Sybase ASE is disk intensive, and therefore you should configure the SUNW.HAStoragePlus resource type.
For more information about the SUNW.HAStoragePlus resource type, see the following documentation:
SUNW.HAStoragePlus(5) man page
Note - Other options also enable you to register and configure the data service. For details about these options, see Tools for Data Service Resource Administration in Oracle Solaris Cluster Data Services Planning and Administration Guide.
To perform this procedure, you must have the following information.
The names of the cluster nodes or zones that master the data service.
The network resource that clients use to access the data service. You typically configure the IP address when you install the cluster. For information about planning the Oracle Solaris Cluster environment and the installation of the Solaris software, see Chapter 1, Planning the Oracle Solaris Cluster Configuration, in Oracle Solaris Cluster Software Installation Guide.
The path to the Sybase ASE application installation.
Note - Perform the following steps on one cluster node or zone.
# clresourcetype register SUNW.sybase
# clresourcetype register SUNW.HAStoragePlus
# clresource create -g sybase-rg -t SUNW.HAStoragePlus \ -p GlobalDevicePaths=sybase-device-group1,/dev/global/dsk/dl \ -p FilesystemMountPoints=/global/sybase-inst \ -p AffinityOn=TRUE sybase-hastp-rs
The resource is created in the enabled state.
Note - AffinityOn must be set to TRUE and the local file system must reside on global disk groups to be failover.
Moving the resource group into a managed state
Bringing the resource group online
This node becomes the primary for device group sybase-set1 and raw device /dev/global/dsk/d1. Device groups that are associated with file systems such as /global/sybase-inst are also made primaries on this node.
# clresourcegroup online -M sybase-rg
# clresource create -g resource-group \ -t SUNW.sybase \ -p Environment_File=environment-file-path \ -p Adaptive_Server_Name=adaptive-server-name \ -p Backup_Server_Name=backup-server-name \ -p Text_Server_Name=text-server-name \ -p Monitor_Server_Name=monitor-server-name \ -p Adaptive_Server_Log_File=log-file-path \ -p Stop_File=stop-file-path \ -p Connect_string=user/passwd \ -p resource_dependencies_offline_restart=storageplus-resource \ -p Wait_for_Online=TRUE \ -p DB_Wait_List=db1, db2, ... \ -p Restart_type=RESOURCE_RESTART|RESOURCE_GROUP_RESTART \ -p Custom_action_file=filepath resource
Specifies the resource group name into which the RGM places the resources.
Specifies the resource type to add.
Sets the name of the environment file.
Sets the name of the adaptive server.
Sets the name of the backup server.
Sets the name of the text server.
Sets the name of the monitor server.
Sets the path to the log file for the adaptive server.
Sets the path to the stop file.
Specifies the user name and password that the fault monitor uses to connect to the database.
Specifies whether the START method has to wait for the database to be brought online before exiting.
Specifies the list of databases that need to be online before the resource can be brought online. The valid values are either an empty list (“ ”), ALL, or a list of databases.
Defines the restart behavior of the resource. If the Restart_type extension property is set to RESOURCE_RESTART, the server fault monitor restarts the database server resource. If the Restart_type extension property is set to RESOURCE_GROUP_RESTART, the server fault monitor restarts the database server resource group. This property was introduced in SUNW.sybase resource type version 5. Prior to and including SUNW.sybase resource type version 5, the server fault monitor restarted the database server resource group.
Sets the path to the custom action file that contains the custom fault monitor actions.
Specifies the resource name to add.
The resource is created in the enabled state.
You do not have to specify extension properties that have default values. For more information, see Setting Solaris Cluster HA for Sybase ASE Extension Properties.
Next Steps
After you register and configure Solaris Cluster HA for Sybase ASE, go to Verifying the Solaris Cluster HA for Sybase ASE Installation and Configuration.