Sun Cluster 3.1 Data Service for Sybase ASE Guide

Creating the Sybase ASE Database Environment

The procedures in this section enable you to complete the following tasks.

Configure Sybase ASE database access with Solstice DiskSuite/Solaris Volume Manager or VxVM.
Create the Sybase ASE database environment.

How to Configure Sybase ASE Database Access With Solstice DiskSuite/Solaris Volume Manager

If you use the Solstice DiskSuite/Solaris Volume Manager, perform the following steps to configure Sybase ASE database access with the Solstice DiskSuite/Solaris Volume Manager.

Configure the disk devices for the Solstice DiskSuite/Solaris Volume Manager software to use.

See the Sun Cluster 3.1 Software Installation Guide for information on how to configure Solstice DiskSuite/Solaris Volume Manager.

If you use raw devices to contain the databases, run the following commands to change each raw-mirrored metadevice's owner, group, and mode.

If you do not use raw devices, do not perform this step.
1. If you create raw devices, run the following commands for each device on each node that can master the Sybase ASE resource group.
  # chown sybase /dev/md/metaset/rdsk/dn # chgrp dba /dev/md/metaset/rdsk/dn # chmod 600 /dev/md/metaset/rdsk/dn
  metaset
  
  Specifies the name of the diskset.
  
  /rdsk/dn
  
  Specifies the name of the raw disk device within the metaset diskset.
2. Verify that the changes are effective.
  # ls -lL /dev/md/metaset/rdsk/dn

How to Configure Sybase ASE Database Access With VERITAS Volume Manager

If you use VxVM software, perform the following steps to configure Sybase ASE database access with the VxVM software.

Configure the disk devices for the VxVM software to use.

See the Sun Cluster 3.1 Software Installation Guide for information on how to configure VERITAS Volume Manager.

If you use raw devices to contain the databases, run the following commands on the current disk-group primary to change each device's owner, group, and mode.

If you do not use raw devices, do not perform this step.
1. If you create raw devices, run the following command for each raw device.
  # vxedit -g diskgroup set user=sybase group=dba mode=0600 volume
  -g resource-group
  
  Specifies the name of the resource group. This name can be your choice but must be unique for resource groups within the cluster.
  
  -h nodelist
  
  Specifies an optional comma-separated list of physical node names or IDs that identify potential masters. The order here determines the order in which the nodes are considered as primary during failover.
2. Verify that the changes are effective.
  # ls -lL /dev/vx/rdsk/diskgroup/volume
3. Reregister the disk device group with the cluster to keep the VxVM namespace consistent throughout the cluster.
  # scconf -c -D name=diskgroup

How to Create the Sybase ASE Database Environment

Before you perform this procedure, 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 Solstice DiskSuite/Solaris Volume Manager software or the VxVM software manage
Locate the Sybase ASE server logs in either the cluster file system or the local file system.
The Sybase ASE 12.0 environment consists of the data server, backup server, monitor server, text server, and XP server. The data server is the only server that you must configure—you can choose whether to configure all of the other servers.
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.

Perform the following steps to create the Sybase ASE database environment.

Run the GUI-based utility srvbuild to create the Sybase ASE database.

The $SYBASE/ASE_12-0/bin directory contains this utility. See the Sybase ASE document entitled 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.

See the Sybase Adaptive Server Enterprise System Administration Guide for details on changing the sa login password.

Create a new Sybase ASE account for fault monitoring.

This account enables the fault monitor to perform the following tasks.

Support queries to system tables.
Create and update 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

See Sun Cluster HA for Sybase ASE Fault Monitor for more information.

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.

See Important Security Issues for more information about the stop file.

Where to Go From Here

After you create the Sybase ASE database environment, go to Installing the Sun Cluster HA for Sybase ASE Packages.