Sybase ADAPTIVE 15.0.2 User Manual

Download

Installation Guide

Adaptive Server® Enterprise

15.0.2

[ HP-UX ]

DOCUMENT ID: 35890-01-1502-01 LAST REVISED: April 2007

Information in this document is subject to change without notice. The software described herein is furnished under a license agreement, and it may be used or copied only in accordance with the terms of that agreement.

To order additional documents, U.S. and Canadian customers should call Customer Fulfillment at (800) 685-8225, fax (617) 229-9845. Customers in other countries with a U.S. license agreement ma y co ntac t Customer Fulfillment via the above fax number. All other

international customers should contact their S ybase subsidiary or local distributor. Upgrades are provided only at regularly scheduled software release dates. No part of this publication may be reproduced, transmitted, or translated in any form or by any means, electronic, mechanical, manual, optical, or otherwise, without the prior written permission of Sybase, Inc.

Sybase, SYBASE (logo), ADA Workbench, Adaptable Windowing Environment, Adaptive Component Architecture, Adaptive Server, Adaptive Server Anywhere, Adaptive Server Ente rprise, Ada ptive Ser ver Enter prise Monitor , Adaptive Ser ver Enterprise Replica tion, Adaptive Server Everywhere, Advantage Database Server, Afaria, Answers Anywhere, Applied Meta, Applied Metacomputing, AppModeler, APT Workbench, APT-Build, APT - Edit, APT-Execute, APT-Translator, APT-Library, ASEP, Avaki, Avaki (Arrow Design), Avaki Data Grid, AvantGo, Backup Server, BayCam, Beyond Connected, Bit-Wise, BizTracker, Certified PowerBuilder Developer, Certified SYBASE Professional, Certified SYBASE Professional Logo, ClearConnect, Client-Library, Client Services, CodeBank, Column Design, ComponentPack, Connection Manager, Convoy/DM, Copernicus, CSP, Data Pipeline, Data Workbench, DataArchitect, Database Analyzer, DataExpress, DataServer, DataWindow, DataWindow .NET, DB-Library, dbQueue, Dejima, Dejima Direct, Developers Workbench, DirectConnect Anywhere, DirectConnect, Distribution Director, Dynamic Mobility Model, e-ADK, E-Anywhere, e-Biz Integrator, E-Whatever, EC Gateway , ECMAP, ECRTP, eFulfillment Accelerator, EII Plus, Electronic Case Management, Embedded SQL, EMS, Enterprise Application Studio, Enterprise Client/ Server, Enterprise Connect, Enterprise Data Studio, Enterprise Manager, Enterprise Portal (logo), Enterprise SQL Server Manager, Enterprise Work Architecture, Enterprise Work Designer, Enterprise Work Modeler, eProcurement Accelerator, eremote, Everything Works Better When Everything Works Together, EWA, ExtendedAssist, Extended Systems, ExtendedView, Financial Fusion, Financial Fusion (and design), Financial Fusion Server, Formula One, Fusion Powered e-Finance, Fusion Powered Financial Destinations, Fusion Powered STP , Gateway Manager, GeoPoint, GlobalFIX, iAnywhere, iAnywhere Solutions, ImpactNow, Industry W a r ehouse St udio, InfoMaker, Information Anywhere, Information Everywhere, InformationConnect, InstaHelp, Intelligent Self-Care, InternetBuilder, iremote, iScript, Jaguar CTS, jConnect for JDBC, KnowledgeBase, Legion, Logical Memory Manager, lrLite, M2M Anywhere, Mach Desktop, Mail Anywhere Studio, Mainframe Connect, Maintenance Express, Manage Anywhere Studio, MAP, M-Business Anywhere, M-Business Channel, M-Business Network, M-Business Suite, MDI Access Server, MDI Database Gateway, media.splash, Message Anywhere Server, MetaWorks, MethodSet, mFolio, Mirror Activator, ML Query, MobiCATS, MobileQ, MySupport, Net-Gateway, Net-Library, New Era of Networks, Next Generation Learning, Next Generation Learning Studio, O DEVICE, OASiS, OASiS logo, ObjectConnect, ObjectC ycle, OmniConnect, OmniQ, OmniSQL Access Module, OmniSQL Toolkit, OneBridge, Open Biz, Open Business Interchange, Open Client, Open ClientConnect, Open Client/Server, Open Client/Server Interfaces, Open Gateway, Open Server, Open ServerConnect, Open Solutions, Optima++, Partnerships that Work, PB-Gen, PC APT Execute, PC DB-Net, PC Net Library, Pharma Anywhere, PhysicalArchitect, Pocket PowerBuilder, PocketBuilder, Power++, Power Through Knowledge, power.stop, PowerAMC, PowerBuilder, PowerBuilder Foundation Class Library, PowerDesigner, PowerDimensions, PowerDynamo, Powering the New Economy, PowerScript, PowerSite, PowerSocket, Powersoft, PowerStage, PowerStudio, PowerTips, Powersoft Portfolio, Powersoft Professional, PowerWare Desktop, PowerWare Enterprise, ProcessAnalyst, Pylon, Pylon Anywhere, Pylon Application Server, Pylon Conduit, Pylon PIM Server, Pylon Pro, QAnywhere, Rapport, Relational Beans, RemoteWare, RepConnector, Report Workbench, Report-Execute, Replication Agent, Replication Driver, Replication Server, Replication Server Manager, Replication Toolkit, Resource Manager, RFID Anywhere, RW-DisplayLib, RW-Library, SAFE, SAFE/PRO, Sales Anyw he re , Search Anywhere, SDF, Search Anywhere, Secure SQL Server, Secure SQL T oolset, Security Guardian, ShareLink, ShareSpool, SKILS, smart.partners, smart.parts, smart.script, SOA Anywhere Trademark,SQL Advantage, SQL Anywhere, SQL Anywhere Studio, SQL Code Checker, SQL Debug, SQL Edit, SQL Edit/TPU, SQL Everywhere, SQL Modeler , SQL Remote, SQL Serve r, SQL Server Manager, SQL SMART, SQL Toolset, SQL Se rver/CFT, SQL Server/D B M , SQ L Se rv e r SNMP SubAgent, SQL Station, SQLJ, Stage III Engineering, Startup.Com, STEP, SupportNow, S.W.I .F.T. Message Format Libraries, Sybase Central, Sybase Client/Server Interfaces, Sybase Development Framework, Sybase Financial Server, Sybase Gateways, Sybase Learning Connection, Sybase MPP , Sybase SQL Desktop, Sybase SQL Lifecycle, Sybase SQL Workgroup, Sybase Synergy Program, Sybase Virtual Server Architecture, Sybase User Workbench, SybaseWare, Syber Financial, SyberAssist, SybFlex, SybMD, SyBooks, System 10, System 11, System XI (logo), SystemTools, Tabular Data Stream, The Enterprise Client/Server Company, The Extensible Software Platform, The Future Is Wide Open, The Learning Connection, The Model For Client/Server Solutions, The Online Information Center, The Power of One, TotalFix, TradeForce, Transact-SQL, Translation Toolkit, Turning Imaginatio n Into Reality, UltraLite, UltraLite.NET, UNIBOM, Unilib, Uninull, Unisep, Unistring, URK Runtime Kit for UniCode, Viafone, Viewer, VisualWriter, VQL, WarehouseArchitect, Warehouse Control Center, W a rehouse Studio, W a rehouse WORKS, W atcom, W atcom SQL, Watcom SQL Server, Web Deployment Kit, Web.PB, Web.SQL, WebSights, WebViewer, WorkGroup SQL Server, XA-Library, XA-Server, XcelleNet, XP Server, XTNDAccess and XTNDConnect are trademarks of Sybase, Inc. or its subsidiaries. 07/06

Unicode and the Unicode Logo are registered trademarks of Unicode, Inc. All other company and product names used herein may be trademarks or registered trademarks of their respective companies. Use, duplication, or disclosure by the government is subject to the restrictions set forth in subparagraph (c)(1)(ii) of DFARS 52.227-7013

for the DOD and as set forth in FAR 52.227-19(a)-(d) for civilian agencies. Sybase, Inc., One Sybase Drive, Dublin, CA 94568.

Contents

About This Book.......................................................................................................................... vii

CHAPTER 1 Overview .......................................................................................... 1

Product licensing with SySAM 2.0.................................................... 2

Product components ........................................................................ 3

Adaptive Server Enterprise ....................................................... 3

Backup Server........................................................................... 4

Stored procedures..................................................................... 5

The client................................................................................... 5

Adaptive Server editions .................................................................. 5

Enterprise Edition...................................................................... 6

Small Business Edition.............................................................. 6

Developer Edition...................................................................... 7

Adaptive Server specifications......................................................... 7

Product descriptions and directory layout ........................................ 8

Sybase support for ADO.NET, OLE DB, and ODBC............... 10

PC-Client product descriptions and directory layout ...................... 11

Separately installable PC-Client products............................... 12

CHAPTER 2 Installing Adaptive Server............................................................ 13

Overview ........................................................................................ 13

System requirements ..................................................................... 14

Pre-installation tasks for SySAM.................................................... 15

Accessing SPDC..................................................................... 16

Getting your host ID ................................................................ 17

Generating licenses at SPDC.................................................. 18

Installing a new license server ................................................ 21

Pre-installation tasks for Adaptive Server ...................................... 23

Installing server components ......................................................... 27

Installation methods ................................................................ 27

Installing components with the Installer in GUI mode ............. 27

Installing version 15.0.2 over an existing 15.x Adaptive Server..... 36

Determining Adaptive Server version...................................... 36

Installation Guide iii

Contents

Backing up Adaptive Server.................................................... 36

Installing the Adaptive Server version 15.0.2 binary overlay... 37 Backward compatibility with previous Adaptive Server 15.x

versions............................................................................ 38

XML Services in Adaptive Server version 15.0.2.................... 38

CHAPTER 3 Post-Installation Tasks.................................................................. 39

Post installation instructions........................................................... 39

Verifying that servers are running .................................................. 40

Verifying that you can connect to servers...................................... 41

Connecting to Adaptive Server via Sybase Central....................... 42

Setting the System Administrator password .................................. 42

The SAMreport............................................................................... 43

Installing sample databases........................................................... 44

Default devices for sample databases .................................... 44

interpubs database.................................................................. 46

jpubs database........................................................................ 47

Maintaining the sample databases.......................................... 48

CHAPTER 4 Installing Sybase PC-Client Products.......................................... 49

Overview........................................................................................ 49

Before you install the PC-Client products ...................................... 50

Installing PC-Client products.......................................................... 50

Installing PowerDesigner, PowerTransfer, and InfoMaker............. 53

Configuring network connections for client products...................... 54

Configuring libtcl.cfg for LDAP ................................................ 54

Adding a server to the interfaces file....................................... 56

Testing the Sybase Central installation................................... 58

CHAPTER 5 Upgrading Adaptive Server .......................................................... 59

Overview of the upgrade process .................................................. 60

System catalog changes during upgrade................................ 61

Pre-upgrade tasks.......................................................................... 62

Checking system and upgrade requirements.......................... 63

Noting server and device names and locations....................... 64

Procedure text is required for upgrade.................................... 64

Reserved words ...................................................................... 64

Preparing the database and devices for the upgrade ............. 66

Upgrading to Adaptive Server 15.0.2............................................. 68

Upgrading the server............................................................... 69

Testing the Adaptive Server upgrade...................................... 70

Post-upgrade tasks........................................................................ 71

Adaptive Server Enterprise

Contents

Run the instmsgs.ebf script..................................................... 71

Restoring functionality in Adaptive Server............................... 72

Reenabling Replication Server................................................ 74

Reenabling auditing................................................................. 77

Shutting down SySAM servers................................................ 78

Upgrading Backup Server, Monitor Server, and XP Server........... 78

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

Upgrading Job Scheduler templates....................................... 80

Upgrading high availability............................................................. 84

Migrating from 32-bit to 64-bit versions.......................................... 86

Recovering from a failed upgrade.................................................. 88

CHAPTER 6 Troubleshooting SySAM Issues .................................................. 91

Calling Sybase technical support for SySAM-related issues ......... 91

Where to look for SySAM-related errors ........................................ 92

Troubleshooting SySAM ................................................................ 93

SySAM grace mode....................................................................... 98

SySAM grace period ...................................................................... 99

Enabling and changing e-mail notifications.................................... 99

CHAPTER 7 Troubleshooting.......................................................................... 101

Overview...................................................................................... 101

Error log locations ........................................................................ 103

Solutions to common installation problems.................................. 104

Adaptive Server fails to start ................................................. 104

The Installer fails to start ....................................................... 104

Stopping Adaptive Server after a failure................................ 104

Recovering from a failed installation ..................................... 105

If Adaptive Server fails the pre-upgrade eligibility test .......... 106

Recovering from a failed upgrade......................................... 106

Upgrading compiled objects with dbcc upgrade_object............... 109

Finding compiled object errors before production ................. 110

Using dbcc upgrade_object................................................... 113

Using database dumps in upgrades...................................... 116

Determining whether a compiled object has been upgraded 117

CHAPTER 8 Removing Adaptive Server ........................................................ 119

Uninstalling Adaptive Server 15.0.2............................................. 119

Removing an old server............................................................... 120

APPENDIX A Alternative Installation Methods................................................ 123

Installation on consoles (non-GUI mode)..................................... 123

Installation Guide v

Contents

Silent installation.......................................................................... 124

Configuration using resource files................................................ 126

Configuring from a resource file............................................ 126

Resource file variables.......................................................... 128

Running the sybatch utility .................................................... 129

APPENDIX B Upgrading Servers with Replicated Databases........................ 131

Introduction .................................................................................. 131

Suspending transaction processing and replication activities...... 132

Draining the transaction logs for primary databases.................... 133

Draining the RSSD transaction log .............................................. 135

Disabling the secondary truncation point..................................... 136

APPENDIX C Using sybsystemprocs ............................................................... 137

Introduction .................................................................................. 137

Increasing the size of the sybsystemprocs database................... 138

Increasing device and database capacity for system procedures 139

Index ........................................................................................................................................... 143

Adaptive Server Enterprise

About This Book

The Installation Guide for Sybase Adaptive Server Enterprise for 15.0.2 provides:

• An overview of the Sybase

• Instructions for installing and upgrading Adaptive Server, and

• Instructions for installing optional Adaptive Server functio nality,

• Instructions on how to install Adaptive Server with SySAM 2.0.

Adaptive Server® Enterprise installation

infrastructure

installing Backup Server™, Monitor Server, XP Server™, jConnect™ for JDBC™, Java utilities, and client products, including the Adaptive Server plug-in for Sybase Central™

such as auditing, and sample databases, and localization information

Audience

How to use this book

This guide is written for Sybase System Administrators and other qualified personnel who are familiar with their system’s environment, networks, disk resources, and media devices.

This book contains the following chapters:

• Chapter 1, “Overview,” provides an overview of Adaptive Server, and describes the Enterprise Edition, Small Business Editi on, Developer Edition, and Express Edition (on Linux) of Adaptive Server. It also provides product descriptions and directory layout information.

• Chapter 2, “Installing Adaptive Server,” describes pre-installation procedures, SySAM related tasks, and how to install server components.

• Chapter 3, “Post-Installation Tasks,” describes how to verify that servers are running, connect to servers, set passwords, install SAMreport, and install sample databases.

• Chapter 4, “Installing Sybase PC-Client Products,” describes how to install Adaptive Server client products like the Adaptive Server plug-in to Sybase Central.

Installation Guide vii

• Chapter 5, “Upgrading Adaptive Server,” describes how to upgrade an existing Adaptive Server to the current version.

• Chapter 6, “Troubleshooting SySAM Issues,” provides info rmation about and solutions to SySAM related errors.

• Chapter 7, “Troubleshooting,” provides installation error messages and possible solutions to installation problems.

• Chapter 8, “Removing Adaptive Server,” describes how to uninstall Adaptive Server.

• Appendix A, “Alternative Installation Methods,” describes how to ins tall Adaptive Server in noninteractive mode.

• Appendix B, “Upgrading Servers with Replicated D at abases,” describes how to upgrade servers with replicated databases.

• Appendix C, “Using sybsystemprocs,” describes how to use the

sybsystemprocs database.

Product licensing with SySAM 2.0

• For information about uninstalling Adaptive Server, see Chapter 8, “Removing Adaptive Server.”

Warning! Before you run Adaptive Server version 15.0 on 32-bit Windows

platforms, you must eith er:

• Install Microsoft Visual C++ 6.0, or

• Download a patch called vcredist.exe referred to in Microsoft Knowledge Base article # 259403. Find the patch at the

http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com: 80/support/kb/articles/Q259/4/03.ASP&NoWebContent=1

Product licensing with SySAM 2.0

Starting with Adaptive Server Enterprise version 15.0, the Sybase Software Asset Management System (S ySAM) implementation has changed. W ith these changes, SySAM configuration is no longer optional, and requi res some changes in the Adaptive Server installation and configuration process. Review the updated SySAM implementati on and plan your SySAM d eployment before you install Adaptive Server Enterprise.

Microsoft Web site at

For information about how to install and configure SySAM 2.0 enabled products, see the following places for information:

• For simple installations, see the Installation Guide (this document,) for instructions. No additional information should be necessary.

• For more complex installations, and for general information about SySAM 2.0, see the Sybase Software Asset Management User’s Guide.

Warning! SySAM 2.0 enabled products work for an initial period without a

license. If you do not install a valid license for your co nfiguration in this gr ace period, the product ceases to function. For general information about SySAM

2.0, see the Sybase Software Asset Management User’s Guide.

Before you install Adap tive Server with SySA M 2.0, you must decide whet her you are using a served or an unserved license. For information on how to determine which is appropriate for your site, see Chapter 2, “Choosing a License Model” in the Sybase Software Asset Management User’s Guide.

2 Adaptive Server Enterprise

The Adaptive Server Installation Guide (this document) has the following information about SySAM-related tasks:

• Installation instruct ions are described in “Installing components with the

Installer in GUI mode” on page 27.

• If you have problems, see Chapter 6, “Troubleshooting SySAM Issues.”

• For information abou t using SySAM for asset management, see “The

SAMreport” on page 43.

Product components

Adaptive Server Enterprise is based on the client/server model. Each Adaptive Server user is associated with a client process that communicates with a server process via a network interface called the Tabular Data Stream™ (TDS) protocol. The client process may execute on one machine and communicate with a database server on the same or a different machine.

CHAPTER 1 Overview

Adaptive Server Enterprise

Adaptive Server runs as an application on top of an operating system and depends solely on the services exported by the operating system to function. Adaptive Server uses operating system services for process creation and manipulation, device and file processing, and inter-process communication. The hardware that the operating system runs on is completely transparent to Adaptive Server which sees only the operating system’s user interfaces.

Adaptive Server has a virtual server architecture and has one or more operating system processes (engines) that service client requests. You can configure multiple processes to enhance performance on multiprocessor systems. A process is divided into two components, a DBMS component and a kernel component. The kernel component manages multiple tasks, while the DBMS component performs the database functions on behalf of the current task. Each client is associated with a task, and there are several tasks that perform specific services; for example, writing buffers or audit data to d isk, and communicating with the network. The DBMS component of Adaptive Server manages the processing of SQL statements, accesses data in a database, and manages different types of server resources.

Installation Guide Evaluation Version 3

Product components

All server processes share two distinct areas of shared memory: a kernel area and a DBMS area. The kernel area contains data structures that relate to task management and operating system services, while the DBMS component contains caches of database buffers, object descriptors, and other resources used by the DBMS component of the server process.

The kernel layer of the server abstracts the operating system-specific functions so that the rest of the server has a consistent view of those functions regardless of the underlying operating system. Essentially, the kernel provides low-level functions, such as task and engine management, network and disk I/O, and low-level memory management to the rest of the server. The part of the server that processes a TDS request (the TDS engine) is part of the kernel layer.

The heart of Adaptive Server is the SQL/DBMS engine. The SQL/DBMS engine processes data manipulation statements (DML), utility commands, which are generally data definition statements (DDL) and administrative functions, and performs stor ed pro cedu re execu tio ns. The DBMS eng ine us es the services provided by the resource manager rou tines and the access methods routines.

A resource manager is a set of subroutines that manage a particular system resource, such as pages, buffers, or a particular dat a structure. The DBMS engine uses these subroutines to manipulate various system resources. There are also a number of tasks within the server that per form specialized tasks. The resource managers, as well as these specialized tasks, rely on the kernel layer for low-level functions.

Access methods have two primary functions: the management of data on disk and manipulation of databas e cons tructs, such as tables and rows. Actu al di sk I/O routines are provided to the access methods routines by the kernel disk I/O routines.

Backup Server

Like Adaptive Server, Backup Server is also an operating system process. Backup Server is dedicated to backing up and res t oring Adaptive Server files . Clients do not communicate directly with Backup Server. Only Adaptive Server communicates with Backup Server.

4 Adaptive Server Enterprise

Stored procedures

The client

CHAPTER 1 Overview

Stored procedures encapsulate a series of SQL commands that the server can execute as a single command. System stored procedures (SSPs) are created when the server is installed.

A client uses functions provided by the CT-Library (CT-Lib) and Common Library (CS-Lib) APIs to establish a conn ection to the server, submit requests to the server, and receive results back from the server.

Figure 1-1: Adaptive Server system model

Application code

Open Client

Request

Response

Network interface

Data tables

procedures

Adaptive Server editions

Adaptive Server is available in the following editions:

• Enterprise Edition – has no limit on scalability and can run all available

options that can be purchased separately.

sql compiler

RPC

SQL executive

Access Manager

Indexes

Transaction

System

Shared memory

Data cache

Procedure cache

log

Installation Guide Evaluation Version 5

Adaptive Server editions

• Small Business Edition – has some limit on scalability, and can run a limited set of options that can be purchased separately.

• Developer Edition – has a limit on scalability and includes many of the options.

Sybase also offers a series of options that you must purchase separately. Some of these options are intended for an enterprise-level site, and are not available in the Small Business Edition.

Adaptive Server editions and optional features are unlocked by providing SySAM licenses. For complete details, see the Sybase Software Asset Management User’s Guide.

Use the your are running. Enter:

sp_lmconfig 'edition' go

Adaptive Server returns value of EE, SE, DE or XE based on the edition it is running. See the Refer ence Manual for more i nformation about the command.

Enterprise Edition

The Enterprise Edition (EE) includes a full-featured Adaptive Server. In addition to the base server, you can purchase options, including High A vailability. Your licensi ng agreement describes the features licen sed for your site.

Small Business Edition

The Small Business Edition (SE) includes features that meet the needs of small businesses. This edition of Adaptive Server includes most of the functionality of the Enterprise Edition, and allows for the following Adaptive Server configuration:

sp_lmconfig command to determine which edition of Adaptive Server

sp_lmconfig

• Number of engines – maximum of 4.

• Number of connections – maximum of 256.

6 Adaptive Server Enterprise

CHAPTER 1 Overview

Developer Edition

The Developer Edition (DE) is a competitively-priced version of Adaptive Server that developers can use to create applications in their development environment. The Developer Edition includes a full set of Adaptive Server Enterprise features and options (that is, DTM, High Availability, and so on), and allows for the following configuration:

• Number of engines – 1.

• Number of connections – 25.

Adaptive Server specifications

Table 1-1 provides system specifications for Adaptive Server on HP-UX.

Table 1-1: Adaptive Server specifications for HP-UX 64-bit PA RISC processor

Hardware and memory

Processor 64-bit Minimum RAM fo r A dapt ive Serve r 90MB 45,056 2K pages Number of shared memory segments 1 to 2 One segment for first GB; a second segment for

next .75+ GB

Memory per user connection Approximately 190K With default stack size, packet size, and user log

cache size

Default user stack size 85K Minimum 35K

Table 1-2 provides system specifications for Adaptive Server on Windows.

Table 1-2: Adaptive Server specifications on Windows

Hardware and memory

Minimum RAM required for Adaptive Server

Minimum RAM per additional user 63K With default stack size, packet size, and user log cache size. This

Default memory per additional user • 402K – with Java enabled

Default user stack size • 32-bit platforms – 45K

Installation Guide Evaluation Version 7

48MB 21,504 2K pages

value depends on the connection needs. See the System Administration Guide for informatio n about con figuring mem ory.

• 100K – with Java disabled

• 64-bit platfor ms – 84K

Product descriptions and directory layout

Note For more information about Adaptive Server specifications see Chapter

1, “Introdu ction” in th e Configuration Guide for your platform.

Product descriptions and directory layout

The Adaptive Server installation installs a wide array of software products into the SYBASE directory. Table 1-3 provides a brief description of the server products installed, and the top-level directory structure.

Note Starting with ASE 15.0.2, the Enhanced Full-Text Search (EFTS)

optional product will be not be shipped with ASE. It is now shipped separately as a stand alone product. Please contact customer serv ice for more information.

Table 1-3: Product description

Product Description

Adaptive Server and Historical Server

Installed into the ASE-15_0 directory.

• Adaptive Server – the database server.

• Backup Server – an Open Server-based application that manages all dat abase backup (dump) and restore (load) operati ons.

• Monitor Server – an Open Server-based application that obtains performance information on Adaptive Server an d make s that in formatio n ava ilable to Monito r Server client applications.

• XP Server– an Open Server appli cation that manages and exe c utes extended stored procedures (ESPs) from within Adaptive Server.

• Job Scheduler – provides a job scheduler for Adaptive Server. Job Scheduler components are located in their own directory at ASE-15_0/jobscheduler/.

8 Adaptive Server Enterprise

CHAPTER 1 Overview

Product Description

Software Developer Kit (SDK)

shared – on UNIX

platforms Shared – on Windows

platforms and shared executables and libraries used by various components.

Adaptive Server Plug-in Installed into ASEP directory. This plug-in contains the management software for

Language Modules Installed into the $SYBASE/$SYBASE_ASE directory . Provides system messages and

Character Sets Installed into the charsets directory. Provides character sets available for use with

Collation Sequences Installed into the collate directory. Provides the collation sequences available for use

ASE Replicator Installed into the RPL-15_0 directory. Provides lightweight replication for those

Sybase Software Asset Management (SySAM)

Web Services Installed into the WS-15_0 directory. An optional product that provides access to

Agent Management Console

Installed into the OCS-15_0 directory.

• Open Client (Ctlib, dblib)

•ESQL/C

• Monitor Client Library

• ESQL/COBOL

• XA Installed into the DataAccess directory:

• ODBC (Windows and Linux only ) – a driver used to connect to Adaptive Server from ODBC bas e d ap plications.

• OLEDB (Windows only) – a provider used to connect to Adaptive Server from OLE DB-based applications.

• ADO.NET (Windows only) – a provider used to connect to Adaptive Server from .NET based applications.

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

• Sybase Central – Sybase Central is a Java-based framework used by the system management tools. In earlier versions, this component was placed into a top-level directory rather than in a shared directory.

• JRE – the Java Runtime Environment (JRE) is a runtime Java virtual machine used to execute Java-based programs such as Sybase Central.

managing Sybase servers and its associa ted servers.

date/time formats.

Adaptive Server.

with Adaptive Server.

companies who do not need a full-featured replication product suc h as Sybase Replication Server.

Installed into the SYSAM-2_0 directory. Provides asset management of Adaptive Servers and optio na l fea t u r es.

Adaptive Server using HTTP/SOAP and WSDL. This is a Sybase Central plug-in that manages the Unified Agent. It is installed into

the AMCP directory.

Installation Guide Evaluation Version 9

Product descriptions and directory layout

Product Description

Interactive SQL Interactive SQL is a GUI tool that allows yo u to execute SQL statements, build

scripts, and display data from Adaptive Server. It is installed into the DBISQL directory.

Unified Agent Unified Agent is a management framework that provides runtime services to

manage, monitor, and control distributed Sybase resources. Agents plug into the framework and provide the ability to m anage specifi c components. It is insta lled into the new UA directory $SYBASE/UAF-2_0.

jutils-2_0 A collection of Adaptive Server utility programs including:

jisql – a JDBC-based GUI isql tool.

•

ribo – a tool to trace TDS traffic between client program and Adaptive Server.

•

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

(JDBC) driver for Adaptive Server.

Sybase support for ADO.NET, OLE DB, and ODBC

Adaptive Server version 15.0.2 contained new ODBC and OLE DB drivers developed by Sybase. The t hird-party rebranded OD BC and OLE DB Driver Kits included with previous versions are no longer shipped.

The retired ODBC Driver Kit was installed in %SYBASE%\ODBC, and registered with the ODBC Driver Manager as “Sybase ASE ODBC Driver”. The new ASE ODBC Driver by Sybase is installed in %SYBASE%\DataAccess\ODBC, and registered as “Adaptive Server Enterprise”. The version shipping with Adaptive Server and SDK 15.0 is version 15.0.0.50.

The retired OLE DB Driver Kit was installed in %SYBASE%\OLEDB, and used the provider short name of “Sybase.ASEOLEDBProvider” and the long name of “Sybase ASE OLE DB Provider”. The new ASE OLE DB Pro vider by Sybase is installed in %SYBASE%\DataAccess\OLEDB, and uses provider short name “ASEOLEDB”. The version shipping with SDK 15.0 is version

15.0.0.51. Sybase recommends that you start y our mig ration pro cess the new ODB C and

OLE DB drivers as soon as possible. New features introduced in Adaptive Server 15.0 are supported only by the new drivers.

See “New Features for OpenServer 15.0 and SDK 15.0 for Windows, Linux and UNIX”, for instructions on migrating to the new drivers.

10 Adaptive Server Enterprise

CHAPTER 1 Overview

Installing ODBC driver from ASE 15.x or SDK 15.x on top of an IQ 12.6 installation might produce a warning. You can ignore this warning. The ODBC driver will be functional at the end of the install.

PC-Client product descriptions and directory layout

The following products are installed as Ad aptive Server PC-Client products. In addition to these products, there are several separately installed products listed in the following sections.

Table 1-4: Products and platforms

Product Description

Software Developer Kit (SDK)

Windows Cluster Server Admin utilities

Shared-executables and

libraries used by various components

Adaptive Server Plug-in Installed into ASEP directory. This plug-in contains the management software for

Installed into the OCS-15_0 directory.

• Open Client ( Ctlib, dblib)

•ESQL/C

• Monitor Client Libra ry

• ESQL/COBOL

• XA

Installed into the DataAccess directory:

• ODBC (W in dow s and Li nu x only ) – a drive r use d t o con nect to Ad apt ive Se rv er from ODBC bas e d ap plications.

• OLEDB (W in do w s only) – a provider used to conn ec t to A daptive Server from OLE DB-based applications.

• ADO.NET (Windows only) – a provider used to connect to Adaptive Server from .NET based applications.

Windows Cluster Administrator is a GUI tool for managing Microsoft Cluster Server (MSCS). It can be used to create, modify and displays the information of groups, resources and the cluster itself. There is also an alternative command-line tool called Cluster.exe for cluster administration.

The shared directory contains components and libraries that are shared by several other compone nts . In earlier versio ns , this directory was na me d shared-1_0.

• Sybase Central – Sybase Central is a Java-based framework used by the system management tools. In earlier versions, this compo nent was placed into a top-level directory rather than in a shared directory.

• JRE – The Java Runtime Environment (JRE) is a runtime Java virtual machine used to execute Java-based pro grams such as Sybase Central.

managing Adaptive Server and its associated servers.

Installation Guide Evaluation Version 11

PC-Client product descriptions and directory layout

Product Description

Language Modules Installed into the locales directory. Provides system messages and date/tim e form ats. Character Sets Installed into the charsets directory. Provides character sets available for use with

Adaptive Server.

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

(JDBC) driver for Adaptive Server.

Agent Management Console

Interactive SQL Interactive SQL is a GUI tool that allows you to execute SQL statements, buil d

Unified Agent Unified Agent is a management fra mework that provides runtime services to manage,

jutils-2_0 A collection of Adaptive Server utility programs including:

This is a Sybase Central plug-in that manages the Unified Agent. It is installed into the AMCP directory.

scripts, and display data from Adaptive Server. It is installed into the DBISQL directory.

monitor, and control distribu ted Sybase resources. Agents plug into the framewor k and provide the ability to manage specific components. It is installed into the new UA directory %SYBASE%\UAF-2_0.

jisql – a JDBC-based GUI isql tool.

•

ribo – a tool to trace TDS traffic between client program and Adaptive Server.

•

Separately installable PC-Client products

The PC-Client CD also contains the following products, which are separately installable:

• InfoMaker® – a tool for p ersonal data access, man agement, and reporting, used by both developers and end users. InfoMaker allows you to create presentation-quality reports and powerful queries without the complexities of programming. It complements client/server business applications and development tools as well as desktop productivity suites.

• PowerDesigner Physical Architect – a tool for data modeling, including database design, generation, maintenance, reverse engineering, and documentation for database architects.

• PowerTransfer – a plug-in for PowerDesigner™ that transfers table data from any supported database to Adaptive Server.

• SAMreport – a Macrovision report generator that helps you monitor the usage of applications that use FLEXnet licensing.

12 Adaptive Server Enterprise

CHAPTER 2

Overview

Installing Adaptive Server

This chapter provides instructions for installing a new Adaptive Server, Backup Server, and Monitor Server.

Topic Page

Overview 13 System requirements 14 Pre-installation tasks for SySAM 15 Pre-installation tasks for Adaptive Server 23 Installing server components 27 Installing version 15.0.2 over an existing 15.x Adaptive Server 36

The installation process copies all of the files from the installation media to the hard drive and then configures a base Adaptive Server. At the end of the installation, the Adaptive Server and associated software is ready to be customized for the user’ s environment – for example, creating devices, databases and tables, and loading data.

The basic process for installing Adaptive Server is: 1 Perform pre-installation tasks related to license administration as

described in “Pre-installation tasks for SySAM” on page 15.

Warning! SySAM 2.0 enabled products work for an initial period

without a license. If you do not install a valid license for your configuration in this grace period, the product ceases to function. For general information about SySAM 2.0, see the Sybase Softwar e Asset Management User’s Guide.

2 Perform the pre-installation tasks as described in “Pre-installation

tasks for Adaptive Server” on page 23.

Installation Guide 13

System requirements

3 Perf orm the inst allati on using any of th e methods desc ribed i n

“Installation methods” on page 27.

4 Perform the post-installation tasks as described in Chapter 3, “Post-

Installation Tasks.”

System requirements

Check to make sure your system has the required version-level, RAM, and network-protocol requiremen ts for Adaptive Server. See the release bulletin for your platform the latest information about required system patches.

Table 2-1: Server system requirements

Hardware Operating system Supported protocols

HP9000/700, or HP9000/800, or 64-bit HP9000 D, K, V Series, (The PA8000 chip is required.)

HP HP-UX 11iV2 SPX or TCP HPIA64, Intel Architecture-64 Itanium HPUX B.11.23 SPX or TCP

HP-UX 11.i running 64-bit runtime kernel

SPX or TCP

Table 2-2: Disk space requirements for HP-UX 64-bit PA RISC platforms

Product Disk space requirements

Adaptive Server typical install 700MB Default databases created during install 150MB Total 1040MB

Table 2-3: Disk space requirements for HP-UX 64-bit Itanium platform

Product Disk space requirements

Adaptive Server typical install 700MB Default databases created during install 150MB Total 1040MB

Table 2-4: Server system requirements

Operating system Hardware Supported protocols

Windows 2000 Pro, Server, Adv.Server and DataCenter Edition SP4 or higher

• Intel Pentium III 600 MHz or higher

• AMD Athlon 1 GHz or higher

•TCP

• IPX/SPX

• Named pipes (not supported for LDAP server connections

14 Adaptive Server Enterprise

CHAPTER 2 Installing Adaptive Server

Operating system Hardware Supported protocols

Windows XP Professional SP1 or higher

Windows 2003 Standard, Enterprise, and Datacenter Editions, SP1

Windows x64

• Intel Pentium III 600 MHz or higher

• AMD Athlon 1 GHz or higher

• Intel Xeon EM64T

•AMD Opteron

Table 2-5: Disk space requirements for Windows platforms

Product Disk space requiremen ts

Adaptive Server typical install 3 60MB Default databa ses cr eated d uring install 153MB (for 2K page size Adapt ive Se rver) Total 1063MB

•TCP

• IPX/SPX

• Named pipes (not supp or ted for LDAP server connections

•TCP

• IPX/SPX

• Named pipes (not supp or ted for LDAP server connections

Pre-installation tasks for SySAM

Before you install Adaptive Server, you should: 1 Decide the SySAM license model you will use. The choices are:

• The unserved license model – gets licenses directly from the license file. If you are using an uns erved l icense, you shoul d si mply sav e the license to the machine on which you have installed Adaptive Server.

• The served license model – uses a license server to manage the allocation of your licenses to multiple machines. See the following for more information.

For information about served and unserved licenses, and which model is best suited for your environment, see Chapter 2, “Choosing a License Model” in the Sybase Software Asset Management User’s Guide.

2 If you plan to use a served license, you need a license server. Decide

whether it will be an existing license server or a new license server. The license server need not be on the same machine or running on the same operating system and architecture.

• If you are going to use an exist ing l icens e s erver, you must know the server host name and po rt number.

Installation Guide 15

Pre-installation tasks for SySAM

• For information about creating a new license server before installing

Note There can be only one instance of a SySAM license server running

on a given machine. If you want to setup a SySAM 2.0 license server on a machine that is already running a SySAM 1.0 license server, the old license server must be migrated to 2. 0. A migrated license server can se rve licenses for both SySAM 1.0 and SySAM 2.0 enabled products.

Please see Appedix F of the Sybase Software Asset Management User's Guide for instructions on migrating a license server.

For information about choosing a license server host, see the “Choosing a license server host” section in Chapter 2, “Choosing a License Model” of the Sybase Software Asset Management User’s Guide.

For information about license server administration, see Chapter 4, “License Server Administration” in the Sybase Software Asset

Management User’s Guide.

Adaptive Server, see “Installing a new license server” on page 21.

Accessing SPDC

3 Sybase recommends that you get your license files from the

Product Download Center (SPDC) at https://sybase.subscribenet.com

Sybase

before you begin installing Adaptive Server. For information about accessing SPDC, see “Accessing SPDC” on page 16, and for information about generating your licenses at SPDC, see “Generating licenses at SPDC” on page 18.

Once you have purchased a Sybase product, typically you are expected to download the product and generate its licenses from the online Web portal, the Sybase Product Download Center (SPDC.)

To access SPDC when you have purchased Sybase products from Sybase:

16 Adaptive Server Enterprise

1 Once you have ordered a Sybase product you receive a welcome e-mail

2 Click on the URL, and when pro mpted, enter the designated user name and

Getting your host ID

To get your host ID: 1 Change to %SYBASE%\SYSAM-2_0\bin. Where %SYBASE% is the

2Enter:

CHAPTER 2 Installing Adaptive Server

that contains a URL to the SPDC site, as well as a user name and pas sword.

Note If you have purchased your Sybase software from a Sybase reseller,

you will receive a web key rather than an e-mail.

password. Your login is typically your e-mail address. If you have forgotten your p assword, use t he password find er on the SPDC l ogin page.

Sybase installation directory.

./lmutil lmhostid

lmutil lmhostid

Note On some platforms, the ho st ID is derived f rom the ne twork adapter

address. If your machine has multiple network adapters,

lmhostid

returns one host ID for each network adap ter. The output may

lmutil

look similar to:

The FLEXlm host ID of this machine is ""0013023c8251 0015c507ea90"" Only use ONE from the list of hostids.

Choose one of these host IDs. Sybase recommends using the value associated with the primary wired Ethernet adapter. Do not use values associated with internal loop back adapters. If you cannot determine which host ID to use from the

lmutil lmhostid output, use the native

operating system command to get additional details to help make the determination. See to the SPDC FAQ titled ,“What’s my Host ID,” or “Appendix A” of the FLEXnet Licensing End User Guide for the exact commands for your platform.

3 Save the host ID so you can use it later at SPDC. Your host ID is

platform-specific, but may be similar to:

Installation Guide 17

Pre-installation tasks for SySAM

778DA450 or #2005771344

ID_STRING=9c766319-db72-d411-af62-0060b05e4c05 on HP-UX

Itanium 64-bit.

00B0A9DF9A32 on Windows platforms.

Generating licenses at SPDC

This section provides information about how to generate a license for a served and an unserved license model. To generate your license, regardless of license model:

1 At the Welcome screen at SPDC, you can view all of the product families

to which you have access. Select the product family that contains the product for which you wish to generate a license.

2 A list of available Sybase products displays. Click the product with the

appropriate edition and version. Make sure you select the product for the operating system you are using.

3 The license agreement displays. You must agree to the terms and

conditions in the license in order to generate a license. To do so, click I Agree.

Note The license agreement only displays the first time you attempt to

download a product. Once you have agreed to the license, you will not encounter the license agreement for all subsequent downloads of that product.

on HP-UX PA-RISC platforms, or

4 At the product download page, click the License Keys link. 5 The License Information page displays. Select the license you wish to

generate. When you are selecting the license you wish to generate, consider:

• The license type for the license you wish to generate. For more

information about license types, see the “License types” in Chapter 3 “Getting and Using your License” of the Sybase Software Ass et Management User’s Guide.

• If you are unsure what you have licensed, your company’s purchase

order should have the product name, edition, and license type.

18 Adaptive Server Enterprise

6 Once you’ ve determined the license you wish to generate, select it via the

Generate radio button on the left side of the screen. Scroll to the bottom of the page, and click Select to Generate.

7 Step one of the SySAM license generation wizard asks you to choose

between a served license and an unserved license. If you choose a served license, continue with the steps in “Generating a served license” on page 19, and if you choose an unserved license, continue with the steps in “Generating an unserved license” on page 20.

Note Some Sybase Products or specific license types do not give you a

choice of license model to use, and therefore do not display this page. If this is the case, proceed with the SySAM license generation wizard to generate your license.

Generating a served license

To generate a served license: 1 Select Served License and click Next. 2 Indicate the quantity of licenses you wish to generate and click Next.

CHAPTER 2 Installing Adaptive Server

3 Enter the License Server Host ID and optionally the host name and port

number. a Sybase recommends that you provide the host name here to ease

future license administration.

b A po rt number is not required unless you are using a 3-node redundant

cluster. A valid number is any unused port number between 0 and

64000. On UNIX, choose a port greater than 1024, since those less than 1024 are privileged port numbers. If no TCP/IP port number is specified, one of the default ports in the range of 27000 and 27009 is used.

c If you want to generate a license f or a 3-n ode redundant cluster, then

you must specify the hos t ID, host name, and p ort number for the thr ee nodes of the cluster. The port number is not optional for this configuration and should be outside of the 27000 to 27009 range.

Installation Guide 19

Pre-installation tasks for SySAM

d You should have gotten your server host ID before you began the

4 Click Generate. 5 Once you have generated the license, you can:

a Download the license file by clicking the Download License File

b Prin t a paper copy of the license b y clicking th e Print Fr iendly butt on. c Return to the license information page to generate additional licenses.

6 Once you have generated all the licenses you need, save them to the

licenses directory in your license server installation.

Note Y ou must save your licen se files with a .lic extension, or SySAM 2.0

will not recognize them.

Sybase recommends that you setup the license server and required licenses before you install your SySAM 2.0 enabled Sybase product.

process of generating y our licenses. For information about how to get the host ID, see “Getting your host ID” on page 17. You have the option to specify redundant server information if you choose to configure your servers for three-server redundancy.

button.

Generating an unserved license

To generate an unserved license: 1 Select Un-served License and click Next. 2 Select the number of machines you want to license and click Next . Y ou can

generate licenses for a maximum of ten machines at a time.

3 Enter th e host ID, and optionally the host name for each machine for which

you want to generate a license. You should have determined the host ID before you began to generate your licenses. For information on getting your host ID and host name, see “Getting your host ID” on page 17.

For some license types, you are asked to enter the number of CPUs or licenses for the machine where this license will be used.

4 Click Generate. 5 Once you have generated the license, you can:

20 Adaptive Server Enterprise

• Download the license file by clicking the Download License File button.

• Print a paper copy of the license by cl icking the Pri nt Friendly button.

• Return to the license information page to generate add itional licenses.

6 Once you have generated all the licenses you need, save them to the

specific location required by your product.

Note Y ou must save your license files with a .lic extension, or SySAM 2.0

does not recognize them.

Installing a new license server

Note If you have selected a served license model, you must install a license

server.

Recommended operating system patches are:

CHAPTER 2 Installing Adaptive Server

For HP-UX 11.11:

• PHCO_25841

• PHKL_26269

• PHKL_25760 Perform the following steps to install a new license server. 1 Mount the CD by running the following command:

mount -F cdfs -o ro,rr <CDROM device> /cdrom

2 Install the license server.

a Insert the CD into the CD drive. The Installer should start

automatically. If it does not, start the setup program manually by selecting Start | Run. Browse to setup.exe.

b Launc h the Sybas e install er pro gram by ente ring :

setup

c The Welcome Window displays. Click Next. d Accept the license agreement.

Installation Guide 21

Pre-installation tasks for SySAM

e Enter or select the destination directory. f Select the Custom installation. g Select only “SySAM License Server” for installation. h Deselect other components, to install the license server only. i Click OK for the installer to install the license server.

Note The license server cannot be started until there is at least one valid

served license installed in the licenses directory.

3 Get the host ID for the machine on which you will be running the license

server. For in format ion on h ow to gener ate the h ost ID, s ee “Getting your host ID” on page 17.

4 Go to the

https://sybase.subscribenet.com

Sybase Product Download Center (SPDC) at

5 Generate the licens es for the produ cts you want to install. For instructions

on generating your licenses, see “Generating licenses at SPDC” on page

18.

6 From command prompt navigate to installed directory Source/Execute to

setup the environment variables.

•

ASE150.bat

7 Copy the license file in the %SYBASE%\%SYBASE_SYSAM%\licenses

directory on the network license server machine.

8 Refresh or restart the license server:

aChange to:

%SYBASE%\%SYBASE_SYSAM%\bin

b If the license server is not already started, start it, by entering:

sysam start

If the license server is already started, use the reread command to make the license server read the new license files:

sysam reread

9 Validate that the license daemon is running by entering:

sysam status

You can expect to see output for a running server that is similar to:

22 Adaptive Server Enterprise

CHAPTER 2 Installing Adaptive Server

> sysam start

Starting the SYSAM service The SYSAM service is starting. The SYSAM service was started successfully.

License server status: 27000@mysysamserver License file(s) on keyserver: /opt/sybase/SYSAM_0/licenses/mysysamserver_60302031

5.lic

For more information, see Chapter 6, “Troubleshooting SySAM Issues.”

Pre-installation tasks for Adaptive Server

Before installing Adaptive Server: 1 Read the release bulletins for the latest information on the products

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

2 Install operating system patches, if required.

Recommended operating system patches are: For HP-UX 11.11:

• PHCO_25841

• PHKL_26269

• PHKL_25760

3 If you are having trouble starting the installer, make sure you have the

required operating system patches for the Java Runtime Environmen t (JRE) version 1.4.2.

Information about the required operating system patches is available from the

Sun Java Web site at http://java.sun.com.

Information about the required operating system patches is available from the

HP Java Web site at http://www.hp.com/java.

Installation Guide 23

Pre-installation tasks for Adaptive Server

4 Revie w t he SySA M pro cedur es an d pl an you r cl ient / server configuration

using the configuration guide for your platform.

5 Create a “syb ase” account on your system to perfor m all installation tasks.

The “sybase” user must have perm iss i on p ri vil eges fro m the t op (or r oot ) of the disk partition or operating system directory down to the specific physical device or operating system file.

6 Log in to the machine as the “sybase” user.

Maintain consistent ownership and privileges for all files and directories. A single user—the Sybase System Administrator with read, write, and execute permissions—should perform all installation, upgrade, and setup tasks.

7 Know what product edition you are installing. The options are:

• Enterprise Edition

• Small Business Edition

• Developers Edition

• Express Edition If you are installing the Small Business or Enterprise Edition, you must

know the license type under which Adaptive Server was licensed. For more inforamtion about license types, see the “License types” in Chapter 3 “Getting and Using your License” of the Sybase Software Asset Management User’s Guide.

8 Sybase recommends that you specify license types at the time of

installation. However, you may choose to specify the product edition and license type later using

sp_lmconfig. For information on sp_lmconfig, see

Reference Manual:Procedures.

9 You must decide if you want licensing events to trigger e-mail alerts and

the severity of the events that will generate e-mail messages. If you choose to have e-mail no tification of license event s, you must know

the:

• SMTP server host name

• Port number for an SMTP server

• E-mail return address

• Recipients of the notifications

24 Adaptive Server Enterprise

CHAPTER 2 Installing Adaptive Server

• Severity level of an event that will trigger mail. Your choices are:

• None

• Informational

•Warning

• Error

10 Verify that the operating system meets the version-level, RAM, and

network protocol requirements for your platform.

11 Adjust the operating system shared memory parameter.

For Adaptive Server to run, the operating system must be configured to allow allocation of a shared memory segment at least as large as the Adaptive Server

total logical memory configuration parameter.

The default

total logical memory parameter for HP is 32,768 2K pages

(64MB) on the 32- bit op erat i ng sy st em, and 45,056 2K pag es (88MB) on the 64-bit operating system. To adjust the shared memory value of the operating system, use the System Administration Manager (SAM).

After you install Adaptive Server, you can change any configuration parameter, procedur e cache, and data cache size. This may require that you increase the value of the configuration parameter

max memory.

12 13

project.max-shm-memory=(priv, 17179869184, deny)

14 Adjust shared memory segments.

Depending on the number and ty pes of devices you use 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.

15 Adjust shared memory segments.

Depending on the number and ty pes of devices you use 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.

Installation Guide 25

Pre-installation tasks for Adaptive Server

Adaptive Server may allocate shared memory segments after start-up if any reconfiguration t hrough may need to account for these additional segments. Allocate the maximum memory you will make available to Adaptive Server, by using the

max shared memory

Administration Guide for more information. 16 17 To optimize asynchronous I/O and to prevent the paging of shared

memory, you must grant MLOCK permissions before you install Adaptive

Server.

To grant MLOCK permissions to a group, enter:

/etc/privgrp add mlock <group name>

or:

/etc/setprivgrp <group name> MLOCK

18 If after adjusting the SHMMAX parameter the server fails to reboot you may

also need to increase the value of another Kernel parameter, SHMALL, which is the maximum amount of shared m emory that can be allocated. Its value is in the file /proc/sys/kernel/shmall. This task requires root permission.

sp_configure requires additional memory. Y ou

allocate

configuration parameter. See the System

26 Adaptive Server Enterprise

Installing server components

Follow the instructions in this section to install Adaptive Server, Backup

Server, and Monitor Server.

Note Adaptive Server Enterprise 15.0.2 includes new major versions of

Adaptive Server and many of t h e su ppo rt ing components. Installing Adap tiv e

Server version 15.0.2 into t he same directory with exist ing products should not

impact the existing products. However, installing other products on top of

Adaptive Server version 15.0.2 will likely result in one or more products not

working correctly.

Sybase strongly recom mend s that A dap t ive Server version 15.0.2 be ins tal l ed

into its own directory if possible. Wh ere this is not practical and other prod ucts

must be installed into the same directory, Adaptive Server version 15.0.2

should be installed last.

Installation methods

The following instructions are for using the Installer in GUI mode. You can

also perform the installation in a non-GUI (text-based) mode or a completely

silent installation with no interaction. Or, you can perform the installation, then

configure Adaptive Server separately us ing either the GUI-based configuration

tools or silently with the use of a resource file. For information on alternate

methods of installation see Appendix A, “Alternative Installation Methods.”

CHAPTER 2 Installing Adaptive Server

Users not already familiar with Adaptive Server should install using the

GUI-based Installer. Select a typical install, and accept the default

configuration.

Installing components with the Installer in GUI mode

Note Sybase recommends installing products as a sybase user. Root

permissions are not required to run the installer.

The Installer creates the target directory (if necessary) an d installs the selected

components into that directory.

Installation Guide 27

Installing server components

At the end of the instal lati on, you can veri fy the pr oduct install ation. You may need to perform additional co nfi gu rati on pro cedures before you can use some products.

Note As part of the installation, the Installer sets most of the environment

variables in %SYBASE%\ASE150.bat. If you need to run any Sybase Application from command prompt you must execute this file first.

To install server components: 1 Stop and shut down all programs before running the installer. 2 Insert the CD into the CD drive, or download and ex tract the Adaptive

Server install image from the Sybase Product Download Center (SPDC).

Launch the Adaptive Server Installer.

Enter:

mount -F cdfs -o ro,rr <CDROM device> /cdrom

Insert the CD into the CD drive. The Installer should start automatically.

If it does not, start the setup program manually by selecting Start | Run.

Browse to setup.exe. 3 The Welcome screen displays. Click Next. 4 When the license selection window displays, select the most appropriate

location from the dro p-d own list, read the license terms, and then click “I

agree...” to proceed. Click Next.

Not every country is listed in the drop-down list. If the country you are

located in is not listed, select the most appropriate area. 5 The Install directory window allows you to select a directory for the

installation by clicking Browse. Click Next to accept the default of:

c:\sybase

You can also enter a directory for installation. 6 If user has Sybase Central previously installed to a directory other than the

one specified in step 5 the following pop-up dialogue will be shown:

The install program detected a previously installed copy of Sybase Central 4.3 in the following directory. It is recommended that the Sybase Central updates and Adaptive Server plugins be installed in this location rather than. Do you want to continue

28 Adaptive Server Enterprise

CHAPTER 2 Installing Adaptive Server

installing Sybase Central and Adaptive Server plugin in?

If you choose “no” to above question, the followin g pop-up dialogue will be shown

You have chosen to install Sybase Central in a new location. Once the installation is complete you will no longer be able to access plug-ins previously registered. In order to access these plug-ins you will need to manually re-register the previously installed plug-ins. Do you want to continue?

7 You can choose from three types of installations in the Install Type

window:

• Typical

Note Be aware that the Typical install does not install the license

server. If you need to install the license server, select the Custom installation and select your components.

• Full

•Custom

8 If you select Custom, the Products and Features Selection window

displays. Select the products you w ant to ins tall by checki ng the box next to each product name.

Note Some features are dependent on other features; therefore, you cannot

unselect some items without first unselecting others.

After you have made your selection, click Next. Before proceeding to the next window, the Installer verifies the selections, and checks for dependencies and available disk space.

9 The Prod uct Select ion Sum mary wi nd ow di sp lay s the se lectio ns th at you

have made. Verify that you have selected the correct type of installation, and that you

have enough disk space to complete the process. Click Next to proceed. 10 The Install Progress window shows the progress of the installation. 11 The Install Status window displays the result of the installation process.

Click Next to configure the software.

Installation Guide 29

Installing server components

12 The Sybase Software Asset Management License Server screen allows

you to designate where Adaptive Server will find its licenses. Where you choose to store your license depends upon whether you have selected a served or unserved license model.

Note For information about served and unserved licenses, and about

choosing the best license server for your environment, seec Chapter 2, “Choosing a License Model” of the Sybase Software Asset Management User’s Guide.

You must specify whether the licenses will be obtained from a license server.

If you answer Yes, you must know the host name of the m achine where the license manager is running, and the port number if you have used a nondefault port number.

If you answer No, you will be using unserved licenses. You will be reminded to download and install the license file after you have finished the installation.

Note When you download the license file, copy it to the

%SYBASE%\%SYBASE_SYSAM%\licenses directory.

13 The Sybase Software Asset Management Notification screen asks you to

configure your server for e-mail notification. When configuration is enabled, designated users receive information about license management events requiring attention.

Provide the following information:

• SMTP server host name

• SMTP server port number

• E-mail Return Address

• Recipient e-mail addresses

• Message severity that triggers e-mail messages

14 The Product Licenses screen asks you to indicate the edition of Adaptive

Server you are installing. You can choose from:

• Unknown

• Enterprise Edition

30 Adaptive Server Enterprise

CHAPTER 2 Installing Adaptive Server

• Small Business Edition

• Developers Edition

• Express Edition

Note Y ou must select only the Adaptive Server edition for which you have

a license. For more information about troubleshooting license type and

edition problems, see Chapter 6, “Troubleshooting SySAM Issues.”

15 If you are installing Enterprise Edition or Small Business Edition, you

must also enter the License T ype under which Adaptive Server is licensed. 16 The Configure New Servers window asks if you want to configure new

servers, depending upon the products you installed. A Full or Custom

installation allows you to choose to:

• Configure new Adaptive Server

• Configure new Backup Se rver

• Configure new Monitor Server

• Configure new XP Server

• Configure new Job Scheduler

• Enable Self Management

• Configure Web Services

• Configure Unified Agent

Select the servers you want to configure. If you do not want to configure

the new servers at this point, unselect the item and click Next. The Custom

Configure New Server Options window appears. 17 The Custom Configure New Server Options window allows you to select

servers to custom configure. If you do not select any servers in this

window, the Installer configures all the servers using default values.

If you choose the default values, the Installer cho oses everything including

the server name, port number, and master device location. It also installs

Backup Server, Monitor Server, and the XP Server, choosing the name,

port number, and error log.

If you accept the defaults, the server names are:

• Adaptive Server – <host name>

• Backup Server – <host name>_BS

Installation Guide 31

Installing server components

• Monitor Server – <host name>_MS

• XP Server – <host name>_XP

• Job Scheduler Agent – <host name>_JSAGENT If you configure the servers with default values, the Configure Server

Attributes Summary window displays next. If you select to configure the server with custom values, you have the

following choices:

• Custom configure new Adaptive Server

• Custom configure new Backup Server

• Custom configure new Monitor Server

• Custom configure new XP Server

• Custom configure new Job Schedule

• Custom configure Self Management

• Custom configure Web Services

• Custom configure new Unified Agent The Custom Configure Input window displays next.

18 The Custom Configure Input window prompts you for the custom

Adaptive Server configuration information.

• Server name

• Port number

• Page size

• Error log – name of error log file and the path where it should be

located.

• Master device – name of master device and the path where it should

be located.

• Master device size (MB). The minimum master device sizes are:

• 2K page size – 24MB

• 4K page size – 45MB

• 8K page size – 89MB

• 16K page size – 177MB

32 Adaptive Server Enterprise

CHAPTER 2 Installing Adaptive Server

• Master database size (MB). The minimum master database sizes are:

• 2K page size – 13MB

• 4K page size – 26MB

• 8K page size – 52MB

• 16K page size – 104MB

• System procedure device

• System procedure device and database minimum size are 124MB.

• System device

• System device size (in MB) The minimum sizes are:

• 2K page size server – 3MB

• 4K page size server – 6MB

• 8K page size server – 12MB

• 16K page size server – 24MB

• System database size (in MB) The minimum sizes are:

• 2K page size server – 3MB

• 4K page size server – 6MB

• 8K page size server – 12MB

• 16K page size server – 24MB

Once you have customized the Adaptive Server configuration, select Next

to record the input fields. 19 The Custom Configure Backup Serv er Input w indow promp ts you for the

Backup Server information.

Once you have entered the appropriate information, click Next to record

the information. 20 The Custom Configure Monitor Serv er Input window prompts you to ent er

the Monitor Server configuration information.

Once you have entered the appropriate information, click Next to record

the information. 21 The Custom Configure XP Server Inpu t wi ndow p rompt s you to enter the

XP Server configuration information.

Installation Guide 33

Installing server components

22 The Custom Configure New Job Sch eduler Input w indow prompts you t o

23 Custom configure Self Management by entering the following

Once you have entered the appropriate information, click Next to record the information.

enter Job Scheduler information:

• Agent name

• Port number

• Management device

• Management device size

• Management database size Once you have entered the appropriate information, click Next to record

the information.

information:

• Self Management user name

• Self Management password

Note If you choose the default user name “sa,” you cannot enter the

password. The “sa” default password is null.

24 The Unified Agent – Discovery Services screen prompts you to choose

either a “Jini” adaptor or a UDP adaptor. The UDP adaptor is the default. When you enter a Jini adaptor, it requires that you enter a:

• Host name

• Port number

• Heart-beat period

25 Security Login Modules – promp ts you to choo se the securi t y login

modules for the Unified Agent. You can choose:

• Simple Login Module

Note If you doubl e-click Simp le Lo gin Modu le, a dial og asks you to

change the user name and password.

• ASE Login Module

• NT Proxy Login Module

34 Adaptive Server Enterprise

CHAPTER 2 Installing Adaptive Server

Select the Enable box to enable a login module. To order the modules

according to priority , select the module, and click Move up or Move down. 26 The Configure New Servers Summary window di splays a summary of the

values that are used to configure the servers. These values are either the

default or custom values. After verifyi ng the in formation, cl ick Next , and

the Installer proceeds with the server configuration. 27 The Configure Server Progress window d isplays the progress o f the server

configuration. 28 The Reboot window displays only when required. It remi nds you to either

log out or restart your machine to complete the installation process. 29 The Installation Complete window is the last win dow.

If you encounter any errors, see the Troubleshooting Guide. Adaptive Server and related products have been successfully installed, and

minimally configured for use. See “Installing sample databases” on page 44, to begin experimenting with your servers, or see the System Administration Guide at

Sybase Product Manuals at http://www.sybase.com/support/manuals for

Installing version 15.0.2 over an existing 15.x Adaptive Server

Unified Agent

Unified Agent and Agent Management Console – Describes the Unified Agent, which provides runtime services to manage, monitor and control distributed Sybase resource s.

Installing version 15.0.2 over an existing 15.x Adaptive Server

Determining Adaptive Server version

Verify that your current Adaptive Server installation is at version 15.x by running the following query from

1> select @@version 2> go

If your server is not running, you can get a version string by running:

%SYBASE%\%SYBASE_ASE\bin\sqlsrvr.exe-v

If this shows that the Adaptive Server is not at version 15.x, you must upgrade Adaptive Server. See Chapter 5, “Upgrading Adaptive Server.”

isql:

If your server is at a 15.x version level, you can begin installing Adaptive Server 15.0.2.

Backing up Adaptive Server

Installing Adaptive Server version 15.0.2 overwrites the current Adaptive Server software. Before installing, verify that your databases are error free and that your $SYBASE directory is backed up.

T o ensure th at your database is error free, run and dbcc checkstorage prior to loading any new Adaptive Server binaries, including the master database. If the the Err or Messages and T r oubles hooting G uide for actions necessary to fi x the problem. If the error is not listed in the man ual, call Sybas e Technical Support.

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

36 Adaptive Server Enterprise

dbcc commands reveal problems, check

dbcc checkdb, dbcc checkcatalog

CHAPTER 2 Installing Adaptive Server

Installing the Adaptive Server version 15.0.2 binary overlay

1 Read “Special Installation Instructions” in the release bulletin for the latest

information that may affect specific 15.0.2 configurations.

This document may also contain last minute installation information for

the 15.0.2 installation. 2 After backing up your databases, shut down Adaptive Server and back up

your SYBASE directory. 3 Installing Adaptive Server 15.0.2 overwrites current Adaptive Server

software. Prior to installing 15.0.2, make sure that your databases are

error-free as described in “Backing up Adaptive Server” on page 36 and

that your SYBASE directory is backed up. 4 Use InstallShield to load the new software from the CD.

For Windows installations, InstallShield starts automatically.

For UNIX installations, change to the CD drive and enter

./setup.

5 Install Adaptive Server 15.0.2 over the $SYBASE installation path.

Note Once files are loaded into your $SYBASE directory, InstallShield

asks if you want to configure the new installed server. Deselect

configuring the new server, and click continue to finish the installation.

6 Restart Adaptive Server. 7 Run select

@@version. The server should now be at version 15.0.2.

8 In Adapt ive Server ver sion 15.0.2, se veral changes hav e been made to the

system stored procedures and many new error messages have been add ed.

Yo u mu st perform the post-installation tasks to make these changes

available.

installmaster and instmsgs.ebf should be run, in addition to following the

instructions in TechNote 1013610,

Adaptive Server Enterprise 12.5 EBFs at

http://www.sybase.com/detail?id=1013610

Post-installation Scripts and Tasks for

for instructions on post-

installation tasks you may need to perform.

Installation Guide 37

Installing version 15.0.2 over an existing 15.x Adaptive Server

Backward compatibility with previous Adaptive Server 15.x versions

Before using the new Adaptive Server 15.0.2 features, read “Adaptive Server

15.0.2 Backward Compatibility,”

http://www.sybase.com/support/techdocs

You can downgrade to earlier 15.x versions of Adaptive Server, but to do so you must take the precautions described in the technical note before using any of the new 15.0.2 features.

the Sybase Web site at

XML Services in Adaptive Server version 15.0.2

If you are planning on using XML in Adaptive Server version 15.0.2, there are installation issues you must take into consideration. See “Appendix E: Migrating Between the Java-based XQL Processor and the Native XML Processor” in XML Services in Adaptive Server Enterprise.

38 Adaptive Server Enterprise

CHAPTER 3

Post-Installation Tasks

After the installation process, you have a minimally configured Adaptive Server. This chapter describes post-installation tasks to administer Adaptive Server and install stored procedures and samp le databas es . For more information, see the configuration guide for your platform.

Topic Page

Post installation instructions 39 Verifying that servers are running 40 Verifying that you can connect to servers 41 Connecting to Adaptive Server via Sybase Central 42 Setting the System Administrator password 42 The SAMreport 43 Installing sample databases 44

Post installation instructions

Sybase recommends that you perform all of the steps below after installing Adaptive Server on W ind ows platform s. These step s sho uld be performed as the “sybase” user that installed the Adaptive Server product. V er ify that the “sybase” user is a member of the W indows system-defined group “Administrators” so the user has the access privileges that allow them to complete the steps described below.

1 Stop all Adaptive Server services.

Using the Administrative To ols, open Services, select each of the Sybase Adaptive Server entries and stop them. There are separate entries in Services for Sybase Adaptive Server SQLServer, XPServer , BCKServer, MONServer, and SYSAM.

Installation Guide 39

Verifying that servers are running

2 Identify the drives and folders where the Adaptive Server software is

installed, and identify Adaptive Server’s disk devices. Use the Windows command line tool on the identified drives and folders. For detailed instructions on the use of

cacls or Windows Explorer, see your Windows documentation or your

Windows Operating System administrator. Sybase recommends granting full control to the user “syb ase” and denying

access to others on all identified drives, files, and folder hierarchies. If users other than “sybase” need access to files (configuration files,

programs, libraries, and so on) in the folder h ierarchy, limit their access to read and execute. Granting this access and any further access permissions should be carefully reviewed by the administrator to ensure they are required.

Note cacls is a command line utility available on Windows 2000 and later

versions. On earlier Windows versions, this utility is available from the NT Resource Kit.

3 Adaptive Server services should start as the user “sybase”:

• Using the Administrative T ools , open Services and select each of the

cacls or Windows Explorer to set access permissions

Sybase Adaptive Server entries installed.

• Set the “Log On” properties for each of the entries to us e “sybase” and

the password for this account. This action results in the user “sybase”

being granted ‘log on as a service” rights by Windows.

4 Start Adaptive Server services. Using the Administrative Tools, open

Services and select each of the Sybase Adaptive Server entries that were stopped in Step 1 and start them.

Verifying that servers are running

After you install and con figure Sybase server s, your servers s hould be running. To verify that the servers are running:

1 From the Windows task manager, select Start | Settings | Control Panel |

Administrative Tools | Services.

2 Scroll through the list of services until you locate Sybase Adaptive Server

Server_servername, where servername is the name of the server.

40 Adaptive Server Enterprise

CHAPTER 3 Post-Installation Tasks

The Status column indicates if it is started. If it is not, select the server,

then click Start.

Verifying that you can connect to servers

Use isql to perform a quick test. Source ASE150.[csh, sh]. Then, use isql to connect to servers:

1 At the command prompt, enter:

isql -Usa -P<password or leave it blank>

-Sserver_name

where server_name is the Adaptive Server name.

Warning! The first time you log in to Adaptive Server, u se the default “sa”

user name and leave the password blan k. After you log in for the f irst time,

change the System Administrator’s password. See “Setting the System

Administrator password” on page 42.

The command prompt is displayed if the login is successful. 2 To display the Adaptive Server version number, enter:

1> select @@version 2> go

The Adaptive Server version numbe r is displayed. The output should show

Adaptive Server at version 15.0.2.

If you encounter errors, see the Troubleshooting Guide. Alternatively, start

dsedit.

1 From the W indows task-bar , select Start | Programs | Sybase | Connectivity

| Open Client Directory Service Editor. 2 Open the Directory Services window by clicking OK. 3 Highlight servername (the name of the server you want to test). 4 From the Server Option drop-down menu, select Ping. 5 A successful connection returns the message that the connection

succeeded.

Installation Guide 41

Connecting to Adaptive Server via Sybase Central

Sybase Central provides a graphical user interface where you can perform Adaptive Server administrative tasks. The Sybase Central interface provides a hierarchical list of servers in the left pane and a list of details for the selected server in the right pane. To select a server, click on it in the left pane.

1 From the Windows task-bar, select Start | Programs | Sybase | Sybase

Central v4.3.

2 In the left pane, click the server to which you want to connect. 3 In the Login window, enter the System Administrator’s user name and

password. You must log in as the System Administrator to perform administrative

tasks.

4 Click OK.

Warning! The first time you log in to Adaptive Server, use the default “sa” user

name and leave the password blank. After you log in for the first time, change the System Administrator’s pas sword. See “Setting the System Administrator password” on page 42.

The Adaptive Server plug-in to Sybase Central does not display all servers listed in the interfaces file. Instead, Sybase Central lists only those servers that you connected to earlier, or those servers that are started as Wi ndo ws serv ices.

T o access a new server for the first time, select T ools | Connect to select a server listed in the interfaces file.

Setting the System Administrator password

A user account called “sa” is created for the Sybase System Administrator when you install the Sybase software. A user logged in as “sa” can use any database on Adaptive Server, including

Immediately after a new installation, there is no password on the “sa” accou nt. The initial default value for the password is NULL. In a production environment, the Sybase System Administrator should always use a non-default password.

42 Adaptive Server Enterprise

master, with full privileges.

The SAMreport

CHAPTER 3 Post-Installation Tasks

The System Administrator should log in to the new Adaptive Server as “sa” and set a password using

%SYBASE%\%SYBASE_OCS%\bin\isql -Usa -P -Sserver-name

1> sp_password null, new_password

2> go

sp_password:

where “null” is the default password and new_password is the password that you are assigning to the “sa” account.

If Job Scheduler was configured to use the sa account an additional step is necessary whenever the sa password is changed. Once the sa password has been changed the following command will need to be executed:

1> sp_addexternlogin loopback, sa, sa, new_password

2> go

For greatest security , Sybase recommends that you set the password to have at least six characters, with a combination of letters and numbers.

SAMreport is a SySAM 2.0 license reporting tool used in conjunction with the SySAM2.0 license server. It is a report generator that reports the license use of FLEXnet-licensed applications. SAMreport reports license use based on license activity recorded in the FLEXnet report logs, and on selected criteria that include product and feature nam e, user , date and time, and d isplay or host.

The reports provided by SAMreport belong to three report families:

• Summary reports – summarize usage information abou t each feature used

from the license server.

• Raw reports – show individual usage detail in textual format.

• Server reports – provide details about a given license server. For more information on SAMreport, see Chapter 5, “Usin g SySAM for Asset

Management” in the Sybase Software Asset Management User’s Guide.

Installation Guide 43

Installing sample databases

This section describes how to install the U.S. English and international language sample databases. For installation instructions specific to each sample database, see the following sections:

• “Running the database scripts” on page 45

• “Installing the interpubs database” on page 46

• “Installing the jpubs database” on page 47 The sample databases contain information about a fictitious business. You can

use this information to learn about the Sybase products, without affecting essential data.

Table 3-1 lists th e scr ipts that you can use to install the sample databases.

Table 3-1: Sample database scripts

Script Description

instpbs2 Installs the

This database contains dat a th at represents a publishing operation. Use this database to test your server connections and to learn Transact-SQL. Most of the examples in the Adaptive Server documentation query the pubs2 database.

instpbs3 Installs the pubs3 sample database.

This updated version of than the tables used in database in its examples.

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

pubs2 sample database.

pubs2 uses referential integrity . In addi tion, its tables are slightly d ifferent

pubs2. Where noted, the Adaptive Se rver documentation uses the pubs3

Note The master device siz e should be at leas t 30MB to install the fu ll pubs2 database, including

the image data. B e sure to run the instpix2 script after you run instpbs2.

Default devices for sample databases

The %SYBASE%\%SYBASE_ASE%\scripts directory contains scripts for installing the and the

44 Adaptive Server Enterprise

us_english sample database, foreign language sample databases,

image data associated with the U.S. English pubs2 sample database.

CHAPTER 3 Post-Installation Tasks

If you have not used

sp_diskdefault to change the status of the master device or

to specify another default device, the scripts install the sample databases on the

master device. Sybase does not recommend this configuration because it uses

valuable space that is best used for system tables. Each sample database requires 3MB on a 2K server, and multiples of 3MB on a 4K, 6K, 8K, and 16K server on your database device.

To avoid installing sample databases on the

master device, do one of the

following:

•Use

sp_diskdefault to specify a default device other than the master device.

For information on

sp_diskdefault, see the Reference Manual.

• Modify each sample database installation script to specify a different

device.

v Running the database scripts

1 Start Adaptive Server. 2 Determine the type (raw partition, logical volume, operating system file,

and so on) and location of the device where you will be storing the

and pubs3 databases. You will need to provide this information later. 3 Make a copy of the original instpbs2 and instpbs3 scripts. Be sure you can

access the copies, in case you have problems with the edited scripts. 4 Use a text editor to edit the script, if necessary, to specify a default device

other than the

master device, or use sp_diskdefault.

pubs2

From the Adaptive Server scripts directory

(%SYBASE%\%SYBASE_ASE%\scripts), use

isql to log in to Adaptive

Server and run the script:

isql -Usa -P***** -Sserver_name -iscript_name

Where:

• server_name – represents 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

isql -Usa -P***** -SVIOLIN

-i %SYBASE%\%SYBASE_ASE%\scripts\instpbs2

pubs2 on a server named VIOLIN, enter:

5 To install the image data associated with pubs2 (pubs3 does not use image

data), run:

%SYBASE%\%SYBASE_ASE%\ isql -Usa -Ppassword

Installation Guide 45

Installing sample databases

Note The image data requires a fair amount of space—there are six pictures,

two each in the PICT, TIFF, and Sun raster file formats. Run instpix2 script only to use or test the displaying display the images after you have extracted them from the database.

For more information about running these scripts, see the configuration guide for your platform.

interpubs database

interpubs is a database similar to pubs2 that contains French and German data.

This data contains 8-bit characters and is available for use at Adaptive Server installations using the ISO 8859-1 (iso_1), ISO 8859-15 (iso15), Roman8, or Roman9 (for HP-UX) character set. To display the French and German data correctly, you must set up your terminal to display 8-bit characters.

-Sservername -i

%SYBASE%\%SYBASE_ASE%\scripts\instpix2

image datatype. Sybase does not supply any tools for

image data. You must use appropriate window graphics tools to

v Installing the interpubs database

1 Be sure iso_1, iso15, Roman8, Roman 9, or UTF-8 is installed as the

default character set or as an additional character set.

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

3 Make a copy of the original installintpubs script. Be sure you can access

this copy, in case you experience problems with the edited script.

4 Use a text editor to edit the script, if neces sary, to specify a default device

other than the

5 Execute the scrip t, using the

master device, or use sp_diskdefault.

-J flag to ensure that the database is installed

with the correct character set:

isql -Usa -Ppassword -Sservername -Jroman8 -i

$SYBASE/$SYBASE_ASE/scripts/roman8/installintpubs

isql -Usa -Ppassword -Sservername -Jiso_1

-i %SYBASE%\%SYBASE_ASE\%scripts\iso_1\

installintpubs

46 Adaptive Server Enterprise

CHAPTER 3 Post-Installation Tasks

jpubs database

For more information on the

-J option in isql, see the Utility Guide.

If you installed the Japanese Langu age Module with your Adaptive Server, the scripts file contains the installjpubs script for installing the

jpubs is a database similar to pubs2 that contains Japanese data. installjpubs

jpubs database.

uses the EUC-JIS (eucjis), UTF-8 (utf8), or the Shift-JIS (sjis) character sets. V erify that you are runni ng HP Native Languag e I/O to ensure that y our system

can display Japanese data correctly.

v Installing the jpubs database

1 Set your terminal to display 8-bit characters. 2 Verify that the EUC-JIS, Shift-JIS, or UTF-8 character set is in stalled as

the Adaptive Server 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

database. You will need to provide this information later. 4 Make a copy o f the original installjpubs script. Be sure that you can access

this copy, in case you experience problems with the edited script. 5 Use a text editor to edit the script, if necessary, to specify a default device

other than the

master device, or use sp_diskdefault. See “Default devices

for sample databases” on page 44.

jpubs

6 Execute the

installjpubs script, using the -J flag to ensure that the databas e

is installed with the correct character set:

isql -Usa -Ppassword -Sservername -Jeucjis

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

or:

isql -Usa -Ppassword -Sservername -Jsjis

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

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

Installation Guide 47

Installing sample databases

Maintaining the sample databases

The sample databases contain a guest user that allows access to the database by any authorized Adaptive Server user. The guest user has a wide range of privileges, including permissions to select, insert, update, and delete user tables. For more information about the guest user and a list of guest permissions, see the System Administration Guide.

Note Sybase recommends that yo u remove the gues t user from u ser databases

in production systems.

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

If space is a problem, you can instruct the user to issue the

begin transaction

command before updating a sample database. After the user has finished updating one of the sample databases, he or she can issue the

transaction

command to undo the changes.

rollback

48 Adaptive Server Enterprise

CHAPTER 4

Overview

Installing Sybase PC-Client Products

Adaptive Server also includes PC-Client products, and this chapter describes how to install client products.

Topic Page

Overview 49 Before you install the PC-Client products 50 Installing PC-Client products 50 Installing PowerDesigner, PowerTransfer, and InfoMaker 53 Configuring network connections for client products 54

Clients, such as Sybase Central and Open Client, are used to access Adaptive Server. See the Open Client/Server Configuration Guide for Desktop Platforms.

Sybase Central, ASE and SySAM plug-ins

Open Client runtime

Installation Guide 49

Sybase Central allows you to connect to Adaptive Server via client connections. You can use Sybase Central to connect to remote servers, local servers (installed on the same machine), and multiple servers. See “Configuring network connections for client pr oducts” on page 54. Before you use the plug-in, restart your computer to implement changes made to the PATH and CLASSPATH environment variables during installation.

The Sybase PC-Client CD includes:

• Software Developer’s Kit (SDK) for Windows platforms. SDK includes:

• Open Client (CT-Library, DB-Library)

• Embedded SQL/C (ESQL/C)

• Embedded SQL/Cobol (ESQL/Cobol)

Before you install the PC-Client products

• Extended Architecture (XA)

• jConnect for JDBC

• ASE ODBC driver by Sybase

• ASE OLE DB provider by Sybase

• ASE ADO.NET Data provider by Sybase

• Language modules

• PowerDesigner

• PowerTransfer

• Infomaker Monitor Client Library requires Open Client/C with the SDK option.

Before you install the PC-Client products

Before starting the installation process for PC-Client products, be sure that you have at least an extra 5MB of disk space, a \temp directory, and that you have set the TEMP environment variable.

The installation program uses the extra space and directory to write files temporarily during the installation. The installation program frees this space after installation is complete.

Installing PC-Client products

The PC-Client CD contains several products that are each packaged with their own installer. When you insert the PC-Client CD, a menu program launches automatically. The menu program presents the list of products that can be installed from the CD and allows you to install them one at a time. The major products on the CD are described in Chapter 1, “Overview.”

These are the menu selections:

•View readme.txt

• Install PC-Client components 15.0.2

50 Adaptive Server Enterprise

CHAPTER 4 Installing Sybase PC-Client Products

• Install PowerDesigner 12.0

• Install PowerTransfer 15.0

• Install InfoMaker 10.5

• View our (Sybase) Web site

•Exit Before installing any products, review the readme.txt file, which contains a

brief description of each of the products, lists dependencies, and contains any last-minute instructions or changes.

In general, some portion of the PC-Cl ient compo nents are qu eried by the other products so it is best to install the PC-Client components first.

Table 4-1: PC-Client system requirements

Operating system Service pack level

Windows 2000 Professional, S erver, Advanced Server, and Data Center Editions

Windows 2003 None; Sybase recommends using the latest service pack from

Windows XP Professional None; Sybase recommends using latest service pack from Microsoft

Windows Server 2003 Edition x64 None; Sybase recommends using latest service pack from Microsoft

Service Pack 4 or higher

Microsoft for best security protection

for best security protection

v Installing PC-Client Components on Windows

The PC-Client CD contains PC-Client Components, PowerDesigner, PowerTransfer, and Infomaker. Each product is separately installable. The PCClient Components are also installed as part of the Adaptive Server installation.

Warning! If PC-Client Components have been installed during the Adaptive

Server installation, do not re-install them, and do not install them in a different directory.

Warning! You must install the 64-bit Adaptive Server on Windows 64-bit

platforms. If you install the 32-bit version of PC-Client with a 64-bit Adaptive Server you will overwrite the 64-bit binaries with the 32-bit binaries.

Installation Guide 51

Installing PC-Client products

PC-Client Components are provided so they can be installed on client computers. You may install PowerDesigner , PowerT ransfer , and Info maker on the same computer as Adaptive Server.

1 Verify that your computer has sufficient disk space for each product. 2 If you are unloading components, log in using an account with

3 Close any open applications or utilities to free memory and system

4 Insert the PC-Client CD in the CD drive. The menu program should start

5 Select Install PC Client Components 15.0.2 from the menu. 6 When the Installer starts, the Welcome window displays. Click next. 7 When the Sybase license agreement displays, select a country, click

administrator privileges.

resources.

automatically. Alternatively, you can start the menu program from the Windows Start

menu. Select Start | Run, and enter the following, where X is your CD drive:

X:\autorun.exe

Agreement, then click Next.

8 Enter the directory path and click Next.

• If user has Sybase Central previously installed to a directory other than the one specified in step 5 the following pop-up dialogue will be shown:

The install program detected a previously installed copy of Sybase Central 4.3 in the following directory '{0}'. It is recommended that the Sybase Central updates and Adaptive Server plugins be installed in this location rather than '{0}'. Do you want to continue installing Sybase Central and Adaptive Server plugin in '{2}'?

• If you choose “no” to above question, the following pop-up

dialogue will be shown

52 Adaptive Server Enterprise

CHAPTER 4 Installing Sybase PC-Client Products

9 Select the type of installation to be performed.

• Typical Install – installs the default components that most users need.

• Full Install – installs every component on the CD.

• Customized Install – allows you to select the components to install.

Certain components are automatically installed if they are required to run other selected components.

10 If you select Customized Install, the next window is the Component

Selection window, which allows you to specify which components to install.

Components that would be installed in a typical installation appear with a check in the check box to the left of the product name. You may select or unselect components from this list.

11 Click Next.

The Summary window displays every component to be installed by the Installer, the required disk space, and the available disk space.

If the target directory does not have enough free space, the available space appears in red. You must either click Previous to return to the previous window and change your selections, or Cancel to quit the installer.

12 Click Next. 13 The Installer displays a progress indicator as it installs components. To configure client network connections to Adaptive Server, see the

Configuration Guide for your platform.

Installing PowerDesigner, PowerTransfer, and InfoMaker

Install PowerDesigner b y selecting Install P owerDesigner 12.0 from t he menu. Select Install InfoMaker 10.5 to install InfoMaker from the menu. You must install PowerDesigner, PC-Client components, and the Microsoft

.NET framework before installing PowerTransfer. To install PowerTransfer, select Install PowerTransfer 15.0 from the menu.

Installation Guide 53

Configuring network connections for client products

Adaptive Server communicates with other Adaptive 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 by remote procedure calls.

For Sybase products to interact with one another, each product must know where the others reside on the network. This information is stored in the interfaces file on Windows or in a Lightweight Directory Access Protocol (LDAP) server.

Configuring libtcl.cfg for LDAP

Use the libtcl.cfg files to specify an LDAP s erver name, port number , DIT base, user name, and password to connect to an LDAP server.

The default libtcl.cfg file is located in %SYBASE%|%SYBASE_OCS%\ini. In its simplest form on 32-bit LDAP drivers, the libtcl.cfg file is in this format:

[DIRECTORY] ldap=libsybdldap.dll

where ldapurl is defined as:

ldap://host:port/ditbase

For a 64-bit LDAP driver, the format is:

[DIRECTORY] ldap=libsybdldap64.dll

You can use either a 32-bit or a 64-bit LDAP driver on Windows x64. When an LDAP server is specified in the libtcl.cfg file and the libtcl64.cfg file

(when applicable to your platform), the server information is accessible only from the LDAP server. Adaptiv e Server ignores the interfaces file. Open Client and Open Server applications that use the libtcl.cfg file and use the interfaces file.

To use a directory service, you must: 1 Con figur e the libtcl.cfg file, and the libtcl64.cfg file (when applicable,) to

use directory services. Use any standard ASCII text editor to:

54 Adaptive Server Enterprise

-i option at start-up ove rride the

CHAPTER 4 Installing Sybase PC-Client Products

• Remove the semicolon (;) comment markers from the beginning of

the LDAP URL lines in the libtcl.cfg file under the [DIRECTORY] entry.

• Add the LDAP URL under the [DIRECTORY] entry. See the

Configuration Guide for supported LDAP URL values.

Warning! You must enter the LDAP URL on a single line.

ldap=libsybdldap.dll ldap://host:port/ditbase??scope?? bindname=username password

For example:

[DIRECTORY] ldap=libsybdldap.dll ldap://huey:11389/dc=sybase,dc=com??one?? bindname=cn=Manager,dc=sybase,dc=com secret

Note On Windows x64, the .dll file is called libsybdldap64.dll.

2 Verify that the appropriate environment variable points to the required

third-party libraries. The Netscape LDAP SDK libraries are located in:

• %SYBASE%\%SYBASE_OCS%\lib3p on 32-bit platforms

• %SYBASE%\%SYBASE_OCS%\lib3p64 on Windows x64 The Windows PATH environment variable must include this directory .

3 Once you have edited the libtcl.cfg file, use

dsedit to add a server to the

directory service: a From the Windows task-bar, select Start | Programs | Sybase |

Connectivity | Open Client Directory Service Editor. b Select LDAP from the list of servers, and click OK. c Click Add New Server Entry. dEnter:

• The server name – this is required.

• Security mechanism – optional. A list of security mechanism OIDs are located in %SYBASE%\ini\objectid.dat.

Installation Guide 55

Configuring network connections for client products

• HA server name – optional. This is the name of the highavailability failover server, if you have one.

e Click Add New Network Transport.

• Select the transport type from the drop-down list.

• Enter the host name.

• Enter the port number.

f Click OK twice to exit the

For more information, see the Configuration Guide for your platform.

Adding a server to the interfaces file

During Adaptive Server product installation, the installer adds entries to th e sql.ini file for the new Adaptive Server, Backup Server, Monitor Server, Historical Server, or XP Server.

To access a Sybase server through the interfaces file, each server must be included in the interfaces file on the client computer.

To add a server entry to the interfaces file on your PC-Client computer: 1 From the Microsoft Windows task bar, select Start | Programs | Sybase |

Connectivity | Open Client Directory Service Editor. 2 Click OK on the first window to open the InterfacesDriver window. 3 Select ServerObject from the menu, and click Add. 4 In t he Input Ser ver Name box, ent er the nam e of the server fo r which you

are creating an entry.

Click OK. 5 In the Attributes column, double-click the server address row you just

added.

dsedit utility.

6 In the ProtocolNetwork Address, click Add. 7 Fro m the dro p-d ow n li st in t he Prot o col box , sel ect TC P, NAMEPIPE, or

SPX.

By default, connections from client products to Adaptive Server are

enabled through the Named Pipes and Winsock network protocols .

56 Adaptive Server Enterprise

CHAPTER 4 Installing Sybase PC-Client Products

8 In the Network Address box, you can enter either the server name or the

IP address, along with the server port number. For example:

machine_name, 4100

where machine_name is the name of the computer, and 4100 is the port number the server is using to “listen” for clients.

Note Windows now accepts TCP-style connection information:

[SERVER] MASTER=NLWNSCK,huey,2222 QUERY=NLWNSCK,huey,2222

[SERVER] MASTER=TCP,heuy,2222 QUERY=TCP,heuy,2222

The preferred format is to use TCP and a space between the host_name and port_number, because it is supported across all platforms. You can edit the interfaces file with any standard ASCII text editor.

9 To find the IP address for a machine, use

ypmatch on a UNIX box, ipconfig

on Windows. S ee your system admi nist ration gu ide for the commands on your system.

Note To conn ect to a UNIX s erver, the entries you add to interfaces must

match the entries in the interfaces file on the UNIX system.

For instructions on using

dsedit to modify existing interfaces file entries or

create new interfaces file entries for existing servers, see the Utility Guide.

Note You can use Windows NT Directory Replication to replicate interfaces

in multiple locations. See the Microsoft documentation for information. You

can also use directory services, which are stored in the Registry.

For additional information on using

dsedit on the client computer, see the Open

Client and Server Configuration Guide for Desktop Platforms and the Open

Client and Server Supplement.

For specific information about entries for connections to Monitor Server and

Historical Server, see:

• Monitor Server User’s Guide

Installation Guide 57

Configuring network connections for client products

• Historical Server User’s Guide

Testing the Sybase Central installation

After you install Adaptive Server, Sybase Central, and the Java Runtime Environment, test the installation and network connections:

1 Select Start | Programs | Sybase | Sybase Central v4.3 from the Windows

task-bar to start Sybase Central. 2 Select Tools | Connect from the Sybase Central menu bar to activate a

Sybase Adaptive Server login window. 3 Log in using the default user ID, “sa”, without a password. I f you changed

the password for Adaptive Server according to the post-installation

instructions, use the new password. 4 From the drop-down list, select the Adaptive Server to which you want to

connect.

If Sybase Central is installed on the same computer as the server, click the

icon for the server.

If prompted to start Adaptive Server , click OK. When the traffic light icon

representing the server is green, the server is running.

Warning! Do not start XP Server from Sybase Central. Adaptive Server

starts XP Server automatically when Adaptive Server receives the first

request for an extended stored procedure.

5 To disconnect from a server, select Tools | Disconnect. 6 Exit Sybase Central. If Adaptive Server fails any of these tests, see Chapter 7, “Troubleshooting.”

Before retrying the installation, follow the instructio ns in Chapter 3, “P ostInstallation Tasks.” For more details on Unified Agent installation and administration, see the Unified Agent / Agent Management Console User Guide.

58 Adaptive Server Enterprise

CHAPTER 5

Upgrading Adaptive Server

This chapter describes the vari ous steps fo r upgrading A daptive Server to version 15.0.2. If you are installing Adaptive Server 15.0.2 on top of an earlier version refer to section Installing version 15.0.2 over an existing

15.x Adaptive Server in Chapter 2, “Installing Ada p tive Server”. If you need information on recoveri ng from a failed up grade refer to the section “Recovering from a failed upgrade” on page 106 in Chapter 7, “Troubleshooting.”

Topic Page

Overview of the upgrade process 60 Pre-upgrade tasks 62 Upgrading to Adaptive Server 15.0.2 68 Post-upgrade tasks 71 Upgrading Backup Server, Monitor Server, and XP Server 78 Upgrading Job Scheduler 79 Upgrading high availability 84 Moving Adaptive Server 128 Recovering from a failed upgrade 88

Topic Page

Installation Guide 59

Overview of the upgrade process

You can upgrade to Adaptive Server 15.0.2 from any of these versions:

• 11.9.2.6 and later

•12.5.x

Note Adaptive Server v ersion 15. 0.2 do es not support u pgrade fro m Adapti ve

Server version 12.5.3a.

For a server installation 1 1.5.x and older , Sybase recommends that you upgrade to version 12.5.4, then upgrade to version 15.0.2.

Y ou can upgrade Adaptive Se rver from a 32-bit vers ion to a 64-bit versio n, but you cannot move from a 64-bit version to a 32-bit version. Likewise, you can upgrade only from an earlier version of Adaptive Server to a more recent version.

Only upgrades to and from the same page size are supported. Changing the server schema from one page size to another is a database migration. See

sybmigrate in the Utility Guide for information about migration.

Upgrading Adaptive Server consists of three processes: 1 Install the new Adaptive Server on top of the old %SYBASE% directory. 2 For the new server installation, perform the pre-upgrade checks on the

older server using the preupgrd.exe utility, located at

%SYBASE%\%SYBASE_ASE%\upgrade. 3

preupgrade runs against the old servers. It checks that all required

databases exist and that they are large enough. It verifies that stored

procedures have the text required for upgrade, and that configuration

parameters are correct for the new serv er and for upgrading. It ver ifies that

datatype definitions do not conflict with the new server ’s requirements.

When

preupgrade runs without reporting any errors, you can then:

a Shut down the old server.

b Start the new server against the old installation.

60 Adaptive Server Enterprise

CHAPTER 5 Upgrading Adaptive Server

c Run the upgrade process.

Note Adaptive Server issues advisory warnings when configuration

parameters are not set to the default. These do not require any action.

The

preupgrade and upgrade utilities are internally called by syconfig.exe or

sybatch.exe.

Each new version of Adaptive Server contains features that introduce new

parameters, commands, reserved words, and so on. For this r eason,

preupgrade

is for preparing the old server for upgrade.

syconfig.exe, sybatch.exe, or preupgrd.exe runs various checks to determine

how much space you must add to the old server to successfully upgrade the old

server to the new.

As part of the pre-upgrade tasks, syconfig.exe, sybatch.exe, or preupgrd.exe

scans all databases and catalogs and determines how much free space is

required to upgrade successfully. Essentially, syconfig.exe, or sybatch.exe

searches for the largest catalog, then calculates the required free space by

doubling the size of the largest catalog, and adding approximately 10 percent

for logging the upgrade changes for each catalog.

During the pre-upgrade process, syconfig.exe, sybatch.exe, or preupgrd.exe

returns informational messages as it checks the old server. You must fix all

reported problems, and run syconfig.exe, sybatch.exe, or preupgrd.exe cleanly

before beginning the upgrade process. Once the old server is eligible to be

upgraded, syconfig.exe, sybatch.exe, or preupgrd.exe shuts down the old

server, starts the new server against the existing databases, and begins the

upgrade process.

System catalog changes during upgrade

Adaptive Server version 15.0.2 i ntroduces some new system catalogs and some

changes to existing catalogs.

The catalog upgrade in 15.0.2 may af fect your existing app lications. If you are

upgrading, see the release bulletin for your platform for a complete list of

catalogs that are affected.

Installation Guide 61

Pre-upgrade tasks

Note Before you begin the upgrade process, install Adaptive Server 15.0.2

onto your system.

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

1 Check system and upgrade requirements. 2 Check RUN_server file location. 3 If you are upgrading Adaptive Server, the previously installed version of

the server must be running. If you are upgrading Backup Server,

Historical Server, Monitor Server , or XP Server , those servers must not be

running. 4 Stored procedure text in the

syscomments table is required for upgrade.

5 Reserved words are resolved using quoted identifiers. 6 Verify that users are logged off. 7 Check database integrity. 8 Back up databases. 9 Dump transaction log. 10 Make sure that master is the default database for the “sa” user. 11 Prepare the database and devices for upgrade using the

• Create a

sybsystemdb database.

preupgrade utility.

• Disable auditing using the command:

sp_configure 'auditing', 0

Save the current audit settings for the pre-15.0.2 Adaptive Server using the command:

sp_displayaudit

• Disable disk mirroring.

• V e rify that your SYBASE envir onment variable points to the location of the new Adaptive Server software files you just unloaded.

62 Adaptive Server Enterprise

CHAPTER 5 Upgrading Adaptive Server

You als o can set the OLDSYBASE, OLDSYBASE_ASE, and OLDSYBASE_OCS environment variable to the location of the server you are upgradi ng, t o avoi d hav in g to t yp e t his p a th when you run

syconfig.exe.

• Disable Job Scheduler. For Windows platforms you must specify the location in detail: a Copy %OLDSYBASE%\%OLDSYBASE_OCS\ini\libtcl.cfg to

%SYBASE%\%SYBASE_OCS\ini\libtcl.cfg.

12 Ensure that the procedure cache size is at a minimum of 150 percent of th e

default procedure cache size, or 7500MB.

13 Copy the following files from earlier versions of Adaptive Server to their

corresponding Adaptive Server 15.x installation. For UNIX platforms:

• $SYBASE/interfaces

• $SYBASE/$SYBASE_ASE/<servername>.cfg

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

• $SYBASE/SYSAM-1_0/licenses/license.dat For Windows platforms:

• %SYBASE%\sql.ini

• %SYBASE%\<servername>.cfg

• %SYBASE%\%SYBASE_OCS%\ini directory

Checking system and upgrade requirements

To verify that your system environment is configured correctly: 1 Verify that the computer on which you plan to upgrade the Sybase

products meets the requirements.

2 Determine whether your server supports an upgrade to Adaptive Server

15.0.2.

3 Verify that your operating system is at the proper version level and has all

operating system patches needed for Adaptive Server.

Installation Guide 63

Pre-upgrade tasks

Noting server and device names and locations

By default, the master (master.dat) and system procedures device (sybsytemprocs.dat) files are installed in the %SYBASE%\data directory. The device file names can be different from their device names.

Be sure that the directory to which your TEMP environment variable points exists. The installation program uses the directory to write files temporarily during the installation, which it locates via the TEMP environment variable.

Procedure text is required for upgrade

If you created any compiled objects or stored proced ures in a pre-11 .9.3 server , then removed the encounter runtime problems. To upgrade stored procedures, the stored procedure text must be available in

To successfully upgrade to Adaptive Server version 15.0.2:

• Reinstall the procedures with text, or

• Remove them and reinstall them after the upgrade.

syscomments text, the upgrade succeeds but you will

syscomments.

You can also hide the text using the

sp_hidetext stored procedure.

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 b e used as identifiers, unless they are enclosed in quotation marks. If you are upgradin g Adaptive Server, and the identifiers in your user databases match new reserved words, errors result when you run queries, stored procedures, or applications that use these identifiers.

Note Before performing your upgr ade, change the name of any user dat abase

that is a reserved word using the sp_renamedb stored procedure.

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.

64 Adaptive Server Enterprise

As part of the pre-upgrade process, syconfig.exe or sybatch.exe can perform the reserved word check for you. See the Refer e nce Ma nua l for a complete list of reserved words.

Note If you change an object name, chang e applications and stored pr ocedures

that refer to that object.

Running a reserved word check

The sp_checkreswords system procedure detects and displays any identifiers in your existing databases that conflict with reserved words. Server Config installs Server Config conflict with reserved words, only the number of conflicts.

Note You must use the sp_checkreswords stored procedure from the new

installation to verify that the old installation of Adaptive Server does not use any reserved words that have been introduced with the new server.

sp_checkreswords and checks the reserved words during the upgrade.

CHAPTER 5 Upgrading Adaptive Server

does not display the names or locations of identifiers that

Server Config always discovers one reserved-word conflict for each database in your Adaptive Server. This is because the

sysobjects table in Adaptive

Server inserts a reserved word with each of its table entries. You do not need to address these conflicts, because they do not adversely affect the upgrade process.

Addressing reserved words conflicts

If any database names are reserved words, you must use sp_renamedb to change the database names before you can u pgrade. Use database to single-user mode, and then run

sp_renamedb, specifying the new

name. See the Reference Manual for more information on these procedures. 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 )

Installation Guide 65

sp_dboption to set the

Pre-upgrade tasks

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

For more information about

sp_rename and sp_checkreswords and methods for

avoiding reserved word conflicts, see the Reference Manual.

Using quoted identifiers

You can enclose the identifiers that are reserved words in double quotation marks and invoke the

quoted_identifier option of the set command in

procedures and queries that include the reserved words. The

quoted_identifier

option tells Adaptive Server to treat any character string

enclosed in double quotation marks as an identifier. To avoid reserved word conflicts, all users on the server must invoke the

quoted_identifier option in all sto red procedures and queries that include the

reserved words.

Preparing the database and devices for the upgrade

If you ran the pre-upgrade option in preupgrd.exe, the utility scanned the system catalogs and calculated how much additional space you need to perform the upgrade.

If you did not run the pre-upgrade check, you must manually calculate how much free space you must add to your system catalogs and databases.As a general rule, you must double the size of the lar gest catalog that you are go ing to upgrade, and add approximately 10 percent more to calculate the free space required for the upgrade to succeed. For example, if you have a large number of stored procedures or compiled object in any database, the

sysprocedures catalogs will require additional space.

set

syscomments and

Note Sybase recommends that you use preupgrade to determine how much

free space is required for the upgrade.

v Increasing default database sizes

You can use sp_helpdb or Sybase Central to determine the current size of the

master, model, sybsystemprocs, and tempdb databases.

To enlarge the

master, tempdb, and model databases:

66 Adaptive Server Enterprise

CHAPTER 5 Upgrading Adaptive Server

1In

isql, use alter database to increase the size of the master database. For

example:

1> use master 2> go 1> alter database master on master=x 2> go

This example increases the size of the master database; x is the number of megabytes of space added to the existing database size.

2 Repeat this step to increase the size of each of the

databases. For example:

1> alter database tempdb on master=x 2> go 1> alter database model on master=x 2> go

Note The model database cannot be larger than the tempdb. If your

changes cause the must first increase the size of

model database.

3 Verify the size of each database. Enter the following, where

database_name is the name of the system database you are checking:

1> sp_helpdb database_name 2> go

Create a sybsystemdb database

In version 11 .9.x, the sybsystemdb datab ase was required o nly for servers us ing two-phase commit tran sacti on s. B egi nn in g wi th version 12.0, all s erv ers mu st have a

sybsystemdb database. Adaptive Server uses this database for tracking

transactions and during recovery. In addition, it is used for applications using two-phase commit and Distributed Transaction Management (DTM).

tempdb and the model

model database to be larger than the tempdb, then you

tempdb, before increasing the size of the

If you have a sybsystemdb database

If you have a sybsystemdb and the database is at least 4MB, you do not need to make any changes. If the database is smaller th an 4MB, increase the size with

alter database.

Installation Guide 67

Upgrading to Adaptive Server 15.0.2

If you do not have a sybsystemdb database

If you do not have a sybsystemdb, and will not be using two-phase commit or DTM applications, create a

If you will be using two-phase commit or DTM, you can either:

sybsystemdb with a minimum of 4MB.

• Create a minimum-sized

• Create a

sybsystemdb of 5 to 20MB, depending on your expected usage.

sybsystemdb for upgrade and expand it later, or

Approximately 25 percent of the database should be data storage, and 75 percent should be log storage.

sybsystemprocs

sybprocsdev is the default name for the device-holding database sybsystemprocs. It is frequently referred to as the sybsystemprocs device in

Adaptive Server. Verify that the

default size for accommodate the existing

sybsystemprocs database is large enough. For an upgrade, the

sybsystemprocs is 124MB, or enough free space to

sybsystemprocs database, and the largest catalog

that is to be upgraded, plus an additional 10 percent for logging upgrade changes. You may need more space if you are adding user-defined stored procedures. 124MB accommodates additional internal data structures, but does not account for the possibility of a larger number of user-defined system procedures.

Upgrading to Adaptive Server 15.0.2

Note Server Config cannot connect to an Adaptive Server that uses named

pipe directory service. You must remove named pipe directory se rvice from the interfaces file before upgrading the Adaptive Server.

To assist with the upgrade process, Sybase recommends you set the OLDSYBASE, OLDSYBASE_ASE, and OLDSYBASE_OCS environment variables to point to the old installation of Adaptive Server. If you set these environment variable to the old i nstallation of the Adaptive Server, the upgrade utility automatically populates input fields with the correct information as you upgrade.

68 Adaptive Server Enterprise

CHAPTER 5 Upgrading Adaptive Server

Set the OLDSYBASE_ASE variable to the SYBASE_ASE appropriate to your older server. If you are upgrading from 12.0 for example, it should be ASE-12_0. If your preupgrade version is earlier than 12.0, specify it as null:

set OLDSYBASE_ASE=""

This is required if you are using sybatch.exe to perform your upgrade. Install the new Adaptive Server into the same directory as the Adaptive Server

you are upgrading. This section covers the upgrade process, and outlines the following tasks:

• Installing version 15.0.2 software on the target computer. See Chapter 2, “Installing Ada pti ve Ser ver.”

• Upgrading the servers with

• Post-upgrade tasks, includ ing how to enabl e earlier versions of programs

Note The installation procedure for Sybase Central and the Adaptive Server

plug-in for Sybase Central has changed. Beginning with version 1 2.0, Adaptive Server uses the following locations: Sybase Central in the x:\Program Files\Sybase\Sybase Central\win32 directory and Adaptive Server plug-in for Sybase Central in the %SYBASE% directory. Earlier versions used the x:\sybtools directory. The Installer modifies your CLASSPATH, PATH, Profiles, and Registry entries to these specific new locations.

Upgrading the server

To upgrade the server after you have installed the new software: 1 Run S tart | Programs | Sybase | Adaptive Server Enterprise | Server Conf ig. 2 Click U pg rade Adapt ive Server in the Configure Syba se Se rvers w indow. 3 Enter the name of the old Sybase directory. Enter the name of the old

syconfig or sybatch.

and databases, allowing them to utilize the new version’s functionality.

Adaptive Server directory, such as ASE-12_0. Enter the old OpenClient Server directory such as OCS-12_0.

4 Click Continue. 5 In the Existing Servers window, select the Adaptive Server to upgrade and

choose Continue.

Installation Guide 69

Upgrading to Adaptive Server 15.0.2

6 In the Password window, enter the administrator login name and

password. 7 Choose Continue. 8 If Adaptive Server is not running, the upgrade program starts it for you

automatically.

Before making any changes to the existing Adaptive Server databases, the

Installer states: You are advised to back up your databases before

upgrading. Do you want to proceed with the upgrade? 9 If you have not backed up the existing databases, choose No in the

Upgrade window and use the

copies.

If you have made the necessary backups, select Y e s. Server Config begins

the database eligibility test.

After all pre-upgrade checks are successful, the old server is shut down

and the new Adaptive Server

device.

binary to perform the upgrade.

dump database command to make backup

dataserver binary is started on the old master

sqlupgrade or the Server Config utility internally runs the upgrade

Note If the upgrade was successful, back up all the databases, including

the master database, in your upgraded Adaptive Server.

To check the upgrade, use the Windows Notepad to view the log file in

%SYBASE%\%SYBASE_ASE%\upgrade\errorlog.upg.

Log information can also be found by viewing the log file in

%SYBASE\%SYBASE_ASE%\init\logs\

The upgrade process:

• Creates the RUN_servername file

•Runs installmaster script

Testing the Adaptive Server upgrade

To start Adaptive Server and test the upgrade: 1 From the Windows task-bar, select Start | Programs | Sybase | Sybase

Central v4.3. 2 Select the upgr aded Adaptive Server. You are prompted to start the se rver.

70 Adaptive Server Enterprise

CHAPTER 5 Upgrading Adaptive Server

After Adaptive Server starts, a green light appears next to the server name.

3 When prompted, log in as a System Administrator.

Your user ID appears in parentheses next to the server name.

4 Connect to each server listed to verify the installation.

Warning! Do not start XP Server from Sybase Central. Adaptive Server

starts XP Server automatically when Adaptive Server receives the first request for an extended stored procedure.

5 To disconnect from each server, select Tools | Disconnect.

6 Close Sybase Central.

If Adaptive Server fails the test, see Chapter 7, “Troubleshooting.” Before

retrying the installation, follow the instructions in “R emoving Adaptive

Server” on page 119.

Post-upgrade tasks

After you have upgraded to the new version of Adaptive Server, perform the

following tasks to make sure your new Adaptive Server is up and running.

Note After you have upgraded, you do not need t o run update statistics on any

tables. The upgrade process does not cause any changes in existing statistics.

Run the instmsgs.ebf script

You must run the instmsgs.ebf script after you upgrade from a 15.0 Adaptive

Server to a 15.0.2 Adaptive Server. Run the instmsgs.ebf script immediately

after runnning the installmaster script.

If you are a localized customer:

• First run the instmsgs.ebf script, and then install any localized language using

langinstall, sqlloc, or syconfig.

• If you run instmsgs.ebf after installing the 15.0.2 localized message, this script may delete some new messages.

Installation Guide 71

Post-upgrade tasks

Restoring functionality in Adaptive Server

To reset or enable options or functionality you had to change before the upgrade:

1 Reset the configuration parameters.

If you changed any configuration parameters before upgrading, use

sp_configure to set them back to their previous values.

2Use

sp_dboption to reset any database options you disabled before

upgrading.

3 After yo u complete the upgrade, but before you use the upgraded Adaptive

Server, verify that all scripts developed at your site point to Adaptive Server 15.0.2.

4 Verify procedure cache allocation after upgrading.

This section is for information only. Adaptive Server ensures that

procedure cache size after upgrade is the same as before upgrade, unless

the original size was less than the default value. If you are upgrading from a versi on of Adaptive Server that is earlier than

version 12.5.x,

cache size

procedure cache percent has been changed to procedure

. Adaptive Server now allocates memory dynamically and determines the size of the procedure and data caches in terms of megabytes. During the upgrade process, Adaptive Server converts the

procedure cache percent to an absolute value and sets procedure cache size

based on this value. For example, if

200MB of memory, then the absolute value of 40MB. During the upgrade process, Adaptive Server converts

cache percent

for

procedure cache size is less than the default value, Adaptive Server sets

procedure cache size to the default value. For example, if procedure cache

is set to 10 percent in the example above, and the absolute value

percent

of 10 percent is less than the default value of

procedure cache size is set to the default value.

procedure cache percent is configured as 20 percent of

procedure cache percent is

procedure

at 20 percent to procedure cache size at 40MB. If the value

procedure cache size, then

With the introduction of dynamically reconfigured memory configuration parameters in Adaptive Server 12.5.x, an increase in Adaptive Server’s memory use does not decrease the si ze of the pr ocedu re cach e or the data cache. That is, if your default data cache is set to 40MB, a nd you increa se your procedure cache, the default data cache is still 40MB.

For more information about

sp_configure, see the Reference Manual.

72 Adaptive Server Enterprise

CHAPTER 5 Upgrading Adaptive Server

5 Check the procedure cache requirements.

Stored procedures, triggers, and other compiled objects require more memory to run than older versions. The memory required to run a stored procedure increased by 20 percent between versions 10.x and 11.5. Adaptive Server 12.5.x needs approximately 4 percent more procedure cache than version 11.5 for the server to maintain the same performance.

You may increase the

sp_configure. You can use the verify option in sp_configure to verify any

procedure cache size during runtime, using

changes you make to the configuration file without having to restart Adaptive Server. The syntax is:

sp_configure "configuration file", 0, "verify", "full_path_to_file"

For example:

sp_configure "configuration file", 0, "verify",

"C:\Sybase\ASE125.cfg"

For more information about sp_configure and sp_sysmon, see the Reference Manual and the Performance and Tuning Guide. For more information about configuring memory, see the System Administration Guide.

6 Verify data cache allocation after upgrading. This section is for

information only. Adaptive Server ensures that all the data cache sizes after upgrading are the same as before upgrade.

In pre-12.5 versions of Adaptive Server, the default data cache available depended on the amount of memory available to Adaptive Server. If the default data cache was set to 2MB, Adaptive Server allocated 2MB to the default data cache. If, after memory was allocated to all user-d efined data caches and to the procedure cache, there was more memory av ailable, that memory was allocated to the default data cache. Howev er, if there was not enough memory available for Adaptive Server to set up the user-defined caches and the procedure cache, then mem ory was taken f rom the default data cache regardless of the designated configuration parameter. Therefore, it was possible to set default data cache to th e default value and have all remaining available memory allocated to the default data cache.

Adaptive Server 12.5.x and later treats the default data cache size as an absolute value and sets it in the config file. The string DEFAULT in the config file has a different meaning for default data cache size in Adaptive Server 12.5.x and later.

Installation Guide 73

Post-upgrade tasks

In pre-12.5 Adaptive Server, it meant all the memory left after allocating memory for other configurations, procedures, and user-defined named caches. In Adaptive Server 12.5.x and later, it means a default value of 8MB.

During the upgrade process, Adaptive Server ensures that the default data cache size remains the same. Therefore, during the pre-upgrade process, the size of the default data cache is obtained and written to the configuration file as an absolute value, not as “DEFAULT”. This enables Adaptive Server to have the same default data cache size as before the upgrade. If this size is less than the default size of default data cache of 8MB, then Adaptive Server allocates a default data cache of size 8MB.

7 If you unmirrored devices, remirror them, using the

command.

8 For information about upgrading compiled objects, see “Upgrading

compiled objects with dbcc upgrade _obje ct ” on page 109.

9 If you used two-phase commit in 11.9.x, run the script to install the

two-phase commit tables:

isql -Usa -Psa_password -Sserver_name

-i%SYBASE%\%SYBASE_ASE%\scripts\instcomm

You do not need to run this script if you do not use two-phase commit.

Reenabling Replication Server

If you disabled replication before the upgrade, you must reenable replication. To do so, first remove any older format log records from your database, and then reenable replication.

Removing old log records

Use the dump tran command to dump the database and transaction logs to remove the older format log records from your database. This prevents Replication Server from accessing the pre-upgrade portion of the transaction logs.

disk remirror

For example, to dump the

1> use master 2> go 1> dump database sales to "\\.\TAPE0"

sales database:

74 Adaptive Server Enterprise

Reenabling replication

Follow the steps in this section to reenable replication after upgradin g the primary databases and primary RSSDs.

For each primary database and RSSD: 1 Start Adaptive Server if it is not already running. 2 Log in to the server. 3 Clear the locator for the database by executing the following command in

4 Enable the truncation point for the database.

CHAPTER 5 Upgrading Adaptive Server

2> go

the RSSD for this database:

1> use RSSD 2> go 3> rs_zeroltm dataserver, database 4> go

1> use database 2> go 1> dbcc settrunc("ltm", "valid") 2> go

5 Restart the Replication Servers and LTMs. 6 Resume the DSI connections that were suspended before the upgrade by

executing the following Replication Server command for each susp ended database:

1> resume connection to dataserver.database 2> go

The replication system is now ready for Adaptive Server 12.5.x, and applications can resume.

If you installed any Sybas e client pro ducts, such as Open Client, us e the

dsedit

utility to edit your interfaces file and to specify the servers to which you want to connect.

For more information about establishing client/server connections, see the Open Client Configuration Guide or Chapter 4, “Installing Sybase PC-Client Products.”

Installation Guide 75

Post-upgrade tasks

Restoring replication after upgrade

Restore the replication functionality: 1 Log in to the RSSD for each replicated primary, and for each replicated

RSSD, and issue:

1> use RSSD_name 2> go

1> rs_zeroltm dataserver, database 2> go

2 Log in to each replicated primary, and replicated RSSD and issue:

1> use database 2> go

1> dbcc settrunc ('ltm', 'valid') 2> go

3 Restart the Replication Server. 4 If the database is also used as a RSSD, resume the Replication Server

connection to the RSSD by issuing the following command to the Replication Server:

1> sysadmin hibernate_off, 'Replication Server' 2> go

Make sure to specify the same string that was specified during the

'hibernate_on' command.

5 Log in to the Replication Server , and res ume the Log Tran sfer connection

for each replicated primary and each replicated RSSD:

1> resume log transfer from server.database 2> go

If this is a replicated RSSD, you must log in to the replicate Replication Server.

6 If you are using Rep Agent, log in to the Adaptive Server and restart the

Rep Agent:

1> use database 2> go 1> sp_start_rep_agent database 2> go

7 If you are using LTM, restart the LTM.

76 Adaptive Server Enterprise

Reenabling auditing

Reenable all auditing options for stored procedures using the audit options you recorded during pre-upgrade. Reenter the audit options using

CHAPTER 5 Upgrading Adaptive Server

sp_audit.

For example, if you had enabled stored procedure auditing for stored procedure in your server before upgrade, run the following command to reenable auditing on

sp_audit "exec_procedure", "all", "sp_addlogin", "on"

sp_addlogin:

sp_addlogin

sp_audit

Adaptive Server 12.5.x and later includes the following global audit options for

sp_audit:

•

security

• dbcc The functionality provided by the following sp_auditoption options is now

covered by the

•

server boot

sp_audit security global audit option:

• roles These options are turned off by def ault and are n ot turn ed o n even if y ou u sed

sp_auditoption "all", "on" to turn on all global audit options in a version earlier

than 11.5. To turn on these options, use:

1> sp_audit "security", "all", "all", "on" 2> go 1> sp_audit "dbcc", "all", "all", "on" 2> go

For more information, see the Reference Manual.

Special considerations for threshold procedures for audit segments

If your installation used a threshold procedure to archive the sysaudits table using T-SQL similar to the following example:

INSERT MyPre15SysAuditHistoryTable SELECT * FROM sysaudits_0n

Where n corresponds to the sysaudits table number 1 – 8 and MyPre15SysAuditHistoryTable is a table defined prior to Adaptive Server version 15.0.2, then you must alter MyPre15SysAuditHistoryTable to add a

nodeid column using the following command:

Installation Guide 77

Upgrading Backup Server, Monitor Server, and XP Server

alter table MyPre15SysAuditHistoryTable

add nodeid tinyint NULL

See the Reference Manual for system tables sysaudits01 through sysaudits08 for further details about the

sysaudits tables.

Shutting down SySAM servers

Shut down the old SySAM servers if they are no longer used by ear lier versions of Adaptive Servers.

Upgrading Backup Server, Monitor Server, and XP Server

Before you can upgrade Backup or Monitor Server, you must upgrade Adaptive Server.

XP Server does not have a formal upgrade process.

Note Back up all databases, including master, after successfully upgrading

Adaptive Server and Backup Server.

v Upgrading Backup and Monitor Servers

The instructions for upgrading Backup Server and Monitor Server are similar. 1 Launch the Server Config utility if it is not already running. Select Start |

Programs | Sybase | Adaptive Server Enterprise | Server Config.

2 Select the B ackup Serv er o r the Mo nitor Server fro m the icons on the left

and click the Upgrade Server button.

3 Enter the name of the old Sybase directory. Enter the name of the old

Adaptive Server directory such as ASE-12_0. Enter the name of the old OpenClient/Server directory such as OCS-12_0.

4 Click Continue. 5 In the Existing Servers window, choose the server you want to upgrade. 6 Click Continue.

78 Adaptive Server Enterprise

CHAPTER 5 Upgrading Adaptive Server

7 Back up all exi st i ng d atab ases bef ore u pgrading. Once you have done so ,

select Yes.

8 When the upgrade is complete, the

“Upgrade completed successfully.” Select OK.

Repeat this procedure to upgrade Monitor Server.

Note To check the upgrade, use the Windows Notepad to view the log file in

%SYBASE%\%SYBASE_ASE%\init\logs

Upgrading Job Scheduler

After upgrading to the new Adaptive Server, perform the following steps to upgrade Job Scheduler.

Note Y o u must hav e $SYBASE/$SY BASE_OCS /bin di rectory in $PATH so the

isql executable is accessible.

v Upgrading Job Scheduler

1 Copy the dir ectory se rvices entr y for JSAGENT (or jsagent) from the old

server to the new server.

syconfig utility displays the message,

2 Make sure your new server is running. 3 Stop the Job Scheduler. From

sybmgmtdb..sp_js_wakeup "stop_js", 1 go

isql, issue :

4 Ensure that at least 9000 locks are configured. If the number of locks on

the server is less than 9000, use

sp_configure to increase the number of

locks:

sp_configure "number of locks", 9000

5 Upgrade the internal Job Scheduler SQL using isql:

use sybmgmtdb go dbcc upgrade_object go

Installation Guide 79

Upgrading Job Scheduler

There is no need to specify any parameters.

6 Restart Adaptive Server. 7If the

sybmgmtdev device is less than 100MB, change the device to be a

minimum of 100MB. From

isql enter the following, where nn.nM is the

number of megabytes needed to get to 100 MB:

use master go disk resize name = 'sybmgmtdev' , size = 'nn.nM' go

8 Optionally, add more log space. On some 64-bit platforms more space is

need for the

use master go alter database sybmgmtdb LOG on sybmgmtdev=20 go

sybmgmtdb log. From isql enter:

9 Upgrade the sybmgmtdb. Using isql, run the installjsdb script that is

included with this release and save the output to a file:

isql -Usa -Psa_password -Sservername -n

-i$SYBASE/$SYBASE_ASE/scripts/installjsdb

-ooutput_file

10 Enable Job Scheduler to star t when Adaptive Server starts. From isql enter

the command:

sp_configure "enable job scheduler", 1

11 Start Job Scheduler. From isql enter the command:

sybmgmtdb..sp_js_wakeup "start_js", 1 go

Upgrading Job Scheduler templates

After upgrading to the new Adaptive Server, perform the following steps to upgrade templates and jobs created from Job Scheduler templates.

Note For the Adaptive Server version 1 5.0.2 release, there are s everal changes

that impact Job Scheduler templates. These changes make some templates incompatible with earlier versions of Adaptive Server. These templates are version 3.0 in the XML files.

80 Adaptive Server Enterprise

CHAPTER 5 Upgrading Adaptive Server

v Upgrading Job Scheduler templates

1 Disable Job Scheduler before ugrading Job Scheduler templates. 2 Update an y environment vari ables, scripts , or applications that refer to th e

Job Scheduler directory path. The Job Scheduler directory has been renamed and moved beneath the ASE-15_0 directory. New location is $SYBASE/$SYBASE_ASE/jobscheduler.

Directories below jobscheduler remain the same.

3 If you have any of your own files i n the old J ob Sc hedule r direct ory, copy

them to the new 15.0.2 di rectory . If you are installing Adap tive Server over the old server directories, the installer will have moved your files to the new jobscheduler directory already.

4 If you have modified any of the Sybase-supplied templates stored

procedures or XML documents, do not overlay the new templates with your versions. If you do, you will lose the enhancements provided by the revised templates. Carefully merge your template changes into the Sybase template files, or better yet, rename your modified templates.

Note Sybase recommends that if you modify Sybase-supplied templates

that you save the changes under new names and in new files.

5 You may need to make minor modifications to jobs you created from 2.0

or earlier templates. In some templates, parameters changed from

archar(5) to int. The following table lists the templates that changed in

v version 2.1 and the changes you need to make to jobs created from them.

Table 5-1: Changed Job Scheduler templates

Modify jobs created

Template Modified files Change description

dump database SybBackupDbToDiskTemplate.xml

jst_dump_databases

dump database log

update statistics

Installation Guide 81

SybBackupLogToDiskTemplate.xml jst_dump_log

SybUpdateStatsTemplate.xml jst_update_statistics

Changed the datatype for the

@use_srvr_name parameter

varchar(5) to int

from

Changed the datatype for the

@truncate_flag and @use_srvr_name parameters

varchar(5) to int

from Changed the datatype for the

@index_flag parameter from varchar(5) to int

from this template

Required, modify job SQL to change

@use_srvr_name to int

datatype. Required, modify job SQL

to change and @use_srvr_name to

int datatype.

Required, modify job SQL to change

int datatype.

@truncate_flag

@index_flag to

Upgrading Job Scheduler

Template Modified files Change description

rebuild indexes SybRebuildIndexTemplate.xml

jst_reorg_rebuild_indexes

rebuild table SybRebuildTableTemplate.xml

jst_reorg_rebuild_tables

reclaim indexes SybReclaimIndexTemplate.xml

jst_reclaim_index_spac

reclaim tables SybReclaimTableTemplate.xml

jst_reclaim_table_space

Changed the datatype for the

@dump_flag varchar(5) to int

parameter from

Changed the datat ype for the

@dump_flag parameter from varchar(5) to int

Required, modify job SQL to

@dump_flag to int

change datatype.

Changed the datat ype for the

@resume_flag parameter

varchar(5) to int

from

6 Some Job Scheduler templates were modified to support new 15.0.2

Adaptive Server functionality. The changes are related to new parameters for specifying a partition name or a datachange value for the Adaptive Server command that have added these options. If you have jobs created from any of the enhanced templates, modify t he SQL of the jobs for 15. 0.2 servers.

Modify jobs created from this template

Required, modify job SQL to change

int datatype.

@dump_flag to

Required, modify job SQL to change

int datatype.

@dump_flag to

Required, modify job SQL to change @resume_flag to int datatype.

Required, modify job SQL to change

@resume_flag

to int datatype.

Note If you have a job scheduled to run on a pre-15.0.2 server and you

need it to run on 15.0.2 servers too, leave the existing job alone and create a new job for 15.0.2 servers as the job commands will be different.

Jobs intended to run on pre-15.0.2 server s do not need to be modified. The following table lists the templates that changed in version 3.0 and the changes you need to 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 will be scheduled on pre-15.0.1 servers; you must use the 2.1 or 2.2 versions for pre-15.0.1 servers.

Table 5-2: Modified Job Scheduler templates

Modify jobs created

Template Modified file Change description

delete statistics SybDeleteStatsTemplate.xml

jst_delete_statistics

Added @ptn_name as third parameter.

from this template

Optional.

82 Adaptive Server Enterprise

CHAPTER 5 Upgrading Adaptive Server

Template Modified file Change description

update statistics

SybUpdateStatsTemplate.xml jst_update_statistics

Added @ptn_name as fifth parameter and

@datachg_threshold as

the 10th parame ter and added reference

rebuild indexes SybRebuildIndexTemplate.xml

jst_reorg_rebuild_indexes

reclaim indexes SybReclaimIndexTemplate.xml

jst_reclaim_index_space

reclaim tables SybReclaimTableTemplate.xml

jst_reclaim_table_space

multiple jst_get_freespace,jst_get_usedspace Replace reserved_pgs and

Added @ndx_ptn_name as third parameter.

Added @ptn_name as third parameter

Added @ptn_name as second parameter

data_pgs with reserved_pages and data_pages

7 Install the Template stored procedures.

Modify jobs created from this template

Required, modify job SQL to include values (or NULL) for new parameters.

Required, modify job SQL to include value (or NULL) for new parameter.

Required, modify job SQLto include value (or NULL) for new parameter.

Required, modify job SQL to include value (or NULL) for new parameter.

No impact on job SQL.

• Move to the JS template stored procedure directory. For example:

cd $SYBASE/$SYBASE_ASE/jobscheduler/Templates/sprocs

• Run the stored procedure install script for each server being upgraded:

installTemplateProcs <servername> <username> <password>

Note Templa te stored procedures s hould be upgraded on al l Job Scheduler

servers and target servers upgraded to Adaptive Server version 15 .0.2. Do not install them on pre-15.0.2 servers.

8 Install the template XML documents.

1 Move to the JS template XML directory. For example:

cd $SYBASE/$SYBASE_ASE/jobscheduler/Templates/xml

2 Run the XML install script on 15.0.1 servers with Job Scheduler

installed:

installTemplateXml <servername> <machinename> <serverport>

<username> <password> [<language_code>]

Installation Guide 83

Upgrading high availability

Use “en” for the language_code or you may omit the parameter completely as “en” is the default.

Note Template XML should be upgraded on all Job Scheduler servers

upgraded to Adaptive Server version 15.0.1. Do not install them on pre-15.0.1 servers or servers where Job Scheduler is not installed.

Upgrading high availability

Using the following steps to upgrade high availability-enabled Adaptive Server in active-active configuration:

1 Drop the high availability companionship. On the secondary server, use

isql:

sp_companion <primary_server_name>, "drop" go

2 Use the cluster syst em command to stop monitor ing res ou rces associated

with Adaptive Server on each cluster node.

3 Follow the upgrade steps in “Upgrading to Adaptive Server 15.0.2” on

page 68 to upgrade each of the Adaptive Servers separately.

4 Run the new Adaptive Server installmaster script against the newly

upgraded Adaptive Servers.

5 Run the new Adaptive Server installhasvss script against the newly

upgraded Adaptive Servers.

6 In the new Adaptive Server installation area, follow the instructions in

Using Sybase Failover in A High Availability System to configure the permission and ownership for $SYBASE/$SYBASE_ASE/bin/sybha and $SYBASE/$SYBASE_ASE/install/sybhauser.

7 In the new Adaptive Server installation area, modify high

availability-related files such as the RUN_server_file, and the SYBASE.csh and SYBASE.sh files, if those files are required on that cluster platform.

8 Reconfigur e each resource associated with Adaptive Server depending on

platform-specific requirements. For example, on Veritas Cluster, the HAase resource properties, the RUN_server_file, and Sybase_home need to be updated.

84 Adaptive Server Enterprise

CHAPTER 5 Upgrading Adaptive Server

9 Manually restart Adaptive Server on each cluster node with trace flag

2209. Use the Adaptive Server command-line option

Warning! Do not use trace flag 2209 after the Adaptive Server

-T2209.

companionship is re-established.

10 Use the cluster system command to restart monitoring resources

associated with Adaptive Server on each cluster node.

11 Re-establish companionship by using

sp_companion <primary_server_name>, configure go

isql to issue:

If user databases exist on the secondary server, warning message may display on the console. There is no need to take any action. You can safely ignore them. The messages look similar to:

Msg 18739, Level 16, State 1: Server 'svr2', Procedure 'sp_hacmpcfgvrfy', Line 102: Database 'svr2_db1': a user database exists. Drop this database and retry the configuration again.

12 Use the cluster command to offline and then online resource associated

with Adaptive Server. Use

isql to connect to each Adaptive Server and

enter the command to verify the correct server companionship:

sp_companion go

Console output on primary server is similar to the following:

Server 'svr1' is alive and cluster configured. Server 'svr1' is configured for HA services. Server 'svr1' is currently in 'Primary normal' mode. (return status = 0)

Console output on secondary server is similar to the following:

Server 'svr2' is alive and cluster configured. Server 'svr2' is configured for HA services. Server 'svr2' is currently in 'Secondary normal' mode. (return status = 0)

Use the following steps to upgrade high availability-enabled Adaptive Servers in active-passive configuration:

1 Use the cluster system command to bring Adaptive Server offline.

Installation Guide 85

Migrating from 32-bit to 64-bit versions

2 Use the cluster syst em command to stop monitor ing res ou rces associated

with Adaptive Server.

3 Follow the upgrade steps provided in “Upgrading to Adaptive Server

15.0.2” on page 68 to upgrade the Adaptive Server to the new version.

4 Run the new Adaptive Server installmaster script against the newly

upgraded Adaptive Server.

5 In new Adaptive Server installation area, modify the high

availability-related files such as the RUN_server_file, and the SYBASE.csh and SYBASE.sh files, if those files are required on that cluster platform.

6 Use the cluster system command to reconfigure resource properties

associated with Adaptive Server to reflect the new Adaptive Server

installation location. 7 Manually restart Adaptive Server. 8 Use the cluster system command to restart monitoring resource as sociated

with Adaptive Server. 9 Use the cluster command to offline and then online resource associated

with Adaptive Server on the same node. Use the cluster command to

switch resource associated with Adaptive Server to another node and then

switch back.

Migrating from 32-bit to 64-bit versions

sqlupgrade upgrades Adaptive Server only from one version to another. This

section describes how to migr ate a 32-bit version of Adaptive Server to a 64- bit version of Adaptive Server.

T o migrate Adaptive Server from the 32-bit to the 64-bit version, you must first install and configure the 64-bit operating system.

Method #1: Dump a nd load

86 Adaptive Server Enterprise

1Run dbcc checks on all databases in the 32-bit Adaptive Server and make

sure they run cleanly. 2 Create a 64-bit Adaptive Server in a new directory.

Sybase ADAPTIVE 15.0.2 User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

About This Book

Product licensing with SySAM 2.0

Product components

Adaptive Server Enterprise

Backup Server

Stored procedures

The client

Adaptive Server editions

Enterprise Edition

Small Business Edition

Developer Edition

Adaptive Server specifications

Product descriptions and directory layout

Sybase support for ADO.NET, OLE DB, and ODBC

PC-Client product descriptions and directory layout

Separately installable PC-Client products

Overview

System requirements

Pre-installation tasks for SySAM

Accessing SPDC

Getting your host ID

Generating licenses at SPDC

Generating a served license

Generating an unserved license

Installing a new license server

Pre-installation tasks for Adaptive Server

Installing server components

Installation methods

Installing components with the Installer in GUI mode

Installing version 15.0.2 over an existing 15.x Adaptive Server

Determining Adaptive Server version

Backing up Adaptive Server

Installing the Adaptive Server version 15.0.2 binary overlay

Backward compatibility with previous Adaptive Server 15.x versions

XML Services in Adaptive Server version 15.0.2

Post installation instructions

Verifying that servers are running

Verifying that you can connect to servers

Connecting to Adaptive Server via Sybase Central

Setting the System Administrator password

The SAMreport

Installing sample databases

Default devices for sample databases

interpubs database

jpubs database

Maintaining the sample databases

Overview

Before you install the PC-Client products

Installing PC-Client products

Installing PowerDesigner, PowerTransfer, and InfoMaker

Configuring network connections for client products

Configuring libtcl.cfg for LDAP

Adding a server to the interfaces file

Testing the Sybase Central installation

Overview of the upgrade process

System catalog changes during upgrade

Pre-upgrade tasks

Checking system and upgrade requirements

Noting server and device names and locations

Procedure text is required for upgrade

Reserved words

Running a reserved word check

Addressing reserved words conflicts

Using quoted identifiers

Preparing the database and devices for the upgrade

Create a sybsystemdb database

If you have a sybsystemdb database

Upgrading to Adaptive Server 15.0.2

If you do not have a sybsystemdb database

sybsystemprocs

Upgrading the server

Testing the Adaptive Server upgrade

Post-upgrade tasks

Run the instmsgs.ebf script

Restoring functionality in Adaptive Server

Reenabling Replication Server