Preparing to Install SAP ASE

Before you start the installer, prepare your system.

1. Back up your current system.
2. Verify that you can uncompress files on your UNIX machine. To uncompress:

   Option	Description
   .zip files	Use the unzip command
   .tgz files	Use gzip or GNU Tar

3. For Sun Solaris SPARC 64-bit, before the installation, set the file descriptors limit to a specific value. After the installation is complete, you can set the file descriptors to unlimited.
4. Ensure that the account used to start the server has read and write permissions for the directory in which you are installing the server. You may need to create nonadministrative logins to install the server into personal directories.
5. Review the SySAM licensing procedures, and plan your server configuration using the configuration guide for your platform.
6. For consistency and security, create an account with administrative privileges. This user account could be "sybase" or any other user name. Use this account to perform all installation and device-creation tasks.

   This user must have permission privileges from the top (or root) of the disk partition or operating system directory, down to the specific physical device or operating system file. Maintain consistent ownership and privileges for all files and directories. A single user—the system administrator with read, write, and execute permissions—should perform all installation, upgrade, and setup tasks.

   If you are installing SAP ASE on more than one computer, create the "sybase" user account on each machine.

7. Log in to the machine as “sybase.”
8. If you have enabled the Java in the database feature, create the sybpcidb database and disable the feature during the installation.
9. Decide where to install SAP ASE:
   • Make sure there is sufficient disk space and temporary directory space available.
   • Ensure there are no spaces in the path name of the directory.
10. Decide whether you want licensing events to trigger e-mail alerts, and the severity of the events that generate e-mail messages.
    If you choose to have e-mail notifications for license events, know your:

    • SMTP server host name
    • Port number for an SMTP server
      Note: If SAP assigns any port numbers to you for use with SAP ASE, exclude these numbers from any port-scanning software you run. SAP ASE attempts to service each scan as a login attempt, which may lead to poor performance.
    • E-mail return address
    • Recipients of the notifications
    • Severity level of an event that triggers mail. Your choices are:
      • None
      • Informational
      • Warning
      • Error
11. Verify that your network software is configured.

    SAP ASE and client applications use network software even when they are installed on a machine that is not connected to a network.

    If you are having connection problems, or to verify your network configuration, ping the host.

12. Adjust the shared memory for your operating system.

• Adjusting the Operating System Shared Memory Parameters
  Adjust shared memory segments if SAP ASE cannot obtain large memory as a single segment, or if Backup Server stripes fail due to insufficient segments.
• Managing Java in the Database During Installations and Upgrades
  If you have enabled Java in the database, create the sybpcidb database before installing or upgrading to SAP ASE version 16.0.
• Multipathing
  Multipathing is the ability of a server to communicate with the same physical or logical block storage device across multiple physical paths between the host bus adapters (HBAs) in the server and the storage controllers for the device, typically in Fibre Channel (FC) or iSCSI SAN environments. You can also achieve multiple connections with direct attached storage when multiple channels are available.