SAP 16.0 SP01 ASE Installation Guide

SAP Adaptive Server Enterprise 16.0 SP01

Document Version: 1.0 – 2015-02-25

Installation Guide for Solaris

PUBLIC

Content

1 Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5

2

2.1

Installation Task Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SAP ASE Software Download. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6

6

2.2 Installation Workflows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6

3

3.1

SAP ASE Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8

SAP ASE Editions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8

Determining the Edition You Have. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9

3.2 SAP ASE Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9

3.3 Managing SAP ASE with SAP Control Center. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

10

3.4 Client Components and Utilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

11

4

4.1

Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13

Solaris System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13

4.2 SAP Java Runtime Environment Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

14

4.3 Memory Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

14

4.4 System Requirements for Clients. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

15

5

5.1

5.2

Planning Your SAP ASE Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

16

SAP ASE Release Bulletin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

16

Obtaining a License. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

16

Comparing License Deployment Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

18

SySAM License Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

19

Determining Host IDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

19

Generating Licenses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

21

Knowing the Product License Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

23

5.3 Installation Directory Contents and Layout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

25

5.4 Creating the SAP ASE User Account. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

27

5.5 Preparing to Install SAP ASE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

28

Adjusting the Operating System Shared Memory Parameters. . . . . . . . . . . . . . . . . . . . . . . . . .

29

Managing Java in the Database During Installations and Upgrades. . . . . . . . . . . . . . . . . . . . . . .

31

Multipathing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

32

6

6.1

Installing SAP ASE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Installing SAP ASE in GUI Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

34

34

6.2 Installing SAP ASE in Console Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

38

6.3 Minimally Configuring an SAP ASE Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

39

2

P U B L I C

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Installation Guide for Solaris

Content

6.4 Installing SAP ASE Using a Response File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

44

Creating a Response File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

44

Installing in Silent Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

46

Command Line Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

47

6.5 Uninstalling SAP ASE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

47

Removing an Existing SAP ASE Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

48

7 Starting and Stopping SAP Control Center. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

49

8

8.1

Postinstallation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

51

Verifying That Servers are Running. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

51

8.2 Verifying Your Connection to the Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

52

8.3 Test the Installation and Network Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

53

8.4 The System Administrator Account. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

54

8.5 Installing Sample Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

54

Default Devices for Sample Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

55

Running the Database Scripts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

55

Installing the interpubs Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

56

Installing the jpubs Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

56

Maintaining Sample Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

57

9

9.1

SAP ASE Upgrades. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

59

Considerations When Upgrading from SAP ASE 15.0.x or Earlier. . . . . . . . . . . . . . . . . . . . . . . . . . .

60

9.2 Considerations for Component Integration Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

61

9.3 Preparing to Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

61

9.4 Changes in SAP ASE Directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

62

9.5 Preupgrade Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

64

Upgrade Stored Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

66

Reserved Words. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

66

Preparing the Database and Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

68

The sybprocsdev device. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

69

9.6 Upgrade to SAP ASE 16.0 SP01. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

73

Upgrading Interactively Using sqlupgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

73

9.7

Upgrading Noninteractively Using sqlupgraderes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

75

Manually Upgrading SAP ASE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

77

Install and Upgrade an Existing Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

77

Upgrading in Silent Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

82

9.8 Postupgrade Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

83

Running the instmsgs.ebf Script. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

84

Restoring Functionality in SAP ASE After Upgrading. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

85

Reenabling Auditing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

86

Restoring Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

87


Content

P U B L I C


3

9.9 Migrate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

87

Migrating Data Using a Dump-and-Load Method. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

87

Migrating Data Using bcp. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

88

Migrating Data by Replacing the Binary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

89

9.10 SAP ASE Components and Related Products. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

89

Upgrading Job Scheduler. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

90

Upgrading High Availability and Cluster Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

94

Upgrading Java in the Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

95

Upgrading Backup Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

96

Upgrading Databases Using Dump and Load. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

96

How Compiled Objects Are Handled When Upgrading SAP ASE. . . . . . . . . . . . . . . . . . . . . . . . .

97

10 SAP ASE Downgrades. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

101

10.1 Downgrading from SAP ASE Version 16.0 SP01. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

101

10.2 Dumping a 16.0 SP01 Database to Load Into an Older Version of SAP ASE 16.0. . . . . . . . . . . . . . . .

103

10.3 Downgrading Job Scheduler. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

104

10.4 Post-downgrade Tasks for SAP ASE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

105

11 Troubleshoot the Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

106

11.1 Error Logs for Installation Utilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

106

11.2 Error Logs for SAP ASE Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

107

11.3 Troubleshooting Common Installation Problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

107

If the Installation Quits While You Are Configuring an SAP ASE Server. . . . . . . . . . . . . . . . . . .

109

11.4 Stopping a SAP ASE Server After a Failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

109

11.5 If SAP ASE Fails the Preupgrade Eligibility Test. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

110

11.6 When an Upgrade Fails. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

110

If You Can Identify the Cause of the Upgrade Failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

110

Restoring Databases After a Failed Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

111

Recovering from a Failed Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

111

If You Cannot Identify the Cause of an Upgrade Failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

113

4

P U B L I C



Content

1 Conventions

These style and syntax conventions are used in SAP Adaptive Server Enterprise (SAP ASE) documentation.

● In a sample window display, commands to be entered exactly as shown appear in: this font

● In a sample window display, words that you should replace with the appropriate value for your installation are shown in:

<this font>

● In the regular text of this document, the names of files and directories appear in this font: /usr/u/ home_dir.

● The names of programs, utilities, procedures, and commands appear in this font: sqlupgrade.

● Commands for both the C shell and the Bourne shell are provided, when they differ. The initialization file for the C shell is called .cshrc. The initialization file for the Bourne shell is called .profile. If you are using a different shell, such as the Korn shell, refer to your shell-specific documentation for the correct command syntax.

Table 1: SQL Syntax Conventions

Key Definition command Command names, command option names, utility names, utility flags, and other keywords are in a bold san-serif font.

<variable >

{ }

Variables, or words that stand for values that you fill in, are in italic.

Curly braces indicate that you choose at least one of the enclosed options. Do not include braces in your option.

[ ]

Brackets mean choosing one or more of the enclosed options is optional. Do not include brackets in your option.

() are to be typed as part of the command.

( )

The vertical bar means you can select only one of the options shown.

|

,

The comma means you can choose as many of the options shown as you like, separating your choices with commas, which are typed as part of the command.


Conventions

P U B L I C


5

2 Installation Task Overview

To successfully install and configure SAP ASE, use the configuration guide along with this installation guide.

The SAP ASE installation guide explains how to unload the SAP ASE software from the distribution media to your hard disk, and perform the minimal set of additional tasks so that you can start SAP ASE on your machine.

The configuration guide provides instructions for:

● Reconfiguring certain attributes of your existing SAP ASE, Backup Server™, and XP Server™ to meet your specific needs.

● Creating network connections.

● Configuring optional functionality.

● Performing operating system administrative tasks.

● Working with system administration issues that are relevant to SAP ASE running on UNIX platforms. This manual supplements the System Administration Guide and the Performance and Tuning Series.

2.1 SAP ASE Software Download

The SAP ASE installation and update packages are available on the SAP Software Download Center (https:// support.sap.com/software.html).

● Installation media for an SAP ASE:

SAP Software Download Center Installations and Upgrades A-Z Index Installations and Upgrades -

A SAP ADAPTIVE SERVER ENTERPRISE SAP ASE 16.0 SP01 Installation

● Support Packages and Patches for SAP ASE:

SAP Software Download Center Installations and

Upgrades A-Z Index Installations and Upgrades - A SAP ADAPTIVE SERVER ENTERPRISE SAP ASE

16.0 SP01 Support Packages and Patches SAP ASE Server 16.0 SP01

2.2 Installation Workflows

Workflows define a complete path for planning, installing, and upgrading.

Whether you plan to install or upgrade SAP ASE, identify the components and options to install or upgrade, and obtain a license.

6

P U B L I C



Installation Task Overview

Installing SAP ASE for the First Time

1. Plan your installation and review system requirements.

2. Install SAP ASE.

3. Perform postinstallation tasks.

Upgrading to a New Version of SAP ASE

1. Determine your upgrade eligibility, plan your installation, and review system requirements.

2. Run the preupgrade utility to prepare SAP ASE for upgrading.

3. Upgrade SAP ASE.

4. Perform postinstallation (postupgrade) tasks.

Uninstalling SAP ASE

See

Uninstalling SAP ASE [page 47] .


Installation Task Overview

P U B L I C


7

3 SAP ASE Components

SAP ASE is based on a client/server model, communicating with its clients over the network via the Tabular

Data Stream™ (TDS) protocol. Each client process may execute on one machine and communicate with a database server on the same or a different machine.

SAP ASE runs as an application on top of an operating system. The hardware that the operating system runs on is completely transparent to SAP ASE, which sees only the operating system's user interfaces. To enhance performance on multiprocessor systems, configure multiple processes (engines).

SAP ASE is divided into a DBMS component and a kernel component. The kernel component uses the operating system services for process creation and manipulation, device and file processing, and interprocess communication. The DBMS component manages SQL statement processing, accesses data in a database, and manages different types of server resources.

3.1 SAP ASE Editions

Analyze your system and scalability requirements to determine which edition of SAP ASE is appropriate for your enterprise.

● Enterprise edition – has no limit on scalability and supports all of the options that can be purchased or licensed separately.

● Small business edition – has limited scalability, and supports a limited set of the options that are purchased or licensed separately.

● Developer edition – has limited scalability and includes many of the options that are included in the enterprise edition.

See the SySAM Users Guide for information about unlocking editions and optional features.

The SAP ASE installer automatically installs a SySAM license server if you choose the full installation option or enter a served license when prompted for the SySAM license key. You can also install the license server using the installer's custom installation option. See the SySAM Users Guide to generate licenses.

8

P U B L I C



SAP ASE Components

3.1.1 Determining the Edition You Have

If you already use SAP ASE, use the sp_lmconfig system procedure to identify the version.

Procedure

Enter: sp_lmconfig 'edition'

SAP ASE returns a value of EE, SE, or DE based on the edition that is currently running. See the Reference

Manual for more information about sp_lmconfig.

3.2 SAP ASE Options

SAP offers various optional features for SAP ASE, such as data compression, partitions, and encrypted columns.

Option

Data compression

Security and directory services

Partitions

Description

Enables compression for regular and large object data, which uses less storage space for the same amount of data, reduces cache memory consumption, and improves performance due to lower I/O demands.

Provides lightweight directory services and network-based authentication and encryption using SSL and Kerberos.

Enables semantic partitioning for table row data.

Encrypted columns Increases security parameters and allows for addition of datatypes.

Tivoli storage manager Enables the database to back up and restore operations to IBM Tivoli Storage

Manager.

In-memory database Provides zero-disk-footprint in-memory database support that is fully integrated with SAP ASE for high-performance transactional applications. Provides performance enhancements to disk-resident databases with relaxed durability properties.

High availability Supports the creation of a two-node hardware cluster with each node running SAP

ASE. If one server fails, the other server automatically picks up its database operations and client connections.

SAP ASE editions and optional features are unlocked by SySAM licenses. See the SySAM Users Guide.

To install any of these optional features to an existing SAP ASE installation, use the same steps as you used to install SAP ASE.



P U B L I C


9

3.3 Managing SAP ASE with SAP Control Center

SAP Control Center (SCC) provides a single, comprehensive, Web-administration console for real-time performance, status, and availability monitoring of large-scale SAP enterprise servers.

SAP Control Center combines a modular architecture, a rich-client administrative console, agents, common services, and tools for managing and controlling SAP products. It includes historical monitoring, thresholdbased alerts and notifications, alert-based script execution, and intelligent tools for identifying performance and usage trends.

The SAP ASE installer installs these SAP Control Center components:

● Remote Command and Control Agent for SAP ASE – a remote command and control agent that runs on a managed server, and which is required to manage SAP ASE tasks within SCC.

● SNMP support for SAP ASE – Simple Network Management Protocol is a standard protocol used for network management. SNMP allows managers and agents to communicate: managers send requests to agents, and agents respond to queries from managers.

In addition, you must also install the SCC Management User Interface for SAP ASE in the custom installation option by selecting the

SAP Control Center Management User Interface for SAP ASE

feature. This feature provides the GUI that allows you to manage and monitor activities in SAP ASE using a Web browser.

In some cases, you may want to use a central SCC server to manage multiple SAP ASE servers and other products rather than using the SCC server that is installed with each SAP ASE server. Deployment considerations include:

● Minimizing network latency – you see better performance if you install SCC near the monitored servers and near the workstations on which SCC Web clients are running.

● Unified SCC environment – installing SCC in a central location lets you manage and monitor your servers from a single SCC installation, which is especially useful in a replication environment.

● Administration and security – you can exercise differing levels of control in different parts of your enterprise, for example, by protecting the data in some servers more strictly than in others.

See Preinstallation Tasks in SAP Control Center Installation Guide for details on installation and deployment considerations.

In a production environment, we recommend that you install the SCC server on a machine other than the one you plan to run SAP ASE on.

See the following for detailed SCC information:

● SAP Control Center Release Bulletin – provides last-minute installation and upgrade information, as well as known problems.

● SAP Control Center Installation Guide – provides complete installation, configuration, and troubleshooting procedures.

● SAP Control Center for SAP Adaptive Server Enterprise – includes SAP ASE configuration procedures, user assistance, and troubleshooting information.

Related Information

Starting and Stopping SAP Control Center [page 49]

10

P U B L I C




SAP ASE Upgrades [page 59]

Installing SAP ASE in GUI Mode [page 34]

Minimally Configuring an SAP ASE Server [page 39]

3.4 Client Components and Utilities

There are several components that you can install onto a PC client to support the SAP ASE server, which are downloaded from the SAP Service Marketplace (SMP). The previous PC-Client installer is replaced in SAP ASE

16.0 SP01 by separately downloadable installers that provide many of the same components.

SDK for SAP ASE

The SAP Community Network provides both 32-bit and 64-bit SDK for SAP ASE images. Download the software development kit (SDK) that matches your version of Windows (32- or 64-bit).

Included in the SDK are:

Product

Open Client™

DataAccess

Description

In addition to Open Client (Client Library, dblib), the following, which are all installed into the OCS-16_0 directory:

● ESQL/C

● ESQL/COBOL

● XA

● SAP ASE extension module for Python

● SAP ASE database driver for Perl

● SAP ASE extension module for PHP

Installed into the DataAccess64 directories:

● ODBC – a driver used that connects to SAP ASE from ODBC-based applications.

● ADO.NET – a provider used that connects to SAP ASE from .NET-based applications.

Java Runtime

Environment (JRE)

Installed into the shared directory, JRE is a runtime Java virtual machine used to execute Java-based programs, such as Interactive SQL, and which is shared by several other components.

Language Modules Installed into the locales directory. Provides system messages and date/time formats.

Character Sets Installed into the charsets directory. Provides character sets that are available for use with SAP ASE.

jConnect Installed into the jConnect-16_0 directory, jConnect provides a Java Database

Connectivity (JDBC) driver for SAP ASE.



P U B L I C


11

Product

Interactive SQL

jutils-3_0

utilities

Description

Installed into the DBISQL-16_0 directory, Interactive SQL is a GUI tool that allows you to execute SQL statements, build scripts, and display data from SAP ASE.

A collection of SAP ASE utility programs that includes ribo, a tool to trace TDS traffic between a client program and SAP ASE.

For download and installation instructions, see 2093510

PowerDesigner Physical Modeler

The modeler is available in the ASE SAP 16.0 SP01 section of the SAP Service Marketplace, and is installed from its own image.

To install the modeler, download and extract the 16.0 SP01 file, then run setup.exe in your root directory.

SySAM Utilities

Access these utilities by searching for

sysam 2.3

in the SAP Service Marketplace.

See the SySAM 2 Users Guide.

QP-Tune

Run this components from the SAP ASE server image directly.


Installation Directory Contents and Layout [page 25]

12

P U B L I C




4 Requirements

Before installing SAP ASE version 16.0 SP01, install 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: showrev -p

4.1 Solaris System Requirements

Verify that your system is up-to-date. 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.

All Solaris systems support the TCP protocol, which requires:

● Sun4u Architecture – Solaris 10, 11

Solaris 64-bit platform system requirements are:

● Processor – 64-bit

● Minimum RAM for SAP ASE – 106MB

● Default user stack size – 94KB

● Memory per user connection – approximately 245KB

Note

SAP ASE supports the 128-bit Zettabyte File System (ZFS) on Solaris 10. To guarantee data integrity, set

DSYNC on. You can turn DSYNC off only for temporary databases that do not require recovery. Use only

DSYNC, as ZFS does not support direct I/O.

Solaris patch requirements:

● Solaris 10 SPARC:

○ 120753-05

○ 120048-03

○ 144190-03

○ 148888-03

● Solaris 10 x64 – 148889-03

● Solaris 11 – Solaris 11U1(11.1) SRU 7 or later, including Solaris 11U2

These patches address an Oracle bug for Solaris::

● Solaris 10 SPARC – 148888-03


Requirements

P U B L I C


13

● Solaris 10 x86/x64 – 148889-03

● Solaris 11 – the latest support repository and update (SRU) containing the fix for Oracle Bug 16054425

Note

Applications running against SAP ASE on Solaris (SPARC and x64) in threaded mode may experience poor performance (response time and throughput). Analysis of sp_sysmon outputs and MDA tables may show high I/O Busy% and high wait times on disk-related events. To prevent this, install Oracle

Bug 16054425 and set the SAP ASE configuration parameter "solaris async i/o mode" to 1: sp_configure "solaris async i/o mode", 1

Solaris disk space requirements:

● Typical installation

○ 64-bit: 985MB

● Default databases created during installation – 306MB

● Total

○ 64-bit: 1141MB

4.2 SAP Java Runtime Environment Requirements

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

For JRE requirements, see 1367498 . Log in with your SAP support account to view the SAP note.

Java applications, such as sybdiag, sybmigrate, and dbisql, which run using SAP JRE, may encounter the following error:

A fatal exception has occurred.

This error is caused by exceeding the number of possible semaphores on the machine running the Java application.

To avoid this error, use the ipcrm utility to terminate semaphores, for example, ipcrm –s

<semid>

, or restart the machine.

4.3 Memory Requirements

Each operating system has a default maximum shared-memory segment. Configure your operating system to allow the allocation of a shared-memory segment at least as large as the maximum memory value.

The amount of memory SAP ASE can use is:

● On Oracle Solaris 10 (SPARC) – 16 GB

● On Oracle Solaris 10 on AMD (x86) – chip-dependent

14

P U B L I C



Requirements

4.4 System Requirements for Clients

Check the system requirements for the machine on which you plan to install the client applications and utilities.

Type

Product

Requirement

Programs and utilities installed onto the PC client

Hardware

Operating system

X86 or X64 system running Xeon or AMD 1.5 GHz or faster

Windows Server 2012, Windows 2008 R2 SP1, Windows 2008 x86, Windows 8,

Windows 7 SP1

Suggested minimum RAM 512MB

Note

If you are using ODBC or ADO.NET drivers, make sure that Microsoft .NET Framework 2.0 Service Pack 1 is installed on your Windows machine. To confirm that it is installed, select

Control Panel Add or Remove

Programs

and verify that .NET Framework appears in the list of currently installed programs.


Requirements

P U B L I C


15

5 Planning Your SAP ASE Installation

Before you install or upgrade, prepare your environment.

Procedure

● Identify the components and options to install or upgrade.

● Obtain a license.

Note

If you are using a served license, you must install the SySAM license server version 2.3 or later.

● Make sure your system meets all requirements for your installation scenario and planned use.

5.1 SAP ASE Release Bulletin

The release bulletin contains last-minute information about installing and upgrading SAP ASE software.

The latest release bulletins are available at the SAP ASE Help Portal at http://help.sap.com/adaptive-serverenterprise .

5.2 Obtaining a License

Before installing your product, choose a SySAM license model, and obtain license files from the SAP Service

Marketplace (SMP) at http://service.sap.com/licensekeys

Context

Note

If you purchased your product from Sybase or an authorized Sybase reseller and have not been migrated to

SAP Service Marketplace (SMP), go to the Sybase Product Download Center (SPDC) at https:// sybase.subscribenet.com

to generate license keys.

16

P U B L I C



Planning Your SAP ASE Installation

Procedure

1. Choose a SySAM license model.

License Model Description

Unserved license model

Licenses are obtained directly from the license file. If you are using an unserved license, save the license file to the machine on which you install the product.

Served license model

A license server manages the allocation of licenses among multiple machines.

Note

The SAP ASE installer automatically installs a SySAM license server if you choose the full installation option or enter a served license when prompted for the SySAM license key. You can also install the license server using the installer's custom installation option. See the SySAM Users Guide to generate licenses.

2. For the served license model, decide whether to use an existing or new license server.

The license server and your product installation need not share the same machine, operating system, or architecture.

Note

There can be only one instance of a SySAM license server running on a given machine. To set up a

SySAM 2 license server on a machine that is already running a SySAM 1.0 license server, follow the migration instructions in the SySAM Users Guide. A migrated license server can serve licenses for both

SySAM 1.0 and SySAM 2-enabled products.

3. Get your host IDs.

When you generate licenses, you must specify the host ID of the machine where the licenses will be deployed.

○ For unserved licenses – the host ID of the machine where the product will run. If you are running a product with per-CPU or per-chip licensing that supports SySAM sub-capacity and want to run the product in a virtualized environment, see SySAM Sub-capacity Licensing in the SySAM Users Guide.

○ For served licenses – the host ID of the machine where the license server will run.

4. Before installing your product, obtain license files from SMP or from SPDC using the access information in your welcome e-mail message.

Note

If you purchased your software from a reseller, rather than an e-mail message you may receive a Web key certificate that contains the location of the SPDC Web key login page at https:// sybase.subscribenet.com/webkey and the activation key to use for the login name.

If you plan to use sub-capacity licensing, see the SySAM Users Guide for information on how to configure using the sysamcap utility.

Use sp_lmconfig to configure and show license management-related information in SAP ASE. See sp_lmconfig in Reference Manual: Procedures.



P U B L I C


17

5.2.1 Comparing License Deployment Models

Learn about license deployment models.

Table 2: Differences Between Unserved and Served Licenses

Unserved Licenses Served Licenses

Licenses can be used only on the machine for which the li cense was generated.

Licenses can be distributed from a network license server to products running on any network machine.

Generate licenses at SMP or SPDC for each machine that will run the product:

1. Specify the host ID of the machine where the product will run.

2. Generate a license for that machine.

3. Save the license to the specified machine.

4. Repeat steps 1 – 3 for each machine where the product will run.

Generate licenses at SMP or SPDC for products running on multiple machines:

1. Specify the host ID of the license server.

2. Specify the number of required licenses.

3. Save the licenses to the license server host machine.

No license administration is required. However, when new li censes are required for product updates, you must update and deploy each license for each machine where the prod uct update will run.

The license server requires administration. When new li censes are required for product updates, SMP or SPDC lets you update all licenses for a specific license server in a sin gle step.

No license reporting or asset management capabilities are available.

Allows license monitoring and reporting of license use, ca pacity planning, and asset management.

Installed locally and always available.

Requires a functioning license server and network. If the li cense server or network fails, you must fix the problem or install an alternate license server before the product grace period expires.

If a machine where the product is running fails, you must re generate all of its licenses and deploy those licenses to the replacement machines.

If a machine where the product is running fails, you can move the product to a new machine, and it will acquire li censes from the running license server.

If the license server host machine fails, use the Manage Li cense Hosts functionality at SMP or SPDC to move its li censes to a new network license server host.

License files are distributed across each machine running a product, and therefore they are difficult to manage and con trol.

License files are centrally located and managed.

Unserved Standalone Seat (SS) licenses do not allow prod uct use via Remote Desktop Connection or other terminal services clients.

Products can be used via Remote Desktop Connection or other Terminal Services clients, irrespective of the type of li cense in use.

18

P U B L I C




5.2.2 SySAM License Server

If you choose to use the served licensed model, make sure you have installed the required SySAM license server version.

The license server is a lightweight application that serves licenses to products running on any operating system.

A license server can run on a low-end machine or a machine with spare cycles. For example, a license server running on a Solaris UltraSparc-60 serving 100 different licenses to 200 product instances, used 50MB of memory, 5 minutes of CPU time per week, and 100MB of disk space per year.

SAP ASE 16.0 SP01 requires SySAM 2.3 or later. To determine the current license server version, use the sysam version command.

Note

This command is not available in SySAM version 2.0 and earlier.

Download the latest SySAM version from http://service.sap.com/patches .

SAP ASE 16.0 SP01 and SySAM 2.3 use FlexNet Publisher version 11.11.

To check the version of FlexNet Publisher used by your license server, examine the license server log or execute the lmgrd -v command.

The license server installer is available in the

<ASE_installer>

/sysam_setup directory.

Note

You cannot start the license server until there is at least one served license saved to the licenses directory on the license server host machine.

5.2.3 Determining Host IDs

When you generate licenses at SMP, you must specify the host ID of the machine where the licenses will be deployed.

Context

● For unserved licenses, specify the host ID of the machine where the product will run. If you are running a product with per-CPU or per-CHIP licensing that supports SySAM sub-capacity, and you want to run the product in a virtualized environment, see SySAM Sub-capacity Licensing in the SySAM Users Guide for information about determining the host ID for unserved licenses.

● For served licenses, specify the host ID of the machine where the license server will run.

SMP remembers the host information so that you can select the same license server when generating additional licenses.



P U B L I C


19

To determine the host ID of the machine, run the lmutil utility from a terminal window or the Windows command prompt. For example: lmutil lmhostid

Note

You can download the lmutil utility from either:

● The SAP ASE installer image, under the sysam_utilities directory; or,

● The Flexera Software Web site at http://www.globes.com/support/fnp_utilities_download.htm

.

.

You can also determine the host ID using native operating system commands. See the Frequently Asked

Questions topic "What is my Host ID?" at https://websmp208.sap-ag.de/~sapidb/

011000358700001006652011E (requires login)

5.2.3.1 Determining Host IDs for Machines with Multiple

Network Adapters

On some platforms, the host ID is derived from the network adapter address.

Context

If the machine where your product is installed or where the license server is hosted has multiple network adapters, running lmutil lmhostid returns one host ID for each network adapter, and returns output similar to this:

The FLEXlm host ID of this machine

is ""0013023c8251 0015c507ea90""

Only use ONE from the list of hostids.

It is important that you:

● Choose only one host ID to enter during license generation.

● Use the value associated with the primary wired Ethernet adapter.

● Do not use values associated with internal loopback or virtual adapters.

If you cannot determine the host ID using the lmutil lmhostid output, use the native operating system commands to get additional details.

20

P U B L I C




5.2.3.2 Using Alternate Host IDs on Windows

If your Windows machine does not have a network adapter, SySAM allows you to use an alternate host ID based on the hard disk serial number.

Procedure

1. At a Windows command prompt on the machine where you will deploy your license, enter: lmutil lmhostid -vsn

This returns output similar to:

The FLEXlm host ID of this machine is "DISK_SERIAL_NUM=70ba7a9d"

2. Use the complete output (DISK_SERIAL_NUM=70ba7a9d) for the host ID value requested during license generation.

5.2.4 Generating Licenses

Before you generate licenses, gather the necessary information and complete these tasks.

Table 3: Information Needed Before Generating Licenses

Required Information or Ac tion

Served Licenses Unserved Licenses Description

License deployment model X X Decide whether to use a served or unserved license deployment model.

Typically, this is a companywide decision that is made only once. Therefore, this is one of the most important things to determine before li cense generation.

Product machine host ID X Determine the host ID of the machine, or machine parti tion where the product will run.



P U B L I C


21

Required Information or Ac tion

Served Licenses

License server – download and install

X

License server host ID X

License server host name X

License server TCP/IP port numbers

X

Unserved Licenses Description

Download and install the Sy

SAM license server before you generate the product’s licenses, and before you in stall the product.

Determine the host ID of the machine where the license server will run.

Determine the host name of the machine where the li cense server will run.

Determine the two port num bers on which the license server will listen for license requests.

5.2.4.1 Generating License Keys at SMP

Use SMP to generate license keys.

Procedure

1. Go to the SAP Marketplace main page at http://service.sap.com/licensekeys .

2. Log in using your SMP credentials.

3. Select

SAP Support Portal

.

4. Select

Keys & Requests License Keys

.

5. Follow the instructions in the "How to generate license keys for SAP Sybase products" presentation available under the "Documentation and Helpful Resources" quick access link.

22

P U B L I C




5.2.5 Knowing the Product License Type

SAP sells products under different license types, which entitle the customer to different rights of use. For example, whether a product is entitled to be used in production, or standby, or development and test environments.

The license type determines the quantity of licenses required; dictating, for example, whether a license is required for each machine; or for each CPU, or CPU chip; or per terabyte of storage.

For example, a product purchased under the CPU License (CP) type requires one license per CPU on the machine, partition, or resource set where it will run. The same product purchased under the Server License

(SR) type requires a single license for the machine, partition, or resource set.

Your account can have the same product licensed under multiple license types. Make sure you select the correct license type when you generate your SySAM license file.

When you generate licenses, each license type is presented on the License Information screen in bold font. For example:

License Type: CPU License (CP)

5.2.5.1 Optional Feature Licenses

Some SAP ASE applications are offered as base products with optional features that require a separate license.

Customers can mix license types. For example, customers can order SAP ASE under the Server License (SR) license type and order an optional feature (for example, High Availability or Enhanced Full Text Search) under the CPU License (CP) type.

Optional features are licensed only with the base product of the same product edition. For example, if you order SAP ASE, you cannot use a Small Business Edition optional feature license with the Enterprise Edition base product. In addition, the entitled use of the license types must be compatible; for example, both types should allow use in a production environment.

5.2.5.2 SySAM Licensing Checkout

If SAP ASE is licensed using a per-processor license type, it checks out a license quantity equal to the number of processors, or, if insufficient licenses are available, allows a 30-day grace period.

If the number of processors is dynamically increased while running and the software cannot check out additional licenses, the software permits a 30-day grace period. If sufficient licenses are not made available within the grace period, the software shuts down. Decreasing the number of processors that the software can use while it is running does not reduce the required license quantity. You must restart the SAP ASE server on the correct number of processors.

See the SySAM Users Guide.



P U B L I C


23

5.2.5.3 Sub-capacity Licensing

Sub-capacity licensing allows you to license a subset of the CPUs available on a physical machine using the

SySAM sub-capacity license functionality.

Platform support

Table 4: SySAM Virtualization Sub-Capacity Compatibility

Vendor Product

HP nPar vPar

Integrity Virtual Machines with Re source Manager

Secure Resource Partitions

Platform Support

HP IA 11.31

IBM AIX 6.1, AIX 7

Sun

LPAR dLPAR

Dynamic System Domains

Solaris Containers/Zones with So laris Resource Manager

Sun Logical Domain (LDOM)

Solaris 10

Intel, AMD VMWare ESX Server Guest O/S:

Windows

Note

VMWare ESX Server excludes

VMWare Workstation, and

VMWare Server.

Virtualization Type

Physical partition

Virtual partition

Virtual machine

OS containers

Virtual partition

Virtual partition

Physical partition

Virtual partition

Virtual partition

VMWare ESX 3.5, ESX 4.0 and

ESX 4.1, ESXi4.1, ESXi 5.0,

Guest OS: Windows 2008 R2,

Windows 7

Virtual machine

VMWare ESX Server Guest OS: Li nux, Sun Solaris x64

VMWare ESX 3.5, ESX 4.0 and

ESX 4.1, ESXi4.1, ESXi 5.0,

Guest OS: RH 5.5, SuSE 11,

Sun Solaris x64

Virtual machine

24

P U B L I C




Vendor Product

Xen, KVM, DomainU: Windows

Note

Xen excludes Sun Solaris x64.

Xen, KVM, DomainU: Linux

Hyper-V

Platform Support Virtualization Type

Windows 2008 R2, Windows 7 Virtual machine

RH 5.5, SuSe 11

Windows 2008 R2

Virtual machine

Virtual machine

Enabling SAP ASE Sub-Capacity Licensing

If you purchased your product from Sybase or an authorized reseller, you must have a sub-capacity licensing agreement with SAP or Sybase before you can enable sub-capacity licensing.

Note

Keep your license server up-to-date.Although the installation media includes a copy of the most recent

SySAM license server, we recommend that you periodically check for updates at https://support.sap.com/ patches .

When using SySAM sub-capacity licensing, set the SYBASE_SAM_CAPACITY environment variable before installing, or copy in the license key after installation.

5.3 Installation Directory Contents and Layout

SAP ASE includes server components that are installed into specific directories.

Product

SAP ASE

Description

Installed into the ASE-16_0 directory.

● SAP ASE – the database server.

● Backup Server – an application based on SAP Open Server that manages all database backup (dump) and restore (load) operations.

● XP Server – an Open Server application that manages and executes extended stored procedures (ESPs) from within SAP ASE.

● Job Scheduler – provides a job scheduler for SAP ASE. Job Scheduler components are located in ASE-16_0/jobscheduler/.

Connectivity

Installed into the OCS-16_0 directory:



P U B L I C


25

Product Description

● Open Client™ (

<Client Library>

,

<dblib>

)

● ESQL/C

● ESQL/COBOL

● XA

Installed into the DataAccess and DataAccess64 directories:

● ODBC (Windows, Solaris SPARC, Solaris x64, Linux Power, HP-UX Itanium, IBM AIX)

– a driver used to connect to SAP ASE from ODBC-based applications.

● ADO.NET (Windows only) – a provider used to connect to SAP ASE from .NET based applications.

Shared Directory The shared directory contains components and libraries that are shared by several other components. In earlier versions, this directory was named shared-1_0.

● Java Runtime Environment (JRE) – is a runtime Java virtual machine used to execute Java-based programs, such as SAP Control Center. SAP ASE includes the

JRE. In typical installations, by default, the JRE is fully installed. In custom installations, if you select a component for installation that requires the JRE, the JRE is also automatically selected. It is located in the shared/SAPJRE-7_1 * directory.

SAP Control

Center

SAP Control Center logs and utilities – files related to the Web-based tool for monitoring the status and availability of SAP ASE servers. They are installed into the $SYBASE/

SCC-3_3 directory.

Language Modules Installed into the locales directory. Provides system messages and date/time formats.

Character Sets

Collation

Sequences

Sybase Software

Asset

Management

(SySAM)

Web Services

Installed into the charsets directory. Provides character sets that are available for use with SAP ASE.

Installed into the collate directory. Provides the collation sequences that are available for use with SAP ASE.

Installed into the SYSAM-2_0 directory. Provides asset management of SAP ASE servers and optional features.

Interactive SQL

jutils-3_0

Utilities

SAP jConnect for

JDBC

OData Server

Installed into the WS-16_0 directory. An optional product that provides access to SAP

ASE using HTTP/SOAP and WSDL.

Interactive SQL is a GUI tool that allows you to execute SQL statements, build scripts, and display data from SAP ASE. It is installed into the DBISQL-16_0 directory.

A collection of SAP ASE utility programs including ribo, a tool to trace TDS traffic between a client program and SAP ASE.

Installed into the jConnect-16_0 directory. Provides a Java Database Connectivity

(JDBC) driver for SAP ASE.

Installed into the ODATA-16_0 directory, OData (Open Data Protocol) enables data services over RESTful HTTP, allowing you to perform operations through URIs

(Universal Resource Identifiers) to access and modify information.

26

P U B L I C




Note

We strongly recommend that you install the ECDA DirectConnect option or MainframeConnect

DirectConnect for z/OS, including DirectConnect Manager, into its own directory.


Client Components and Utilities [page 11]

5.4 Creating the SAP ASE User Account

To ensure that SAP ASE product files and directories are created with consistent ownership and privileges, create a system administrator account.

Context

One user—typically the system administrator, who has read, write, and execute privileges—should perform all installation, configuration, and upgrade tasks.

Procedure

1. To create a system administrator account, choose an existing account, or create a new account and assign a user ID, group ID, and password for it.

This account is sometimes called the “sybase” user account. See your operating system documentation for instructions on creating a new user account.

If you have installed other SAP software, the "sybase" user should already exist.

2. Verify that you can log in to the machine using this account.



P U B L I C


27

5.5 Preparing to Install SAP ASE

Before you start the installer, prepare your system.

Procedure

1. Back up your current system.

2. Verify that you can uncompress files on your UNIX machine. To uncompress:

Option

.zip

files

.tgz

files

Description

Use the unzip command

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

28

P U B L I C




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.


Preupgrade Tasks [page 64]

Reenabling Auditing [page 86]

Managing Java in the Database During Installations and Upgrades [page 31]

5.5.1 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.

Context

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. There are six default shared memory segments available for process attachments.

If any reconfiguration through sp_configure requires additional memory, SAP ASE allocates shared memory segments after start-up. To account for these additional segments, allocate the maximum memory that is



P U B L I C


29

available to SAP ASE by using the allocate max shared memory configuration parameter. See the System

Administration Guide.

Procedure

1. If the installer cannot update to Solaris 10 patch ID 120012-14, edit your /etc/user_attr file with: sybase::::type=normal;project=project-sybase

--------------------

To confirm that the update to this patch has taken effect, use either of these commands:

# projects -d sybase project-sybase

# id -p sybase uid=204409(sybase) gid=1(other) projid=200(project-sybase)

This update allows changes to shared-memory parameters within Solaris 10.

2. 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.

SAP ASE may allocate shared memory segments after start-up if any reconfiguration through sp_configure requires additional memory. You may need to account for these additional segments.

Allocate the maximum memory available to SAP ASE, by using the allocate max shared memory configuration parameter. The default max memory size is 138MB. See the System Administration Guide for more information.

To adjust shared memory segments of the operating system, add the following line to the configuration file, where

<x>

is the number of shared memory segments./etc/system: set shmsys:shminfo_shmseg=

<x>

30

P U B L I C




5.5.2 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 SP01.

Procedure

1. 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 = "48M"

5> go

1> create database sybpcidb on sybpcidb_dev = 48

2> go

The device and database sizes depend on the SAP ASE server page size. The minimum and default size requirements for sybpcidb are:

○ 2KB page size server – 48MB

○ (Default) 4KB page size server – 96MB



2. Disable Java in the database:

1> sp_configure 'enable java', 0

2> go

3. Reenable the feature after you have successfully installed or upgraded to SAP ASE 16.0 SP01:


2> go




Preparing to Install SAP ASE [page 28]



P U B L I C


31

5.5.3 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.

Multipathing provides connection fault tolerance, failover, redundancy, high availability, load balancing, and increased bandwidth and throughput across the active connections. Multipathing automatically isolates and identifies device connection failures, and reroutes I/O to alternate connections.

Typical connection problems involve faulty adapters, cables, or controllers. When you configure multipathing for a device, the multipath driver monitors the active connection between devices. Because multipathing is managed at the device level, when the multipath driver detects I/O errors for an active path, it fails over the traffic to the device’s designated secondary path. When the preferred path becomes healthy again, control can be returned to the preferred path. Multipathing prevents single points of failure in any highly available system.

A common example of multipath connectivity is a SAN-connected storage device. Usually one or more Fibre

Channel HBAs from the host are connected to the fabric switch and the storage controllers are connected to the same switch. A simple example of multipath connectivity is: two HBAs connected to a switch to which the storage controllers are connected. In this case, the storage controller can be accessed from either of the HBAs that are providing multipath connectivity.

All OS platforms provide their own solutions to support multipathing. There are numerous other vendors that also provide multipathing applications for all available platforms, such as:

● AIX – Multiple Path I/O (MPIO)

● HP-UX 11.31 – Native MultiPathing (nMP)

● Linux – Device-Mapper (DM) Multipath

● Solaris – Multiplexed I/O (MPxIO)

● AntemetA Multipathing Software for HP EVA Disk Arrays

● Bull StoreWay Multipath

● NEC PathManager

● EMC PowerPath

● FalconStor IPStor DynaPath

● Fujitsu Siemens MultiPath

● Fujitsu ETERNUS Multipath Driver

● Hitachi HiCommand Dynamic Link Manager (HDLM)

● HP StorageWorks Secure Path

● NCR UNIX MP-RAS EMPATH for EMC Disk Arrays

● NCR UNIX MP-RAS RDAC for Engenio Disk Arrays

● ONStor SDM multipath

● IBM System Storage Multipath Subsystem Device Driver (SDD)

● Accusys PathGuard

● Infortrend EonPath

● OpenVMS

● FreeBSD - GEOM_MULTIPATH and GEOM_FOX modules

● Novell NetWare

● Sun StorEdge Traffic Manager Software

32

P U B L I C




● ATTO Technology multipath driver Fibreutils package for QLogic HBAs

● RDAC package for LSI disk controllers

● lpfcdriver package for Emulex HBAs

● Veritas Dynamic Multi Pathing (DMP)

● Pillar Data Systems

● Axiom Path

● iQstor MPA

5.5.3.1 Setting Up Multipathing

If you choose to use it, set up multipathing before you install SAP ASE.

Context

Solaris Multiplexed I/O (MPxIO) is a multipathing solution for storage devices that is part of the Solaris operating environment. The stmsboot program is an administrative command for managing enumeration of multipath-capable devices with Solaris I/O multipathing. Solaris I/O multipathing-enabled devices are enumerated under scsi_vhci(7D), providing multipathing capabilities. Solaris I/O multipathing-disabled devices are enumerated under the physical controller.

In the /dev and /devices trees, Solaris I/O multipathing-enabled devices receive new names that indicate that they are under Solaris I/O multipathing control. This means a device has a different name than its original name (after enabling) when it is under Solaris I/O multipathing control. The stmsboot command automatically updates /etc/vfstab and dump configuration to reflect the device names changes when enabling or disabling Solaris I/O multipathing. One reboot is required for changes to take effect.

Procedure

1. Run stmsboot -e to enable multipathing. The stmsboot -L option lists all available paths.

2. (Optional) You can also use the mpathadm command to manage multipathing.



P U B L I C


33

6 Installing SAP ASE

Install SAP ASE using your chosen method.

Prerequisites

Complete installation planning tasks.

Procedure

1. Choose an installation method:

○ GUI wizard (recommended)

○ Console mode

○ Response file

2. Follow the instructions for your chosen method.

3. Perform postinstallation steps.

6.1 Installing SAP ASE in GUI Mode

Use GUI mode to install SAP ASE and related products.

Prerequisites

Shut down all programs before running the installer.

Context

The installer creates the target directory (if it does not yet exist) and installs the selected components into that directory.

34

P U B L I C



Installing SAP ASE

Note

Version 16.0 included new major versions of SAP ASE and many supporting components. Installing version

16.0 and higher into the same directory with existing products should not impact the existing products.

SAP ASE version 15.5 and later uses InstallAnywhere for its installation, while versions earlier than 15.5 and other products use InstallShield Multiplatform. Do not use both installers to install products into the same directory, as this creates files to be installed incorrectly and overwritten without warning.

At the end of the installation, verify that the product has installed correctly. You may also need to perform additional configuration procedures.

Procedure

1. Insert the installation media in the appropriate drive, or download and extract the SAP ASE installation image from the SAP Service Marketplace (SMP).

2. If you downloaded the product from SAP Service Marketplace, go to the directory where you extracted the installation image and start the installer:

./setup.bin

3. If you are installing using a CD or DVD, mount the disk.

The location of the mount command is site-specific and may differ from the instructions shown here. If you cannot mount the drive using the path shown, check your operating system documentation or contact your system administrator.

The operating system automatically mounts the disk. Log in as “sybase.” If disk-reading errors occur, check your operating system kernel to make sure that the ISO 9660 option is turned on. If you have previously installed a Sybase disk on your system, the # sign interferes with the installation process.

Before installing your current disk, either:

○ Restart your system, or,

○ Eject the disk. Delete the

<Volume Label>

file in /vol/dsk, and reinsert the disk

4. Launch the installer: cd /

<device_name>

/Volume Label

./setup.bin

Where:

○

<device_name>

is the directory (mount point) you specified when mounting the CD or DVD drive.

○ setup.bin is the name of the executable file name for installing SAP ASE.

If there is not enough disk space in the temporary disk space directory, set the environment variable

IATEMPDIR to

<tmp_dir>

before running the installer again, where

<tmp_dir>

is where the installation program writes the temporary installation files. Include the full path to

<tmp_dir>

.

5. If you are prompted with a language selection list, specify the appropriate language.

6. On the Introduction screen, click

Next

.

7. Accept the default directory or enter a new path to specify where to install SAP ASE, then click

Next

.



P U B L I C


35

Note

Do not use the following when specifying the installation path:

○ Double-byte characters

○ Single- or double-quote characters

The installer does not recognize these, and displays an error.

If you see

Choose Update Installation

, this means that there is an older version of SAP ASE in the directory you specified for the installation, and you need to perform an upgrade rather than a new installation.

8. Select the type of installation:

Option Description

Typical (Default) Recommended for most users, this option installs a default set of components, including the SAP Control Center Remote Command and Control Agent plug-in. This option does not install the SySAM license server.

Full Installs every SAP ASE component, including all the supported language modules, as well as the SCC Agent plug-in and Management UI.

Customize Lets you select the components to install. Some components are automatically installed if they are required to run your selected components.

9. Select the software license type for the SAP ASE suite:

○

Install licensed copy of SAP ASE Suite

○

Install Free Developer Edition of SAP ASE Suite

○

Evaluate SAP ASE Suite

An evaluation is valid for 30 days from the installation date.

10. Choose the most appropriate region, read the license terms, then click

I agree

. Click

Next.

11. If you have a licensed copy of SAP ASE Suite:

1. Specify the license type:

○ Enter a license file. If it is a served license key, you are prompted to set up the license server.

○ Use an existing license server.

○ Proceed without specifying license information for the duration of 30 days from the installation date.

2. Specify the product edition:

○

Enterprise Edition

○

Small Business Edition

○

Developer Edition

○

Unknown

– select this if you are unsure about the license type.

Note

Choosing

Unknown

prevents you from being able to select

Optimize SAP ASE

later in the installation process.

Depending on the edition, you can also select the license type under which the product is licensed.

3. Configure your server to send e-mail notifications about license management events that require attention:

36

P U B L I C




○ SMTP server host name

○ SMTP server port number

○ E-mail return address

○ Recipient e-mail addresses

○ Message severity that triggers e-mail messages

12. In the preinstallation summary, verify the installation type and that you have enough disk space for the installation. Click

Next

.

The installation status window displays the result of the installation process.

13. In the Configure New Servers window, configure:

○ SAP ASE

○ Backup Server

○ XP Server

○ Job Scheduler

○ SAP Control Center

Note

When you connect to a server that you create during installation, log in using the -X option: isql -S

<server>

-U

<user>

-P

<pwd>

-I interfaces –X

14. If you select to configure an SAP ASE, you see:

1. The Configure with Different User Account window, which allows you to enable a different user for the

SAP ASE you are installing. If you click

Yes

to enable a different user for the SAP ASE you are installing, enter:

○ The name of the account

○ The password of the account

SAP ASE, Backup Server, XP Server, and Job Scheduler are then automatically configured under the account name you specify.

If you keep the default,

No

, the fields are disabled.

2. The User Configuration Data Directory window.

Note

The default directory is the installation directory. If you specified a different directory, make sure you or the account specified in the Configure with Different User Account window has write permission to it.

SAP ASE creates these files during installation to place in the data directory:

○ The interfaces file.

○ RUN_server file – in the ASE-16_0/install subdirectory.

○ Configuration utilities log files – in the ASE-16_0/init/logs subdirectory.

○ SAP ASE configuration file (.cfg) – in the ASE-16_0 subdirectory.

○ SAP ASE shared memory file (.krg) – in the ASE-16_0 subdirectory.

○ SAP ASE SySAM properties file – in the ASE-16_0/sysam subdirectory.

○ Job Scheduler template .ini files – in the ASE-16_0/jobscheduler/Templates subdirectory.



P U B L I C


37

Database device files and server error log files are also created in the data directory you specify, but you can move them after the installation is finished.

Next Steps

Configure some basic settings for SAP ASE, Backup Server, Job Scheduler self-management, Web Services, and the SAP Control Center.




Managing SAP ASE with SAP Control Center [page 10]

6.2 Installing SAP ASE in Console Mode

Choose command line installation if you prefer a nonwindowing interface, or if you are developing custom installation scripts.

Prerequisites

Launch the installer in console mode. If the installer launches automatically, click

Cancel

to cancel the GUI installation, then launch the setup program from a terminal or console.

Context

The steps for installing components in an interactive text mode are the same as those described for installing in GUI mode, except you use the following command to execute the installer from the command line, and you enter text to select installation options: setup.bin -i console

38

P U B L I C




Procedure

1. At the command line, start the installation program: setup.bin -i console

2. Follow the remaining prompts to install SAP ASE, then specify the basic settings for your installation. The flow of the installation is identical to a GUI installation, except output is written to a terminal window and responses are entered using the keyboard.

6.3 Minimally Configuring an SAP ASE Server

Use GUI mode to minimally configure an SAP ASE server and related products for use.

Prerequisites

The Configure screen shows a list of everything you can minimally configure. By default, all products are selected. Unselect any products you do not want to configure now. If you are configuring in console mode, enter the corresponding number:

● 1.

Configure New SAP ASE

● 2.

Configure New Backup Server

– see the System Administration Guide

● 3.

Configure New XP Server

– see the Transact-SQL Users Guide

● 4.

Configure Job Scheduler

– see the Job Scheduler Users Guide

● 5.

Enable Self Management

● 6.

Configure SAP Control Center

– see SAP Control Center Installation Guide

When finished, click

Next

in the GUI wizard, or enter

0

in console mode. You are now ready to begin configuring the SAP ASE server.

Procedure

1. Set the

Configure New SAP ASE

option:

Option

SAP ASE Name

System Administrator's

Password

Confirm System

Administrator's Password

Description

Default is the machine name.

Enter your password.

Enter your password.



P U B L I C


39

Option

Port Number

Error Log

Application Type

Page Size

Description

Default is 5000.

Name and location of the error log file. Defaults to servername.log.

These options are numbered only in console mode:

○ 1. (Default) MIXED – both OLTP and DSS.

○ 2. OLTP – online transaction processing generally consists of smaller, less complex transactions.

○ 3. DSS – decision-support systems generally have less update activity with large complex queries.

○ 2KB

○ (Default) 4KB – if you plan to load database dumps from an SAP ASE with a page size that is not 4KB, enter the page size that matches the database dump.

○ 8KB

○ 16KB

Default: us-english. In typical installations, only us-english is available.

Default is iso_1.

Language

Default Character Set

Default Sort Order

Optimize SAP ASE Server

Configuration

Default is bin_iso_1.

Specify

Yes

if you want to optimize the configuration for your system. The default is

No

.

Available Physical Memory for SAP ASE Server

Appears when you select

Yes

for

Optimize SAP ASE Configuration

. The numeric value is 80 percent of the sum of combined default physical memory and default OS shared memory.

Note

If you specify a value that is larger than the available resource for allocation to the server, the optimize configuration may fail, causing the server to not start.

Available CPU for SAP ASE Appears when you select

Yes

for

Optimize SAP ASE Configuration

. The value is 80 percent of the physical CPU, with a default minimum of 1.

Create Sample Databases Select this option for the installer to install sample databases.

2. After customizing your SAP ASE configuration, click

Next

to record the input fields. You see

Enter the custom configuration values

:

Configuration

Master Device

Value

Name, including location, of the master device.

Master Device Size (MB) The minimum sizes are:

○ 2KB page size – 29MB


40

P U B L I C




Configuration Value



The default sizes are:





master Database Size

(MB)

The minimum and default sizes are:





System Procedure Device The complete file path name.

System Procedure Device

Size (MB) and System

Procedure Database Size

(MB)

The minimum for both is 184; the default for both is 196MB.

System Device

Tempdb Device

The complete file path name.

System Device Size (MB) and System Database Size

(MB)

The default options for both are:





The full path of the device.

Tempdb Device Size (MB) and Tempdb Database Size

(MB)

The default for both is 100MB for all page sizes.

Enable PCI in SAP ASE

PCI Device

Enable the pluggable component interface. The PCI is a generic interface internal to SAP ASE that is installed by default when you install or upgrade

SAP ASE. See Java in Adaptive Server Enterprise.


Enable PCI

. The default is sybpcidbdev_data.dat in $SYBASE/data.

PCI Device Size (MB) and

PCI Database Size (MB)


Enable PCI

. The PCI device and PCI database size are the same:





After customizing your SAP ASE configuration, click

Next

to record the input fields.

3. Set the

Configure New Backup Server

option:



P U B L I C


41

Configuration Value

Backup Server Name The default is

<machinename>

_BS.

Port Number

Error Log

Allow Hosts

The port number of the Backup Server. The default is 5001.

The full path to the error log file.

Comma-separated lists of hosts that are allowed to connect to this Backup

Server. When null, only the dataserver running on the same host as the Backup

Server can access this Backup Server. The default value is null.

4. Set the

Configure New XP Server

option:

Configuration Value

XP Server Name The XP Server name is set automatically, in the form of

<machinename>

_XP.

Port Number The port number of the XP Server. The default is 5002.

Error Log The full path to the error log file.

5. Set the

Configure Job Scheduler

option:

Configuration

Job Scheduler Agent name

Port number

Management device

Management device size, in MB

Management database size, in MB

Value

The default is <

<ASE Server Name>

>_JSAGENT.

The default is 4900.

The full path to the device.

The default is 76.

The default is 76.

Click

Next

.

6. Set the

Configure Self Management

option to create a scheduled job to run update statistics on any table in any SAP ASE database:

○ Self-management user name – default is "sa". Entering a new user name creates it in SAP ASE.

○ Self-management password.

7. Set the

SAP Control Center – Configure Self Discovery Service Adapter

option:

○ Configure UDP Adapter

○ Configure JINI Adapter – if you select this option, enter:

○ JINI host name – default is localhost.

○ JINI port number – default is 4160.

○ JINI heartbeat period, in seconds – default is 900.

Note

If you do not select an adapter, you see a message similar to:

You must choose at least one adapter to configure.

8. If you installed the SAP Control Center Management User Interface for SAP ASE, set the

SCC Configure

HTTP Ports

option.

Accept the default options, or specify other, unused ports, ensuring that the port numbers do not conflict with those used by other applications or services on your system:

42

P U B L I C




○ HTTP port – choose an integer between 1025 and 65535.

○ HTTPs port – choose an integer between 1025 and 65535.

9. Set the

SAP Control Center – Configure RMI Port

option with a port number (1025 to 65535) that is not used by another application or service on the system. The default is 9999.

10. Set the user names and passwords in

Configure Administration Passwords

. If you installed:

Option Description

If you installed the SAP Control Center Management User Inter face for SAP ASE:

Enter:

○ SCC administrator user

○ SCC administrator password

○ Confirm SCC administrator password

If you installed either the SAP Control Center Management User

Interface for SAP ASE or the Remote Command and Control

Agent for SAP ASE:

Enter:

○ SCC agent administrator user

○ SCC agent administrator password

○ Confirm SCC agent administrator password

11. Set the

Repository Password

– enter the password for the repository.

12. Verify that the values that appear in the Configure New Servers Summary window are correct, then click

Next

. You see the Configure Server Progress window.

13. In the Installation Completed window:

Option

GUI mode

Console mode

Description

Click

Done

press

Enter

to exit the installation

Results

SAP ASE and related products have been successfully installed, and minimally configured for use. See

Installing Sample Databases [page 54]

, to begin experimenting with your servers, or see the System

Administration Guide for more advanced topics.

If you encounter any errors, see the Troubleshooting Guide.








P U B L I C


43

6.4 Installing SAP ASE Using a Response File

Unattended or silent installations are typically used to update multiple systems across the enterprise.

Procedure

To perform a silent, or "unattended" installation, run the installer and provide a response file that contains your preferred installation configuration.

6.4.1 Creating a Response File

By saving installation configuration information into a response file during the initial GUI installation, you can perform subsequent installations of SAP ASE using a silent—or unattended—method.

Context

Note

SAP ASE version 16.0 and higher uses a rearchitected installation program that is incompatible with response files generated for versions 15.0.3 and earlier. Do not use response files from these earlier versions; instead, create a new one from a 16.0 SP01 installation.

To create a response file when installing in GUI or console mode, specify the -r command line argument. The

-r argument records your responses to the installation wizard prompts and creates a response file when the

InstallAnywhere wizard exits. The response file is a text file that you can edit to change any responses before you use it in any subsequent installations. You can find a sample response file in

<installer image>

/ sample_response.txt.

Procedure

1. Create a response file during GUI installation: setup.bin -r [

<response_file_name>

]

Where:

○ -r – specifies the command line argument.

○

<response_file_name>

– is the absolute path of the file into which the installation information is stored, such as /tmp/responsefile.txt.

44

P U B L I C




Note

The directory path you specify must already exist.

2. Verify that the response file includes the passwords for the SAP ASE sa login, SAP Control Center admin, and SCC agent admin by including these lines in the file:

SY_CFG_ASE_PASSWORD=<

<ASE sa password>

>

CONFIG_SCC_CSI_SCCADMIN_PWD=<

<SCC admin password>

>

CONFIG_SCC_CSI_UAFADMIN_PWD=<

<SCC agent admin password>

>

CONFIG_SCC_REPOSITORY_PWD=<

<SCC repository password>

>

Each password must be at least six characters long. The sccadmin and uafadmin logins need not be the same as the sa password.

You can also set these passwords using these environment variables:

○ SY_CFG_ASE_PASSWORD

○ CONFIG_SCC_CSI_SCCADMIN_PWD

○ CONFIG_SCC_CSI_UAFADMIN_PWD

○ CONFIG_SCC_REPOSITORY_PWD

Note

Secure these response files appropriately if they contain passwords.

3. To enable a different user for the SAP ASE you are installing, define these properties:

SY_CFG_USER_ACCOUNT_CHANGE=<yes | no>

SY_CFG_USER_ACCOUNT_NAME=<

<user name>

>

SY_CFG_USER_ACCOUNT_PASSWORD=<

<user password>

>

SY_CFG_USER_DATA_DIRECTORY=<

<data directory>

>

You need not configure SY_CFG_USER_ACCOUNT_NAME or SY_CFG_USER_ACCOUNT_PASSWORD unless you set SY_CFG_USER_ACCOUNT_CHANGE to

yes

.

For the SY_CFG_USER_DATA_DIRECTORY property, enter a directory other than the installed directory to which SAP ASE can create all the data files during configuration.

SAP ASE creates these files during installation to place in the data directory:

○ The interfaces file.

○ RUN_server file.

○ Configuration utilities log files.

○ SAP ASE configuration file (.cfg) – under the ASE-16_0 subdirectory.

○ SAP ASE shared memory file (.krg) – under the ASE-16_0 subdirectory.

○ SAP ASE SySAM properties file – under the ASE-16_0/sysam subdirectory.

○ Job Scheduler template .ini files – under the ASE-16_0/jobscheduler/Templates subdirectory

Database device files and server error log files are created in the data directory, but you can move them after the installation is finished.

Note

Make sure that the user you specify in this property setting has read/write/modify permissions to access the data directory.



P U B L I C


45

6.4.2 Installing in Silent Mode

To perform a silent, or unattended installation, run the installer and provide a response file that contains your preferred installation configuration.

Prerequisites

Use setup.bin -r

<responseFileName>

to generate an installation response file during a console or GUI installation, or edit and use the sample_response.txt sample responses file located in the installer image's top directory (

<installer_image>

/sample_response.txt)

Procedure

1. Run the following, where

<responseFileName>

is the absolute path of the file name containing the installation options you chose: setup.bin –f responseFileName -i silent

-DAGREE_TO_SAP_LICENSE=true -DRUN_SILENT=true

Note

You must agree to the SAP License Agreement when installing in silent mode. You can either:

○ Include the option -DAGREE_TO_SAP_LICENSE=true in the command line argument, or,

○ Edit the response file to include the property AGREE_TO_SAP_LICENSE=true.

Except for the absence of the GUI screens, all actions of InstallAnywhere are the same, and the result of an installation in silent mode is exactly the same as one performed in GUI mode using the same responses.

2. The installer for SAP ASE requires non-null passwords for the sa login in SAP ASE, and uafadmin and sccadmin logins in SAP Control Center. For this reason, add these rows to the response file:

SY_CFG_ASE_PASSWORD=

<ASE sa password>

CONFIG_SCC_CSI_SCCADMIN_PWD=

<SCC admin password>

CONFIG_SCC_CSI_UAFADMIN_PWD=

<SCC agent admin password>

CONFIG_SCC_REPOSITORY_PWD=

<SCC repository password>

Each password must be at least six characters long. The sccadmin and uafadmin logins need not be the same as the sa password.

You can also set these passwords using these environment variables:

○ SY_CFG_ASE_PASSWORD

○ CONFIG_SCC_CSI_SCCADMIN_PWD

○ CONFIG_SCC_CSI_UAFADMIN_PWD

○ CONFIG_SCC_REPOSITORY_PWD

46

P U B L I C




Note

For security purposes, treat response files with care if they contain passwords.

6.4.3 Command Line Options

Options for installing or uninstalling SAP ASE in console mode.

Option Purpose

-i console Uses the console interface mode, where messages appear on the Java console and the wizard runs in console mode.

-i silent

Installs or uninstalls the product in silent mode, without user interaction.

-D

Passes custom variables and properties. For example, to override the default installation directory when you run the installer, enter:

<install_launcher_name>

-DUSER_INSTALL_DIR=/sybase

-r

-f

-l

-\?

Generates a response file and a reference.

References response files.

Sets the installer’s locales.

Displays the installer help.

6.5 Uninstalling SAP ASE

To remove SAP ASE, run the uninstaller. The uninstallation process reverses only those actions originally performed by the installer, leaving intact any files or registry entries you created after the installation.

Prerequisites

Shut down all servers.



P U B L I C


47

Procedure

1. Execute:

$SYBASE/sybuninstall/ASESuite/uninstall

2. Click

Next

in the Uninstall Welcome window.

3. Choose one of the following, then click

Next

:

Option Description

Complete Uninstall

Uninstalls everything originally installed by the installer.

Uninstall Specific

Features

Displays a list of features. If any unselected products/components are dependent on features selected for uninstallation, you can still proceed with the uninstallation but dependent features are not uninstalled.

You see a window indicating that the uninstallation process is being performed. There is no progress bar.

Note

You may need to confirm the deletion of some files that have been modified since installation.

4. When you see the final window, click

Done

to exit the uninstallation program.

5. Manually remove any files or registry entries you created after the installation.

6.5.1 Removing an Existing SAP ASE Server

Remove an existing SAP ASE server.

Procedure

1. From $SYBASE and $SYBASE/$SYBASE_ASE, enter:

rm <servername>.*

2. Change to $SYBASE/$SYBASE_ASE/install and run: rm RUN_

<servername>

.* rm

<servername>

.*

3. Edit $SYBASE/interfaces, to remove all references to the SAP ASE.

4. Remove any operating system files for existing database devices.

48

P U B L I C




7 Starting and Stopping SAP Control

Center

SAP Control Center (SCC) for SAP ASE is a Web-based tool for monitoring the status and availability of SAP

ASE servers. Set the $SYBASE environment variables and start an SCC agent on your SAP ASE server.

Prerequisites

Before starting SAP Control Center, make sure you have installed both:

● SCC agent for SAP ASE – a remote command and control agent that runs on a managed server, and which is required to manage SAP ASE tasks within SCC.

● SCC Management User Interface for SAP ASE – provides the GUI that allows you to manage and monitor activities in an SAP ASE server using a Web browser.

A "typical" installation includes the SCC agent, but the management UI is available only if you select the

"custom" installation option.

Context

There are several ways to run SCC:

● From the command line in the foreground

● From the command line in the background

● Set up a daemon to run it as a service

Use these steps to run SAP Control Center for the first time and to verify the installation. For complete instructions, see

Get Started Launching SAP Control Center Starting and Stopping SAP Control Center

in the SCC online help, as well as Starting and Stopping SAP Control Center in UNIX in the SAP Control Center

Installation Guide.

Procedure

● To start SAP Control Center:

1. Before you start the SCC agent for the first time, source either the SYBASE.csh or SYBASE.sh environment script.

2. Start the SCC agent:

$SYBASE/SCC-3_3/bin/scc.sh


Starting and Stopping SAP Control Center

P U B L I C


49

3. Verify that the SCC agent is running. After you run the SCC script, you see the SCC console prompt.

At this prompt, enter: scc-console> status

You should see a status message similar to:

Agent Home: /remote/perf_archive/mymachine/Install_Testing/157CE_C3/SCC-3_3/instances/ solstrs3 Connection URL: service:jmx:rmi:///jndi/rmi://solstrs3:9999/agent Status: RUNNING

● To shut SCC down from the console: scc-console> shutdown



50

P U B L I C



Starting and Stopping SAP Control Center

8 Postinstallation Tasks

After you install the server, set it up.

The SAP ASE installation includes directories that contain sample client library applications. These sample programs are included for training purposes only and are not intended to be installed in a production environment.

If you are setting up a production environment, remove these directories:

● $SYBASE/OCS-16_0/sample

● $SYBASE/DataAccess*/ODBC/samples

● $SYBASE/jConnect-16_0/sample2

● $SYBASE/jConnect-16_0/classes/sample2

● $SYBASE/ASE-16_0/sample

● $SYBASE/WS-16_0/samples



8.1 Verifying That Servers are Running

Verify that the servers are running.

Prerequisites

Before starting the server, make sure you have stopped, then started the services related to the server.

Context

If you have already started the server, do not run the command a second time. Running it more than once can cause problems.


Postinstallation Tasks

P U B L I C


51

Procedure

1. From a UNIX command line, set the environment variables.

○ In the C shell: source

<ASE_install_location>

/SYBASE.csh

○ In the Bourne shell:

<ASE_install_location>

/SYBASE.sh

2. Show all SAP ASE-related processes that are on the system:

$SYBASE/$SYBASE_ASE/install/showserver

8.2 Verifying Your Connection to the Servers

Use isql to verify your connection to the servers.

Context

1. At the command prompt, enter the following: isql -Usa -P

<password>

-S

<server_name>

Where:

○

<password>

– is the password for sa.

○

<server_name>

is the SAP ASE server name.

You see the isql prompt if the login is successful.

2. At the isql prompt, enter:

1> select @@version

2> go

The output should show that you are at the current version and edition of SAP ASE.

If you encounter errors, see the Troubleshooting Guide.

52

P U B L I C




8.3 Test the Installation and Network Connections

After installing SAP ASE, SAP Control Center, and the Java Runtime Environment, test the installation and network connections.

Context

The SAP ASE server communicates with other SAP ASE servers, Open Server applications (such as Backup

Server), and client software on your network. Clients can talk to one or more servers, and servers can communicate with other servers using remote procedure calls.

For SAP Control Center to work, install both the SCC agent for SAP ASE as well as the SCC Management User

Interface for SAP ASE. A "typical" installation includes the agent, while the SCC Management User Interface for SAP ASE is available only if you select the "custom" installation option. See the SAP Control Center

Installation Guide for details about installing and setting up SCC.

For SAP products to interact with one another, each product must know where the others reside on the network. SAP stores this information in the interfaces file on Windows or in a Lightweight Directory Access

Protocol (LDAP) server.

Follow the instructions in SAP Control Center for SAP Adaptive Server Enterprise to launch SCC and configure the SAP ASE server for monitoring. You can then view a list of monitored servers in the Administration Console of the Perspective Resources view in SCC to verify your connections.

Procedure

1. Use the libtcl.cfg file to specify an LDAP server name, port number, directory information tree (DIT) base, user name, and password to connect to an LDAP server.

For details, see Use the Lightweight Directory Access Protocol as a Directory Service in the configuration guide.

2. Use the dsedit utility to add a server to the directory service.

If you do not have X-Windows installed on your system to use dsedit, use dscp.

For details, see Set Up Communications Across the Network > Create a Directory Services Entry in the configuration guide and the Utility Guide.

3. Adding a server to the interfaces file.

For details, see Set Up Communications Across the Network > Create a Directory Services Entry in the configuration guide.



P U B L I C


53

8.4 The System Administrator Account

When you install SAP software, the software creates a system administrator account called "sa," which can use any database on an SAP ASE server, including master, with full privileges.

The password for "sa" is autoamtically created during installation. See the Security Administration Guide for more information about passwords.

8.5 Installing Sample Databases

The sample databases, which contain fictitious information, are designed to help you learn how to use SAP

ASE. The sample databases are intended for training purposes only. Do not install them in an SAP ASE production environment.

File Name Description

installpubs2

Installs the pubs2 sample database. This database contains data that represents a publishing operation. Use this database to test your server connections and to learn

Transact-SQL. Most of the examples in the SAP ASE documentation query the pubs2 database.

Note

The master device size should be at least 30MB to install the full pubs2 database, including the image data.

installpubs3

Installs the pubs3 sample database. This updated version of pubs2 uses referential integrity. In addition, its tables are slightly different than the tables used in pubs2. Where noted, the SAP ASE documentation uses the pubs3 database in its examples.

installpix2

Installs the image data that is used with the pubs2 database.

Run the installpix2 script after you run installpubs2.

The image data requires 10MB—there are six pictures, two each in the PICT, TIFF, and Sun raster file formats. Run installpix2 script only to use or test the image datatype. SAP does not supply any tools for displaying image data; you must use appropriate window graphics tools to display the images after you have extracted them from the database.


Postinstallation Tasks [page 51]


54

P U B L I C




8.5.1 Default Devices for Sample Databases

The SAP ASE installation includes scripts for installing the us_english sample database, foreign language sample databases, and the image data associated with the US English pubs2 sample database on a default device.

These scripts are located in $SYBASE/$SYBASE_ASE/scripts.

By default, these scripts install the sample databases on the master device. Because the databases use valuable space on the master device that is best reserved for system tables – each sample database requires

3MB on a 2KB server, and multiples of 3MB on a 4KB, 8KB, and 16KB server on your database device – we recommend that you change the default to a device other than the master device.

To change the default location where the scripts install these databases, use sp_diskdefault. See sp_diskdefault in Reference Manual: Procedures. Alternatively, use a text editor to revise the script directly.

8.5.2 Running the Database Scripts

After you determine your default device, run the scripts to install the sample databases.

Prerequisites

Back up the original installpubs2 and installpubs3 scripts, in case you have problems with the edited scripts.

Procedure

1. Start SAP ASE.

2. Go to the scripts directory at $SYBASE/$SYBASE_ASE/scripts.

3. Use isql to log in to the SAP ASE server and run the script: isql -Usa -P***** -S

<server_name>

-i

<script_name>

Where:

○

<server_name>

– is the destination server for the database.

○

<script_name>

– is the full path to and file name of the script to run.

For example, to install pubs2 on a server named VIOLIN, enter: isql -Usa -P***** -SVIOLIN -i $SYBASE/$SYBASE_ASE/scripts/installpubs2

4. Install the image data associated with pubs2: isql -Usa -P

<password>

-S

<servername>



P U B L I C


55

-i$SYBASE/$SYBASE_ASE/scripts/installpix2

The pubs3 database does not use image data.

For more information about running these scripts, see the Configuration Guide for UNIX.

8.5.3 Installing the interpubs Database

The interpubs database is similar to pubs2, and contains French and German data.

Prerequisites

Back up the original installintpubs script, in case you experience problems with the edited script.

Procedure

1. Set your terminal to display 8-bit characters.

2. Verify that iso_1, iso_15, Roman8, Roman 9, or UTF-8 is installed as either the default character set or as an additional character set.

The interpubs database contains 8-bit characters and is available for use at SAP ASE installations using the ISO 8859-1 (iso_1), ISO 8859-15 (iso_15), Roman 8, or Roman9 (for HP-UX) character set.

3. Determine the type (raw partition, logical volume, operating system file, and so on) and location of the device where you will be storing the interpubs database. You will need to provide this information later.

4. Execute the script, using the -J flag to ensure that the database is installed with the correct character set: isql -U

<sa>

-P

<password>

-S

<servername>

-Jiso_1 \

-i $SYBASE/$SYBASE_ASE/scripts/iso_1/installintpubs

8.5.4 Installing the jpubs Database

If you installed the Japanese language module with your server, you can run the installjpubs script to install jpubs, which is a database similar to pubs2 that contains Japanese data. installjpubs uses the

EUC-JIS (eucjis), UTF-8 (utf8), or the Shift-JIS (sjis) character sets.

Prerequisites

Copy the original installjpubs script, in case you experience problems with the edited script.

56

P U B L I C




Procedure

1. Set your terminal to display 8-bit characters.

2. Verify that the EUC-JIS, Shift-JIS, or the UTF-8 character set is installed either as the SAP ASE default character set or as an additional character set.

3. Determine the type (raw partition, logical volume, operating system file, and so on) and location of the device where you will be storing the jpubs database. You will need to provide this information later.

4. Execute the installjpubs script, using the -J flag to ensure that the database is installed with the correct character set: isql -U

<sa>

-P

<password>

-S

<servername>

-Jeucjis \

-i $SYBASE/$SYBASE_ASE/scripts/eucjis/installjpubs isql -U

<sa>

-P

<password>

-S

<servername>

-Jeucjis \

-i %SYBASE%\%SYBASE_ASE%\scripts\eucjis\installjpubs or: isql -U

<sa>

-P

<password>

-S

<servername>

-Jsjis \

-i $SYBASE/$SYBASE_ASE/scripts/sjis/installjpubs isql -U

<sa>

-P

<password>

-S

<servername>

-Jsjis \

-i %SYBASE%\%SYBASE_ASE%\scripts\sjis\installjpubs

For more information on the -J option in isql, see the Utility Guide.

8.5.5 Maintaining Sample Databases

The sample databases contain a guest user option that allows authorized users to access the database. Guest users have a wide range of privileges, including permissions to select, insert, update, and delete user tables.

Context

We recommend that you remove the guest user option from user databases in production systems. For more information about the guest user and a list of guest permissions, see the System Administration Guide.

Procedure

● If possible, and if space allows, give each new user a clean copy of the sample databases so that he or she is not confused by other users’ changes.

● If space is a problem, instruct users to issue the begin transaction command before updating a sample database.



P U B L I C


57

● After users have finished updating one of the sample databases, instruct them to issue the rollback transaction command to undo the changes.

58

P U B L I C




9 SAP ASE Upgrades

You can upgrade to SAP ASE version 16.0 SP01 from versions 12.5.4 or later.

Upgrades are supported only between nonclustered editions of SAP ASE. You cannot upgrade from SAP

Adaptive Server Enterprise Cluster Edition to a nonclustered edition.

You can upgrade to SAP ASE version 16.0 SP01 from versions 12.5.4, 15.0 through 15.7 by executing the upgrade sequence from the same node on which the database resides. This is a major upgrade, and requires that you perform preupgrade tasks.

You can also perform a minor upgrade from a previous version of 16.0, which includes 16.0, and 16.0 PL01 through PL05.

You can upgrade from a 32-bit version to a 64-bit version.

You cannot upgrade to this version of SAP ASE from:

● Version 11.9.x

● Version 12.0.x

If you are running either of these versions, upgrade first to version 12.5.4 before upgrading to version 16.0

SP01.

If your server has replicated databases, consult the Replication Server Configuration Guide before starting the upgrade preparatory tasks.

Only upgrades to and from the same page size are supported. If you are migrating between servers with the same major version number, you can use sybmigrate to re-create the schema and load data from one page size to another. See the Utility Guide.

SAP ASE version 16.0 SP01 includes both new and changed system catalogs that may affect your existing applications. See the SAP Adaptive Server Enterprise What's New for a complete list.

Caution

Once you upgrade to SAP ASE 16.0 SP01, you cannot revert back to an version earlier than 16.0.






SAP ASE Upgrades

P U B L I C


59

9.1 Considerations When Upgrading from SAP ASE 15.0.x or Earlier

A minor change was made to the format of a log record in SAP ASE version 15.5 that introduces an unlikely possibility for the SAP ASE server to misinterpret this changed log record in cases where the upgraded server contains a database that is the primary database for replication. This change should not affect your upgrade process; however, it requires you to strictly follow some steps when you move from SAP ASE 15.0.x or earlier to SAP ASE 15.5.x and later. See the following table for all possible combinations of upgrades.

An upgrade is done by:

● Upgrading your entire installation by switching binaries.

● Upgrading a single database using online database, having first loaded it with a database dump and transaction logs taken on a server with an earlier version.

Table 5: Upgrading Your Entire Installation

Current Ver sion

Upgrading to Special Upgrade Information

SAP ASE

15.0.x or ear lier

SAP ASE 16.0

SP01

If you are using Replication Server to replicate one or more databases in the version to be upgraded, ensure that all transactions have been replicated before the polite shutdown is done, by draining the log. See Upgrading ASE in a Replication System and Upgrading Replication Server in the Replication Server Configuration Guide for your platform.

SAP ASE Clus ter Edition

15.5.x or later

SAP ASE

15.5.x

SAP ASE 16.0

SP01

SAP ASE 16.0

SP01

Upgrading any version of SAP ASE Cluster Edition to a nonclustered version is not supported.

No special upgrade instructions.

Table 6: Upgrading a Single Database

Current Ver sion

Upgrading to Special Upgrade Instructions

SAP ASE

15.0.x and ear lier

SAP ASE 16.0

SP01

When you use online database to upgrade a single database in SAP ASE 16.0

SP01 after loading a database dump and transaction logs from SAP ASE 15.0.x or earlier, if the database you are upgrading is also replicated, make sure the databa se's transaction log is truncated before you turn replication back on.

SAP ASE Clus ter Edition

15.5.x or later

SAP ASE 16.0

SP01

SAP ASE

15.5.x

SAP ASE 16.0

SP01

Upgrading a database from any version of the Cluster Edition to a nonclustered ver sion is not supported.

No special upgrade instructions.

60

P U B L I C





Postupgrade Tasks [page 83]

9.2 Considerations for Component Integration Services

If you have both a local and a remote server running on SAP ASE version 15.x and are upgrading both of them to version 16.0 SP01, upgrade the local server first. If you plan to upgrade one server but not the other, upgrade the local server.

SAP does not certify that Component Integration Services running on earlier versions of SAP ASE can connect to later versions. You may encounter errors if an earlier version of SAP ASE maps a proxy table to a later version and if the remote table uses functionality that is unavailable in the earlier version.

SAP certifies that each version of SAP ASE connects to earlier versions through Component Integration

Services. Component Integration Services is tested and certified to connect to earlier versions of SAP ASE.

9.3 Preparing to Upgrade

Use the preupgrade, upgrade, sqlupgrade, and sqlupgraderes utilities to upgrade SAP ASE versions earlier than 16.0.

Prerequisites

Caution

Since it is not possible to downgrade once you upgrade to SAP ASE 16.0 or higher, make sure to back up all databases, including master and other system databases, before beginning the upgrade process.

Context

To perform an upgrade from:

● A version earlier than 16.0 to version 16.0 SP01, run the preupgrade utility to test the upgrade eligibility then use sqlupgrade (or sqlupgraderes) to upgrade the server..

● Version 16.0 to 16.0 SP01, run the updatease utility.

You must have system administrator privileges to perform an upgrade.



P U B L I C


61

Each new server version contains features that introduce parameters, commands, reserved words, and so on.

The preupgrade utility prepares the old server by making sure all necessary directories and settings are correct for the upgrade. When running the preupgrade utility, manually stop and start the server. You need not start the server before running the sqlupgrade upgrade utility; the utility starts the server when needed.

If you are upgrading from:

● Version 12.5.4 with cache bindings on sybsystemdb – drop the cache bindings for sybsystemdb that are bound to a user-defined cache before you run the preupgrade utility.

● Earlier than version 16.x but later than 12.5.4 – from the SAP ASE 16.0 installation directory, use the preupgrade utility to perform the preupgrade checks on the old server. The utility is located in $SYBASE/

ASE-16_0/bin.

Manually drop objects before you execute procedures for the first time. The first time you run the server after an upgrade, the server internally rebuilds procedures from the text in syscomments. The procedure may not execute properly if it contains code that drops, then re-creates, an existing object.

Procedure

1. Go to the directory where the new version of SAP ASE is installed.

2. Go to the ASE-16_0 directory.

3. Go to the bin directory.

4. Enter preupgrade to run the preupgrade utility.

9.4 Changes in SAP ASE Directories

The directory structures for SAP ASE installations differ, depending on version.

Directory Changes

Component

SAP ASE

SAP Control

Center

Location

● 12.5.4 – $SYBASE/ASE-12_5

● 15.0.2, 15.0.3, 15.5, 15.7 GA, and 15.7 ESD #1, ESD #2, ESD #3, and SP100 –

$SYBASE/ASE-15_0

● 16.0 and later – $SYBASE/ASE-16_0

● 15.7 SP100 – $SYBASE/SCC-3_2

● 16.0 and later – $SYBASE/SCC-3_3

62

P U B L I C




Component

SAP jConnect for

JDBC

Location

● Versions of 15.7 –$SYBASE/jConnect-7_0

● 16.0 and later –$SYBASE/jConnect-16_0

Interactive SQL

● Versions of 15.7 –$SYBASE/DBISQL

● 16.0 and later –$SYBASE/DBISQL-16_0

JRE

Language settings

(locales)

● 12.5.4 and 15.0.2 – $SYBASE/locales

● 15.0.3, 15.5, 15.7 GA, and 15.7 ESD #1, ESD #2, ESD #3, and SP100 – $SYBASE/ locales and $SYBASE/ASE-15_0/locales

● 16.0 and later – $SYBASE/locales and $SYBASE/ASE-16_0/locales

Connectivity

● 12.5.4 – $SYBASE/shared/jre142

● 15.0.2 – $SYBASE/shared/jre142_*

● 15.0.3 – $SYBASE/shared/JRE-6_0*

● 15.5, 15.7 GA, and 15.7 ESD #1 – $SYBASE/shared/JRE-6_0*

● 15.7 ESD #2, ESD #3, and SP100 – $SYBASE/shared/JRE-7_0*

● 16.0 and later – (32-bit) $SYBASE/shared/SAPJRE-7_1_*_32BIT and (64-bit)

$SYBASE/shared/SAPJRE-7_1_*_64BIT

● 12.5.4 – $SYBASE/OCS-12_5


$SYBASE/OCS-15_0

● 16.0 and later – $SYBASE/OCS-16_0

Web Service

● 12.5.4 – $SYBASE/WS-12_5


$SYBASE/WS-15_0

● 16.0 and later – $SYBASE/WS-16_0

SySAM

● 12.5.4 – $SYBASE/SYSAM-1_0

● 15.0.2, 15.0.3, 15.5, 15.7 GA, and 15.7 ESD #1, ESD #2, ESD #3, SP100, 16.0 and later

– $SYBASE/SYSAM-2_0

Job Scheduler

● 12.5.4 – $SYBASE/JS-12_5


$SYBASE/ASE-15_0/jobscheduler

● 16.0 and later – $SYBASE/ASE-16_0/jobscheduler

Unified Agent

● 15.0.2 and 15.0.3 – $SYBASE/UAF-2_0

● 15.5, 15.7 GA – $SYBASE/UAF-2_5

● 15.7 ESD #1, ESD #2, ESD #3, and SP100 – $SYBASE/SCC-3_2

● 16.0 and later – No longer shipped. Included with SCC.



P U B L I C


63

9.5 Preupgrade Tasks

To ensure a successful upgrade, review and perform preparatory tasks as necessary. Depending on the old server configuration, you may not need to perform all preparatory tasks.

Prerequisites

● You need the master and system procedures files to upgrade the server. By default, the master

(master.dat) and system procedures device (sybsytemprocs.dat) files are in the $SYBASE/data directory.

● The previously installed version of the server must be running. If you are upgrading Backup Server or XP

Server, those servers must not be running.

Context

Note

Follow these steps only if you are performing a major upgrade from an SAP ASE version earlier than 16.0.

Skip these preparatory tasks if you plan to use sqlupgrade, which performs these tasks automatically.

Procedure

1. Install SAP ASE 16.0 SP01 into the old ASE directory.

2. Check system and upgrade requirements.

3. Ensure that the directory to which your TEMP environment variable points exists.

4. Verify the name and location of the runserver file, and that you have renamed it to RUN_

<servername>

as it appears in the interfaces file, where

<servername>

is the name of the old server.

The default RUN_

<servername>

file for a server called SYBASE is RUN_SYBASE. If the

RUN_

<servername>

file for your current server is named differently, use the actual name of your server during the upgrade process.

5. Verify that the text of all stored procedures you upgrade is available in syscomments by either:

○ Reinstalling the procedures with text, or,

○ Removing and reinstalling the procedures after the upgrade.

This step can allow you to inspect the stored procedures for any hidden or unwanted text.

6. Make sure reserved words use quoted identifiers.

7. Verify that users are logged off.

64

P U B L I C




8. Use dbcc to check for database integrity.

9. Back up databases.

10. Dump the transaction log.

11. Verify that master is the default database for the "sa" user.

12. Prepare the database and devices for upgrade using the preupgrade utility. See preupgrade in the

Utility Guide for more information. After preupgrade finds no errors by exiting with status 0 (zero):

1. Create a sybsystemdb database if it does not already exist.

2. Disable auditing by running sp_configure 'auditing', 0.

3. Disable Job Scheduler.

4. Obtain the current audit settings for the pre-16.0 SAP ASE using sp_displayaudit; use this saved information to reenable auditing after you complete the upgrade.

5. If you made any site-specific changes to the permissions for system stored procedures, obtain the current permission settings for them using sp_helprotect; then use this saved information to reenable the permissions after you complete the installation. Pay special attention to

○ Any stored procedures that are not granted execute permission to public, such as sp_addauditrecord, sp_monitor, and sp_sysmon.

○ Any stored procedures where execute permission has been revoked from public.

6. Disable disk mirroring.

7. Verify that your SYBASE environment variable points to the location of the new server software files you just installed.

Fix any problems that preupgrade utility reports.

You can safely ignore any warnings SAP ASE issues about configuration parameters not being set to the default, as these are only for your information.

13. If you are upgrading from a nonclustered 12.5.4, 15.0.2, 15.5, or 15.7 server, and archive database access has been applied in the lower version server, disable the related functionality before upgrading.

14. Ensure that the procedure cache size is at least 150 percent of the default procedure cache size, or between 53,248 and 2,147,483,647 2KB pages.

15. Copy these files from earlier versions of the server to their corresponding SAP ASE 16.0 SP01 installation locations:

○ $SYBASE/interfaces

○ $SYBASE/$SYBASE_ASE/

<servername>

.cfg – where

<servername>

is your server name.

○ $SYBASE/$SYBASE_OCS/config/libtcl.cfg

○ $SYBASE/SYSAM-2_0/licenses/

<license_file_name>

16. If you have enabled the Java in the database feature, create the sybpcidb database and disable the feature during the installation.

17. Set the environment variables by sourcing the SYBASE.[csh, sh, env] file.

Caution

Do not run the environment variable script more than once.



P U B L I C


65





9.5.1 Upgrade Stored Procedures

If you modified any system stored procedures without altering their names, back them up before you upgrade

SAP ASE. The upgrade process overwrites these modified procedures with default versions.

9.5.2 Reserved Words

Reserved words are pieces of SQL syntax that have special meaning when used as part of a command.

Transact-SQL does not allow words that are part of command syntax to be used as identifiers unless they are enclosed in quotation marks. If you are upgrading SAP ASE, you see errors when you run queries, stored procedures, or applications that use these identifiers in your user databases.

Note

Before upgrading, use sp_renamedb to change the name of any user database that is a reserved word.

If you change an object name, also change applications and stored procedures that refer to that object.

Conflicts between object names do not prevent the upgrade process from completing. However, applications that refer to conflicting object names may not work after the upgrade. Rename all objects that use reserved words.

As part of the preupgrade process, you can have sqlupgrade, sqlupgraderes, or preupgrade perform a reserved-word check for you. See the Reference Manual: Building Blocks for a complete list of reserved words.

9.5.2.1 Running a Reserved Word Check

Run the reserved word check on the SAP ASE server you are upgrading.

Context

Even if you plan to use sqlupgraderes to upgrade SAP ASE noninteractively, you can still first run the interactive sqlupgrade utility to perform reserved-word checks and other potential upgrade eligibility problems, and then continue with the upgrade if no problems are found.

66

P U B L I C




Both sqlupgrade and sqlupgraderes automatically install new reserved words and the sp_checkreswords system procedure, which detects and displays identifiers in your existing databases that conflict with reserved words in the new database. You can use sp_checkreswords at any time while performing preupgrade tasks.

Note

Do not use an older version of sp_checkreswords to check for reserved words, as it does not contain the most current list of reserved words.

Procedure

1. Checking for reserved words generates a list of identifiers that conflict with reserved words, and the owners of those identifiers, in the file $SYBASE/$SYBASE_ASE/init/logs/sqlupgrade

<MMDD.nnn>

.

Review this file to determine which identifiers to change.

2. The sqlupgrade utility installs sp_checkreswords and checks the reserved words during the upgrade.

9.5.2.2 Addressing Reserved Words Conflicts

Change any database names that are reserved words.

Procedure

1. Use sp_dboption to set the database to single-user mode, then run sp_renamedb, specifying the new name.

2. If other identifiers are reserved words, you can use:

○ sp_rename to change the name of the object, before or after the upgrade.

○ Quoted identifiers.

○ Brackets around the identifier. For example: create table [table] ( [int] int, [another int] int )

3. Run sp_checkreswords in master and in each user database to display the names and locations of conflicting identifiers.

See Reference Manual: Procedures for information about sp_dboption, sp_rename, and sp_checkreswords.



P U B L I C


67

9.5.2.3 Quoted Identifiers

To avoid reserved word conflicts, all users on the server must invoke the quoted_identifier option in all stored procedures and queries that include the reserved words.

To invoke the quoted_identifier option of the set command in procedures and queries that include the reserved words, enclose the reserved words that are identifiers in double quotation marks. The set quoted_identifier option tells SAP ASE to treat any character string enclosed in double quotation marks as an identifier.

See Reference Manual: Commands for more information on set quoted_identifier.

9.5.3 Preparing the Database and Devices

Before starting the upgrade process, confirm that you have enough space for the upgrade to succeed.

Procedure

1. To calculate the free space required for the upgrade to succeed, double the size of the largest catalog that you are going to upgrade, then add approximately 10 percent. For example, if you have a large number of stored procedures or compiled objects in any database, the syscomments and sysprocedures system tables require additional space.

The preupgrade utility scans the system catalogs and performs this calculation automatically.

2. If you are:

○ Not using two-phase commit or distributed transaction management (DTM) applications, create a sybsystemdb with a minimum of 4MB if it does not already exist.

○ Using two-phase commit or DTM, create either:

○ A minimum-sized sybsystemdb for upgrade and expand it later, or

○ A sybsystemdb of 5MB to 20MB, depending on your expected usage. Approximately 25 percent of the database should be data storage, and 75 percent should be log storage.

3. If it does not already exist, create the sybsystemdb database. Servers that use a 2KB logical page size require a sybsystemdb that is at least 4MB. Servers that use a larger logical page size require a sybsystemdb that is at least as large as the model database:

1> create database sybsystemdb on default = '4M'

2> go

1> use sybsystemdb

2> go

1> sp_create_syscoordinations

2> go

SAP ASE uses this database for tracking transactions, and during recovery. It is also used by applications using two-phase commit and DTM.

4. Verify that the sybsystemdb database is large enough. For an upgrade, the default size for sybsystemdb is 124MB, or enough free space to accommodate the existing sybsystemdb database, and the largest

68

P U B L I C




catalog that is to be upgraded, plus 10 percent for logging upgrade changes. You may need more space if you are adding user-defined stored procedures.

5. If you use Java in the database, the preupgrade utility detects that you set sp_configure "enable java" to

1

, and requests that you enable PCI and configure sybpcidb before you upgrade the server.

6. Increase the default database size:

1. Use alter database to increase the size of the master database.

For example:

1> alter database tempdb on master=

<X>

2> go

1> alter database model on master=

<X>

2> go

<X>

is the megabytes of space you are adding.

Repeat this process for each temporary and model databases, making sure that model is at no point larger than tempdb.

2. Use sp_helpdb to verify the size of each system database you increase in size.

3. Use sp_configure to update the values as indicated by the preupgrade utility.

This example updates the number of locks available for all users on the SAP ASE server to 6,000: sp_configure 'number of locks', 6000

9.5.4 The sybprocsdev device

System stored procedures are stored in the sybsystemprocs database, which is stored in the sysprocsdev device. You may need to increase the size of sysprocsdev before upgrading SAP ASE.

Regardless of page size, when configuring a new server, the size of sybsystemprocs is:

● Minimum – 184 MB

● Default – 196 MB

For upgrades, you need an additional 10 percent of this.

You may need more space if you are adding user-defined stored procedures.

If your sybsystemprocs database does not meet these requirements and you have enough room on the device to expand the database to the required size, use the alter database command to increase the database size.

Use:

● sp_helpdb to determine the size of the sybsystemprocs database:

1> sp_helpdb sybsystemprocs

2> go

● sp_helpdevice to determine the size of the sysprocsdev device:

1> sp_helpdevice sysprocdev

2> go

If the

<db_size>

setting is less than the required minimum, increase the size of sysprocdev.



P U B L I C


69

9.5.4.1 Increasing the Size of the sybsystemprocs

Database

Create a new database with sufficient space if your current sybsystemprocs database does not have the minimum space required for an upgrade. The minimum size of sybsystemprocs is 184MB; the recommended size is 196MB.

Prerequisites

Create a current backup of your old database.

Context

Although you can drop the old database and device and create a new sysprocsdev device, SAP recommends that you leave the old database and device and add a new device that is large enough to hold the additional memory, and alter the sybsystemprocs onto the new device.

Procedure

1. In isql, use alter database to increase the size of the sybsystemprocs database. For example:

1> use master

2> go

1> alter database sybsystemprocs on sysprocsdev=40

2> go

In this example, "sysprocsdev" is the logical name of the existing system procedures device, and 40 is the number of megabytes of space to add. If the system procedures device is too small, you may receive a message when you try to increase the size of the sybsystemprocs database.

If there is space available on another device, expand sybsystemprocs to a second device, or initialize another device that is large enough.

2. Verify that the SAP ASE server has allocated more space to sybsystemprocs:

1> sp_helpdb sybsystemprocs

2> go

Results

When the database is large enough to accommodate the increased size of sybsystemprocs, continue with the other preupgrade tasks.

70

P U B L I C




9.5.4.2 Increasing Device and Database Capacity for

System Procedures

Perform one of these methods if you cannot fit the enlarged sybsystemprocs database on the system procedures device. The minimum size of sybsystemprocs is 184MB; the recommended size is 196MB.

Procedure

● Perform this step if the device that contains sybsystemprocs is a file on a storage system – where the device is not a raw device, and thus can have its size modified – and there is additional space on the storage system that contains that file.

● Make the existing device larger.

1. Use disk resize to extend the device.

For example, if sybsystemprocs exists entirely on device sybprocsdev, and both the device and the database are 124 MB, The desired size of sybsystemprocs is 196 MB:

1> disk resize name=sybprocsdev, size='72M'

2> go

This adds the requisite space on sybprocsdev (196 MB - 124 MB = 72 MB).

2. Use alter database to increase the size of the database.

1> alter database sybsystemprocs on sybprocsdev='72M'

2> go

Your existing device should now be larger.

● Use the following method only if the previous step could not make your existing device larger, as this method drops and re-creates the database.

Note

This procedure removes all stored procedures you have created at your site. Before you begin, save your local stored procedures using the defncopy utility. See the Utility Guide.

● This procedure involves dropping the database. For more information on drop database, see the

Reference Manual.

1. Determine which device you must remove: select

<d.name>

,

<d.phyname>

from sysdevices d, sysusages u where u.vstart between d.low and d.high | u.vdevno = d.vdevno and u.dbid = db_id("sybsystemprocs") and d.status & 2 = 2 and not exists (select vstart

from sysusages u2

where u2.dbid != u.dbid

and u2.vstart between d.low and d.high | u.vdevno = d.vdevno)

Where:



P U B L I C


71

○

<d.name>

– is the list of devices to remove from sysdevices.

○

<d.phyname>

– is the list of files to remove from your computer.

○ u.vstart between d.low and d.high – is the syntax you use for SAP ASE version 12.5.4

○ u.vdevno = d.vdevno – is the syntax you use for SAP ASE versions 15.0 and later

The not exists clause in this query excludes devices that are used by sybsystemprocs and other databases.

Make a note of the names of the devices to use in subsequent steps.

Caution

Do not remove any device that is in use by a database other than sybsystemprocs, or you will destroy that database.

2. Drop sybsystemprocs:

1> use master

2> go

1> drop database sybsystemprocs

2> go

Note

In versions earlier than 15.x, use sysdevices to determine which device has a low through high virtual page range that includes the vstart from step 2.

In version 15.x, select the

<vdevno>

from sysusages matching the

<dbid>

retrieved in step 1.

3. Remove the device:

1> sp_configure "allow updates", 1

2> go

1> delete sysdevices

where name in ("

<devname1>

", "

<devname2>

", ...)

2> go

1> sp_configure "allow updates", 0

2> go

The where clause contains the list of device names returned by the query in step 1.

Note

Each device name must have quotes. For example, "devname1", "devname2", and so on.

If any of the named devices are OS files rather than raw partitions, use the appropriate OS commands to remove those files.

4. Remove all files that were returned in the

<d.phyname>

list.

Note

File names might not be complete path names. If they are relative paths, note that they are relative to the directory from which your server was started.

72

P U B L I C




5. Find another existing device that meets the requirements for additional free space, or use a disk init command similar to the following to create an additional device for sybsystemprocs, where / sybase/work/ is the full, absolute path to your system procedures device:

1> use master

2> go

1> disk init

2> name = 'sysprocsdev',

3> physname = '/sybase/work/sysproc.dat',

4> size = '200M'

5> go

Note

Server versions 12.0.x and later accept, but do not require "vdevno=number". For information about determining whether vdevno is available, see the System Administration Guide.

The size you provide should be the number of megabytes of space needed for the device, multiplied by

1024. disk init requires the size to be specified in 2KB pages. In this example, the size is 200 MB

(200 x 1024 = 204,800). For more information on disk init, see the Reference Manual: Commands.

6. Create a sybsystemprocs database of the appropriate size on that device, for example:

1> create database sybsystemprocs on sysprocsdev = 180

2> go

7. In the old server installation directory, enter: isql -Usa -P

<password>

-S

<server_name>

-i$SYBASE/ASE-15_0/scripts/ installmaster

9.6 Upgrade to SAP ASE 16.0 SP01

If you are performing a major upgrade from a version earlier than 16.0, and you successfully run the preupgrade utility to test upgrade eligibility (verifying that you have enough free space in databases, there are no reserved word conflicts, and so on), you can upgrade the server, using sqlupgrade or sqlupgraderes.

9.6.1 Upgrading Interactively Using sqlupgrade

Use the interactive sqlupgrade tool to upgrade SAP ASE using an X-Windows or Motif GUI.

Prerequisites

Set the OLDSYBASE_ASE variable to the SYBASE_ASE that is appropriate to your older server. If you are upgrading from 15.7 for example, OLDSYBASE_ASE should be ASE-15_0.



P U B L I C


73

We recommend that you also set the OLDSYBASE, and OLDSYBASE_OCS environment variables to point to the older version installation of SAP ASE, so the upgrade utility that you run from the new $SYBASE directory automatically populates input fields with the correct information as you upgrade.

Source SYBASE.csh before running sqlupgrade if you have not already so.

The sqlupgrade utility automatically restarts the server you are upgrading.

Procedure

1. Verify that you have backed up databases, devices, and so on, and click

Next

.

2. Enter:

$SYBASE/$SYBASE_ASE/bin/sqlupgrade

The available command options for sqlupgrade are:

○ -s

<sybase_dir>

– specifies the value to use for the SYBASE environment variable.

○ -r

<resource_file>

– executes the specified resource file.

○ -D

<data_directory>

– specifies a working directory that differs from the default $SYBASE directory. This allows users other than the sa to configure and use SAP ASE without the need to have access permission to the $SYBASE directory. If you do not use -D, SAP ASE uses $SYBASE as the default.

○ -v – prints the version number and copyright message for sqlupgraderes and then exits.

3. In the Specify SAP ASE Directories dialog, enter:

○ The full path of the new SAP ASE release directory.

○ The full path of the data directory for the new SAP ASE release directory. This field allows you to specify a working directory that differs from the default $SYBASE directory, which allows users other than the sa to configure and use SAP ASE without the need to have access permission to the

$SYBASE directory.

○ The name of the component directory that contains the new SAP ASE version.

○ The full path of the old release directory.

○ The name of the component directory that contains the earlier version of SAP ASE.

○ The name of the component directory that contains the earlier version of Open Client/Server Library.

Click

OK

.

4. Select the server to upgrade from the list of servers.

5. Enter the password for the sa login, then click

OK

.

6. Specify an upgrade option, then click

OK

. sqlupgrade performs a preupgrade review to verify that your current server meets the requirements for upgrade to the new version.

If your current server fails the preupgrade review, fix the problem based on the information from the results of the test.

7. Click

OK

to upgrade your server.

You see the Status Output window, which shows the completion status and informational messages about the upgrade process.

74

P U B L I C




Caution

Do not interrupt the upgrade, connect to SAP ASE, or run any stored procedures while the upgrade is in progress.

You can also check progress by viewing the sqlupgrade log in $SYBASE/$SYBASE_ASE/init/logs/ sqlupgrade

<MMDD>

.

<NNN>

, where:

○

<MM>

– is the month.

○

<DD>

– is the date.

○

<NNN>

– is a three-digit number identifying the sqlupgrade server upgrade session.

After all preupgrade checks are successful, sqlupgrade shuts the old server down, then starts the new

SAP ASE dataserver binary on the old master device.

Results

When the upgrade succeeds, you can:

● Click

OK

to specify another server to upgrade, or

● Exit sqlupgrade and perform post-upgrade tasks.

The upgrade process:

● Creates the RUN_servername file, which contains the information required to restart the server

● Runs the installmaster script to create system procedures

To verify that the upgrade was successful, log in to the server and run:

● select @@version – SAP ASE should return 16.0.

● sp_configure "upgrade version" – SAP ASE should return 16000000 (16 million).

9.6.2 Upgrading Noninteractively Using sqlupgraderes

You can upgrade SAP ASE without the graphical user interface (GUI), in noninteractive mode by using values from a resource file that defines the attributes for the server to be upgraded.

Prerequisites

Set the OLDSYBASE_ASE variable to the SYBASE_ASE that is appropriate to your older server. If you are upgrading from 15.7 for example, OLDSYBASE_ASE should be ASE-15_0.

In addition, set the OLDSYBASE, and OLDSYBASE_OCS environment variables to point to the older version installation of SAP ASE. The upgrade utility that you run from the new $SYBASE directory populates input fields with the correct information as you upgrade.

Source SYBASE.csh before running sqlupgraderes if you have not already so.



P U B L I C


75

The sqlupgraderes utility automatically restarts the server you are upgrading.

Procedure

1. Edit the sample resource file included in your SAP ASE distribution in $SYBASE/$SYBASE_ASE/init/ sample_resource_files. Use a text editor to edit the resource file.

2. Execute sqlupgraderes by entering the following at the UNIX prompt, where

<resource_file>

specifies the resource file containing the attributes that describe the server to upgrade:

$SYBASE/$SYBASE_ASE/bin/sqlupgraderes -r

<resource_file>

The available command options for sqlupgraderes are:

○ -s

<sybase_dir>

– specifies the value to use for the SYBASE environment variable. •

○ -r

<resource_file>

– executes the specified resource file.

○ -D

<data_directory>

– specifies a working directory that differs from the default $SYBASE directory. This allows users other than the sa to configure and use SAP ASE without the need to have access permission to the $SYBASE directory.

○ -v – prints the version number and copyright message for sqlupgraderes and then exits.

Running the sqlupgraderes utility creates a new file containing the values you specified for the upgrade session, and writes it to the sqlupgradeMMDD.NNN-server_name.rs file in $SYBASE/$SYBASE_ASE/ init/logs/.

Where:

○

<server_name>

– is the server you are upgrading.

○

<MM>

– is the month.

○

<DD>

– is the date.

○

<NNN>

– is a three-digit number identifying the sqlupgrade session.

If the resource file you are modifying was created by sqlupgrade, the prefix of the attribute name may vary. sqlupgraderes ignores this prefix when processing the resource file. The attributes and their default values are:

○ sybinit.release_directory – $SYBASE [

<path = _name_of_old_release>

]

○ sybinit.product – sqlsrv

○ sqlsrv.server_name –

<server_name>

○ sqlsrv.new_config – no default value

○ sqlsrv.sa_login –

<current_login>

○ sqlsrv.sa_password –

<current_password>

○ sqlsrv.do_upgrade – Yes

○ sqlsrv.do_reserved_word_check –Yes

All attributes are required, and all values are case-sensitive.

76

P U B L I C




9.6.3 Manually Upgrading SAP ASE

You can upgrade manually without using a wizard or utility.

Prerequisites

Source SYBASE.csh to set up the environment variables if you have not already done so.

Context

To upgrade SAP ASE manually, use the upgrade executable located in $SYBASE/ASE-16_0/bin.

Procedure

1. Shut down:

○ The pre-16.0 SAP ASE server

○ All additional servers that are using the same $SYBASE directory as the SAP ASE

2. If you installed ASE 16.0 SP01 into a directory other than the old ASE directory, copy the server entry from the old interfaces file to the new interfaces file.

3. Copy the

<server_name>

.cfg file from old directory to the new $SYBASE directory.

4. Start the 16.0 SP01 server with the old master device from the old server.

5. Copy and edit the RUN_

<server>

file to the ASE-16_0/install directory from install directory of the old version of SAP ASE you are upgrading from (for example, ASE-12_5/install or ASE-15_0/ install).

6. Restart all the additional servers you shut down after shutting down the pre-16.0 SAP ASE.

7. Run upgrade. If problems occur, fix them, and re-run the upgrade process.

8. Reinstall the SAP ASE-supplied stored procedures to prevent any errors caused from changes to the system catalogs.

9.6.4 Install and Upgrade an Existing Installation

Use a binary overlay to install SAP ASE 16.0 SP01 over an existing version 16.0 installation directory.

If you have enabled the Java-in-the-database feature, create the sybpcidb database and disable the feature during the installation.

After you install SAP ASE verion 16.0 SP01 over an existing 16.0 directory, run the updatease utility to upgrade the ASE servers.



P U B L I C


77



9.6.4.1 Determining the SAP ASE Version

Before using the binary overlay, verify that your current version of SAP ASE is at least 16.0.

Procedure

1. Verify that you have version 16.0 or higher:

○ If your server is running:

1> select @@version

2> go

○ If your server is not running:

$SYBASE/$SYBASE_ASE/bin/dataserver -v

2. Source environment variables before executing dataserver -v.

Results

If the result shows that SAP ASE is earlier than version 16.0, you cannot use the binary overlay, but must use

an upgrade method instead. See SAP ASE Upgrades [page 59]

.

9.6.4.2 Backing Up SAP ASE

Installing SAP ASE version 16.0 SP01 and later overwrites the current SAP ASE software. Before installing, verify that your databases are error-free, and back up the SAP ASE directory.

Procedure

1. To ensure that your database is error free, run dbcc checkdb, dbcc checkcatalog, and dbcc checkstorage before loading any new SAP ASE binaries, including the master database. If the dbcc commands reveal problems, check the Error Messages and Troubleshooting Guide for actions necessary to fix the problem. If the error is not listed in the manual, call Technical Support.

78

P U B L I C




2. After you have verified that your database is error free, back up your $SYBASE directory in case you need to roll back to the original version of the software.

3. SAP ASE provides the uninstmsgs.ebf script for backing up sysmessages before upgrading to 16.0

SP01. Use it to back up sysmessages before running instmsgs.ebf.

9.6.4.3 Installing SAP ASE Using the Binary Overlay

Use the installer to install SAP ASE version 16.0 SP01 on top of your existing SAP ASE, if it is no earlier than version 16.0.

Procedure

1. From your SAP ASE directory, shut down the servers that are using the binaries. Use a regular "polite" shutdown as opposed to using the shutdown with nowait option, both as the initial and final steps.

Doing so flushes free space accounting figures, object statistics, and runs checkpoint on the database to minimize recovery work during the upgrade process.

2. Use the installer to load the new software from the installation media.

Navigate to the CD or DVD drive and enter ./setup.bin.

3. Select the language.

4. On the Introduction screen, click

Next

.

5. Specify the destination directory with the SAP ASE you want to update, then click

Next

.

Note

Do not use single or double quotes character when specifying a path. The installer does not recognize quote marks, and displays an error.

6. If you see

Choose Update Installation

, this means that there is an older version of SAP ASE in the directory you specified for the installation.

If you click:

○

Yes

– the installer identifies which features you already have, and automatically updates them to the newest version.

○

No

– the installer prompts you to perform a typical, full, or custom installation to specify what features you want to update.

Note

Clicking

No

does not take you to the previous screen to change the installation directory. To do this, click

Previous

.

7. Click

Next

.

The installer checks that the version you wish to update is compatible with the version of SAP ASE you are installing. If the version is incompatible, the

Check Upgrade Incompatible Version

dialog appears, and you see a message similar to:



P U B L I C


79

Warning: The current "SAP Adaptive Server Enterprise Suite" in your destination directory is not compatible with this version upgrade; some bug fixes may be unavailable if you proceed. See the release note for more information.

You may see a similar message if your SAP ASE is an out-of-band release, such as an emergency bug fix, one-off, controlled, or instrumental release:

Warning: The current "SAP Adaptive Server Enterprise Suite" in your destination directory is an out-ofband release; some bug fixes may be unavailable if you proceed. Verify that the bug fixes you need are in this newer version before proceeding with the upgrade.

If you see such messages, click

Cancel

to stop the installation process. To override the error and continue with the installation, select

Proceed installation with incompatible version

and click

Next

.

Caution

Upgrading to an incompatible version may cause software regression. We recommend that you cancel the installation and obtain a compatible version of SAP ASE.

If you perform the installation in a silent, or unattended mode, and the versions are incompatible, the installer asks you to rerun the installer with this argument, then quit:

DALLOW_UPGRADE_TO_INCOMPATIBLE_VERSION=true

8. Install SAP ASE 16.0 SP01 into the existing $SYBASE installation path.

If you are upgrading from SAP ASE version 15.7.x, once the installer unloads the files, the installer displays the Choose Update Adaptive Server dialog, which installs and updates SAP ASE, system stored procedures, and messages. If you select

Update Adaptive Server

, the installer prompts you to select your

SAP ASE, and enter the system administrator password.

9. Run select @@version. The server should now be at version 16.0 SP01.


Postinstallation Tasks [page 51]

Installing in Silent Mode [page 46]

The updatease Utility [page 80]

9.6.4.4 The updatease Utility

The updatease utility reinstalls scripts and updates system stored procedures and messages.

The updatease executable file is located in the $SYBASE/SYBASE_ASE/bin/ directory.

When you perform a minor upgrade or update from SAP ASE version 16.0 and later, you must also reinstall the scripts in $SYBASE/ASE-16_0/scripts/ as well as update the system stored procedures and messages.

updatease can perform these tasks for you.

80

P U B L I C




Note

If you performed the minor upgrade using the SAP ASE installer, the installer ran updatease in the background; you need not perform any additional steps.

Syntax

updatease -S

<server_name>

-P

<ASE_password>

-k

Parameters

-S <server_name>

specifies the SAP ASE you are updating.

-P <ASE_password>

is the SAP ASE "sa" password. If you do not specify this, updatease obtains the information from the SYBASE_ASE_SA_PWD environment variable or at the prompt.

-k

(optional) when specified, skips the database free-space check.

Usage

The updatease utility requires system databases to be at least 2GB. If your system databases are smaller, updatease does not work, and you see a message similar to:

Arithmetic overflow occurred.

When this happens, manually run updatease ($SYBASE/ASE-16_0/bin/updatease) using the -k argument to update the SAP ASE.

Permissions

To use updatease, you must be an SAP ASE system administrator, or log in with the sa_role.



P U B L I C


81

9.7 Upgrading in Silent Mode

To perform a silent, or unattended installation, run the installer and provide a response file that contains your preferred installation configuration.

Procedure

1. Create a response file during a console or GUI upgrade: setup.bin -r

<response_file_for_upgrade>

2. If you are upgrading to SAP ASE 16.0 SP01 from SAP ASE 15.5 or later, set the following properties in the response file to

true

:

Property Description

DO_UPDATE_INSTALL

When you set DO_UPDATE_INSTALL to

true

, the installer reviews and updates the installed components in $SYBASE.

DO_UPDATE_ASE_SERVER (Optional) When you set DO_UPDATE_ASE_SERVER to

true

, the installer installs (or reinstalls) system procedures, messages, scripts, and so on in the

SAP ASE instance.

DO_UPDATE_ASE_SERVER is valid only if you set DO_UPDATE_INSTALL to

true

.

The DO_UPDATE_ASE_SERVER property requires that you also set:

○ UPDATE_ASE_SERVER_NAME_[

<n>

]=

<SAP_ASE_name_to_update>

○ UPDATE_ASE_PASSWORD_[

<n>

]=

<SAP_ASE_password>

– if the SAP

ASE password is null, set this value to "

NA

".

For example:

DO_UPDATE_ASE_SERVER=true

UPDATE_ASE_SERVER_NAME_1=SYBASE1

UPDATE_ASE_PASSWORD_1=NA

UPDATE_ASE_SERVER_NAME_2=SYBASE2

UPDATE_ASE_PASSWORD_2=NA

You also can set UPDATE_ASE_SERVER_NAME_[

<n>

] and

UPDATE_ASE_PASSWORD_[

<n>

] property values through the

UPDATE_ASE_SERVER_NAME_[

<n>

] and UPDATE_ASE_PASSWORD_[

<n>

] environment variables.

If you choose to update the SAP ASE instance manually after the installation, you need not set DO_UPDATE_ASE_SERVER.

Note

Do not include the DO_UPDATE_INSTALL property in the response file if you are upgrading from a version of SAP ASE earlier than 15.5, as this causes the installer to fail.

82

P U B L I C




3. Run: setup.bin –f


-i silent

-DUSER_INSTALL_DIR=

<install_location>

-DAGREE_TO_SAP_LICENSE=true where:

○


– is the absolute path of the file name containing the upgrade options you chose.

○

<install_location>

– is the directory in which you are upgrading SAP ASE.

Agree to the SAP License Agreement when upgrading in silent mode using one of these methods:

○ Include the option -DAGREE_TO_SAP_LICENSE=true in the command line argument

○ Edit the response file to include the property AGREE_TO_SAP_LICENSE=true.

Except for the absence of the GUI screens, all actions of InstallAnywhere are the same, and the result of an upgrade in silent mode is exactly the same as one done in GUI mode with the same responses.


Installing SAP ASE Using a Response File [page 44]

Creating a Response File [page 44]

Installing in Silent Mode [page 46]

9.8 Postupgrade Tasks

After you have upgraded, make sure your new SAP ASE server is up and running.

Context

The upgrade process does not cause any changes in existing statistics, so you need not run update statistics on any tables after the upgrade. If you are upgrading from SAP ASE version 15.x, however, restart the server to make the statistics available.

Procedure

1. To explicitly re-compile the objects, run dbcc upgrade_object() for each database.

2. If you upgraded from SAP ASE version 12.5.2 or earlier, ensure there are no issues with OAM pages by running dbcc checkcatalog with the fix option: dbcc checkcatalog (

<database_name>

, fix)



P U B L I C


83

3. If you have any system stored procedures that you had saved from before the upgrade (because you had modified them without altering their names), reload them now.

4. Execute: dbcc gam (

<dbname>

,0,0,'check')

This command performs upgrade operations on text and image columns that are deferred during the

SAP ASE upgrade process, and prevents dbcc checkstorage from taking a long time when it is run for the first time after the upgrade.


Considerations When Upgrading from SAP ASE 15.0.x or Earlier [page 60]

Restoring Functionality in SAP ASE After Upgrading [page 85]

How Compiled Objects Are Handled When Upgrading SAP ASE [page 97]

9.8.1 Running the instmsgs.ebf Script

Run message-related scripts after upgrading from version 16.0 to version 16.0 SP01.

Procedure

1. If you upgraded from SAP ASE version 16.0, run uninstmsgs.ebf to safeguard your modified messages in the master database before you install the default version 16.0 SP01 messages: isql -Usa -P

<password>

-w1000 -iuninstmsgs.ebf -orestoremsgs.ebf

2. Run instmsgs.ebf to install the default 16.0 SP01 messages: isql -Usa -P

<password>

-iinstmsgs.ebf

Note

To undo instmsgs.ebf changes, run this script once you have downgraded to the version from which you upgraded: isql -S -Usa -P

<password>

-irestoremsgs.ebf

3. If you use localized files, install any localized language using langinstall, sqlloc, or syconfig.

If you run instmsgs.ebf after installing the 16.0 SP01 localized messages, this script may delete some new messages.

84

P U B L I C




9.8.2 Restoring Functionality in SAP ASE After Upgrading

Restore functionality in the server after an upgrade.

Procedure

1. If you changed any configuration parameters before upgrading, use sp_configure to set them back to their earlier values.

2. Use sp_dboption to reset any database options you disabled before upgrading.

3. Before you use the upgraded server, verify that all custom scripts point to SAP ASE 16.0.

4. Verify procedure cache allocation. The size should be the same as before upgrading, unless the original size was smaller than the default value.

5. Check the procedure cache requirements. Version 16.0 stored procedures, triggers, and other compiled objects require much more memory to run than earlier versions.

Use sp_configure to increase the procedure cache size during runtime, and sp_configure verify to verify any changes you make to the configuration file without having to restart SAP ASE: sp_configure "configuration file", 0, "verify", "

<full_path_to_file>

"

See Reference Manual: Procedures and the Performance and Tuning Guide for details about sp_configure and sp_sysmon, and the System Administration Guide for information about configuring memory.

6. Verify data cache allocation.

During the upgrade process, the server ensures that the default data cache size remains the same.

Therefore, during the preupgrade process before the upgrade, the size of the default data cache is obtained and written to the configuration file as an absolute value, not as a default. This enables the server to have the same default data cache size as before the upgrade. If this size is less than the default size of

8MB, the server allocates a default data cache of 8MB.

7. If you unmirrored devices, remirror them using the disk remirror command.

8. If you used compiled objects, see

How Compiled Objects Are Handled When Upgrading SAP ASE [page

97] .

9. If you used two-phase commit in the earlier version of SAP ASE, run the script to install the two-phase commit tables: isql -U

<sa>

-P

<sa_password>

-S

<server_name>

-i$SYBASE/$SYBASE_ASE/scripts/installcommit



How Compiled Objects Are Handled When Upgrading SAP ASE [page 97]



P U B L I C


85

9.8.3 Reenabling Auditing

If the server you upgraded from was configured for auditing, reenable auditing in the upgraded server.

Procedure

1. Enter: sp_configure 'auditing', 1

2. Reenable auditing for all system stored procedures for which auditing was enabled before the upgrade.

1. Use the output of sp_displayaudit recorded during the preupgrade process to identify the system stored procedures for which auditing was enabled.

2. Reenter the audit options using sp_audit. For example, if you had enabled stored procedure auditing for sp_addgroup stored procedure in your server before upgrading, run: sp_audit "exec_procedure", "all", "sp_addgroup", "on"





9.8.3.1 Updating Threshold Procedures for Audit Segments

An post-upgrade task is required for threshold procedures used to archive audit segments.

If your previous installation used a threshold procedure, similar to this, execute the following to archive the

<sysaudits>

table:

INSERT MyPre15SysAuditHistoryTable SELECT * FROM sysaudits_0n where

<n>

corresponds to the sysaudits table number 1–8 and MyPre15SysAuditHistoryTable is a table defined prior to version 16.0, then you must alter MyPre15SysAuditHistoryTable to add a nodeid column using: alter table MyPre15SysAuditHistoryTable

add nodeid tinyint NULL

See the Reference Manual: Tables for system tables for details about the sysaudits tables.

86

P U B L I C




9.8.4 Restoring Permissions

If the server you upgraded from had site-specific permissions on system stored procedures, restore those permissions in the upgraded server.

Context

9.9 Migrate

You can migrate from 32-bit to 64-bit versions on different computers or partitions.

To migrate SAP ASE from the 32-bit to the 64-bit version, first install and configure the 64-bit operating system.

To migrate, you can:

● Use dump and load.

● Use the bcp utility.

● Replace the binary.

9.9.1 Migrating Data Using a Dump-and-Load Method

To perform migrations, back up and restore databases using the dump and load commands.

Procedure

1. In the 32-bit SAP ASE server, run dbcc checks (checkdb, checkalloc, checkcatalog, and checkstorage) on all databases in the 32-bit SAP ASE server to ensure they are error free.

2. Create a 64-bit server in a new directory.

3. Create devices and databases to match those in the 32-bit server. Make sure the

<sysusages>

mapping is correct.

Note

Allow 10 percent additional space for the sybsystemprocs database.

4. Dump the databases from the 32-bit server.

5. Load the databases to the 64-bit server.



P U B L I C


87

6. If you have partitioned tables, update partition statistics.

7. Run dbcc checks on the 64-bit server and make sure they run cleanly.

For information on upgrading compiled objects, see Finding Compiled Object Errors Before Production

[page 98]

.

9.9.2 Migrating Data Using bcp

If you use DDL scripts to create devices, databases, tables, rules, stored procedures, triggers, and views, you can use bcp to migrate data from a 32-bit SAP ASE to a 64-bit SAP ASE.

Context

If you:

● Do not have DDL scripts, use the ddlgen utility to re-create the schema for the SAP ASE you are about to migrate. See the Utility Guide.

● Have DDL scripts to create devices, databases, tables, rules, stored procedures, triggers, and views, you can use bcp to move data out of the old database and into the new.

Procedure

1. In the 32-bit SAP ASE, run dbcc checks (checkdb, checkalloc, checkcatalog, and checkstorage) on all databases in the 32-bit SAP ASE to ensure they are error free.

2. Use bcp to extract all the data from all the tables in the databases.

3. Create a new 64-bit SAP ASE in a new directory.

4. Create devices, databases, and tables.

5. Use bcp to bulk copy data into tables.

6. Re-create all views, triggers, and stored procedures.

7. Run dbcc checks on the 64-bit SAP ASE server and make sure they run cleanly.

88

P U B L I C




9.9.3 Migrating Data by Replacing the Binary

Migrate data from a 32-bit server to a 64-bit server by replacing the binary.

Procedure

1. In the 32-bit SAP ASE, run dbcc checks (checkdb, checkalloc, checkcatalog, and checkstorage) on all databases in the 32-bit SAP ASE to ensure that they are error free.

2. Copy the files for the 64-bit SAP ASE into a new directory.

3. Shut down the 32-bit server.

4. Copy the interfaces file and the configuration file from the 32-bit $SYBASE directory to the 64-bit

$SYBASE directory.

5. Copy the 32-bit $SYBASE/$SYBASE_ASE/install/RUN_

<server>

file to the equivalent 64-bit

$SYBASE/$SYBASE_ASE/install directory.

6. Edit the RUN_server file to reflect the new location of the interfaces, configuration, and log files.

7. Remove all references to the 32-bit $SYBASE directories from your

<$PATH>

definition.

8. Change to the 64-bit $SYBASE directory and source the SYBASE.csh script (C shell).

9. Change to the 64-bit $SYBASE/$SYBASE_ASE/bin directory and execute:

startserver -f < RUN_server>

10. After the 64-bit server starts, run installmaster, installmodel, and instmsgs.ebf.

11. If you used dbccdb for dbcc checkstorage, run installdbccdb. This re-creates tables in the dbccdb.

This may cause you to lose data.

12. Drop and re-create the compiled objects, such as stored procedures, triggers, views, and defaults.

13. If you have partitioned tables, update partition statistics.

14. Run dbcc again on all databases to verify that they run cleanly.

9.10 SAP ASE Components and Related Products

After you finish upgrading SAP ASE, upgrade its components and related products.

Refer to Using SAP Failover in a High Availability System for instructions on how to upgrade an SAP ASE configured with high availability.



P U B L I C


89

9.10.1 Upgrading Job Scheduler

After upgrading to a new SAP ASE server, upgrade Job Scheduler.

Context

Note

You must have $SYBASE/$SYBASE_OCS/bin directory in $PATH so the isql executable is accessible. Use isql to perform all the steps in this task.

Procedure

1. Copy the directory services entry for JSAGENT (or jsagent) from the old server to the new server.

2. Make sure the new server is running.

3. Ensure that at least 9000 locks are configured. If the number of locks on the server is fewer than 9000, increase it:

1> sp_configure "number of locks", 9000

2> go

4. Before you restart the SAP ASE server and run Job Scheduler, run the installjsdb script to update Job

Scheduler tables and stored procedures:

1. Disable Job Scheduler:

1> sp_configure "enable job scheduler", 0

2> go

1> sybmgmtdb..sp_sjobcontrol @name=NULL, @option="stop_js"

2> go

2. Run the installjsdb script: isql –Usa –Psa_password –S

<servername>

–i$SYBASE/$SYBASE_ASE/scripts/installjsdb

Note

The directory with the isql executable ($SYBASE/$SYBASE_OCS/bin) must be in your path.

The installjsdb script looks for the sybmgmtdb database.

3. Enable Job Scheduler:

sp_configure "enable job scheduler", 1

4. To start Job Scheduler, either restart the server, or enter:

1> use sybmgmtdb

90

P U B L I C




2> go

1> sp_sjobcontrol @name=NULL, @option="start_js"

2> go

5. Restart the SAP ASE server if you restarted Job Scheduler manually.

6. (Optional) Add more log space. Some 64-bit platforms require additional space for the sybmgmtdb log:

1> use master

2> go

1> alter database sybmgmtdb LOG on sybmgmtdev=20

2> go

7. To upgrade sybmgmtdb, run the installjsdb script that is included, saving the output to a file: isql -Usa -P

<sa_password>

-S

<servername>

-n -i$SYBASE/$SYBASE_ASE/scripts/ installjsdb

-o

<output_file>

Note

When upgrading to SAP ASE version 16.0 SP01 from earlier versions, make sure that the size of sybmgmtdb is at least 160MB, so that it has at least 60 MB of free log space.

9.10.1.1 Upgrading Job Scheduler Templates

After upgrading to the new server, upgrade the templates and jobs created by Job Scheduler.

Context

Note

Several changes impact the Job Scheduler templates. These changes make some templates incompatible with earlier versions of the server. The current templates are version 3.0 in the XML files.

Procedure

1. Disable Job Scheduler.

2. Update any environment variables, scripts, or applications that refer to the Job Scheduler directory path.

The Job Scheduler directory is under the ASE-16_0 directory, in $SYBASE/$SYBASE_ASE/ jobscheduler .

Directories below jobscheduler remain the same.

3. Copy files from the jobscheduler directory to the ASE-16_0 directory. If you are installing the new server directories over the old server directories, the installer automatically moves your files to the new jobscheduler directory.



P U B L I C


91

4. If you modified SAP-supplied templates, stored procedures, or XML documents, do not overlay the new templates with your modified versions. If you do, you lose the enhancements provided by the revised templates. Carefully merge your template changes into the SAP template files, or better yet, rename your modified templates.

5. You may need to make minor modifications to jobs you created from 2.0 or earlier templates. In some templates, parameters changed from varchar(5) to int. The following table lists the templates that changed in version 2.1 and the changes you must make to the SQL code in the jobs created from the templates.

Table 7: Changed Job Scheduler Templates

Template Modified Files Datatype for <parameter> Changed from varchar(5) to int dump database jst_dump_databases @use_srvr_name dump database log update statistics rebuild table jst_dump_log jst_update_statistics rebuild indexes jst_reorg_rebuild_indexes jst_reorg_rebuild_tables

@truncate_flag and

@use_srvr_name

@index_flag

@dump_flag

@dump_flag reclaim indexes jst_reclaim_index_spac reclaim tables jst_reclaim_table_space

@dump_flag

@resume_flag

6. Some Job Scheduler templates have been modified to support new server functionality. These changes are related to new parameters for specifying a partition name, or a data change value for the new server commands that added these options. If you have jobs created from any of the enhanced templates, modify the SQL of the jobs for the 16.0 SP01 servers.

If you have a job scheduled to run on a pre-16.0 server and you need it to also run on 16.0 SP01 servers, leave the existing job alone and create a new job for pre-16.0 servers, as the job commands are different.

You need not modify any jobs you run on pre-16.0 servers. The following table lists the templates that changed in version 3.0 and the changes you must make to jobs created from them.

Note

All templates listed below, except delete statistics, are incompatible with pre-15.0.1 servers. Do not use them to create jobs that are scheduled on pre-15.0.1 servers; you must use the 2.1 or 2.2 versions for pre-15.0.1 servers.

Table 8: Modified Job Scheduler Templates

Template Modified File delete statistics jst_delete_statistics

Change Description

Added @ptn_name as third parameter.

Job Modifications

Optional.

92

P U B L I C




Template update statistics rebuild indexes reclaim indexes reclaim tables multiple

Modified File jst_update_statistics

Change Description Job Modifications

Added @ptn_name as fifth parameter,

@datachg_threshold as the 10th parameter, and added reference.

Required. Include values (or

NULL) for new parameters.

jst_reorg_rebuild_indexes Added @ndx_ptn_name as third parameter.

Required. Include value (or

NULL) for new parameter.

jst_reclaim_index_space jst_reclaim_table_space jst_get_freespace jst_get_usedspace

,

Added @ptn_name as third parameter.



Added @ptn_name as sec ond parameter.



Replace reserved_pgs and data_pgs with reserved_pages and data_pages .

No impact on job SQL.

7. Install the template stored procedures and move them to the Job Scheduler template stored procedure directory. For example: cd $SYBASE/$SYBASE_ASE/jobscheduler/Templates/sprocs

Run the stored procedure installation script for each server being upgraded: installTemplateProcs <

<servername>

> <

<username>

> <

<password>

>

Note

Upgrade template stored procedures on all Job Scheduler servers and target servers that are upgraded to SAP ASE version 16.0 SP01. Do not install them on pre-15.5 servers.

8. Install and move the template XML documents into the JS template XML directory. For example: cd $SYBASE/$SYBASE_ASE/jobscheduler/Templates/xml

9. Before running the installTemplateXml XML installation script, set the SYBASE_ASE_SA_USER environment variable and SYBASE_ASE_SA_PWD variable in the SYBASE.csh file before running the XML installation script:

10. Run the XML installation script on 16.0 SP01 servers with Job Scheduler installed: installTemplateXml

<servername> <machinename> <serverport>

<username> <password>

[

<language_code>

]

Use "en" for the

<language_code>

or omit the parameter completely, as "en" is the default.

Note

Upgrade template XML documents on all Job Scheduler servers upgraded to SAP ASE version 16.0

SP01. Do not install them on pre-16.0 servers or servers where Job Scheduler is not installed.



P U B L I C


93

9.10.2 Upgrading High Availability and Cluster Support

Upgrade the cluster subsystem.

Context

Note

Use these steps to upgrade a cluster subsystem for a nonclustered edition of SAP ASE.

SAP ASE 16.0 and higher supports these cluster platforms for high availability:

● HPIA – MCSG 11.18

● IBM AIX – PowerHA 7.1

● Sun Solaris – VCS4.0, SunCluster 3.2

● Linux-AMD – VCS4.1

● Win2008 R2 – Failover Cluster

There are two ways to upgrade a cluster subsystem:

Procedure

● Perform a major upgrade, which involves cluster downtime, then shut down and restart all servers. You must:

1. Run sp_companion suspend, as described in Using SAP Failover in a High Availability System.

2. Take offline the resource groups of primary and secondary companions on both nodes. Ensure that the companion server and corresponding resource groups are not automatically brought online until the cluster system upgrade is complete.

3. Upgrade the cluster subsystem following the instructions from the cluster system vendor. You may find options to migrate the current resource groups to the new cluster version. If such an option is not available (or if the resource groups get deleted or corrupted), re-create the resource groups and configure them appropriately after you have upgraded the cluster system.

4. Bring the resource groups online. This should bring primary and secondary companions online on their respective nodes.

5. Run sp_companion resume as described in Using SAP Failover in a High Availability System.

● To avoid cluster downtime, perform a minor upgrade. Nodes are failed over to other nodes and upgraded one at a time. For example, assuming ASE1 is the primary companion on node N1, and ASE2 is secondary companion running on node N2:

1. Upgrade the primary companion:

1. Relocate the primary resource group to N2 or shut down ASE1. This causes ASE1 to fail over from

N1 to N2.

2. Upgrade the cluster subsystem on N1 following the upgrade instructions provided by the vendor.

3. Fail back ASE1 from N2 to N1. See the appropriate cluster chapter in Using SAP Failover in a High

Availability System for more details on SAP ASE failback.

94

P U B L I C




2. Upgrade the secondary companion. If you are using a symmetric configuration, follow the steps in

"upgrade the primary companion," above, for ASE2.

If you are using an asymmetric configuration:

1. Take the secondary resource group offline and verify that ASE2 is shut down. ASE2 is unavailable during this upgrade.

2. Upgrade the cluster subsystem on N2 following the upgrade instructions from the vendor.

3. Start ASE2 by bringing the secondary resource group online to N2.

9.10.3 Upgrading Java in the Database

If Java in the database functionality is currently enabled, you must run the installpcidb script, which creates tables and stored procedures in the sybpcidb database.

Procedure

1. Use isql to run the installpcidb script, saving the output to an operating system file.

isql -Usa -P<

<sa_password>

> -S<

<server_name>

>

-i$SYBASE/$SYBASE_ASE/scripts/installpcidb -o<

<output_file>

>

2. Enable the Java in the database functionality:

1> sp_configure 'enable pci', 1

2> go


2> go

You may need to increase 'max memory' to enable these parameters. Restart the server for changes to take effect. You can configure the maximum size of the PCI bridge memory pool through the 'pci memory size' configuration parameter. For more information, see Java in Adaptive Server Enterprise.

9.10.3.1 Enabling Java in the Database in a High Availability

System

You can use the Java in the database feature on a system that also uses high availability.

Context

Drop high availability companionship before installing the sybpcidb database, and reestablish companionship afterwards.



P U B L I C


95

Java in the database functionality must be either enabled or disabled on both nodes of the high availability system.

9.10.4 Upgrading Backup Server

You can upgrade Backup Server at any point after you upgrade SAP ASE using similar steps. XP Server does not have a formal upgrade process.

Procedure

1. If you are:

Option

Upgrading during the initial server installation

Upgrading after the initial installation

Description

Select:

○

Upgrade Existing Servers

when the installer prompts

○

Upgrade SAP ASE Server and Backup Servers

This launches the sqlupgrade utility. Click

OK

.

Start the sqlupgrade utility from the command line. Enter:

$SYBASE/$SYBASE_ASE/bin/sqlupgrade

2. Perform the upgrade steps as prompted.

9.10.5 Upgrading Databases Using Dump and Load

When you upgrade SAP ASE, you can also upgrade databases and transaction logs from versions of SAP ASE as early as 12.5 using the dump and load commands.

Context

Some issues of which you should be aware:

● The upgrade process requires space for copying data and logging changes to the system tables. If the source database in the dump was full, the upgrade process might fail. You can use alter database to extend the free space in the event of insufficient-space errors.

● After reloading an older dump, run sp_checkreswords from the new installation on the loaded database to check for reserved words.

96

P U B L I C




9.10.6 How Compiled Objects Are Handled When Upgrading

SAP ASE

SAP ASE upgrades compiled objects based on their source text.

Compiled objects include:

● Check constraints

● Defaults

● Rules

● Stored procedures (including extended stored procedures)

● Triggers

● Views

The source text for each compiled object is stored in the syscomments table, unless it has been manually deleted. The upgrade process verifies the existence of the source text in syscomments. However, compiled objects are not actually upgraded until they are invoked.

For example, if you have a user-defined stored procedure named list_proc, the presence of its source text is verified when you upgrade. The first time list_proc is invoked after the upgrade, SAP ASE detects that the list_proc compiled object has not been upgraded. SAP ASE recompiles list_proc, based on the source text in syscomments. The newly compiled object is then executed.

Upgraded objects retain the same object ID and permissions.

You do not receive any notification if the compiled objects in your database dump are missing source text.

After loading a database dump, run sp_checksource to verify the existence of the source text for all compiled objects in the database. Then, you can allow the compiled objects to be upgraded as they are executed, or you can run dbcc upgrade_object to find potential problems and upgrade objects manually.

Compiled objects for which the source text has been hidden using sp_hidetext are upgraded in the same manner as objects for which the source text is not hidden.

For information on sp_checksource and sp_hidetext, see Reference Manual: Procedures.

Note

If you are upgrading from a 32-bit to a 64-bit SAP ASE, the size of each 64-bit compiled object in the sysprocedures table in each database increases by approximately 55 percent when the object is upgraded. The preupgrade process calculates the exact size; increase your upgraded database size accordingly.

To determine whether a compiled object has been upgraded when you upgrade to a 64-bit pointer size in the same version, look at the

<sysprocedures.status>

column. It contains a hexadecimal bit setting of 0x2 to indicate that the object uses 64-bit pointers. If this bit is not set, it indicates a 32-bit object, which means it has not been upgraded.

To ensure that compiled objects have been upgraded successfully before they are invoked, upgrade them manually using the dbcc upgrade_object command.



P U B L I C


97



Restoring Functionality in SAP ASE After Upgrading [page 85]

9.10.6.1 Finding Compiled Object Errors Before Production

Use dbcc upgrade_object to identify potential problem areas that may require manual changes to achieve the correct behavior.

After reviewing the errors and potential problem areas, and fixing those that need to be changed, use dbcc upgrade_object to upgrade compiled objects manually instead of waiting for the server to upgrade the objects automatically.

Table 9: Upgrade Problems

Problem Description

Missing, truncated, or corrupted source text

Temporary table refer ences

Reserved word errors

If the source text in syscomments has been deleted, truncated, or otherwise corrupted, dbcc upgrade_object may report syntax errors.

Solution

If:

● The source text was not hidden

– use sp_helptext to verify the completeness of the source text.

● Truncation or other corruption has occurred – drop and recreate the compiled object.

If a compiled object, such as a stored procedure or trigger refers to a temporary table (#temp

<table_name>

) that was created outside the body of the object, the upgrade fails, and dbcc upgrade_object returns an error.

Create the temporary table exactly as expected by the compiled object, then execute dbcc upgrade_object again. Do not do this if the compiled object is up graded automatically when it is in voked.

If you load a database dump from an earlier version of

SAP ASE into version 15.7 or later and the dump contains a stored procedure that uses a word that is now reserved, when you run dbcc upgrade_object

on that stored procedure, the command returns an error.

Either manually change the object name or use quotes around the ob ject name, and issue the command set quoted identifiers on . Then drop and re-create the compiled object.

98

P U B L I C




9.10.6.1.1 Quoted Identifier Errors

Quoted identifiers are not the same as literals enclosed in double quotes. The latter do not require you to perform any special action before the upgrade.

Context

dbcc upgrade_object returns a quoted identifier error if:

● The compiled object was created in a pre-11.9.2 version with quoted identifiers active (set quoted identifiers on).

● Quoted identifiers are not active (set quoted identifiers off) in the current session.

For compiled objects the upgrade process automatically activates or deactivates quoted identifiers as appropriate.

Procedure

1. Activate quoted identifiers before running dbcc upgrade_object.

When quoted identifiers are active, use single quotes instead of double quotes around quoted dbcc upgrade_object keywords.

2. If quoted identifier errors occur, use the set command to activate quoted identifiers, and then run dbcc upgrade_object to upgrade the object.

9.10.6.1.2 Determining Whether to Change select * in Views

Determine whether columns have been added to or deleted from the table since the view was created.

Context

Perform these queries when dbcc upgrade_object reports the existence of select * in a view:

Procedure

1. Compare the output of syscolumns for the original view to the output of the table.



P U B L I C


99

In this example, you have the following statement: create view all_emps as select * from employees

Caution

Do not execute a select * statement from the view. Doing so upgrades the view and overwrites the information about the original column information in syscolumns.

2. Before upgrading the all_emps view, use these queries to determine the number of columns in the original view and the number of columns in the updated table: select name from syscolumns

where id = object_id("all_emps") select name from syscolumns

where id = object_id("employees")

3. Compare the output of the two queries by running sp_help on both the view and the tables that comprise the view.

This comparison works only for views, not for other compiled objects. To determine whether select * statements in other compiled objects need to be revised, review the source text of each compiled object.

If the table contains more columns than the view, retain the preupgrade results of the select * statement. Change the select * statement to a select statement with specific column names.

4. If the view was created from multiple tables, check the columns in all tables that comprise the view and rewrite the select statement if necessary.

100

P U B L I C




10 SAP ASE Downgrades

An SAP ASE server that has been upgraded to 16.0 SP01 requires specifics tasks before it can be downgraded to a version of 16.0.

You can downgrade SAP ASE version 16.0 SP01 to version 16.0.

Even if you have not used any of the new features in SAP ASE 16.0 SP01, the upgrade process added columns to system tables. This means you must use sp_downgrade_esd to perform the downgrade.

There are additional steps to perform if you are using encryption or replicated databases. See Replication

Server Administration Guide Volume 2 for information on downgrades and replicated databases.

Note

You cannot downgrade a single database through dump and load directly from SAP ASE 16.0 SP01 to an earlier version.

10.1 Downgrading from SAP ASE Version 16.0 SP01

Use sp_downgrade_esd to downgrade SAP ASE 16.0 SP01.

Prerequisites

To use sp_downgrade_esd, you must have sa_role, and be in the master database.

Context

Use the sp_downgrade_esd system procedure to downgrade a database from SAP ASE version 16.0 SP01 to

16.0

Note sp_downgrade_esd does not downgrade an entire SAP ASE installation at once.


SAP ASE Downgrades

P U B L I C


101

Procedure

1. Restart the SAP ASE server in single-user mode by specifying the -m option.

2. In a loop, run sp_downgrade_esd on each database. You need not downgrade temporary databases – including tempdb as well as user-created temporary databases – as they are re-created from a template database when the SAP ASE server starts. To downgrade your entire installation, run sp_downgrade_esd for each database in your installation.

Caution

If you are downgrading the entire installation, downgrade the master database last, only after performing sp_downgrade_esd on all of your non-temporary databases

The syntax for sp_downgrade_esd is:

sp_downgrade_esd @

<database_name>

[, @

<target_version>

[, @verbose]] where:

○

<@database_name>

– is the name of the database you are downgrading

○

<@target_version>

– is a string that specifies what version of 16.0 to go back to. It accepts values

“GA” (the default) or “SP0 PLxx” where “xx” is an integer. “GA” is an abbreviation for “SP0 PL0”. The valid options are:

○ "GA" – (default) for SAP ASE version 16.0.

○ "SP0 PL

<xx>

" – where

<xx>

is an integer. Specifying "SP0 PL0" is the same as using "GA"

○ @

<verbose>

– is an integer that, when used, displays the output in the verbose mode. Valid values are:

○ 1 – the procedure produces extra messages about what it is doing

○ 0 – produces no additional messages

For example:

1> sp_downgrade_esd sybsystemprocs, GA

2> go

Reverting database 'sybsystemprocs' to 'GA'.

Database 'sybsystemprocs' is now suitable for use by GA.

(return status = 0)

1>

2> sp_downgrade_esd sybsystemdb, GA

3> go

Reverting database 'sybsystemdb' to 'GA'.

Database 'sybsystemdb' is now suitable for use by GA.

(return status = 0)

1> sp_downgrade_esd model, GA

2> go

Reverting database 'model' to 'GA'.

Database 'model' is now suitable for use by GA.

(return status = 0)

1> sp_downgrade_esd MYASE_tdb_1, GA

2> go

Reverting database 'MYASE_tdb_1' to 'GA'.

Database 'LUMINOUS_tdb_1' is now suitable for use by GA.

(return status = 0)

1> sp_downgrade_esd master, GA

2> go

Reverting database 'master' to 'GA'.

Database 'master' is now suitable for use by GA.

102

P U B L I C




(return status = 0)

1> shutdown

2> go

3. Shut down the 16.0 SP01 version of SAP ASE.

4. With your 16.0 SP01 SAP ASE shut down, start your older version of SAP ASE 16.0 using the same master device that the 16.0 SP01 was using.

10.2 Dumping a 16.0 SP01 Database to Load Into an Older

Version of SAP ASE 16.0

You can open an SAP ASE 16.0 SP01 database in a 16.0 SAP ASE by using the sp_downgrade_esd system procedure.

Context

If you have a database in SAP ASE version 16.0 SP01 that you want to open in SAP ASE 16.0, you can downgrade the database with sp_downgrade_esd and perform the dump and load. You can then revert the database so that it is usable in the current version of SAP ASE again.

Note

Use these steps only to open a 16.0 SP01 database in an earlier 16.0 version of SAP ASE, and not to downgrade SAP ASE itself.

Perform these steps for one database at a time, and only for the databases you want to open in version 16.0 of

SAP ASE.

Procedure

1. Put a database (

<@db_name>

) in single-user mode.

2. Run sp_downgrade_esd

<@db_name>

on the database.

The syntax for sp_downgrade_esd is:

sp_downgrade_esd @

<database_name>

[, @

<target_version>

[, @verbose]] where:

○

<@database_name>

– is the name of the database you are downgrading

○

<@target_version>

– is a string that specifies what version of 16.0 to go back to. It accepts values

“GA” (the default) or “SP0 PLxx” where “xx” is an integer. “GA” is an abbreviation for “SP0 PL0”. The valid options are:



P U B L I C


103

○ "GA" – (default) for SAP ASE version 16.0.

○ "SP0 PL

<xx>

" – where

<xx>

is an integer. Specifying "SP0 PL0" is the same as using "GA"

○ @

<verbose>

– is an integer that, when used, displays the output in the verbose mode. Valid values are:

○ 1 – the procedure produces extra messages about what it is doing

○ 0 – produces no additional messages

3. Use dump database

<@db_name>

to dump the database.

4. Run online database

<@db_name>

. This brings the affected database back to its proper revision level after the downgrade procedure.

5. Take the

<@db_name>

database out of single-user mode.

10.3 Downgrading Job Scheduler

If you are downgrading to SAP ASE version 16.0, run installjsdb script from the earlier version.

Procedure

1. Disable Job Scheduler:

1> sp_configure "enable job scheduler", 0

2> go

1> sybmgmtdb..sp_sjobcontrol @name=NULL, @option="stop_js"

2> go

2. Follow the downgrade steps for your platform.

3. After downgrading, enter this command from the earlier version of SAP ASE: isql –Usa –Psa_password –S

<servername>

–i$SYBASE/$SYBASE_ASE/scripts/installjsdb

Note

The directory with the isql executable ($SYBASE/$SYBASE_OCS/bin) must be in your path.

4. Enable Job Scheduler: sp_configure "enable job scheduler", 1

5. To start Job Scheduler, either restart the server, or enter:

1> use sybmgmtdb

2> go

1> sp_sjobcontrol @name=NULL, @option="start_js"

2> go

104

P U B L I C




10.4 Post-downgrade Tasks for SAP ASE

After you perform the basic downgrade steps, finish the process by handling residual tasks.

Procedure

1. Installing system stored procedures over the old version drops auditing information about system stored procedures. Use the output of sp_displayaudit recorded during predowngrade to help determine the system stored procedures for which auditing was enabled. Reenter the audit options using sp_audit. For example, if sp_addlogin was audited in your server before upgrading, run this command to reenable auditing on sp_addlogin: sp_audit "exec_procedure", "all", "sp_addlogin", "on"

After you run installmaster, installmodel, installcommit, installsecurity, installhasvss, installjsdb, and installmsgsvss on your downgraded server, return system stored procedures to their earlier form. New stored procedures introduced in releases subsequent to the downgraded server are not removed.

Caution

Executing new stored procedures against an older binary may cause unpredictable results.

2. The on-disk structures of stored procedures, triggers, and views may contain statement identity tokens, datatypes, and object references that are not understood by the earlier SAP ASE versions. You must drop all compiled objects that use features introduced into SAP ASE subsequent to the version to which you are downgrading.

3. If during the upgrade process you ran update all statistics on syslogins, you must delete statistics for syslogins and re-create them.

spt_values are dropped and re-created when you run installmaster from the release area you downgraded to. Any new types are eliminated from this table.

4. Run installmaster from the release area of the server to which you downgraded to remove configuration parameters that belong to 16.0 SP01, by deleting

<sysconfigures>

rows for configuration parameters that do not exist in syscurconfigs. After running installmaster, the error messages no longer appear when you start the server.

If you start a downgraded server using the 16.0 SP01 configuration file, the new options generate an

Unknown parameter message. The unknown options are reported the first time you restart the server.

You can ignore these messages; the configuration file is rewritten without the unknown options.



P U B L I C


105

11 Troubleshoot the Server

Determine the cause of problems and apply the recommended solution.

To determine the cause of an error, first look in the log file of the utility being used, to identify the task the utility was performing when it failed. Then check the server error log.

This table lists possible causes and solutions for common problems that you might encounter during a firsttime installation, or an upgrade. If you continue to have problems, retry the installation or upgrade.

If the installation program or srvbuild unexpectedly quits, or if you cannot correct the problem, see the Error

Messages and Troubleshooting Guide.

Problem Solution

The installation program cannot start the SAP

ASE server

● Make sure you meet RAM requirements. If you have the required amount of

RAM, remove, then reinstall all applications to the hard drive and restart the installation.

● After SAP ASE is installed, there should be 25MB of free disk space left in the disk drive. SAP ASE needs approximately 18MB to create shared memory files.

● The SAP ASE server may not start if it cannot find a SySAM license or if the grace period has expired. Check the SAP ASE error log for the cause of the license checkout failure and fix the issues.

The installation program cannot connect to the upgraded SAP ASE server

Verify that the environment variables and password are correct.

11.1 Error Logs for Installation Utilities

The information in the error logs may help determine the reason and possible solutions for problems with installation-related utility programs.

Utility Default Location and File Name

SAP ASE Installer $SYBASE/log/ASE_Suite.log

srvbuildres

$SYBASE/$SYBASE_ASE/init/logs/srvbuild

<MMDD>

.

<NNN>

where:

●

<MM>

– is the month.

●

<DD>

– is the date.

●

<NNN>

– is a three-digit number identifying the srvbuild session.

106

P U B L I C



Troubleshoot the Server

Utility

sqlupgraderes

Default Location and File Name

● $SYBASE/$SYBASE_ASE/init/logs/sqlupgrade

<MMDD>

.

<NNN>

● $SYBASE/$SYBASE_ASE/bin/upgrade.

<NNN>

– is a temporary file created by the upgrade process.

11.2 Error Logs for SAP ASE Servers

The information in the error logs may help to determine the reason and possible solution for an error message.

Server

SAP ASE

Default Location and File Name

$SYBASE/$SYBASE_ASE/install/

<servername>

.log

Backup Server


<servername>

.log

XP Server


<servername>

.log

11.3 Troubleshooting Common Installation Problems

Identify the cause of installation problems and apply the recommended solutions.

If your installation fails, review error messages and your SAP ASE error log to determine the cause of the failure.

Problem

Cannot use X-

Windows.

Resolution

If the setup and configuration utilities do not show correctly, you may need to adjust the resolution on your monitor.

To change to a smaller font size, issue the following UNIX commands:

% cd $SYBASE/ASE-16_0

% chmod +w xappdefaults

% cd xappdefaults

% chmod +w *

% foreach i(*)

? cat $i | sed -e "s/140/100/g" | sed -e "s/^#D/D/g" | sed -e

"s/^#S/S/g" > p

? mv p $i

? end

%

The installation utilities will now use approximately 25 percent less window space.

Cannot eject the CD or DVD from the drive.

If you cannot eject the CD from the drive, check:



P U B L I C


107

Problem Resolution

● Whether the disk drive path is the current directory (pwd) in a UNIX terminal window. If it is, change (cd) to another directory.

● For sybhelp processes. If these processes exist, kill them using the UNIX kill command.

DISPLAY environment variable not set correctly.

The resolution to the DISPLAY variable problem should instruct you to open Exceed

(under Hummingbird Connectivity) and set DISPLAY equal to hostname:

<b>

, where

<b>

is the number in the parentheses following Exceed in the Exceed window.

Client not authorized to connect to server.

This error message means a remote machine does not have permission to display the user interface on the local machine where you start working:

Xlib: connection to "host_name" refused by server

Xlib: Client is not authorized to connect to Server xhost: unable to open display "host_name"

To correct the problem:

1. Enter the following command at the UNIX prompt of your local machine, where

<remote_machine>

is the machine on which you are running the installer: xhost +

<remote_machine>

2. Restart the installer.

Address already in use.

SAP ASE fails to start. The shared memory of the operating system may not be set high enough. Adjust the shared memory value. Restart the installation or upgrade process.

The installer fails to start.

Verify that the operating system has all the patches required by the SAP JRE.

Cannot start XP

Server.

Enter a different port number on the srvbuild window. The command netstat -a produces a list of port numbers in use.

You may receive the following message from XP Server when it is invoked by xp_cmdshell or some other extended stored procedure:

Msg 11018, Level 16, State 1:

Procedure "xp_cmdshell", Line 2:

XP Server must be up for ESP to execute.

(return status = -6)

Troubleshooting resource file installations.

Verify that there is an XP Server entry in the SAP ASE sysservers table. If you created XP Server in a different srvbuild session than SAP ASE and you did not specify a related SAP ASE server, srvbuild cannot update the sysservers table.

Verify that the XP server exists in the interfaces file or LDAP server.

Use sp_addserver to add an entry to the sysservers table.

If you encounter problems during the build, configuration, or upgrade process while using the srvbuild[res], sqlloc[res], or sqlupgrade[res], it may be that these utilities did not allow enough time for a SAP ASE server to shut down properly.

108

P U B L I C




Problem Resolution

Set the SYBSHUTWAIT environment variable to force the utilities to wait for the SAP

ASE server to shut down. For example, this command forces the utility to wait for two minutes before proceeding with the next task:

% setenv SYBSHUTWAIT 120

11.3.1 If the Installation Quits While You Are Configuring an

SAP ASE Server

Perform specific steps if the installation suddenly quits.

Procedure

1. View the contents of the log file generated by the SAP ASE server.

2. Take any suggested actions to correct the problem. If the installation fails after:

○ The installation program created any operating system files, such as the master device or system procedures device files, delete those files.

○ The installation program starts the SAP ASE server that you are attempting to install, shut down that server.

3. Use the srvbuild utility to restart the configuration.

11.4 Stopping a SAP ASE Server After a Failure

If the installation or upgrade session fails after you start a SAP ASE server for any reason, use the shutdown command.

Procedure

1. Log on as "sa".

2. Shut down the SAP ASE server using the shutdown with nowait command. This stops the SAP ASE server immediately, without waiting for currently executing SQL statements to finish:

1> shutdown with nowait

2> go

3. If the installation or upgrade session fails after you start the SAP ASE server, try using SAP Control Center to shut down the server. If SAP Control Center cannot shut down the server, use the shutdown command.



P U B L I C


109

11.5 If SAP ASE Fails the Preupgrade Eligibility Test

Examine the log file to determine why SAP ASE is ineligible for an upgrade.

Context

If SAP ASE fails the preupgrade test, you see:

Server

<SERVER_NAME>

failed preupgrade eligibility test. See log for more information.

Procedure

1. From the Upgrade window, select

Exit

.

2. Examine the log file in $SYBASE/$SYBASE_ASE/init/logs.

After you resolve any problems, shut down the SAP ASE server and use sqlupgrade to complete the upgrade session.

11.6 When an Upgrade Fails

If the upgrade process fails, the installation program displays error messages.

Once you start SAP ASE on the new version, you cannot start SAP ASE on the earlier version. Attempts to do so result in having to restore from backups.

11.6.1 If You Can Identify the Cause of the Upgrade Failure

If the error logs or messages clearly indicate the cause of failure, and you are confident that your databases have not been damaged, you can attempt to fix the problem and immediately re-run the upgrade.

Context

If the upgrade process fails again and you cannot determine the cause of failure, check the error log file to find out when and where the upgrade failed, and contact SAP Product Support.

By default, the log file is located in $SYBASE/$SYBASE_ASE/install/<

<servername>

>log.

110

P U B L I C




Procedure

1. Exit the sqlupgrade program.

2. Perform the necessary actions to fix the problem.

For example, if the error log indicates that the upgrade failed because your existing databases do not contain enough space, use the alter database command to increase the available space.

3. If needed, shut down the SAP ASE server.

Shutting down the server enables the installation program to start the server and re-run the upgrade session.

4. Start sqlupgrade again.

5. Select

Upgrade SAP ASE

, and proceed with the upgrade.

11.6.2 Restoring Databases After a Failed Upgrade

You may need to restore your databases due to a failed upgrade.

Procedure

● If you think the upgrade failure or its cause may have damaged your databases, restore the databases from backups. For information about restoring databases, see the System Administration Guide.

● If you are concerned about the possible corruption of your databases, exit Server Config, but do not attempt to restart the upgrade session until you have restored the databases from backup. After restoration is complete, retry the upgrade.

11.6.3 Recovering from a Failed Upgrade

Upgrade issues may be due to a failure to upgrade an individual database, or a failure to complete configuration changes after all databases have been upgraded.

Context

Use the output from the upgrade utility to correct the problem that caused the failure.



P U B L I C


111

Procedure

● If the upgrade failed because the process ran out of some resource, such as data or log space, locks, or auxiliary scan descriptors, add space to the database using the alter database command.

You may also correct other resource failures by changing the server’s configuration using the sp_configure stored procedure.

● If an upgrade failure leaves a database offline, and the failure can be corrected only by making data changes in the database, you can gain access to the failed database by using isql or a similar program to connect to the affected server as user "sa" and issuing this command: dbcc traceon(990)

Having set this trace flag, user "sa" can now use the offline database and make the necessary changes to correct the upgrade failure.

Note

This trace flag grants access only to user "sa"; "sa_role" does not work. If you have disabled the "sa" login, reenable it to get access using this method.

To restart a server that has not successfully upgraded, use: online database

<failed_db_name>

The server restarts that database’s upgrade from the point of failure.

● If the failure occurs after all databases have been upgraded, or if a failure somehow causes the upgrade utility to fail, manually re-run the utility. After you diagnose and correct the failure, run the upgrade utility:

$SYBASE/$SYBASE_ASE/bin/upgrade

When restarted in this way, the upgrade process says it is "verifying" the upgrade rather than "starting" it, but it makes all the same checks as for the original upgrade.

● To verify that a database has upgraded successfully, check any database’s upgrade status using the online database command. If any upgrade is required for a database, this command performs it. You may also use a procedure such as this to check all databases at a given installation: declare @dbname varchar(255) select @dbname = min(name) from master..sysdatabases while @dbname is not null begin online database @dbname select @dbname = min(name) from master..sysdatabases where name > @dbname end

● Reinstall system stored procedures using the scripts from the new version: isql -Usa -P

<password>

-i $SYBASE/$SYBASE_ASE/scripts/installmaster

112

P U B L I C




Note

When a server fails during an upgrade process, it attempts to upgrade the databases when it restarts.

When the installation is fully recovered, re-run the upgrade utility to ensure that all postupgrade configuration work is done. Then reinstall the system stored procedures.

● During the upgrade process, the log may become too full due to recorded catalog changes. If so, log in to the new server using isql, and issue: isql> dump tran

<dbname>

with truncate_only

1. If truncate_only indicates that it cannot truncate the log, retry the command as no_log instead.

2. If this does not truncate the log successfully, use the alter database command to extend the database as explained below.

● In some cases, preupgrade space estimations are insufficient for the data copy phase of upgrade. You see a message that there is insufficient space in the system segment for the upgrade. When this happens, the upgrade process stops responding, waiting for space to be provided. To increase the size of the database, log in to the new server using isql, and use alter database: isql> alter database

<dbname>

on

<device_name>

= "

<2>

m" alter database allows you to specify the size to alter the database with the unit specifier "m", or "M".

Note

There are certain upgrade failures from which the server cannot recover. For example, attempts to upgrade system tables to version 15.x are quite sensitive to failures at certain points during the required changes. If you encounter such a failure, restore the failed database from backup. To prevent the upgrade from failing again, correct the problem that caused the original failure before issuing the online database command for that database. These catastrophic failures are nearly always caused by running out of resources, as described above, which then causes a failure to undo the aborted transaction.

11.6.4 If You Cannot Identify the Cause of an Upgrade

Failure

Your attempts to upgrade may continue to fail.

Procedure

1. If attempts to upgrade continue to fail, check the error log file to identify where and where the upgrade failed.

By default, the log file is located in $SYBASE/$SYBASE_ASE/install/<servername>.log.

2. Contact Product Support with the information.



P U B L I C


113

Important Disclaimers and Legal Information

Coding Samples

Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP intentionally or by SAP's gross negligence.

Accessibility

The information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication; it is in no way intended to be a binding guideline on how to ensure accessibility of software products. SAP in particular disclaims any liability in relation to this document. This disclaimer, however, does not apply in cases of wilful misconduct or gross negligence of SAP. Furthermore, this document does not result in any direct or indirect contractual obligations of

SAP.

Gender-Neutral Language

As far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as

"sales person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun does not exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.

Internet Hyperlinks

The SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any damages caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are categorized for transparency (see: http://help.sap.com/disclaimer ).

114

P U B L I C






P U B L I C


115

www.sap.com/contactsap


No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. The information contained herein may be changed without prior notice.

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies.

Please see http://www.sap.com/corporate-en/legal/copyright/ index.epx

for additional trademark information and notices.

SAP 16.0 SP01 ASE Installation Guide

Assistant Bot

SAP Adaptive Server Enterprise 16.0 SP01

Document Version: 1.0 – 2015-02-25

Installation Guide for Solaris

PUBLIC

Content

1 Conventions

2 Installation Task Overview

2.1 SAP ASE Software Download

2.2 Installation Workflows

3 SAP ASE Components

3.1 SAP ASE Editions

3.1.1 Determining the Edition You Have

3.2 SAP ASE Options

3.3 Managing SAP ASE with SAP Control Center

3.4 Client Components and Utilities

4 Requirements

4.1 Solaris System Requirements

4.2 SAP Java Runtime Environment Requirements

4.3 Memory Requirements

4.4 System Requirements for Clients

5 Planning Your SAP ASE Installation

5.1 SAP ASE Release Bulletin

5.2 Obtaining a License

5.2.1 Comparing License Deployment Models

5.2.2 SySAM License Server

5.2.3 Determining Host IDs

5.2.3.1 Determining Host IDs for Machines with Multiple

Network Adapters

5.2.3.2 Using Alternate Host IDs on Windows

5.2.4 Generating Licenses

5.2.4.1 Generating License Keys at SMP

5.2.5 Knowing the Product License Type

5.2.5.1 Optional Feature Licenses

5.2.5.2 SySAM Licensing Checkout

5.2.5.3 Sub-capacity Licensing

5.3 Installation Directory Contents and Layout

5.4 Creating the SAP ASE User Account

5.5 Preparing to Install SAP ASE

5.5.1 Adjusting the Operating System Shared Memory

Parameters

5.5.2 Managing Java in the Database During Installations and Upgrades

5.5.3 Multipathing

5.5.3.1 Setting Up Multipathing

6 Installing SAP ASE

6.1 Installing SAP ASE in GUI Mode

6.2 Installing SAP ASE in Console Mode

6.3 Minimally Configuring an SAP ASE Server

6.4 Installing SAP ASE Using a Response File

6.4.1 Creating a Response File

6.4.2 Installing in Silent Mode

6.4.3 Command Line Options

6.5 Uninstalling SAP ASE

6.5.1 Removing an Existing SAP ASE Server

7 Starting and Stopping SAP Control

Center

8 Postinstallation Tasks

8.1 Verifying That Servers are Running

8.2 Verifying Your Connection to the Servers

8.3 Test the Installation and Network Connections

8.4 The System Administrator Account

8.5 Installing Sample Databases

8.5.1 Default Devices for Sample Databases

8.5.2 Running the Database Scripts

8.5.3 Installing the interpubs Database

8.5.4 Installing the jpubs Database

8.5.5 Maintaining Sample Databases

9 SAP ASE Upgrades

9.1 Considerations When Upgrading from SAP ASE 15.0.x or Earlier

9.2 Considerations for Component Integration Services

9.3 Preparing to Upgrade

9.4 Changes in SAP ASE Directories

9.5 Preupgrade Tasks

9.5.1 Upgrade Stored Procedures

9.5.2 Reserved Words

9.5.2.1 Running a Reserved Word Check

9.5.2.2 Addressing Reserved Words Conflicts

9.5.2.3 Quoted Identifiers

9.5.3 Preparing the Database and Devices

**9.10.6.1.2 Determining Whether to Change select * in Views**