System Requirements

Before installing Adaptive Server, ensure that your system is updated with the latest patches and system requirements. Do not use a patch that is earlier than the version suggested for your operating system. Use the patch recommended by the operating system vendor, even if it supersedes the patch listed.

To list all currently installed patches and display the operating system version level, enter:
rpm -q -a
Note: The Java Virtual Machine (JVM) and associated Adaptive Server support require at least 250MB of virtual memory space to start, and may need more depending on the requirements of the individual Java executions. For this reason, you may need to adjust the memory parameters when running Java to ensure that it has enough virtual memory space to start, and that both Adaptive Server and Java tasks can successfully coexist.

In particular, systems that have Adaptive Server total memory set to a value higher than 1.5GB (or 2.5GB on some Enterprise servers) may experience problems, and you may have to reduce Adaptive Server total memory.

Linux Requirements for Cluster Edition

Adaptive Server specifications for Linux
Hardware Memory
Processor AMD Opteron Processor or Intel Xeon with EM64T support
Minimum RAM required for Adaptive Server 128MB
Default user stack size 86KB
Minimum RAM per additional user Approximately 233KB
Operating system requirements for Linux
Hardware Operating system Updates Preferred RAM
x86_64 processor (AMD Opteron or Intel Xeon with EM64T) Red Hat Enterprise Linux Server release 5.5 (Tikanga)
  • kernel-2.6.18-194.el5
  • glibc-2.5-49
  • compat-glibc-2.3.4-2.26
5 At least 1GB
x86_64 processor (Intel Xeon with EM64T) Red Hat Enterprise Linux Server release 6.0 (Santiago)
  • kernel-2.6.32-71.el6.x86_64
  • glibc-2.12-1.7.el6.x86_64
  • compat-glibc-2.5-46.2.x86_64
1 1GB
x86_64 processor (AMD Opteron or Intel Xeon with EM64T) SuSE Linux Enterprise Server 11 (x86_64); version 11 patch level 0:
  • kernel-2.6.27.19-5.1
  • glibc-2.9-13.2
3 1GB
Note: If you install on RHEL5 with glibc2.5 or higher, SLES 10.2 or higher, or SuSE 10 or 10.1, before you start your server or Backup Server, set:
  • For SuSE10 or 10.1:export LD_POINTER_GUARD=1
  • For RHEL5 with glibc2.5 or higher and SLES 10.2 or higher:export LD_POINTER_GUARD=0
Minimum disk space requirements for Linux
Platform Typical Installation Default Databases Management Features Total Disk Space Requirements
Linux x86-64 794MB 150MB 25MB 969MB
Clustered file system for Linux
Operating System Product
RHEL 4, 5 Global File System 6.1
SuSE Enterprise 9, 10 OCFS2
Adaptive Server requires these X/Motif-related RPM package manager files before you can start the installation:
  • libXtst-devel
  • openmotif-devel
  • libXmu-devel
  • libXt-devel
  • libXext-devel
  • libXp-devel
  • libX11-devel
  • libSM-devel
  • libICE-devel
These files should be compatible with RHEL5.3 or later.

Before you can install a 64-bit Adaptive Server version 15.7 to a Red Hat Enterprise Linux 6.x x86_64, install the 32-bit GNU C Libraries package (glibc-2.xx-x.xx.el6.i686.rpm).

Ensure that you have the required operating system patches for the Java Runtime Environment (JRE) version 6.

Information about the required operating system patches is available from http://www.java.com/en/download/help/linux_install.xml.

See the Clusters Users Guide for hardware requirements for using Infiniband, Interconnect on a production system. Sybase does not support file system devices when running on multiple nodes.

If you intend to run the cluster under Symantec Storage Foundation for Sybase Cluster Edition, see Chapter 11, “Using the Cluster Edition with the Veritas Cluster Server,” in the Clusters Users Guide. Veritas Cluster Server for Sybase Cluster Edition is only supported on Solaris Sparc64 and Linux x86-64. It is not available for Solaris x86-64.

Database devices in the Cluster Edition must support SCSI-3 persistent group reservations (SCSI PGRs). Cluster Edition uses SCSI PGRs to guarantee data consistency during cluster membership changes. Sybase cannot guarantee data consistency on disk subsystems that do not support SCSI PGRs (such a configuration is supported for test and development environments that can tolerate the possibility of data corruption).