Preinstallation tasks

If you plan to install both Open Server and Adaptive Server on the same machine, install Open Server before installing Adaptive Server.

If you have already installed Adaptive Server, answer yes during the Open Server installation when you are prompted to override Open Server, srvlib, Common Client Library, and Client Library components. Then use the Adaptive Server 15.0.3 installation program to reinstall CT-lib components.

Before installing Adaptive Server:

Read the release bulletins for the latest information on the products (Adaptive Server, Monitor Server, and so on) that you are installing. See “Special Installation Instructions” in the release bulletin.

Install operating system patches, if required.

For information about operating system requirements, see “System requirements”.
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 operating system patches is available from the Sun Java Web site.
Review the SySAM procedures and plan your client/server configuration using the configuration guide for your platform.
Create a “sybase” account on your system to perform all installation tasks.

The “sybase” 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.
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 are installing Adaptive Server 15.0.3 over an existing Adaptive Server 15.0.x version then, and the Java in the database feature is enabled, perform these steps:
- Create the sybpcidb database, which stores configuration information for the Pluggable Component Interface (PCI) and all Pluggable Component Adapter (PCA) components. This database is used by the installpcidb script. For example:
```
1> disk init
2> name = “sybpcidb_dev”
3> physname = “${SYBASE}/data/sybpcidb_dev.dat”
4>size = '24MB'
4>go
6> create database sybpcidb on sybpcidb_dev = 24
6> go
```
  The device and database sizes depend on the Adaptive Server page size:
  - 2k page size – 24MB
  - 4k page size – 48MB
  - 8k page size – 96MB
  - 16k page size – 192MB
  If you are upgrading from a 15.0.x Adaptive Server, disable the Java feature before you upgrade, and reenable it after you have finished the upgrade.
  
  To disable the Java feature, use:
```
1> sp_configure 'enable java',
2> go
```
Know what product edition you are installing. The options are:
- Enterprise Edition
- Small Business Edition
- Developers Edition – Available on Linux x86, 64-bit, Solaris SPARC, and Windows systems.
If you are installing the Small Business or Enterprise Edition, you must know the license type under which Adaptive Server was licensed. For more information about license types, see the “License types” in Chapter 3 “Getting and Using your License” of the Sybase Software Asset Management Users Guide.
Sybase recommends that you specify license types at the time of installation. However, you may choose to specify the product edition and license type later using sp_lmconfig. For information on sp_lmconfig, see Reference Manual:Procedures.
You must decide if 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, you must know the:
- SMTP server host name
- Port number for an SMTP server
- E-mail return address
- Recipients of the notifications
- Severity level of an event that triggers mail. Your choices are:
  - None
  - Informational
  - Warning
  - Error
Verify that the operating system meets the version-level, RAM, and network protocol requirements for your platform.
Adjust shared memory segments.

Depending on the number and types of devices used for backup (dump) and recovery (load), you may need to adjust the shared memory segment parameter in the operating system configuration file to accommodate concurrent Backup Server processes. The default number of shared memory segments available for process attachments is 6.

If after adjusting the SHMMAX parameter the server fails to reboot you may also need to increase the value of another Kernel parameter, SHMALL, which is the maximum amount of shared memory that can be allocated. Its value is in the file /proc/sys/kernel/shmall. This task requires root permission.