Using the Sybase ASE Toolkit in a Serviceguard Cluster on HP-UX README: Release B.06.00

Again, using a naming convention for the VG(s) that includes the

instance

name (${ASE_SERVER}) could be used to associate a VG with a

unique

instance.

EXAMPLE:

use with Asynchronous disk access and file systems:

/dev/vg01_SYBASE0/lvol1 #Logical volume Sybase ASE data

/dev/vg02_SYBASE0/lvol1 #Logical volume Sybase ASE data

/dev/vg02_SYBASE0/lvol2 #Logical volume Sybase ASE data

Please refer to the Sybase ASE documentation to determine which format

more appropriate for the setup environment that user prefers.

File system for Sybase ASE data files:

/SYBASE0 - mount point for /dev/vg03_SYBASE0/lvol1

All data belonging to the database must reside on shared logical

volumes

(file system), space needs to be allocated and shared for the

following:

- Sybase ASE system data tables

- Sybase ASE indexes

- Sybasse ASE stored procedures

- Sybase ASE transaction log files

After defining the shared volume groups/logical volumes/file systems

for

these entities, refer to Sybase ASE documentation for creating

the

database.

D. Setting up the Toolkit

- Toolkit Setup

After installing the toolkit, this README and SGAlert.sh file will be

/opt/cmcluster/toolkit/sybase directory. One script will be present in

/etc/cmcluster/scripts/ecmt/sybase directory. The other file for

package attribute definition file will be present in the