Configuring Sybase ASE Database Access and Creating the Sybase ASE Database Environment

Configuring Sybase ASE database access and creating the Sybase ASE Database Environment involves the following tasks.

1. Configuring Sybase ASE database access with the volume manager that you are using:

   • If you are using Solstice DiskSuite/Solaris Volume Manager, see How to Configure Sybase ASE Database Access With Solstice DiskSuite/Solaris Volume Manager.

   • If you are using VERITAS Volume Manager (VxVM), see How to Configure Sybase ASE Database Access With VERITAS Volume Manager.

2. Creating the Sybase ASE database environment

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

Steps

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

   For information about how to configure Solstice DiskSuite/Solaris Volume Manager, see Sun Cluster Software Installation Guide for Solaris OS.

2. 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 disk set

      /rdsk/dn

      Specifies the name of the raw disk device within the metaset disk set

   2. Verify that the changes are effective.

      # ls -lL /dev/md/metaset/rdsk/dn

Next Steps

Go to How to Create the Sybase ASE Database Environment.

How to Configure Sybase ASE Database Access With VERITAS Volume Manager

Steps

1. Configure the disk devices for the VxVM software to use.

   For information about how to configure VERITAS Volume Manager, see Sun Cluster Software Installation Guide for Solaris OS.

2. 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

Next Steps

Go to How to Create the Sybase ASE Database Environment.

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 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.

Steps

1. 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).

2. 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.

3. 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.

4. 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

   ---

   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 Sun Cluster HA for Sybase ASE Fault Monitor.

5. 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.

Next Steps

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