ASE installation is a topic that is not often taught through formal instruction. It seems to be assumed the database administrator can thumb through the ASE installation manuals and complete the task. While this is often true, a simpler, step-by-step approach is needed. The approaches outlined in this chapter contain some examples of how to install ASE and its components, and offer screen shots, steps, and command-line examples from three different methods of ASE installation. This chapter highlights how to install ASE, along with how to install some of the ASE components such as ASE Backup Server and the Job Scheduler. The installation process descriptions attempt to remain platform independent; however, the screen shots and examples are representative of the installation steps for Solaris systems and Windows environments.

For the installation of ASE, this chapter offers instructions for three installation types:

The authors of this book have installed countless ASE servers, using all of the mentioned installation methods in this chapter. Installing ASE through the GUI and launching with srvbuild for Unix environments or syconfig.exe for Windows environments is the simplest method for beginners. This method offers a step-by-step question/ answer interface, which also reminds the database administrator of all installation options available.

As database administrators become more advanced and are responsible for a multitude of servers, the resource file installation method is perhaps the best installation method. It will reduce the amount of time the database administrator spends performing installations.

Prior to Installation for All Methods

Prior to beginning the installation process with any installation method, several tasks must be completed:

Some items are optional for the installation process of ASE:

Installation with Resource Files

According to many industry contacts, installation of ASE with the use of a resource file is a common method of installation for environments where database administrators are required to support many ASE servers. As such, this chapter covers resource file installation first, before continuing with installations through the graphical server build utility.

The resource file installation method provides the database administrator three main advantages:

%SYBASE%\%SYBASE_ASE%*.res

$SYBASE/$SYBASE_ASE/*.res

C:\%SYBASE%\%SYBASE_ASE%insybatch.exe

C:sybaseASE-15_0in>sybatch -r %SYBASE%\%SYBASE_ASE%myserver.res

$SYBASE/$SYBASE_ASE/srvbuildres

$SYBASE/$SYBASE_ASE/bin/srvbuldres −r $SYBASE/$SYBASE_ASE/myserver.res

C:sybaseASE-15_0in>sybatch -r %SYBASE%\%SYBASE_ASE%myserver.res
Running task: update Sybase Server entry in interfaces file.
Task succeeded: update Sybase Server entry in interfaces file.
Running task: create the master device.
Building the master device
.........Done
Task succeeded: create the master device.
Running task: update Sybase Server entry in registry.
Task succeeded: update Sybase Server entry in registry.
Running task: start the Sybase Server.
waiting for server 'SYBASE_BRIAN' to boot...
waiting for server 'SYBASE_BRIAN' to boot...
waiting for server 'SYBASE_BRIAN' to boot...
Task succeeded: start the Sybase Server.
Running task: create the sybsystemprocs database.
sybsystemprocs database created.
Task succeeded: create the sybsystemprocs database.
Running task: install system stored procedures.
Installing system stored procedures : 10% complete...
Installing system stored procedures : 20% complete...
Installing system stored procedures : 30% complete...
Installing system stored procedures : 40% complete...
Installing system stored procedures : 50% complete...
Installing system stored procedures : 60% complete...
Installing system stored procedures : 70% complete...
Installing system stored procedures : 80% complete...
Installing system stored procedures : 90% complete...
Installing system stored procedures : 100% complete...
Task succeeded: install system stored procedures.
Running task: set permissions for the 'model' database.
Task succeeded: set permissions for the 'model' database.
Running task: set local Adaptive Server name.
Task succeeded: set local Adaptive Server name.
Running task: set the XP Server for the Adaptive Server.
Task succeeded: set the XP Server for the Adaptive Server.
Running task: update XP Server entry in registry.
Task succeeded: update XP Server entry in registry.
Running task: set the default character set and/or default sort order for the
Adaptive Server.
Setting the default character set to cp850
Sort order 'binary' has already been installed.
Character set 'cp850' is already the default.
Sort order 'binary' is already the default.
Task succeeded: set the default character set and/or default sort order for the
Adaptive Server.
Running task: set the default language.
Setting the default language to us_english
Language 'us_english' is already the default.
Task succeeded: set the default language.
Running task: install sybsystemdb database.
sybsystemdb database extended.
Task succeeded: install sybsystemdb database.
Running task: shutdown the Sybase Server.
Waiting 15 seconds for the operating system to reclaim resources before rebooting.
Task succeeded: shutdown the Sybase Server.
Running task: start the Sybase Server.
waiting for server 'SYBASE_BRIAN' to boot...
waiting for server 'SYBASE_BRIAN' to boot...
Task succeeded: start the Sybase Server.
Configuration completed successfully.
Exiting.
The log file for this session is 'C:sybaseASE-15_0initlogslog1107.005'.

#
# --- This file was generated by Sybase InstallShield Installer ---
#
sybinit.boot_directory:                        C:sybase
sybinit.release_directory:                     C:sybase
sqlsrv.do_add_server:                          yes
sqlsrv.network_hostname_list:                  BRIAN
sqlsrv.network_port_list:                      2125
sqlsrv.network_protocol_list:                  tcp
sqlsrv.notes:
sqlsrv.connect_retry_delay_time:               5
sqlsrv.connect_retry_count:                    5
sqlsrv.new_config:                             yes
#
sqlsrv.server_name:                            SYBASE_BRIAN
sqlsrv.sa_password:
sqlsrv.sa_login:                               sa
sqlsrv.server_page_size:                       2k
#
# --- Set up master ----
#
sqlsrv.master_device_physical_name:            C:sybasedatamaster2.dat
sqlsrv.master_device_size:                     200
sqlsrv.master_db_size:                         150
sqlsrv.disk_mirror_name:
#
# --- Set up sybsystemprocs ----
#
sqlsrv.do_create_sybsystemprocs_device:        yes
sqlsrv.sybsystemprocs_device_physical_name:    C:sybasedatasysprocs2.dat
sqlsrv.sybsystemprocs_device_size:             200
sqlsrv.sybsystemprocs_db_size:                 200
sqlsrv.sybsystemprocs_device_logical_name:     sysprocsdev
#
# --- Set up sybsystemdb ----
#
sqlsrv.do_create_sybsystemdb:                  yes
sqlsrv.do_create_sybsystemdb_db_device:        yes
sqlsrv.sybsystemdb_db_device_physical_name:    C:sybasedatasybsysdb2.dat
sqlsrv.sybsystemdb_db_device_physical_size:    3
sqlsrv.sybsystemdb_db_size:                    3
sqlsrv.sybsystemdb_db_device_logical_name:     sybsystemdb
#
sqlsrv.errorlog:                               C:sybaseASE-15_0install
                                               SYBASE_BRIAN.log
sqlsrv.sort_order:                             binary
sqlsrv.default_characterset:                   cp850
sqlsrv.default_language:                       us_english
#
sqlsrv.preupgrade_succeeded:                   no
sqlsrv.network_name_alias_list:
sqlsrv.resword_conflict:                       0
sqlsrv.resword_done:                           no
sqlsrv.do_upgrade:                             no
sqlsrv.characterset_install_list:
sqlsrv.characterset_remove_list:
sqlsrv.language_install_list:
sqlsrv.language_remove_list:
sqlsrv.shared_memory_directory:
sqlsrv.addl_cmdline_parameters:
sqlsrv.eventlog:                               yes
sqlsrv.atr_name_shutdown_required:             yes
sqlsrv.atr_name_qinstall:                      no
#
sybinit.charset:                               cp850
sybinit.language:                              us_english
sybinit.resource_file:
sybinit.log_file:
sybinit.product:                               sqlsrv
#
sqlsrv.default_backup_server:                  SYBASE_BRIAN_BS

#
# --- This file was generated by Sybase InstallShield Installer ---
#
# Creating a Job Scheduler and Self Management
#
sybinit.boot_directory:                         C:sybase
sybinit.release_directory:                      C:sybase
sybinit.product:                                js
sqlsrv.server_name:                             SYBASE_BRIAN
sqlsrv.sa_login:                                sa
sqlsrv.sa_password:
js.do_add_job_scheduler:                        yes
js.job_scheduler_agent_name:                    SYBASE_BRIAN_JSAGENT
js.network_port_list:                           4905
js.network_hostname_list:                       BRIAN
js.network_protocol_list:                       tcp
js.do_create_sybmgmtdb:                         yes
js.sybmgmtdb_device_physical_name:
   C:sybasedatasybmgmtdb2.dat
js.sybmgmtdb_device_logical_name:               sybmgmtdev
js.sybmgmtdb_device_size:                       75
js.sybmgmtdb_db_size:                           75
js.do_add_self_management:                      yes
js.self_management_login:                       sa
js.self_management_password:

C:sybaseASE-15_0in>sybatch -r %SYBASE%\%SYBASE_ASE%js.res

$SYBASE/$SYBASE_ASE/bin/srvbuldres −r $SYBASE/$SYBASE_ASE/js.res

C:sybaseASE-15_0in>sybatch -r %SYBASE%\%SYBASE_ASE%js.res
Running task: Update Job Scheduler Agent entry in interfaces file.
Task succeeded: Update Job Scheduler Agent entry in interfaces file.
Running task: Create Sybase management database.
Created Sybase management database
Task succeeded: Create Sybase management database.
Running task: Install Sybase management stored procedures.
Installing Sybase management stored procedures : 10% complete...
Installing Sybase management stored procedures : 20% complete...
Installing Sybase management stored procedures : 30% complete...
Installing Sybase management stored procedures : 40% complete...
Installing Sybase management stored procedures : 50% complete...
Installing Sybase management stored procedures : 60% complete...
Installing Sybase management stored procedures : 70% complete...
Installing Sybase management stored procedures : 80% complete...
Installing Sybase management stored procedures : 90% complete...
Installing Sybase management stored procedures : 100% complete...
Task succeeded: Install Sybase management stored procedures.
Running task: Install Job Scheduler stored procedures templates.
Task succeeded: Install Job Scheduler stored procedures templates.
Running task: Install Job Scheduler XML templates.
C:sybaseASE-15_0jobschedulerTemplatesxmlenSybBackupDbToDiskTemplate.xml
.Done
C:sybaseASE-15_0jobschedulerTemplatesxmlenSybBackupLogToDiskTemplate.xml
.Done
C:sybaseASE-15_0jobschedulerTemplatesxmlenSybDeleteStatsTemplate.xml
.Done
C:sybaseASE-15_0jobschedulerTemplatesxmlenSybRebuildIndexTemplate.xml
.Done
C:sybaseASE-15_0jobschedulerTemplatesxmlenSybRebuildTableTemplate.xml
.Done
C:sybaseASE-15_0jobschedulerTemplatesxmlenSybReclaimIndexSpaceTemplate.xml
.Done
C:sybaseASE-15_0jobschedulerTemplatesxmlenSybReclaimTableSpaceTemplate.xml
.Done
C:sybaseASE-15_0jobschedulerTemplatesxmlenSybReconfLocksTemplate.xml
.Done
C:sybaseASE-15_0jobschedulerTemplatesxmlenSybReconfMdCacheTemplate.xml
.Done
C:sybaseASE-15_0jobschedulerTemplatesxmlenSybReconfUsrConnsTemplate.xml
.Done
C:sybaseASE-15_0jobschedulerTemplatesxmlenSybUpdateStatsTemplate.xml
.Done
C:sybaseASE-15_0jobschedulerTemplatesxmlenSybSvrUpdateStatsTemplate.xml
.Done
Task succeeded: Install Job Scheduler XML templates.
Running task: Set Job Scheduler Agent name.
Task succeeded: Set Job Scheduler Agent name.
Running task: Enable Job Scheduler.
Exiting.
The log file for this session is 'C:sybaseASE-15_0initlogslog1107.006'.

GUI Installation Method with srvbuild Executable

After the Sybase software is downloaded from the Sybase Product Download Center (SPDC) or the installation CD is mounted to the system, the Sybase ASE software will need to be unpacked. Locate the setup executable for ASE and run it.

Installation with the srvbuild or setup utility with ASE 15 launches an InstallShield Wizard to accomplish the installation process. This installation method, in the author’s opinion, is the most time-consuming option.

On all operating environments, a similar look and feel will exist with the ASE 15 Installer. With the Sybase Installer, the database administrator traverses through a series of GUI screens, participating in a question and answer session with the common interface.

The following preinstallation step is necessary for Unix environments:

For Unix environments, the GUI installation assumes the database administrator has the X-Windows environment set up. Additionally, the $DISPLAY environment variable must be set up to direct the X-Windows session to the appropriate client session. This involves locating the client’s IP address and setting the $DISPLAY environment variable to reflect the client’s IP address.

One method to obtain the IP address is to first open a DOS session on the Windows client:

Figure 12-1

Then obtain the IP address with the ipconfig command:

Figure 12-2

Within the context of an X-Windows session, set the $DISPLAY environment variable to reflect the client’s IP address, and append “:0.0” to the end of the IP address:

UNIXhost:~ 7> setenv DISPLAY 192.68.0.101:0.0

Step 1: For Windows, run the setup.exe executable from the directory containing the Sybase ASE 15 software. Click OK once the path and executable are designated.

Figure 12-3

For Windows systems, the following message may appear depending on the security settings enabled. Click OK.

Figure 12-4

The InstallShield application is launched.

Figure 12-5

For Unix:

Similar to the setup.exe executable in Windows environments, the Unix installation executable will launch a GUI-based Installer application. The prompt to launch the Unix installer is as follows:

$SYBASE/$SYBASE_ASE/bin/srvbuild

Step 2: At this stage of the installation process, it is recommended to shut down all Sybase products on the host server. Click Next on the Welcome screen to begin the installation.

Figure 12-6

Step 3: Select your country of origin, and accept the license agreement by clicking on the “I agree” radio button. Click Next.

Figure 12-7

Step 4: Pick the appropriate location for the unpacked Sybase binaries, and the $SYBASE or %SYBASE% directory, then click Next.

Figure 12-8

If the chosen Sybase directory does not exist, click Yes, and the Sybase installer will create the designated directory.

Figure 12-9

Step 5: Select the appropriate installation type. For most installations, the “Typical” installation is sufficient. This book will proceed with the “Custom” installation to demonstrate the interactive menu system for all possible installation items. After selecting the “Custom” radio button, click Next.

Figure 12-10

Step 6: Since this installation is custom, the GUI will direct the database administrator to a preselected list of installation options. Check items to designate products for installation. After products are selected, click Next. For this installation, the Job Scheduler Templates and Utilities are added to the installation.

Figure 12-11

Step 7: The installation GUI will check system information at this step.

Figure 12-12

Step 8: After system information is verified, review and confirm the software to be installed by the Installer program. At this stage, the installation contents could be modified by clicking the Back button.

Figure 12-13

Step 9: On the same screen, scroll to the bottom to verify how much physical disk will be utilized by the unpacked Sybase ASE software. For this installation example, the Installer program indicates 929.6 MB of disk will be utilized by the Sybase software alone. Click Next to confirm the installed items.

Figure 12-14

Step 10: The GUI Installer will then begin the process of extracting the Sybase software.

Figure 12-15

Step 11: After the Sybase software extraction is complete, a confirmation message is displayed. Click Next to proceed.

At this stage of the installation of the ASE 15 software, the installation process could be aborted if an alternative installation method is desired. Reasons to abort the installation process at this stage could be a need to build an ASE server with a resource file, or with the creation of a server using the dataserver binary.

This stage may also be a good point to stop in the installation process to perform pre-upgrade validations against pre-ASE 15 installations.

Figure 12-16

Step 12: Next, the installation asks for information on how to obtain ASE licenses. On this screen, the host name and port number of the Sybase Software Asset Management is placed into the GUI by the Installer. SySAM was covered in Chapter 11, so at this point we will not make any license manager selections. This will be an example of the “Try and Buy” installation.

For reference, if “Yes” is selected, have the host name and port number available for the host of the Sybase Software Asset Management.

Figure 12-17

If you choose “No,” this screen will gray out the host and port number selections. Click Next to proceed.

Figure 12-18

Step 13: An information message will be displayed, reminding you to download and install the license file after this installation. Additionally, the SySAM host and port number can be supplied at a later time. The different license approaches are discussed in Chapter 11.

Figure 12-19

Step 14: The next screen will allow the configuration of the email alert mechanism. This is for the publication of license information to a designated email address. Enter the SMTP email host name along with the SMTP server’s port number, the sender’s and recipient’s email addresses, and the severity level for messages generated by SySAM. Click Next when complete.

Figure 12-20

Step 15: Select the license type to install, and click Next.

Figure 12-21

Step 16: With the ASE 15 Installer, the database administrator can configure ASE and other ASE-related products through the installation process. Check any products that need to be configured during the installation process and click Next.

Figure 12-22

Step 17: The next screen asks for which items need to be configured during the installation process. Click any items to be configured where the default values are not acceptable, and then click Next.

Figure 12-23

Step 18: Next, select configuration options for ASE, including the server name, page size, errorlog location, and master device size. Remember, the server’s page size cannot be changed after the server is built. Choose a value for the server’s page size carefully. As a general guideline, a page size of2Kisideal for OLTP-based systems, while larger page sizes are preferable for DSS-based systems. The page size of2Kisthedefault, and is recommended to be selected if the system’s usage type is unknown. Click Next when complete.

Figure 12-24

Step 19: At this stage, the entries for the ASE server are complete. This exercise continues with the installation steps for ASE’s Backup Server. On this screen, accept or modify entries for the ASE Backup Server. Click Next when complete.

Figure 12-25

Step 20: Accept or modify entries for the Sybase Monitor Server, and click Next when complete.

Figure 12-26

Step 21: At this stage, the entries for the Backup Server are complete. This example continues with the installation selections for the XP Server. Select a port number for the XP Server or accept the default and click Next.

Figure 12-27

Step 22: At this stage, the installation selections for ASE, Backup Server, and XP Server are complete. This example continues with the option selections for installing the Job Scheduler Agent. On the next screen, accept the default entries for the Job Scheduler Agent, or modify the defaults and then click Next.

Figure 12-28

Step 23: Enter the login ID to be used for Self Management of ASE. Click Next to select the default of sa, or enter a different login and click Next.

Figure 12-29

Step 24: For the installation of the Sybase Unified Agent, select the appropriate adapter type and configuration settings for the Sybase Unified Agent interface. Click Next when complete.

Figure 12-30

Step 25: Select the Security Login Modules for the Unified Agent, then click Next when complete.

Figure 12-31

Step 26: At this stage, all entries for ASE, ASE Backup Server, XP Server, Job Scheduler, and the Unified Agent are complete. Take a moment to review the settings from the options selected through the GUI screens. If the entries presented by the New Servers Summary screen are correct, click Next to proceed with the server specifications selected.

Figure 12-32

Step 27: The Installer will then proceed to build the master device and commence the installation of all selected products.

Figure 12-33

Step 28: Upon success, the message in Figure 12-34 will display.

Figure 12-34

Upon failure of any product, a message similar to the one shown in Figure 12-35 will display.

Figure 12-35

If no errors occurred, click the radio button to restart the computer for Windows environments and click OK. For Unix-based environments, it is not necessary to reboot the host server.

Installation with the Dataserver Executable

A third method of installation is the dataserver executable method. This method is perhaps the most “brute force” installation for ASE. The installation involves invoking the dataserver executable with several parameters to tell ASE how to build a very basic and incomplete server. Upon completion of the installation with the dataserver executable, the result is a very basic server.

A valid reason to choose this type of installation is the independence from X-Windows for various environments. Independence from X-Windows may be necessary due to an inability to set up the environment. You may also choose this if the installation needs to be performed via a remote connection. If a remote connection is slow, the installation process with X-Windows can take considerable time.

To invoke the ASE installation for Unix environments:

dataserver −b200m -d /Sybase/master.dat −e/Sybase/errorlogs/errorlog/
   SYBASE.log −sSYBASE −z2k

For Windows environments:

Sqlsrvr −b200m −d c:Sybasemaster.dat −e c:Sybaseerrorlogserrorlog
   SYBASE.log −sSYBASE −z2k

After the dataserver executable is executed, a master device and an errorlog are present, but not much else. In order to launch ASE after this step, the following steps are necessary:

#!/bin/sh
#
# ASE page size (KB):   2k
# Master device path:   /dev/vx/rdsk/sandg/master
# Error log path:       /sybase/logs/errorlog_BRIAN_TEST
# Configuration file path:
   /sybase/sybase15/ASE-15_0/BRIAN_TEST.cfg
# Directory for shared memory files:    /sybase/sybase15/ASE-15_0
# Adaptive Server name: BRIAN_TEST
#
#LM_LICENSE_FILE="9999@hostname:9999@hostname”
SYBASE_LICENSE_FILE="9999@hostname:9999@hostname:4030@hostname"
export SYBASE_LICENSE_FILE
# setenv SYBASE_LICENSE_FILE 9999@hostname:9999@hostname:4030@hostname

/sybase/sybase15/ASE-15_0/bin/dataserver 
-sBRIAN_TEST 
-d/sybase/master.dat 
-e/sybase/logs/BRIAN_TEST.log 
-c/sybase/sybase15/ASE-15_0/BRIAN_TEST.cfg 
-M/sybase/sybase15/ASE-15_0 

rem
rem Adaptive Server Information:
rem name:                           SYBASE
rem master device:                  C:sybasedatamaster3.dat
rem server page size:               2048
rem master device size:             200
rem errorlog:                       C:sybaseerrorlogSYBASE.log
rem interfaces:                     C:sybaseini
rem
C:sybaseASE-15_0insqlsrvr.exe -dC:sybasedatamaster3.dat
   -sSYBASE_150 -eC:sybaseerrorlogSYBASE.log -iC:sybaseini
   -MC:sybaseASE-15_0

SYBASE
   master tcp ether BRIAN 2500
   query tcp ether BRIAN 2500

[SYBASE]
master=NLWNSCK,BRIAN,2500
query=NLWNSCK,BRIAN,2500

$SYBASE/$SYBASE_ASE/install ./startserver -f RUN_SYBASE

C:%SYBASE%\%SYBASE_ASE%install>startsrv.exe -f RUN_SYBASE.bat

disk init name="sysprocsdev",
physname = "/dev/vx/rdsk/rootdg/sysprocsdev",
size=128000
go
create database sybsystemprocs on sysprocsdev = 250
go

disk init name = "sysprocsdev",
Physname = "C:sybasesysprocsdev.dat",
Size = 128000
go
create database sybsystemprocs on sysprocsdev = 250
go

host:~/Sybase/ASE-15_0/scripts > isql -Usa -SBRIAN_TEST
   -i./installmaster -o./installmaster.out
host:~/Sybase/ASE-15_0/scripts > isql -Usa -SBRIAN_TEST
   -i./installmodel -o./installmodel.out
host:~/Sybase/ASE-15_0/scripts > isql -Usa -SBRIAN_TEST
   -i./installupgrade -o./installupgrade.out
host:~/Sybase/ASE-15_0/scripts > isql -Usa -SBRIAN_TEST
   -i./instmsgs.ebf -o./instmsgs.ebf.out

C:sybaseASE-15_0scripts>isql -Usa -SSYBASE -iinstmstr
   -oinstmstr.out
C:sybaseASE-15_0scripts>isql -Usa -SSYBASE -iinstmodl
   -oinstmodl.out
C:sybaseASE-15_0scripts>isql -Usa -SSYBASE -iinsupgrd
   -oinsupgrd.out
C:sybaseASE-15_0scripts>isql -Usa -SSYBASE -iinstmsgs.ebf
   -oinstmsgs.out

Summary

This chapter has touched upon three different yet common installation methods for ASE and the supporting components. Each of the installation methods has advantages and disadvantages that depend upon the level of expertise and confidence of the database administrator. Additionally, each installation method has appropriate areas of application that can be selected based upon the needs of the individual server installation requirements. As indicated in the beginning of this chapter, a general trend toward resource file installations is expected as experience level and the number of servers supported by a database administrator or DBA team increase.