Preinstallation Tasks for the Server Installation

Ensure that there is at least 1 gigabyte of space available in the temp directory before beginning the installation.

Install the appropriate operating system patches on each node.

If you are installing on a Linux system and have the environment variable LD_ASSUME_KERNEL set, unset the variable before installing.

Shut down all clusters that use the previous version of the Cluster Edition before beginning the software installation.

If you are having trouble starting the installer, make sure you have the required operating system patches for the Java Runtime Environment (JRE) version 6. Information about the required system patches is available from the Sun Java Web site.

Create a “sybase” account on your system to perform all installation tasks.

This account should own all devices and files, and must have permission to read and write all devices the cluster uses.
Create all devices with the “sybase” account.
Ensure that all disk devices are accessible from all the nodes in the cluster.
Ensure that the account used to start the cluster has permissions to read and write to all of the disk devices.
Ensure that the cluster and the SCSI generic driver have write permission on the /dev/sg* files that correspond to configured database devices. The SCSI driver expects write access to /dev/sg* files for SCSI-3 PGR commands used in IO fencing.

Ensure that the current shell has the appropriate inheritable privileges.

sudo lssecattr -p $$ 
    487528 eprivs= mprivs= iprivs=PV_KER_RAS lprivs=PV_ROOT uprivs= 
    > $SYBASE/ASE-15_0/bin/iofenceutil /dev/rhdisk2 
    /dev/rhdisk2

If it is not fence capable, grant the current shell the appropriate inheritable privileges.
```
sudo setsecattr -p iprivs=+PV_KER_RAS $$ 
Then restart UAF
```

Use the ls -l commands to verify paths and file permissions.

Use the dd utility to verify that the sybase account can read and write to the devices.

If you need to change the permissions, use chmod or chown to correct the write permissions for /dev/sg* files. You can change the access permissions for these files to root only after rebooting the machine. Write permissions should be corrected prior to starting the server.

Log in to the machine as the “sybase” user. Maintain consistent ownership and privileges for all files and directories. A single user—the Sybase system administrator with read, write, and execute permissions—should perform all installation, upgrade, and setup tasks.

If you do not have open administrative priviledges you must create a destination directory prior to running InstallAnywhere.

If you are using a local account local to just one physical box, then create the sybase user on each machine and make sure it has the same user ID.

Decide where the Adaptive Server software will be installed.

Make sure there is sufficient disk space and temporary directory space available.
Ensure that there are no spaces in the path name of the directory.
If this is a shared installation, the $SYBASE location must be on a shared file system, accessible from all cluster nodes using the same path.
If this is a private installation, install the Adaptive Server software on each node of the cluster.
Each instance in the cluster must have its own $SYBASE directory. The private installation mode does not use a Network File System (NFS) or cluster file system.

Verify that the operating system meets the version-level, RAM, and network protocol requirements for your platform.

Verify that your network software is configured. The Cluster Edition implicitly requires that your network be configured for the nodes you plan to include in the cluster. If you are having connection problems, or to verify your network configuration, ping the host.

Adjust the operating system shared memory parameter for your platform. See Adjusting the Operating System Shared Memory Parameters for information on how to do this.