Adaptative Server Enterprise 11.9.2 Install Manual

Sybase® Adaptive Server™ EnterpriseInstallation Guide

Linux/Intel

Adaptive Server Enterprise Version 11.9.2

Document ID: 30119-01-1192-01

Last Revised: June 30, 1999

Principal author: Emeryville Technical Publications

Document ID: 30119-01-1192

This publication pertains to Adaptive Server Enterprise Version 11.9.2 of theSybase database management software and to any subsequent release untilotherwise indicated in new editions or technical notes. Information in thisdocument is subject to change without notice. The software described herein isfurnished under a license agreement, and it may be used or copied only inaccordance with the terms of that agreement.

Document Orders

To order additional documents, U.S. and Canadian customers should callCustomer Fulfillment at (800) 685-8225, fax (617) 229-9845.

Customers in other countries with a U.S. license agreement may contact CustomerFulfillment via the above fax number. All other international customers shouldcontact their Sybase subsidiary or local distributor.

Upgrades are provided only at regularly scheduled software release dates.

Copyright © 1989–1999 by Sybase, Inc. All rights reserved.

No part of this publication may be reproduced, transmitted, or translated in anyform or by any means, electronic, mechanical, manual, optical, or otherwise,without the prior written permission of Sybase, Inc.

Sybase Trademarks

Sybase, the SYBASE logo, Adaptive Server, APT-FORMS, Certified SYBASEProfessional, the Certified SYBASE Professional logo, Column Design,ComponentPack, Data Workbench, First Impression, InfoMaker, ObjectCycle,PowerBuilder, PowerDesigner, Powersoft, Replication Server, S-Designor, SQLAdvantage, SQL Debug, SQL SMART, Transact-SQL, Visual Components,VisualWriter, and VQL are registered trademarks of Sybase, Inc.

Adaptable Windowing Environment, Adaptive Component Architecture,Adaptive Server Enterprise Monitor, Adaptive Warehouse, ADA Workbench,AnswerBase, Application Manager, AppModeler, APT-Build, APT-Edit, APT-Execute, APT-Library, APT-Translator, APT Workbench, Backup Server, BayCam,Bit-Wise, ClearConnect, Client-Library, Client Services, CodeBank, ConnectionManager, DataArchitect, Database Analyzer, DataExpress, Data Pipeline,DataServer, DataWindow, DB-Library, dbQueue, Developers Workbench,DirectConnect, Distribution Agent, Distribution Director, Embedded SQL, EMS,Enterprise Application Server, Enterprise Application Studio, EnterpriseClient/Server, EnterpriseConnect, Enterprise Data Studio, Enterprise Manager,Enterprise SQL Server Manager, Enterprise Work Architecture, Enterprise WorkDesigner, Enterprise Work Modeler, EWA, Formula One, Gateway Manager,GeoPoint, ImpactNow, InformationConnect, InstaHelp, InternetBuilder, iScript,Jaguar CTS, jConnect for JDBC, KnowledgeBase, Logical Memory Manager,MainframeConnect, Maintenance Express, MAP, MDI Access Server, MDI

Database Gateway, media.splash, MetaBridge, MetaWorks, MethodSet,MySupport, Net-Gateway, NetImpact, Net-Library, Next Generation Learning,ObjectConnect, OmniConnect, OmniSQL Access Module, OmniSQL Toolkit, OpenClient, Open ClientConnect, Open Client/Server, Open Client/Server Interfaces,Open Gateway, Open Server, Open ServerConnect, Open Solutions, Optima++,PB-Gen, PC APT-Execute, PC DB-Net, PC Net Library, Power++, Power AMC,PowerBuilt, PowerBuilt with PowerBuilder, PowerDynamo, PowerJ, PowerScript,PowerSite, PowerSocket, Powersoft Portfolio, PowerStudio, Power ThroughKnowledge, PowerWare Desktop, PowerWare Enterprise, ProcessAnalyst,Replication Agent, Replication Driver, Replication Server Manager, Report-Execute, Report Workbench, Resource Manager, RW-DisplayLib, RW-Library,SAFE, SDF, Secure SQL Server, Secure SQL Toolset, Security Guardian, SKILS,smart.partners, smart.parts, smart.script, SQL Code Checker, SQL Edit, SQLEdit/TPU, SQL Modeler, SQL Remote, SQL Server, SQL Server/CFT, SQLServer/DBM, SQL Server Manager, SQL Server SNMP SubAgent, SQL Station,SQL Toolset, Sybase Central, Sybase Client/Server Interfaces, SybaseDevelopment Framework, Sybase Financial Server, Sybase Gateways, SybaseLearning Connection, Sybase MPP, Sybase SQL Desktop, Sybase SQL Lifecycle,Sybase SQL Workgroup, Sybase Synergy Program, Sybase Virtual ServerArchitecture, Sybase User Workbench, SybaseWare, SyberAssist, SyBooks, System10, System 11, the System XI logo, SystemTools, Tabular Data Stream, TheEnterprise Client/Server Company, The Extensible Software Platform, The FutureIs Wide Open, The Learning Connection, The Model for Client/Server Solutions,The Online Information Center, Translation Toolkit, Turning Imagination IntoReality, UltraLite, UNIBOM, Unilib, Uninull, Unisep, Unistring, URK Runtime Kitfor UniCode, Viewer, VisualSpeller, VisualWriter, WarehouseArchitect, WarehouseStudio, Warehouse WORKS, Watcom, Watcom SQL, Watcom SQL Server, Web.PB,Web.SQL, WebSights, WebViewer, WorkGroup SQL Server, XA-Library, XA-Server, and XP Server are trademarks of Sybase, Inc. 2/99

Unicode and the Unicode Logo are registered trademarks of Unicode, Inc.

All other company and product names used herein may be trademarks orregistered trademarks of their respective companies.

Acknowledgements

Larry Ewing, and the GIMP (General Image Manipulation Program) for the use ofthe Linux 2.0 Penguin.

Restricted Rights

Use, duplication, or disclosure by the government is subject to the restrictions setforth in subparagraph (c)(1)(ii) of DFARS 52.227-7013 for the DOD and as set forthin FAR 52.227-19(a)-(d) for civilian agencies.

Sybase, Inc., 6475 Christie Avenue, Emeryville, CA 94608.

Installation Guide for Linux/Intel v

Table of Contents

About This BookAudience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiiHow To Use This Book. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiiRelated Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xivOther Sources of Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi

Sybase Certifications on the Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviiConventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviiiIf You Need Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix

1. OverviewInstallation Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1User Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1Product Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Installation and Setup Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

DSLISTEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6DSQUERY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6PATH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6SYBASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6Shared Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

Sybase Installation Directory ($SYBASE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6Client/Server Communication (the interfaces File) . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7Adaptive Server Devices and System Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9

Master Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9sysprocsdev Device. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10Optional Devices and Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10

sybsecurity Device and Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10sybsystemdb Device and Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11Sample Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11sybsyntax Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11dbccdb Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11

What’s Next? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12

2. Installation RequirementsSystem Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

vi Table of Contents


Product Disk Space Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2Language Module Sizes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2Adaptive Server Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3What’s Next? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

3. Unloading Server Products from Distribution MediaOverview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1Pre-Unloading Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1Unloading Using Red Hat Package Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3Unloading in an X-Windows Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4Installing the Java Runtime Environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9What’s Next? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10

4. Installing Sybase ServersOverview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Installation Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2Pre-Installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Determining the Location, Type, and Size of a Database Device. . . . . . . 4-4Quick Start Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6

Beginning the Quick Start Installation Process . . . . . . . . . . . . . . . . . . . . . 4-7Continuing Quick Start Installation – Adaptive Server . . . . . . . . . . . . . . 4-8Continuing Quick Start Installation – Backup Server . . . . . . . . . . . . . . . 4-10Continuing Quick Start Installation – Monitor Server . . . . . . . . . . . . . . 4-12Continuing Quick Start Installation – XP Server . . . . . . . . . . . . . . . . . . . 4-14

Custom Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16Beginning the Custom Installation Process . . . . . . . . . . . . . . . . . . . . . . . 4-16Continuing Custom Installation – Adaptive Server . . . . . . . . . . . . . . . . 4-18Continuing Custom Installation – Backup Server . . . . . . . . . . . . . . . . . . 4-22Continuing Custom Installation – Monitor Server . . . . . . . . . . . . . . . . . 4-26Continuing Custom Installation – XP Server . . . . . . . . . . . . . . . . . . . . . . 4-29

Viewing the Installation Status Output Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31Changing the Default Language and Character Set . . . . . . . . . . . . . . . . . . . . . . . . . 4-31Installation Complete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-32Resource File Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-32

Editing a Resource File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33Editing a Sample Resource File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33Editing a Resource File Created by srvbuild . . . . . . . . . . . . . . . . . . . . 4-33Resource File Attributes for Adaptive Server . . . . . . . . . . . . . . . . . . 4-33Resource File Attributes for Backup Server . . . . . . . . . . . . . . . . . . . . 4-34

Installation Guide for Linux/Intel vii


Using srvbuildres . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-35Resource File Installation Complete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-36

Post-Installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-36Verifying That Servers Are Running . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-36Setting the Sybase System Administrator Password. . . . . . . . . . . . . . . . 4-36Information Required for XP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-37

What’s Next? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-37

5. Installing Sybase PC-Client ProductsPreinstallation Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1Installing PC Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1Configuring Network Connections for Client Products . . . . . . . . . . . . . . . . . . . . . . . 5-4

Adding a Server to the sql.ini File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4Enabling TCP Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6

Installing the Adaptive Server Plug-In for Sybase Central . . . . . . . . . . . . . . . . . . . . . 5-6Installing the Plug-In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7Installing the Required Microsoft DLL on Windows 95 . . . . . . . . . . . . . . 5-7

Checking the Current File Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7Replacing the File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8

Running the Japanese Version of the Plug-In . . . . . . . . . . . . . . . . . . . . . . . 5-8Installing the Java Runtime Environment. . . . . . . . . . . . . . . . . . . . . . . . . . 5-8Installing Java Utilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9

Installing jisql and ribo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9Installing the Java Development Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10

System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11What’s Next? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12

6. Upgrading Sybase ServersOverview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1Pre-Upgrade Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Verifying Your Adaptive Server Environment . . . . . . . . . . . . . . . . . . . . . . 6-2Preparing Your Server for Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3Increasing the Size of the sybsystemprocs Database . . . . . . . . . . . . . . . . . . 6-7

Increasing the Size of sybsystemprocs Only . . . . . . . . . . . . . . . . . . . . . . 6-7Increasing sybsystemprocs Beyond the Capacity of sysprocsdev . . . . . 6-8

Upgrading a Database That Uses Auditing . . . . . . . . . . . . . . . . . . . . . . . 6-10Preparing to Upgrade with Replicated Databases. . . . . . . . . . . . . . . . . . 6-11

Upgrading Adaptive Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11Using sqlupgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12

viii Table of Contents


Using sqlupgraderes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15Editing a Resource File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15Upgrading using sqlupgraderes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17

Post-Upgrade Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17Verifying That Servers Are Running . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17Restoring Functionality in Adaptive Server . . . . . . . . . . . . . . . . . . . . . . . 6-18

Upgrading Backup Server, Monitor Server, and XP Server . . . . . . . . . . . . . . . . . . . . 6-21What’s Next? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21

7. Adding Optional Functionality to Adaptive ServerInstalling Auditing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Audit System Devices and Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1The sybsecurity Device and Database. . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1Tables and Devices for the Audit Trail . . . . . . . . . . . . . . . . . . . . . . . . . 7-2Device for syslogs Systems Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2

Overview of Audit Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2Pre-Installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2Audit Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3

Creating a Device for an Audit Table . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4Creating a Device for the Audit Database Transaction Log. . . . . . . . 7-6Enabling Auditing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8Deleting a Device Entry. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8Changing a Device Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9

Installing Two-Phase Commit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9About Two-Phase Commit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9Enhancements to Two-Phase Commit . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10

spt_comittab Moved to sybsystemdb . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10Improved Performance for the Commit Identifier . . . . . . . . . . . . . . 7-10

Configuring for Two-Phase Commit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11Installing Online Help for Transact-SQL Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12

Online Syntax Help: sp_syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12Default Device for the sybsyntax Database . . . . . . . . . . . . . . . . . . . . . . . . 7-13Installing sybsyntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14

Installing Sample Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16Default Devices for Sample Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16pubs2 and pubs3 Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16

Installing the pubs2 and pubs3 Databases . . . . . . . . . . . . . . . . . . . . . . 7-17interpubs Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-18

Installing the interpubs Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-18jpubs Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-18

Installation Guide for Linux/Intel ix


Installing the jpubs Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-19Maintaining the Sample Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-19

8. Starting and Stopping ServersOverview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1Starting Servers From the UNIX Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Using the Runserver File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2Using the startserver Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2Using the monserver Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3

Starting Servers When the Operating System Restarts . . . . . . . . . . . . . . . . . . . . . . . 8-3Stopping Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3

Stopping Adaptive Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4Stopping Backup Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4Stopping Monitor Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5Using the kill Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5Shutdown and Shared Memory Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7

9. TroubleshootingOverview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1Error Log Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

For Installation Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2For Sybase Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2

Solutions to Common Installation Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2You Do Not Have a 17-Inch Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3If sybsetup Prompts for a Customer Authorization String (CAS). . . . . . . 9-3Cannot Eject the CD from the Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3DISPLAY Environment Variable Not Set Correctly . . . . . . . . . . . . . . . . . . 9-3Connection Refused; Client Not Authorized to Connect to Server. . . . . 9-4Address Already in Use. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4Adaptive Server Failed to Boot. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5Cannot Start XP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5Pre-Upgrade Eligibility Test Failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5

A. Preparing to Upgrade Servers with Replicated DatabasesSuspend Transaction Activity in the Databases and Suspend Replication . . . . . . . . A-1Drain Transaction Logs for Primary Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2

Manually Draining the RSSD Transaction Log. . . . . . . . . . . . . . . . . . . . . A-3Disable the LTM Truncation Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4

x Table of Contents


Drain Each Replicated Primary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4Restore Replication After Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6Shut Down Replication Servers and LTMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6Upgrade Adaptive Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6

Index

Installation Guide for Linux/Intel xi

List of Tables

Table 1-1: Product descriptions .....................................................................................................1-2Table 1-2: Installation and setup utilities .....................................................................................1-5Table 2-1: System requirements for Adaptive Server.................................................................2-1Table 2-2: System requirements for client products ...................................................................2-1Table 2-3: Product disk space requirements ................................................................................2-2Table 2-4: Language module sizes ................................................................................................2-2Table 2-5: Adaptive Server specifications for Linux...................................................................2-3Table 3-1: Adding SYBASE and $SYBASE/bin to the PATH environment variable .............3-3Table 3-2: Summary of steps after unloading Adaptive Server..............................................3-10Table 4-2: Adaptive Server database devices ..............................................................................4-4Table 4-3: Resource file attributes for Adaptive Server............................................................4-34Table 4-4: Resource file attributes for Backup Server ...............................................................4-35Table 5-1: System requirements for Windows NT and Windows 95 .....................................5-11Table 5-2: System requirements for UNIX .................................................................................5-11Table 6-1: Resource file attributes for upgrading Adaptive Server........................................6-16Table 7-1: sp_syntax installation scripts .....................................................................................7-13Table 9-1: Error log locations for installation utilities ................................................................9-2Table 9-2: Error log locations for Sybase servers.........................................................................9-2

xii List of Tables


Installation Guide for Linux/Intel xiii

About This Book

This guide, Installation Guide for Linux/Intel, provides:

• An overview of the Sybase® Adaptive Server™ Enterpriseinstallation infrastructure

• Instructions for installing and upgrading Adaptive Server, andinstalling Backup Server™, Monitor Server, XP Server™, andclient products, including the Adaptive Server plug-in for SybaseCentral™

• Instructions for installing optional Adaptive Server functionality,such as auditing, sample databases, and two-phase committransactions, and localization information

Audience

This guide is written for Sybase System Administrators and otherqualified installers who are familiar with their system’senvironment, networks, disk resources, and media devices.

How To Use This Book

This book contains the following chapters:

• Chapter 1, “Overview,” provides product definitions and anoverview of the installation process and the Adaptive Serverinstallation infrastructure.

• Chapter 2, “Installation Requirements,” provides descriptionsand system-related information such as required RAM and diskspace for all Adaptive Server server and client products for thisrelease.

• Chapter 3, “Unloading Server Products from DistributionMedia,” describes how to unload Adaptive Server products fromthe distribution media to your system.

• Chapter 4, “Installing Sybase Servers,” describes three ways toinstall Adaptive Server: Quick Start installation, custominstallation, and resource file installation. This chapter alsoprovides instructions for changing the language used for servermessages.

xiv About This Book

Related Documents Adaptive Server Enterprise Version 11.9.2

• Chapter 5, “Installing Sybase PC-Client Products,” describes howto install Adaptive Server client products like the AdaptiveServer plug-in to Sybase Central and SQL Advantage®.

• Chapter 6, “Upgrading Sybase Servers,” describes how toupgrade an existing Adaptive Server to the current release.

• Chapter 7, “Adding Optional Functionality to Adaptive Server,”describes how to install additional functionality such as auditing,sample databases that can be used for learning Transact-SQL®,and two-phase commit.

• Chapter 8, “Starting and Stopping Servers,” describes thedifferent methods of starting and stopping Adaptive Server,Backup Server, and other servers.

• Chapter 9, “Troubleshooting,” provides installation errormessages and possible solutions to installation problems.

• Appendix A, “Preparing to Upgrade Servers with ReplicatedDatabases,” provides instructions on how to prepare for anAdaptive Server upgrade if you are running Replication Serveron your system.

• Appendix B, “Installing and Using the Performance ArchiveDatabase,” provides instructions on how to install thePerformance Archive Database to obtain real-time performanceand tuning recommendations from Sybase.

Related Documents

The following table lists the documents you need for installing andusing Adaptive Server Enterprise and Adaptive Server EnterpriseMonitor™.

See This Document For This Purpose

Adaptive Server Enterprise

Release Bulletin To review last-minute product ordocument information that wastoo late to be included in thebooks.

New Functionality in Adaptive ServerEnterprise 11.9.2

To learn about the newfunctionality available inAdaptive Server version 11.9.2.

Installation Guide for Linux/Intel xv

Adaptive Server Enterprise Version 11.9.2 Related Documents

Installing Adaptive Server To install or upgrade AdaptiveServer and Sybase-relatedproducts.

Configuring Adaptive Server To customize setup andfunctionality.

What’s New in Adaptive Server Enterprise? To review the new features andsystem changes in AdaptiveServer version 11.5.

Navigating the Documentation for AdaptiveServer

To access online links to theconcepts and syntax in theAdaptive Server documentation.This online document is task-oriented.

Transact-SQL User’s Guide To learn about Transact-SQL,Sybase’s enhanced version of therelational database language.

System Administration Guide To learn about administeringservers and databases inAdaptive Server.

Adaptive Server Reference Manual As a reference to Adaptive Servercommands, functions, systemprocedures, and datatypes.

Managing and Monitoring Sybase AdaptiveServer Enterprise

To manage Adaptive ServerEnterprise and monitor itsactivities using Sybase Central.

Performance and Tuning Guide To tune Adaptive Server formaximum performance.

Utility Programs for UNIX Platforms As a reference to Adaptive Serverutilities.

Security Administration Guide As a System Administrator, tolearn how to administer a secureoperating environment andcontrol user access to data.

Security Features User’s Guide As a non-administrative user, tolearn how to use the securityfeatures of Adaptive Server.

Quick Reference Guide As a quick reference to AdaptiveServer 11.5 syntax andcommands.


xvi About This Book

Other Sources of Information Adaptive Server Enterprise Version 11.9.2

Other Sources of Information

Use the Sybase Technical Library CD and the Technical Library Website to learn more about your product:

• Technical Library CD contains product manuals and technicaldocuments and is included with your software. The DynaTextbrowser (included on the Technical Library CD) allows you toaccess technical information about your product in an easy-to-use format.

Refer to the Technical Library Installation Guide in yourdocumentation package for instructions on installing andstarting Technical Library.

• Technical Library Web site includes the Product Manuals site,which is an HTML version of the Technical Library CD that youcan access using a standard Web browser. In addition, you’ll findlinks to the Technical Documents Web site (formerly known asTech Info Library), the Solved Cases page, and Sybase/Powersoftnewsgroups.

To access the Technical Library Web site, go tosupport.sybase.com, click the Electronic Support Services tab,and select a link under the Technical Library heading.

Troubleshooting and Error Messages Guide To resolve system problems andfrequently occurring errormessages.

Adaptive Server Glossary To find definitions of technicalterms used in the Adaptive Serverdocumentation.

Adaptive Server Enterprise Monitor

Release Bulletin To review last-minute product ordocument information that wastoo late to be included in thebooks.

Adaptive Server Enterprise MonitorHistorical Server User's Guide

To set up and use HistoricalServer.

Adaptive Server Enterprise Monitor ServerUser's Guide

To set up and use Monitor Server.

Adaptive Server Enterprise Monitor ClientLibrary Programmer’s Guide

To write Monitor Client Libraryapplications.


Installation Guide for Linux/Intel xvii

Adaptive Server Enterprise Version 11.9.2 Other Sources of Information

Sybase Certifications on the Web

Technical documentation at the Sybase Web site is updatedfrequently.

For the latest information on product certifications and/or the EBF Rollups:

1. Point your Web browser to Technical Documents at thefollowing Web site:

techinfo.sybase.com

2. In the Browse section, click on the Hot entry.

3. Explore your area of interest: Hot Docs covering various topics,or Hot Links to Technical News, Certification Reports, PartnerCertifications, and so on.

If you are a registered SupportPlus user:


techinfo.sybase.com


3. Click on the EBF Rollups entry.

You can research EBFs using Technical Documents, and you candownload EBFs using Electronic Software Distribution (ESD).

4. Follow the instructions associated with the SupportPlusSM

Online Services entries.

If you are not a registered SupportPlus user, and you want to become one:

You can register by following the instructions on the Web.

To use SupportPlus, you need:

• A Web browser that supports the Secure Sockets Layer (SSL),such as Netscape Navigator 1.2 or later

• An active support license

• A named technical support contact

• Your user ID and password

xviii About This Book

Conventions Adaptive Server Enterprise Version 11.9.2

Whether or not you are a registered SupportPlus user:

You may use Sybase’s Technical Documents. Certification Reportsare among the features documented at this site.


techinfo.sybase.com


3. Click on the topic that interests you.

Conventions

The following style conventions are used in this manual:

• In a sample screen display, commands you should enter exactlyas shown are given in:

this font

• In a sample screen display, words that you should replace withthe appropriate value for your installation are shown in:

this font

• In the regular text of this document, the names of files anddirectories appear in this font:

/usr/u/sybase

• The names of programs, utilities, procedures, and commandsappear in this font:

sybsetup

• Commands for both the C shell and the Bourne shell are providedin this document, when they differ. The initialization file for the Cshell is called .cshrc. The initialization file for the Bourne shell iscalled .profile. If you are using a different shell, such as the Kornshell, refer to your shell-specific documentation for the correctcommand syntax.

Installation Guide for Linux/Intel xix

Adaptive Server Enterprise Version 11.9.2 If You Need Help

The following table shows the conventions for syntax statements inthis manual.

If You Need Help

Each Sybase installation that has purchased a support contract hasone or more designated people who are authorized to contact SybaseTechnical Support. If you cannot resolve a problem using themanuals or online help, please have the designated person contactSybase Technical Support or the Sybase subsidiary in your area.

Key Definition

command Command names, command option names, utilitynames, utility flags, and other keywords are in bold.

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

{ } Curly braces indicate that you choose at least one ofthe enclosed options. Do not include braces in youroption.

[ ] Brackets mean choosing one or more of the enclosedoptions is optional. Do not include brackets in youroption.

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

| The vertical bar means you can select only one of theoptions shown.

, The comma means you can choose as many of theoptions shown as you like, separating your choiceswith commas to be typed as part of the command.

xx About This Book

If You Need Help Adaptive Server Enterprise Version 11.9.2

Installation Guide for Linux/Intel 1-1

1 Overview 1.

This chapter introduces important concepts about the installation ofAdaptive Server and related products.

Topics covered include:

• Installation Definitions 1-1

• User Roles 1-1

• Product Descriptions 1-2

• Installation and Setup Utilities 1-4

• Environment Variables 1-5

• Sybase Installation Directory ($SYBASE) 1-6

• Client/Server Communication (the interfaces File) 1-7

• Adaptive Server Devices and System Databases 1-9

• What’s Next? 1-12

Installation Definitions

In this book, these terms are defined as follows:

• Unload – to copy Adaptive Server products from the distributionmedia to your machine, using the sybsetup or the Redhat PackageManager (RPM) utility.

• Install – to make the Adaptive Server products fully functionalby configuring various attributes, using the srvbuild utility.

• Upgrade – to configure an existing Adaptive Server (or SQLServer) to a more recent Adaptive Server version level.

User Roles

The Adaptive Server installation and setup process defines varioususer roles. Different user roles have different responsibilities andprivileges. These user roles clarify the way Adaptive Server is to beintegrated into your system:

• Operating System Administrator – The individual whomaintains the operating system. This individual has superuser or“root” privileges.

1-2 Overview

Product Descriptions Adaptive Server Enterprise Version 11.9.2

• System Administrator – The individual in charge of AdaptiveServer system administration, creating user accounts, assigningpermissions on databases, and creating new databases. Atinstallation time, the System Administrator’s login name is “sa”.The “sa” login is not a UNIX login. The “sa” login is specific toAdaptive Server and is used to log in to Adaptive Server usingthe isql command.

• Sybase Login – The “sybase” login is a UNIX login that owns allthe Sybase installation directories and files, sets permissions onthose directories and files, and performs the installation andupgrading of Adaptive Server.

Product Descriptions

Table 1-1 provides a description of the server and client products inyour Adaptive Server package.

Table 1-1: Product descriptions

Product Description

Adaptive Server The relational database server. The default unloading processincludes:

• Adaptive Server

• Backup Server

• Monitor Server

• XP Server

• Adaptive Server utilities

• Scripts and configuration files

Adaptive Server Plug-In toSybase Central™

Sybase Central is a common framework for managing servers. Itallows you to manage Adaptive Server installations using the SybaseCentral graphical management tool. You can manage Adaptive Serverrunning on any platform from a PC that is running Windows 95 orWindows NT.

For information on how to use Sybase Central to manage AdaptiveServer, see Managing and Monitoring Sybase Adaptive Server Enterprise.


Adaptive Server Enterprise Version 11.9.2 Product Descriptions

Adaptive Server EnterpriseMonitor

An Open Server™ application that obtains performance statistics onAdaptive Server and makes those statistics available to MonitorServer client applications.

Adaptive Server Enterprise Monitor (also called Monitor Server)includes:

• Monitor Server for Adaptive Server Enterprise 11.9.x – an OpenServer application that obtains performance statistics on AdaptiveServer and makes those statistics available to monitors in SybaseCentral, Monitor Historical Servers, and applications built withMonitor Client Library. Monitor Server for SQL Server 11.0.x is alsoavailable.

• Adaptive Server plug-in for Sybase Central – this graphical userinterface obtains Adaptive Server performance data from MonitorServer and displays the data, in real time, in tables and graphs.

• Monitor Client Library – a programming interface that providesaccess to Adaptive Server performance data.

• Monitor Historical Server – an Open Server application thatobtains performance statistics for many Adaptive Servers viaMonitor Servers and records the data to specified file locations.

Backup Server Backup Server is an Open Server-based application that manages alldatabase backup (dump) and restore (load) operations for AdaptiveServer. Backup Server provides the following features:

• Allows you to use up to 32 dump devices (this is called dumpstriping) in parallel to dump or load a single database ortransaction log.

• Allows one dump to span multiple tapes or allows multiple dumpsto be made to a single tape.

• Allows dumping and loading over the network to or from a deviceon another machine.

• Provides automated determination of tape device characteristics,by using operating system commands, for a dump operation.

• Platform-specific tape handling options support dump and loadcommand syntax specification for volume naming, dismount andload control, tape density, block size, tape capacity, days to retain,initialization, file naming for multidump volumes, and listingheader or file information.

Install Backup Server if you plan to back up and restore databases inAdaptive Server. Backup Server is unloaded, by default, when youunload Adaptive Server software from the distribution media. Usethe srvbuild utility to set up Backup Server and to connect BackupServer and Adaptive Server through the interfaces file.

Table 1-1: Product descriptions (continued)

Product Description

1-4 Overview

Installation and Setup Utilities Adaptive Server Enterprise Version 11.9.2

Installation and Setup Utilities

Table 1-2 lists the Adaptive Server installation and setup utilities youcan use to unload, install, upgrade, or customize Adaptive Serverand its products on UNIX systems. Use of these utilities is not

Language Modules (Server) Provides system messages and date/time formats to help you localizeyour applications. Default installation includes the us_englishlanguage module and the following character sets:

• cp437 – IBM CP437, U.S. code set

• cp850 – IBM CP850, European code set

• iso_1 – ISO 8859-1, Latin-1

• mac – Standard Macintosh coding

• roman8 – HP Roman-8

Other languages for Adaptive Server and Sybase client products areFrench, German, and Japanese. Language modules for Spanish,Korean, Brazilian Portuguese, and Simplified Chinese are alsoavailable for Adaptive Server.

For more information on server language modules and character sets,see Configuring Adaptive Server for UNIX Platforms, version 11.5.1.

Language Modules(Connectivity)

Provides messages and support files for running Open Client™applications in various languages.

ODBC Driver Allows Windows NT client applications to access Adaptive Serverdata.

Open Client Provides libraries and utilities for developing any Open Clientapplication.

XP Server An Open Server application that manages and executes extendedstored procedures (ESPs) from within Adaptive Server. ESPs providea method for calling procedural language functions from withinAdaptive Server.

XP Server is unloaded, by default, when you unload Adaptive Serversoftware from the distribution media. Use the srvbuild utility to set upXP Server and to connect XP Server and Adaptive Server through theinterfaces file.

Table 1-1: Product descriptions (continued)

Product Description


Adaptive Server Enterprise Version 11.9.2 Environment Variables

described in this installation guide. For information see ConfiguringAdaptive Server for UNIX Platforms.

Environment Variables

It is crucial to the operation of Sybase products that you set thesystem environment variables correctly. Environment variables areset in the user’s environment either interactively or by includingthem in the user’s .login and .cshrc files (for C shell) or .profile file (forBourne shell). The installation instructions in this guide explainwhen to set these variables.

Table 1-2: Installation and setup utilities

Utility Use To Environment

dscp Modify the interfaces file. Interactive, text-based interface

dsedit Modify the interfaces file. X-Windows/Motif GUI

sqlloc Modify localization settings, such aslanguage and character set.

X-Windows/Motif GUI

sqllocres Modify localization settings, such aslanguage and character set, using a resourcefile.

Use of this utility is not described in thisinstallation guide. For information on usingsqllocres, see Utility Programs for UNIXPlatforms.

Noninteractive, file-basedinterface

sqlupgrade Upgrade Adaptive Server. X-Windows/Motif GUI

sqlupgraderes Upgrade Adaptive Server using a resourcefile.


srvbuild Build a functional server. X-Windows/Motif GUI

srvbuildres Build a functional server using a resourcefile.


sybsetup • Provide a main selection menu fromwhich to select the installation or setuptask you want to perform.

• Unload Adaptive Server products fromdistribution media.

X-Windows/Motif GUI

1-6 Overview

Sybase Installation Directory ($SYBASE) Adaptive Server Enterprise Version 11.9.2

DSLISTEN

The DSLISTEN environment variable defines the name AdaptiveServer uses to listen for client connections if no name is given duringthe Adaptive Server start-up. If DSLISTEN is not set, and no name isgiven during the Adaptive Server start-up, the Adaptive Servername defaults to the server name given at installation.

DSQUERY

The DSQUERY environment variable defines the Adaptive Servername that client programs try to connect to if no Adaptive Server isspecified with a command line option. If DSQUERY is not set, andyou do not supply the Adaptive Server name with a command lineoption, clients attempt to connect to the server name given atinstallation.

PATH

The PATH environment variable specifies which directory path tosearch for executables. The Sybase executables are located in the$SYBASE/bin directory.

SYBASE

The SYBASE environment variable defines the path of the Sybaseinstallation directory. The installation program uses the SYBASEenvironment variable during installation.

Shared Libraries

The name of the shared library environment variable is different foreach UNIX platform. Chapter 3, “Unloading Server Products fromDistribution Media,” defines this environment variable for yourplatform.

Sybase Installation Directory ($SYBASE)

The Sybase installation directory structure is created by theinstallation process. Adaptive Server is placed in the directory you


Adaptive Server Enterprise Version 11.9.2 Client/Server Communication (the interfaces File)

indicate when you run sybsetup. Figure 1-1 illustrates a portion of theAdaptive Server installation directory structure.

Figure 1-1: Adaptive Server installation directory structure

The Adaptive Server installation directory contains executable filesand administrative tools, which are added as each product isinstalled.

Client/Server Communication (the interfaces File)

Adaptive Server communicates with other Adaptive Servers, OpenServer applications (such as Backup Server), and client software onyour network. Clients can talk to one or more servers, and serverscan communicate with other servers, by remote procedure calls.

For Sybase products to interact with one another, each product needsto know where the others reside on the network. This information is

bin

charsets

init

install

locales

Executable files (such as bcp, isql, and dataserver)

Character set and sort order definition files

Support directories

Install programs, setperm files, runserver files

Localization files for language support

scripts SQL scripts, including sample database installation scripts

upgrade Upgrade programs

SYBASE

$

1-8 Overview

Client/Server Communication (the interfaces File) Adaptive Server Enterprise Version 11.9.2

stored in an interfaces file, named interfaces on UNIX platforms,located in the Adaptive Server installation directory. After yourAdaptive Server or client software is installed, it can connect withany server on the network that is listed in the interfaces file.

The interfaces file is like an address book. It lists the name andaddress of every known server. When you are using a clientprogram, and you want to connect with a particular server, the clientprogram looks up the server name in the interfaces file and connectsto that server (see Figure 1-2). You can supply the name of the serverby using the DSQUERY environment variable.

On TCP/IP networks, the port number gives clients a way to identifythe Adaptive Server to which they want to connect. It also tellsAdaptive Server where to listen for incoming connection attemptsfrom clients. Adaptive Server uses a single port for these two services(referred to as query service and listener service).

On SPX networks, the socket number gives clients and servers a wayto identify each other.

Figure 1-2: Communicating with a server

During installation, you use the srvbuild utility to create a new server.The srvbuild process adds entries to the interfaces file for your newAdaptive Server, Backup Server, Monitor Server, and XP Server.

For instructions on using dsedit or dscp to modify interfaces file entriesor to create new interfaces file entries for existing servers, seeConfiguring Adaptive Server for UNIX Platforms.

“Connect meto the TEST

Adaptive Server.”

TEST

interfaces file

DSQUERY =

TEST

$SYBASE/interfaces

DataWorkbench

TEST

Adaptive Server


Adaptive Server Enterprise Version 11.9.2 Adaptive Server Devices and System Databases

Adaptive Server Devices and System Databases

Devices are files or portions of a disk that are used to store databasesand database objects. You can initialize devices, using raw diskpartitions (for production systems) or operating system files (fornonproduction uses).

Adaptive Server requires the following devices:

• Master device – to store system databases

• sysprocsdev device – to store system procedures

The master and sysprocsdev devices are created by srvbuild when youcreate a new Adaptive Server.

Master Device

The master device contains the following databases:

• master – controls the operation of Adaptive Server as a whole andstores information about all users, user databases, devices,objects, and system table entries. The master database is containedentirely on the master device and cannot be expanded onto anyother device.

• model – provides a template for new user databases. The modeldatabase contains required system tables, which are copied into anew user database with the create database command.

• tempdb – the work area for Adaptive Server. Each time AdaptiveServer is started the tempdb database is cleared and rebuilt fromthe model database.

The sample databases are stored on the master device at installation,but should be moved to a user-defined device after installation. Forinformation on the sample databases, see “Optional Devices andDatabases” on page 1-10.

➤ NoteFor recovery purposes, Sybase recommend that you not create other

system or user databases or user objects on the master device.

1-10 Overview

Adaptive Server Devices and System Databases Adaptive Server Enterprise Version 11.9.2

sysprocsdev Device

The sysprocsdev device stores the sybsystemprocs database, whichcontains most of the Sybase-supplied system procedures. Systemprocedures are a collection of SQL statements and flow-of-controlstatements that perform system tasks; for example, sp_configure.System procedure names begin with “sp_”.

The system procedures that are needed during recovery situationsare stored in the master database.

➤ Notesysprocsdev is the default system name for this device. However, it is

frequently referred to as the sybsystemprocs device, since it stores the

sybsystemprocs database.

Optional Devices and Databases

The following devices and databases are needed only if youconfigure Adaptive Server for optional functionality, like auditing ortwo-phase commit transactions.

sybsecurity Device and Database

The sybsecurity device stores the sybsecurity database and theauditing system procedures with which you can configure auditingfor your system.

The auditing system records system security information in anAdaptive Server audit trail. You can use this audit trail to monitor theuse of Adaptive Server or system resources.

Install auditing using the auditinit utility. The sybsecurity device iscreated as part of the auditing installation process.

See Chapter 7, “Adding Optional Functionality to Adaptive Server,”for instructions on how to configure Adaptive Server for auditing.

The auditing system is discussed in more detail in the SecurityAdministration Guide.


Adaptive Server Enterprise Version 11.9.2 Adaptive Server Devices and System Databases

sybsystemdb Device and Database

The sybsystemdb device stores the sybsystemdb database, which storesinformation about two-phase commit transactions.

See Chapter 7, “Adding Optional Functionality to Adaptive Server,”for instructions on how to create the sybsystemdb device and databaseand how to configure Adaptive Server for two-phase commit.

Sample Databases

The pubs2 and pubs3 databases are sample databases provided as alearning tool for Adaptive Server. pubs2 is used for most of theexamples in the Adaptive Server documentation; other examples usepubs3. Both are available in U.S. English versions of Adaptive Server.

The interpubs database contain French and German data. jpubscontains Japanese data.

For information about installing the sample databases, see Chapter 7,“Adding Optional Functionality to Adaptive Server.”

For information on the contents of these sample databases, see theTransact-SQL User’s Guide.

sybsyntax Database

The syntax database, sybsyntax, contains syntax help forTransact-SQL commands, Sybase system procedures, AdaptiveServer utilities, and Open Client routines. Users can retrieve thisinformation using the system procedure sp_syntax.

For example, to see the syntax of the Transact-SQL select command,enter:

sp_syntax "select"

Adaptive Server includes scripts for creating the sybsyntax database.

See Chapter 7, “Adding Optional Functionality to Adaptive Server,”for instructions on how to install sybsyntax.

See the Adaptive Server Reference Manual for more information aboutsp_syntax.

dbccdb Database

The database consistency checker (dbcc) provides commands forchecking the logical and physical consistency of a database. The

1-12 Overview

What’s Next? Adaptive Server Enterprise Version 11.9.2

dbccdb database stores the results of dbcc when the dbcc checkstoragecommand is used.

dbcc checkstorage records configuration information for the targetdatabase, operation activity, and the results of the operation in thedbccdb database. Stored in the database are dbcc stored procedures forcreating and maintaining dbccdb and for generating reports on theresults of dbcc checkstorage operations.

Information on installing dbccdb is located in Chapter 18, “CheckingDatabase Consistency,” of the System Administration Guide.

What’s Next?

For Adaptive Server product descriptions, and server and databasespecifications, see Chapter 2, “Installation Requirements.”


2 Installation Requirements 2.

This chapter covers:

• System Requirements 2-1

• Product Disk Space Requirements 2-2

• Language Module Sizes 2-2

• Adaptive Server Specifications 2-3


For easier installation, make a copy of this chapter, so you have therequirements information available as you perform thepre-installation, installation, or upgrade procedures.

System Requirements

Table 2-1 shows the release-level, RAM, and network-protocolrequirements for Adaptive Server.

Table 2-2 lists the RAM required for client products.

Table 2-1: System requirements for Adaptive Server

Platform and Operating System Release Level RAM Required Network Protocol

Linux Intel Certified on Kernel VersionLinux 2.2.5 CommonRuntime Environmentglibc-2.0.7-29

32MBrequired;128MB+recommended

TCP/IP Sockets

Table 2-2: System requirements for client products

Product RAM Required

Monitor Client Library 16MB (32MB recommended)

Open Client/C 16MB

jisql 18MB

ribo 14MB

2-2 Installation Requirements

Product Disk Space Requirements Adaptive Server Enterprise Version 11.9.2

Product Disk Space Requirements

Table 2-3 lists the disk space requirements for each product.

Language Module Sizes

Table 2-4 lists the sizes for the Adaptive Server and Open ClientLanguage Modules.

Table 2-3: Product disk space requirements

Product and Version Level Disk Space Required

Adaptive Server 11.9.2 140MB

Open Client/C 11.1.1 52MB

Language Modules (Server 11.9.2) 2–7MB per language

Language Modules (Open Client 11.1.1) 3–6MB per language

Monitor Server 11.9.2 1.6MB

Monitor Historical Server 11.9.2 - NT 2.9MB

Monitor Client Library 11.9.2 - NT 4.0MB

jisql 2.0MB

ribo 14KB

Table 2-4: Language module sizes

Language Size of Adaptive ServerLanguage Module

Size of Open ClientLanguage Module

Brazilian Portuguese 6.5MB 1.2MB

Chinese (simplified) 2MB 1.2MB

French 6.5MB 1.5MB

German 6.5MB 1.5MB

Japanese 4.5MB 1.2MB

Korean 2MB 1.2MB

Spanish 6.5MB 1.2MB


Adaptive Server Enterprise Version 11.9.2 Adaptive Server Specifications

Adaptive Server Specifications

This section provides Adaptive Server specifications for Linux.

Table 2-5: Adaptive Server specifications for Linux

Hardware

Processor 32-bit Intel 486

Minimum RAM required forAdaptive Server

>32MB 16,000 2K pages

Minimum RAM per additionaluser

80K With default stack size, packetsize, and user log cache size

Default user stack size 34,816 bytes Minimum 26,624 bytes

Database Specifications

Databases per Adaptive Server 32,767 Practical limit is approximately100

Default database size 2MB Minimum 2MB

Maximum database size 242

(4TB)Maximum device size * 128devices per database

Maximum size of a databasedevice (disk partition)

235

(32GB)• Requires Solaris 2.5.1 or later

• 2GB maximum device size ifusing operating system files

• 32GB device size withoperating system files will besupported with Solaris 2.7

Maximum number of databasedevices per server

256

Maximum number of devicesor device pieces per database

128

Maximum number of segmentsper database

31

master database 5MB

7MB

Minimum required for a newinstallation

Minimum required for anupgrade

model database 2MB

3MB




Adaptive Server Specifications Adaptive Server Enterprise Version 11.9.2

tempdb database 2MB

3MB



sybsystemprocs database 45MB

60MB


Recommended for an upgrade

pubs2 database 2MB

3MB



pubs3 database 2MB

3MB



interpubs database 2MB

3MB



jpubs database 2MB

3MB



Table Specifications

User objects per database 231 – 100

Columns per table 250

Indexes per table 250 (one clusteredindex)

Rows per table Limited byavailable storage

Maximum 232

Maximum user data per row 1960 bytes

Maximum number of databytes per text/image page

1800 bytes

Columns per composite index 31

Bytes per index key 600

Creation of clustered index Free space neededon segment is1.2 * (size of table)

For sorted data, approximately20% of the table size needed

Table 2-5: Adaptive Server specifications for Linux (continued)


Adaptive Server Enterprise Version 11.9.2 What’s Next?

What’s Next?

To unload Adaptive Server software to your system, see Chapter 3,“Unloading Server Products from Distribution Media.”

Characters per database objectname

30

Query Specifications

Maximum number of tables ina “union” query

256

Maximum number ofdatabases participating in onetransaction

16 Includes database wheretransaction began, all databaseschanged during transaction, andtempdb, if it is used for results orworktables

Practical number of databasesparticipating in one query

16 Includes each occurrence of eachdatabase queried and tempdb, if itis used for results or worktables

Maximum number of tablesparticipating in a query

16 Includes all worktables, resulttables, tables referenced by views(the view itself is not counted),correlations, and self-joins

Maximum number of tableswith referential integrityconstraints for a query

192

Procedure Specifications

Number of buffers andprocedure buffers

Configurable Limited by amount of RAM andmaximum size of shared memorysegment

Minimum memory requiredper stored procedure

2K

Maximum number ofparameters per storedprocedure

255

Table 2-5: Adaptive Server specifications for Linux (continued)




3 Unloading Server Productsfrom Distribution Media 3.

This chapter describes how to unload Adaptive Server Enterpriseserver products for UNIX from the Sybase distribution media ontoyour system.

To unload client products, see Chapter 5, “Installing Sybase PC-Client Products.”


• Overview 3-1

• Pre-Unloading Tasks 3-1

• Unloading in an X-Windows Environment 3-4


Overview

Unload the server product files from the distribution media to yourmachine, using the instructions provided in this chapter. When youhave finished unloading the products, either:

• Build the server products, using the instructions provided inChapter 4, “Installing Sybase Servers.”

• Upgrade server products, using the instructions provided inChapter 6, “Upgrading Sybase Servers.”

Pre-Unloading Tasks

Before unloading server products onto the system:

1. Read the release bulletins for the latest information on theproducts (Adaptive Server, Monitor Server, and so on) that youare unloading.

Your Sybase products shipment includes printed releasebulletins; they are also available at the Sybase Web site:

http://www.sybase.com

2. If you plan to run sybsetup on a remote machine, that machinemust have permission to display the sybsetup screens on the localmachine on which you are working. To give the remote machine

3-2 Unloading Server Products from Distribution Media

Pre-Unloading Tasks Adaptive Server Enterprise Version 11.9.2

permission to display screens on your local machine, enter thefollowing command at the UNIX prompt of your local machine:

xhost + remote_machine

where remote_machine is the machine on which you are runningsybsetup.

3. At the remote machine where you are running sybsetup, verifythat the DISPLAY environment variable is set to the localmachine on which you are viewing sybsetup screens and output.If sybsetup cannot find your DISPLAY variable, you cannot runthe graphical user interface.

For C shell:

setenv DISPLAY host_name :0.0

For Bourne shell:

DISPLAY=host_name :0.0; export DISPLAY

where host_name is the name of the local (display) machine.

4. Run sybsetup as root (uid=0). Under Linux, sybsetup invokes theRPM for correct product installation. The installation progressbar does not accurately indicate installation progress.

➤ NoteA post-installation script, $SYBASE/install/sybinstall.sh, is automatically

initiated by RPM during the sybsetup install. This script performs required

post-install actions. It attempts to create a Sybase account on your system

and to set the correct Sybase runtime environment variables.

5. Identify or create a directory location for the Sybase installationdirectory, where you unload the server products.

6. Verify that the directory location for the Sybase installationdirectory is in a UNIX file system that has sufficient space toaccommodate unloading the software.

Space requirements for Adaptive Server Enterprise products arelisted in Chapter 2, “Installation Requirements.”

7. Set the SYBASE environment variable to the path of the Sybaseinstallation directory. For example:

setenv SYBASE /opt/sybase

The SYBASE environment variable is used by the installationand setup utilities.


Adaptive Server Enterprise Version 11.9.2 Unloading Using Red Hat Package Manager

➤ NoteIf you are upgrading your current Adaptive Server (or SQL Server) to

Adaptive Server 11.9.2, set the SYBASE environment variable to the new

Sybase installation directory rather than your current installation.

8. RPM sets correct product permissions and ownership.

9. During post-installation, RPM creates a .profile file for Bourneshell and a .cshrc file for C shell. When you log in as sybase forthe first time after installation, check to see that the SYBASEenvironment variable is correctly set and that $SYBASE/bin is inyour search path.

Unloading Using Red Hat Package Manager

In the Linux platform, you can choose to unload Adaptive Serverwith either the Red Hat Package Manager (RPM) included in thestandard bundle by all Linux distributors, or Sybase’s sybsetup utility.

To unload Adaptive Server products using RPM:

1. Verify that you are logged in as the “root” superuser and thatyour environment is set up as described in “Pre-UnloadingTasks” on page 3-1.

2. Veryify that you have a directory called /opt on your server, andthat it has sufficient space to accommodate unloading thesoftware. If an /opt directory does not already exist, the LinuxRPM will create it in the root directory.

3. Place the Adaptive Server product CD in the CD-ROM drive.

4. At the # prompt, enter:

# mount -t iso9660 /dev/cdrom /mnt/cdrom

Table 3-1: Adding SYBASE and $SYBASE/bin to the PATH environment variable

OperatingSystem Shell After Unloading, Set SYBASE and PATH As Follows

Bourne (sh) export SYBASE = ‘rpm -q --queryformat ’%{installprefix}’ sybase-common‘

export PATH = “$SYBASE/bin: $PATH”

C (csh) setenv SYBASE ‘rpm -q --queryformat ’%{installprefix}’ sybase-common‘

set path = ($SYBASE/bin $path)


Unloading in an X-Windows Environment Adaptive Server Enterprise Version 11.9.2

5. Extract your Sybase products using RPM. For help on RPM,enter:

# /bin/rpm

➤ NoteAll products depend on the “sybase-common-11.9.2-1.i386.rpm” package.

Install the “sybase-common” package before you install any other package.

6. Unload all of your necessary Sybase products into the /opt/sybasedirectory by entering:

# rpm -hiv /mnt/cdrom/RPMS/sybase-ase-11.9.2-1.i386.rpm

➤ NoteThe packages can be relocated during installation using the

rpm(1) --relocate option. Refer to the rpm(1) manual pages for correct

command line instructions.

7. When unloading is complete, unmount the CD from the drive atyour # prompt by entering:

# umount /dev/cdrom

Remove the CD by entering:

# eject

You have now successfully unloaded Adaptive Server onto yoursystem; however, you do not yet have a fully functional product. Tocontinue, see “What’s Next?” on page 3-10.

Unloading in an X-Windows Environment

In an X-Windows environment, use the sybsetup utility to unloadfrom CD.

To unload Adaptive Server products:

1. Verify that your environment is set up as described in “Pre-Unloading Tasks” on page 3-1.

2. Place the Adaptive Server product CD in the CD-ROM drive.

3. If you are still logged in as the “sybase” user (from doing thepre-unloading tasks), log out.


Adaptive Server Enterprise Version 11.9.2 Unloading in an X-Windows Environment

4. Log in as “root” to the UNIX system attached to the CD-ROMdrive. You must have “root” permission to mount the CD.

This login can be either local or remote. If you are runningsybsetup from a machine that is not attached to the CD-ROM, youmust log in remotely.

5. Mount the CD-ROM:

# mount -t iso9660 /dev/cdrom /mnt/cdrom

➤ NoteWhen you mount the CD using the /etc/fstab directive, make sure to enable

the exec option. See the manual page on mount(8) for the directive.

6. Execute the sybsetup utility by entering the command:

# /mnt/cdrom/sybsetup

The sybsetup screen is displayed.



➤ NoteDepending on your platform, there may be slight differences between the

screen image on your terminal and the screen image presented in this

document. These differences do not affect the instructions provided.

7. Choose Unload Sybase Products from the sybsetup menu.

➤ Notejisql and ribo are not available on the Adaptive Server Enterprise CD. However, youcan run jisql and ribo on Linux. These utilities are included on the PC Client CD. See

the section titled “Installing jisql and ribo” on page 5-9 to learn how to install

these products.

The Installation Destination screen is displayed:

8. Verify that the location of the installation directory displayed bysybsetup is where you want to unload Sybase software.

sybsetup displays the value of the SYBASE environment variable,which you should have set as described in “Pre-UnloadingTasks” on page 3-1. For new installations, this is the value youwant to use.


Adaptive Server Enterprise Version 11.9.2 Unloading in an X-Windows Environment

◆ WARNING!If you are unloading for an upgrade, you must change the installationdirectory location so that it is different from the value of your currentinstallation; otherwise, the current installation will be overwritten, andthe upgrade will fail.

If the SYBASE environment variable is not set, set it as describedin “Pre-Unloading Tasks” on page 3-1.

To install in a location that is different from the locationdisplayed by sybsetup, change the directory location displayed onthe sybsetup screen. Changing the installation directory in sybsetupdoes not reset the SYBASE environment variable on yoursystem.

9. Click continue (the checkmark button).

The Installation Source Device screen is displayed.

10. Provide the device media and device location, and indicatewhether the source device is local or remote.

To specify a CD-ROM device:

a. Select CD-ROM (if not already selected by default).

b. Enter /mnt/cdrom/sybimage as the name of theCD-ROM image.

c. Select Local for the source device location (if it is not alreadyselected by default).



11. Click continue (the checkmark button).

The Product Selection screen is displayed.

12. At the top of the Product Selection screen, verify that theinstallation directory, media device, and machine name arecorrect.

If any part of this information is incorrect, return to the mainmenu of sybsetup and begin again.

13. Click each product you want to install.

After you make a product selection, the Disk Space Availablefield indicates the available space remaining in the installationdirectory.

If you unload any languages on Adaptive Server in addition tothe language you specify as the default, you may need to extendyour master database. Each server language requires 2–7MB inthe master database.

➤ NoteBy default, Backup Server and XP Server are unloaded with Adaptive

Server.

14. Click Continue to unload the products.

sybsetup displays the Installation Status screen, which shows theprogress of the unloading process.

➤ NoteUnloading the software may take half an hour or more, depending on the

performance of your machine and how many products you are unloading.

The progress meter is known not to show the progress of installation in this

release.

15. At the end of the unloading process, you are asked if you wantto install the sybsetup executable in the $SYBASE/bin directory.This allows you to run sybsetup and invoke the setup utilitieslater without remounting the CD.

16. Click Yes or No, depending on whether you want to installsybsetup in $SYBASE/bin.

The Success screen is displayed after sybsetup is successfullyunloaded.


Adaptive Server Enterprise Version 11.9.2 Installing the Java Runtime Environment

17. Unmount the CD-ROM:

# umount /mnt/cdrom

then enter:

# eject

18. You have successfully unloaded Adaptive Server onto yoursystem. To continue, see “What’s Next?” on page 3-10.

To install jisql and ribo, see “Installing jisql and ribo” on page 5-9.

To install the Java Runtime Environment, see “Installing the JavaRuntime Environment” on page 3-9.

Installing the Java Runtime Environment

If the Java Runtime Environment is not already installed on your PC,you can install it from the PC Client CD.

Follow these steps:

1. When the Sybase installation program displays, click Exit to quitthe installer.

2. Start the Windows NT Explorer.

3. Click the CD-ROM drive name to display the CD’s contents inthe Explorer.

4. In the Windows Explorer, navigate to the java directory on theCD.

5. Double-click jre116i-win32.exe.

6. Follow the instructions from the self-extracting zip file.



What’s Next?

To determine your next step, see Table 3-2.

Table 3-2: Summary of steps after unloading Adaptive Server

To Do This See

Perform a first-time installation of:

• Adaptive Server

• Backup Server

• Monitor Server

• XP Server

Chapter 4, “Installing Sybase Servers”

Install client products Chapter 5, “Installing Sybase PC-ClientProducts”

Upgrade an existing:

• Adaptive Server

• Backup Server

• Monitor Server

• XP Server

Chapter 6, “Upgrading Sybase Servers”

Configure and use Historical Server Sybase Adaptive Server EnterpriseMonitor Historical Server User’s Guide

Configure and use Monitor ClientLibrary

Sybase Adaptive Server EnterpriseMonitor Client Library Programmer’sGuide


4 Installing Sybase Servers 4.

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


• Overview 4-1

• Pre-Installation Tasks 4-3

• Quick Start Installation 4-6

• Custom Installation 4-16

• Viewing the Installation Status Output Screen 4-31

• Changing the Default Language and Character Set 4-31

• Installation Complete 4-32

• Resource File Installation 4-32

• Post-Installation Tasks 4-36


For information on how to upgrade an existing server, see Chapter 6,“Upgrading Sybase Servers.”

For information on how to install additional Adaptive Serverproducts, see Chapter 5, “Installing Sybase PC-Client Products.”

Overview

After you have unloaded the Adaptive Server product files from thedistribution media, you are ready to install one or more of thefollowing Sybase servers:

• Adaptive Server

• Backup Server

• Monitor Server

• XP Server

These products are described in Chapter 1, “Overview.”

4-2 Installing Sybase Servers

Overview Adaptive Server Enterprise Version 11.9.2

The basic process for installing Sybase servers is:

1. Perform the pre-installation tasks as described in “Pre-Installation Tasks” on page 4-3.

2. Perform the installation using any of the methods described in“Installation Methods” on page 4-2.

3. Perform the post-installation tasks as described in “Post-Installation Tasks” on page 4-36.

Installation Methods

You can install Sybase servers by using any of the followingmethods:

• Quick Start installation – use the srvbuild utility to install serverswith minimum customizing, using only system defaults andrequired parameters. Use the Quick Start method to install:

- A nonproduction prototype to test new features andfunctionality before going into production

- A default server to be used for training purposes

- A basic production server that requires no customizing to meetthe needs of your site

This method is described in “Quick Start Installation” on page4-6

• Custom installation – use the srvbuild utility to install servers withfull customization. This method allows you to override systemdefaults and adding parameters. Use this method to customizeservers for a production environment. Fully customizing a serverat installation time will reduce the need to make changes later.This method is described in “Custom Installation” on page 4-16

• Resource file installation – use the srvbuildres utility to installAdaptive Server and Backup Server at sites that want to installmultiple identical servers. Also enables installation if X-Windowsis not available. Monitor Server and XP Server cannot be installedusing resource files. This method is described in “Resource FileInstallation” on page 4-32.


Adaptive Server Enterprise Version 11.9.2 Pre-Installation Tasks

Pre-Installation Tasks

Before installing the Sybase servers:

1. Read the “Special Installation Instructions” section in the releasebulletin.

2. Verify that your operating system meets the release-level, RAM,and network-protocol requirements.

The operating system requirements are fully documented inChapter 2, “Installation Requirements.”

3. If you have not unloaded the Adaptive Server software from theCD onto your system, complete the procedures in Chapter 3,“Unloading Server Products from Distribution Media.”

4. Verify that your SYBASE environment variable is set to theSybase installation directory.

5. Verify that $SYBASE/bin has been added to the PATHenvironment variable.

6. Install operating system patches, if required.

Required operating system patches are described in the releasebulletin for the product (Adaptive Server, Monitor Server, and soon).

7. Verify that your network is configured to run in loopback mode.

Although Adaptive Server and Sybase client applications areinstalled on a machine that is not connected to a network, Sybasesoftware uses the network software, which must be configuredto run in loopback mode.

If you are having connection problems, or if you want to verifyyour network configuration, follow these steps:

a. Log in to your host machine with this UNIX command:

telnet host

This command gives you a login prompt for the same machine.

b. Without logging out, log in to your host machine again, usingthe same command.

c. Log out twice.

If you cannot log in to the machine a second time, your networksoftware is not properly configured to run in loopback mode. Seethe network software documentation, or consult your vendor.

8. Adjust shared memory segments.


Pre-Installation Tasks Adaptive Server Enterprise Version 11.9.2

Depending on the number and types of devices you use forbackup (dump) and recovery (load), you may need to adjust theshared memory segment parameter in the operating systemconfiguration file to accommodate concurrent Backup Serverprocesses. The default number of shared memory segmentsavailable for process attachments is 6.

9. Determine the location, type, and size of each database device.

You must provide this information during the installation ofAdaptive Server. Devices are operating system files or portionsof a disk (called raw partitions) used to store databases anddatabase objects. For details, see “Determining the Location,Type, and Size of a Database Device” on page 4-4.

➤ NoteAt this time, Linux does not provide raw device support or a setup for

Asynchronous Disk I/O. The Sybase Adaptive Server Enterprise installation

does allow you to target block devices.

When support for raw partitions becomes available under Linux and under

Adaptive Server Enterprise, use an unbuffered raw partition for a

production system “master device.” This reduces the risk of compromised

data recovery after an operating system or server crash.

Determining the Location, Type, and Size of a Database Device

Adaptive Server requires several database devices, as shown inTable 4-2.

Table 4-2: Adaptive Server database devices

Device Purpose MinimumSize

Recommended Sizeand Type

master Stores system databases 25MB 30MBRaw partition

sysprocsdev(also called thesybsystemprocs device)

Stores the sybsystemprocsdatabase

45MB 60MB (plus any space forholding stored proceduresthat you have created)Raw partition

sybsystemdb (optional) Required for two-phasecommit

5MB 5MBRaw partition


Adaptive Server Enterprise Version 11.9.2 Pre-Installation Tasks

Do not run Adaptive Server on network-mounted devices, such asNFS- or RFS-mounted files, for these reasons:

• Network problems can cause serious data integrity problemsbecause the network lies between Adaptive Server and thedevices on which it writes.

• If the remote machine is down when you reboot Adaptive Server,and database devices cannot be activated, automatic recoveryfails.

• Adaptive Server is suspended when the remote machine ornetwork is down.

You may need to repartition the disk you choose. Contact youroperating system administrator for assistance.

When preparing a raw partition device, follow these guidelines:

• Do not initialize a database device on the partition that containsyour Sybase installation software, or you will destroy all existingfiles on that partition.

• A raw partition designated for use by Sybase cannot be mountedfor use by the operating system for any other purpose, such as forfile systems or swap space.

• To avoid any possibility of using a partition that contains thepartition map, do not use cylinder 0.

• After a Sybase configuration utility or the disk init command hasinitialized a portion of a partition as a database device, youcannot use the partition for any other purpose. Any space left onthe partition beyond the size specified for the device becomesinaccessible, unless you drop and re-create the device.

• For best performance, place the Sybase software and all diskdevices, including the master device, on the same machine.

• Place the database device on a character device, because theAdaptive Server recovery system needs unbuffered system I/O.The character devices are in the /dev directory.

sybsecurity (optional) Required for auditing 0–5MB 7MB; more for specializedauditingRaw partition

Table 4-2: Adaptive Server database devices (continued)


Quick Start Installation Adaptive Server Enterprise Version 11.9.2

To determine whether a device is a block device or a character device,run ls -l on the /dev directory. In the left column, “b” (block) or “c”(character) appears.

To choose a raw partition:

1. Determine which raw partitions are available.

2. Determine the sizes of the raw partitions.

3. From the list of available raw partitions, select a raw partition foreach device, based on the size recommendations inTable 4-2 on page 4-4.

4. Verify with the operating system administrator that the partitionyou have chosen is available.

5. Make sure the “sybase” user has read and write privileges to theraw partition.

➤ NoteFor more information on choosing a raw partition, see your operating

system documentation.

Quick Start Installation

With Quick Start installation, you can install Adaptive Server only, oryou can install Adaptive Server and one or more of the other servers(Backup Server, Monitor Server, and XP Server), using only thesystem defaults and required fields. Use the Quick Start method toinstall:

• A nonproduction prototype to test new features and functionalitybefore going into production

• A default server to be used for training purposes

• A basic production server that requires no customizing to meetthe needs of your site

For information on installing client products, see Chapter 5,“Installing Sybase PC-Client Products.”

You can use the Quick Start installation method only if you:

• Perform the installation in an X-Windows environment

• Install the servers from the CD


Adaptive Server Enterprise Version 11.9.2 Quick Start Installation

• Use operating system files, not raw partitions, for system devices

• Will use only required server attributes and server defaults

Beginning the Quick Start Installation Process

The following procedure provides instructions for beginning theinstallation process for Adaptive Server and any other serverproducts you unloaded, such as Backup Server. To complete theinstallation process, you will go to other sections as described in step6 at the end of this procedure.

To begin the Quick Start installation process:

1. Be sure that:

- You are logged in as “sybase”.

- Your environment is set up as described in “Pre-UnloadingTasks” on page 3-1.

- You have performed the “Pre-Installation Tasks” on page 4-3.

2. Start the srvbuild utility in one of two ways:

- Choose Build New Servers from the sybsetup menu, or

- At the UNIX prompt, enter:

$SYBASE/bin/srvbuild

3. From the srvbuild screen, choose the server type to be installed.

Only the server types that were unloaded from the distributionmedia are displayed on the srvbuild screen. For example, if youdid not unload Monitor Server, it will not appear on the srvbuildscreen.



If this is a first-time installation for your site, you must chooseAdaptive Server. You can choose all server types at once or anycombination of server types.

srvbuild consecutively displays the attributes screen for eachserver you choose, in the order listed on the screen. For example,if you chose Adaptive Server, Backup Server and XP Server, theattributes screen for Adaptive Server appears first. When youfinish choosing the attributes for Adaptive Server, and click OK,the Backup Server attributes screen appears. When you arefinished with that screen, the XP Server attributes screenappears. The Monitor Server attributes screen does not appearbecause you did not check the box for installing that product.

4. Provide a name for each server you are installing.

srvbuild provides a default server name using the name of themachine on which you are installing.

5. Click OK.

6. Go to the section in this manual that describes the next part ofthe Quick Start installation process for the product you chose toinstall.

If you chose:

- Adaptive Server – go to “Continuing Quick Start Installation –Adaptive Server” on page 4-8.

- Backup Server – go to “Continuing Quick Start Installation –Backup Server” on page 4-10.

- Monitor Server – go to “Continuing Quick Start Installation –Monitor Server” on page 4-12.

- XP Server – go to “Continuing Quick Start Installation – XPServer” on page 4-14.

Continuing Quick Start Installation – Adaptive Server

The following procedure assumes that you have completed theprocedure in the section “Beginning the Quick Start InstallationProcess” on page 4-7. To continue installing Adaptive Server,complete the following procedure.



To continue Adaptive Server installation:

1. If you selected Adaptive Server to be installed, the AdaptiveServer attribute screen is displayed:

2. Provide an operating system file for the master andsybsystemprocs device paths:

/op_system_dir /master.dat

/op_system_dir /systemprocs.dat

where op_system_dir is the name of the operating systemdirectory you are going to use.

srvbuild creates the master.dat and systemprocs.dat files for you.

srvbuild displays a warning regarding the use of an operatingsystem file for the master and sybsystemprocs device paths. If thisAdaptive Server is not intended for production use, you canignore this warning.

3. For the other attributes, use the default values provided.



4. Do one of the following:

- To proceed to the attribute screen for the next server type, clickOK. Then, go to the section in this manual that describes thenext part of the Quick Start installation process for that server.If you chose:

Backup Server – go to “Continuing Quick Start Installation –Backup Server” on page 4-10.

Monitor Server – go to “Continuing Quick Start Installation –Monitor Server” on page 4-12.

XP Server – go to “Continuing Quick Start Installation – XPServer” on page 4-14.

- To create the server or servers you have specified, click BuildServer.

srvbuild displays a Status Output screen that shows the status ofthe various installation tasks as they execute. Go to “Viewingthe Installation Status Output Screen” on page 4-31.

Continuing Quick Start Installation – Backup Server

The following procedure assumes that you have completed theprocedure in the section “Beginning the Quick Start InstallationProcess” on page 4-7. To continue installing Backup Server, completethe following procedure.



To continue Backup Server installation:

1. If you selected Backup Server to be installed, the Backup Serverattribute screen is displayed:

2. Provide the Related Adaptive Server name that will use thisBackup Server.

If the related Adaptive Server is created in the same srvbuildsession as Backup Server, this field does not appear. TheAdaptive Server you are creating is used as the related AdaptiveServer.

3. Provide the Sybase System Administrator (SA) user name for therelated Adaptive Server, or accept the default value.

If the related Adaptive Server is created in the same srvbuildsession as Backup Server, this field does not appear.

4. Provide the Adaptive Server SA password. This is the passwordfor the related Adaptive Server.






- To proceed to the attribute screen of the next server type, clickOK. Then, go to the section in this manual that describes thenext part of the Quick Start installation process for that server.If you chose:

Monitor Server – go to “Continuing Quick Start Installation –Monitor Server” on page 4-12.




Continuing Quick Start Installation – Monitor Server

The following procedure assumes that you have completed theprocedure in the section “Beginning the Quick Start InstallationProcess” on page 4-7. To continue installing Monitor Server,complete the following procedure.

➤ NoteYou must install Monitor Server on the same machine as the Adaptive

Server that is being monitored.



To continue Monitor Server installation:

1. If you selected Monitor Server to be installed, the Monitor Serverattributes screen is displayed:

2. Provide the Related Adaptive Server name. This is the name ofthe Adaptive Server that will be monitored by this MonitorServer.

If the related Adaptive Server is created in the same srvbuildsession as Monitor Server, this field does not appear. TheAdaptive Server you are creating is used as the related AdaptiveServer.


If the related Adaptive Server is created in the same srvbuildsession as Monitor Server, this field does not appear.


If the related Adaptive Server is created in the same srvbuildsession as Monitor Server, this field does not appear.




The default value for Maximum Number of Connections is 5.


- To proceed to the attribute screen of the next server type, clickOK. Then, go to the section in this manual that describes thenext part of the Quick Start installation process for that server.If you chose:




Continuing Quick Start Installation – XP Server

The following procedure assumes that you have completed theprocedure in the section “Beginning the Quick Start InstallationProcess” on page 4-7. To continue installing XP Server, complete thefollowing procedure.



To continue XP Server installation:

1. If you selected XP Server to be installed, the XP Server attributesscreen is displayed:

2. Provide the Related Adaptive Server name that will be using XPServer.

If the related Adaptive Server is created in the same srvbuildsession as XP Server, this field does not appear. The AdaptiveServer you are creating is used as the related Adaptive Server.


If the related Adaptive Server is created in the same srvbuildsession as XP Server, this field does not appear.


If the related Adaptive Server is created in the same srvbuildsession as XP Server, this field does not appear.

5. For the other attributes, accept the default values provided.

6. To create the server or servers you have specified, click BuildServer.


Custom Installation Adaptive Server Enterprise Version 11.9.2

srvbuild displays a Status Output screen that shows the status ofthe various installation tasks as they execute. Go to “Viewing theInstallation Status Output Screen” on page 4-31.

Custom Installation

Follow the instructions in this section to do a customized installationof Adaptive Server, Backup Server, Monitor Server, or XP Server.

Beginning the Custom Installation Process

1. Be sure that:

- You are logged in as “sybase”.

- Your environment is set up as described in “Pre-UnloadingTasks” on page 3-1.

- You have performed the “Pre-Installation Tasks” on page 4-3.

2. Use the srvbuild utility to build a server. You can start srvbuild inone of two ways:

- Choose Build New Servers on the sybsetup menu, or

- At the command line, enter:

$SYBASE/bin/srvbuild

3. From the srvbuild screen, choose the server type that you want toinstall.

Only the server types that were unloaded from the distributionmedia are displayed on the srvbuild screen. For example, if youdid not unload Monitor Server, it will not appear on the srvbuildscreen.


Adaptive Server Enterprise Version 11.9.2 Custom Installation

If you unloaded Monitor Server for SQL Server 11.0.x, it does notappear on the srvbuild screen. For information on how to installand configure this product, see the release bulletin for AdaptiveServer Enterprise Monitor.

If this is a first-time installation for your site, you must selectAdaptive Server. You can choose all server types at once or anycombination of server types in addition to Adaptive Server.srvbuild consecutively displays the attribute screen for each serveryou choose, in the order listed on the screen.

4. Provide a name for each server you install.

srvbuild provides a default server name using the name of themachine you are installing on. You can change the default name.Server naming conventions are as follows:

- The name should not exceed 30 characters.

- The initial character must be a letter; the characters that followmust be letters, numbers, or underscores (_).

- Characters not allowed include: Control characters, spaces,ampersands (&), asterisks (*), periods (.), and question marks(?).

- Use a name that is descriptive of your intended use and uniqueto your network.

- Use the extensions (“_back”, “_mon”, “_XP”) to relate otherserver types to Adaptive Server.

- The XP Server name must be all uppercase. Although srvbuilddoes this for you automatically, you should be aware of thisrequirement in case you need to modify the XP Server name inthe interfaces file.

If you are installing a new Backup Server to accompany anupgraded Adaptive Server, follow these guidelines whenchoosing your Backup Server name:

- If you are upgrading from version 11.x, do not change the nameof Backup Server.

The server names are stored in the interfaces file by srvbuild andare used by clients and other servers to establishcommunication.



5. Click OK.

6. Go to the section in this manual that describes the next part ofthe custom installation process for the product you chose toinstall.

If you chose:

- Adaptive Server – go to “Continuing Custom Installation –Adaptive Server” on page 4-18.

- Backup Server – go to “Continuing Custom Installation –Backup Server” on page 4-22.

- Monitor Server – go to “Continuing Custom Installation –Monitor Server” on page 4-26.

- XP Server – go to “Continuing Custom Installation – XPServer” on page 4-29.

Continuing Custom Installation – Adaptive Server

The following procedure assumes that you have completed theprocedure in the section “Beginning the Custom InstallationProcess” on page 4-16. To continue installing Adaptive Server,complete the following procedure.



To continue Adaptive Server installation:

If you selected Adaptive Server to be installed, the AdaptiveServer attribute screen is displayed:

1. Provide a location for the master device.

For production systems, it is recommended that you use a diskpartition, instead of an operating system file, for the masterdevice. For example:

/dev/ disk_partition

where disk_partition is the disk partition you are going to use.

If you have not selected a disk partition location, see “Pre-Installation Tasks” on page 4-3.

If you use an operating system file, see “Continuing Quick StartInstallation – Adaptive Server” on page 4-8 in the Quick StartInstallation section.

2. Provide a size for the master device.

The default value is the recommended size.



If you entered a disk partition as the master device, the masterdevice size reflects the size of the disk partition. You do not needto change the size.

If you entered an operating system file, you can change the size.You can provide a size that is less than the default size, but theminimum allowable size is 25MB. The maximum size is the sizeof the file system.

3. Provide a size for the master database.

The default size is recommended. If you are adding additionalserver languages for localization, you will need an additional2–7MB of space in the master database per language.

4. Provide a location for the sybsystemprocs device.

For production systems, it is recommended that you use a diskpartition, instead of an operating system file, for thesybsystemprocs device. For example:

/dev/ disk_partition

where disk_partition is the disk partition you are going to use.

It is also recommended that the sybsystemprocs device be locatedon a device separate from the master device. The sybsystemprocsdatabase usually increases in size from release to release, thustaking space from the master device.

If you have not selected a disk partition location, see “Pre-Installation Tasks” on page 4-3.

If you use an operating system file, see “Continuing Quick StartInstallation – Adaptive Server” on page 4-8 in the Quick StartInstallation section.

➤ Notesysprocsdev is the default system name for this device. However, it is

frequently referred to as the sybsystemprocs device, as in the Adaptive

Server attribute screen, since it stores the sybsystemprocs database.

5. Provide a size for the sybsystemprocs device.

The default value is the recommended size. Because thesybsystemprocs database is constantly increasing in size, allowspace for growth on the device.



If you entered a disk partition as the sybsystemprocs device, thesybsystemprocs device size reflects the size of the disk partition.You do not need to change the size.

If you entered an operating system file, you can change the size.You can provide a size that is less than the default size, but theminimum allowable size is 45MB. The maximum size is the sizeof the file system.

6. Provide a size for the sybsystemprocs database.

The default is the recommended size. If the sybsystemprocs deviceis large enough you have the option of making thesybsystemprocs database larger to accommodate future growth.

7. Provide an error log path name.

You can provide a path name other than the default pathprovided.

8. For Interfaces File Entry, specify the transport type, host name,and port number.

These entities comprise the interfaces file entry. This entrydefines how servers and clients find and communicate with eachother on the network. srvbuild adds this entry to the interfaces fileduring the installation process.

- Transport type – the menu provides a list of network protocolssupported by Sybase. TCP is the default. Some networkprotocols in the menu may not be valid for your platform.Check with your operating system administrator.

- Host name – do not change the host name. The host name is themachine name where you installed Adaptive Server.

- Port number – if you did not change the default protocol, theport number displayed is the first available port address. Theport number you specify cannot be used for any purpose otherthan installing Adaptive Server.

If you change the default port number, verify that the new portis not in use.

If you selected a protocol other than the default, you may notbe able to use the first available port number supplied. Checkwith the operating system administrator to see what portnumbers are available.



9. Click Edit Advanced Adaptive Server Attributes if you want to:

- Create a sybsystemdb device path for the sybsystemdb database.Define this attribute if you want to add two-phase commitfunctionality. See Chapter 7, “Adding Optional Functionalityto Adaptive Server.”

- Place shared memory files in a directory other than the defaultlocation under $SYBASE.

- Change your default Backup Server.


- To proceed to the attribute screen for the next server type, clickOK. Then, go to the section in this manual that describes thenext part of the custom installation process for that server. Ifyou chose:

Backup Server – go to “Continuing Custom Installation –Backup Server” on page 4-22.

Monitor Server – go to “Continuing Custom Installation –Monitor Server” on page 4-26.

XP Server – go to “Continuing Custom Installation – XPServer” on page 4-29.



Continuing Custom Installation – Backup Server

The following procedure assumes that you have completed theprocedure in the section “Beginning the Custom InstallationProcess” on page 4-16. To continue installing Backup Server,complete the following procedure.



To continue Backup Server installation:

1. If you selected Backup Server to be installed, the Backup Serverattribute screen is displayed:

2. Provide the Related Adaptive Server name. This is the name ofthe Adaptive Server that will use this Backup Server.

If the related Adaptive Server is created in the same srvbuildsession as Backup Server, this field does not appear. TheAdaptive Server you are creating is used as the related AdaptiveServer.



4. Provide the SA password for the related Adaptive Server.




5. Determine the error log path name for Backup Server. Accept thedefault provided or provide another location.

6. Determine the location of the tape configuration file.

Backup Server reads this file, when a dump command is issued, todetermine the device type and characteristics of the dumpdevice specified in the dump command. Having access to thisinformation speeds up the dump (recovery) process.

The default location is $SYBASE/backup_tape.cfg.

7. Specify the language you want Backup Server to use for its errormessages. The default language is us_english.

The language available depends on which Language Moduleswere downloaded from distribution media to your system. Ifyou unload languages into Adaptive Server in addition to thelanguage you specify as the default, you may need to extendyour master database. Each language requires 2–7MB in themaster database.

8. Specify the character set you want Backup Server to use.

All character sets are installed by default.

Other options are:

- cp850: Code Page 850 (Multilingual) character set

- cp437: Code Page 437 (United States) character set

- mac: Macintosh default character set for Western Europeanlocales

9. Specify the maximum number of network connections.

You can accept the default or change it.

This option specifies the total number of network connectionsavailable if you are backing up (dump) or restoring (load) adatabase over the network to a remote Backup Server.

This option is not necessary if you are dumping to the defaultBackup Server, which is local.

10. Specify the maximum number of server connections.

You can accept the default or change it.

This option specifies the number of server connections toBackup Server. Backup Server requires at least:

- Two connections for each dump (backup) operation

- One connection for each load (recovery) operation



- One connection for volume change messages

Allow a maximum of three times the number of expectedconcurrent dump and load sessions.

11. For the Interfaces File Entry attribute, specify the transport type,host name, and port number.

These entities comprise the interfaces file entry. This entrydefines how Backup Server and Adaptive Server find andcommunicate with each other on the network. srvbuild adds thisentry to the interfaces file during the installation process.

- Transport type – The menu provides a list of network protocolssupported by Sybase. TCP is the default. Some networkprotocols in the menu may not be valid for your platform.Check with your operating system administrator.

- Host name – The host name is the machine name where youinstalled Backup Server.

- Port number – If you did not change the default protocol, theport number displayed is the first available port address.

The port number you specify cannot be used for any purposeother than Backup Server.

If you change the default port number, verify that the new portis not already in use. Check with your operating systemadministrator.

If you selected a protocol other than the default, you may notbe able to use the first available port number. Check with theoperating system administrator to see what port numbers areavailable.



Monitor Server – go to “Continuing Custom Installation –Monitor Server” on page 4-26.






Continuing Custom Installation – Monitor Server

The following procedure assumes that you have completed theprocedure in the section “Beginning the Custom InstallationProcess” on page 4-16. To continue installing Monitor Server,complete the following procedure.

To continue Monitor Server installation:

1. If you selected Monitor Server to be installed, the Monitor Serverattribute screen is displayed:

2. Provide the Related Adaptive Server name.

This is the name of the Adaptive Server that Monitor Server willbe monitoring. This field does not appear, if the related AdaptiveServer is created in the same srvbuild session as Monitor Server.The Adaptive Server you are creating is used as the relatedAdaptive Server.



3. Specify the Sybase System Administrator (SA) user name.

This option is required unless the USER environment variable isset.

This name specifies the user name of the Monitor Serversuperuser. It must be a valid login account for the AdaptiveServer to be monitored. For production systems, it isrecommended that you use the “sa” or “sybase” user account asthe Monitor Server superuser.

Monitor Server uses the superuser account to connect toAdaptive Server to run special stored procedures and to verifyshutdown requests that can be performed only by the superuser.

This field does not appear, if the related Adaptive Server iscreated in the same srvbuild session as Monitor Server.

4. Provide the Adaptive Server SA password for the MonitorServer superuser.

If the password is omitted, Monitor Server prompts for apassword during start-up.

This field does not appear, if the related Adaptive Server iscreated in the same srvbuild session as Monitor Server.

5. Determine the maximum number of connections allowed toMonitor Server.

Valid values are 1–20. The default is 5.

A connection to Monitor Server can be any of the following:

- A monitor in Sybase Central,

- An active Historical Server session or a scheduled HistoricalServer recording session, or

- A connection to Monitor Server from a Monitor Client Libraryapplication.

For example, if a user starts a Historical Server recordingsession, and another user opens the Performance SummaryMonitor in Sybase Central, two connections to Monitor Serverare used. If the default configuration of five connections is ineffect, three additional connections to Monitor Server areavailable.

6. Specify the error log path.

This is the path name of the Monitor Server log file, whereinformational and error messages are logged.



The default location is the directory from which Monitor Serveris started and the error log name is ms.log.

7. Specify the path of the configuration file.

This is the path name of the Monitor Server configuration file. Adefault configuration file is not provided. This file is optional,but if specified, the values in the configuration file override thedefault runtime parameters that are otherwise used by MonitorServer.

8. Specify the shared memory directory.

This specifies the name of the directory where theadaptiveservername.krg shared memory file is located.

If this parameter is omitted, Monitor Server looks for the sharedmemory file in the Sybase installation directory.

The shared memory file name must be specified or impliedwhen you start Adaptive Server and Monitor Server.

9. For the Interfaces File Entry attribute, specify the transport type,host name, and port number. These entities comprise theinterfaces file entry. This entry enables Monitor Server andAdaptive Server to find and communicate with each other on thenetwork. srvbuild adds this entry to the interfaces file during theinstallation process.


- Host name – The host name is the machine name where youinstalled Monitor Server.


The port number you specify cannot be used for any purposeother than installing the Monitor Server.

If you change the default port number, verify that the new portis not already in use.

If you selected a protocol other than the default, you may notbe able to use the first available port number. Check with theoperating system administrator to see what port numbers areavailable.








Continuing Custom Installation – XP Server

The following procedure assumes that you have completed theprocedure in the section “Beginning the Custom InstallationProcess” on page 4-16. To continue installing XP Server, complete thefollowing procedure.

To continue XP Server installation:

1. If you selected XP Server to be installed, the XP Server attributescreen is displayed:

2. Provide the Related Adaptive Server name.



This specifies the name of the Adaptive Server that will be usingXP Server.

This field does not appear, if the related Adaptive Server iscreated in the same srvbuild session as XP Server. The AdaptiveServer you are creating is used as the related Adaptive Server.


This field does not appear, if the related Adaptive Server iscreated in the same srvbuild session as XP Server.

4. Provide the SA password for the related Adaptive Server.

This field does not appear, if the related Adaptive Server iscreated in the same srvbuild session as XP Server.

5. For the Interfaces File Entry attribute, specify the transport type,host name, and port number. These entities comprise theinterfaces file entry. This entry enables XP Server and AdaptiveServer to find and communicate with each other on the network.srvbuild adds this entry to the interfaces file during theinstallation process.


- Host name – The host name is the name of the machine whereyou installed XP Server.


The port number you specify cannot be used for any purposeother than installing the XP Server.

If you choose to change the default port number, verify that thenew port is not already in use.

If you selected a protocol other than the default, you may notbe able to use the first available port number. Check with theoperating system administrator to see what port numbers areavailable for use.

6. To create the server or servers you have specified, click BuildServer.


Adaptive Server Enterprise Version 11.9.2 Viewing the Installation Status Output Screen

srvbuild displays a Status Output screen that shows the status ofthe various installation tasks as they execute. Go to “Viewing theInstallation Status Output Screen” on page 4-31.

Viewing the Installation Status Output Screen

Use the information in this section each time you click the BuildServer button after specifying the attributes for the server.

1. Review the Status Output screen for informational messagesabout the installation process.

If the installation is not successful, see Chapter 9,“Troubleshooting.”

If the installation is successful, a message similar to thefollowing is displayed in the Status Output screen:

Server server_name was successfully created.Done.

2. If you installed Adaptive Server during this srvbuild session, go to“Changing the Default Language and Character Set” on page4-31.

Changing the Default Language and Character Set

◆ WARNING!Make all changes to the character set and sort order for a newAdaptive Server before you create any user databases or make anychanges to the Sybase-supplied databases. Changing the characterset and sort order after data or data structures have been added toAdaptive Server can cause incorrect behavior. If you need to changethe character set or sort order after you have added data, see theSystem Administration Guide .

If you installed Adaptive Server, srvbuild displays a SrvbuildQuestion screen asking if you want to localize your Adaptive Serverto a language other than us_english and if you want to use acharacter set or sort order other than the default.

srvbuild creates an Adaptive Server with the following defaults:

• us_english language


Installation Complete Adaptive Server Enterprise Version 11.9.2

• Binary sort order

Valid language options depend on the Language Modules youunloaded from distribution media.

All character sets are installed by default.

You have two options:

• Click No to accept the defaults, and then go to “InstallationComplete” on page 4-32.

• Click Yes to change the defaults.

The sqlloc menu is displayed. sqlloc is the GUI utility used tochange default languages, character sets, and sort orders. Whenyou finish this task, go to “Installation Complete” on page 4-32.

For information on using sqlloc, see Chapter 5, “LocalizationIssues,” in Configuring Adaptive Server for UNIX Platforms.

Installation Complete

You have completed the installation process. Go to “Post-InstallationTasks” on page 4-36.

Resource File Installation

You can create an Adaptive Server or Backup Server, using valuesspecified in a resource file that defines the attributes for the server.Resource files allow you to create servers in batch mode. You cancreate servers on multiple systems from the same resource file byediting a few values in that file. Within a single resource file, you cancreate only one server at a time.

➤ NoteYou cannot install Monitor Server or XP Server using resource files.

To install an Adaptive Server or Backup Server using resource files:

1. Edit a resource file as described in “Editing a Resource File” onpage 4-33.

2. Execute the srvbuildres utility, using the edited resource file asdescribed in “Using srvbuildres” on page 4-35.


Adaptive Server Enterprise Version 11.9.2 Resource File Installation

Editing a Resource File

You can edit a resource file by:

• Editing a sample resource file

• Editing the resource file created by the srvbuild utility

Editing a Sample Resource File

Sample resource files for creating Adaptive Server and BackupServer are included in your Adaptive Server distribution in$SYBASE/init/sample_resource_files. Edit these files to specify theattributes for the servers you want to create.

Editing a Resource File Created by srvbuild

You can create a resource file by running the srvbuild utility. A new filecontaining the values you specified for each server is written to$SYBASE/init/logs/srvbuildMMDD.VVV-servername.rs. Edit thesefiles to specify the attributes for the servers you want to create.

◆ WARNING!Be sure to edit the resource file generated by srvbuild to changeattributes, such as device names, that may be different on anothersystem.

Resource File Attributes for Adaptive Server

Table 4-3 on page 4-34 shows the Adaptive Server resource fileattributes, their default values, and other options.

The attributes in bold type are required.

All alpha values are case sensitive.

The prefix of the attribute name varies, depending on whether theresource file was created by srvbuild or by sybinit (from a pre-11.5 SQLServer). The prefix is ignored by srvbuildres when processing theresource file.


Resource File Installation Adaptive Server Enterprise Version 11.9.2

The attribute names in Table 4-3 are the attribute names provided inthe sample resource file included in your Adaptive Serverdistribution.

Resource File Attributes for Backup Server

Table 4-4 shows the Backup Server resource file attributes, theirdefault values, and other options.

The attributes in bold type are required.

Table 4-3: Resource file attributes for Adaptive Server

Attribute Default Value [Other Options]

sybinit.release_directory The value of $SYBASE at your site

sybinit.product sqlsrv

sqlsrv.server_name server_name

sqlsrv.new_config yes (This is the required value.)

sqlsrv.do_add_server(to interfaces file)

yes [no]

sqlsrv.network_protocol_list tcp [spx]

sqlsrv.network_hostname_list hostname

sqlsrv.network_port_list port_number

sqlsrv.master_device_physical_name path_and_name_of_master_device

sqlsrv.master_device_size 30 (MB)

sqlsrv.master_database_size 5 (MB)

sqlsrv.errorlog $SYBASE/install/server_name.log

sqlsrv.do_upgrade no (This is the required value.)

sqlsrv.sybsystemprocs_device_physical_name path_and_name_of_sybsystemprocs_device

sqlsrv.sybsystemprocs_device_size 45 (MB)60 (MB) recommended

sqlsrv.sybsystemprocs_database_size 45 (MB)60 (MB) recommended

sqlsrv.sybsytemdb_device_physical_name path_and_name_of_ sybsystemdb_device

sqlsrv.sybsystemdb_device_size 5 (MB)

sqlsrv.sybsystemdb_database_size 5 (MB)

sqlsrv.default_backup_server server_name_back


Adaptive Server Enterprise Version 11.9.2 Resource File Installation

All values are case sensitive.

The prefix of the attribute name varies, depending on whether theresource file was created by srvbuild or by sybinit (from a pre-11.5 SQLServer). The prefix is ignored by srvbuildres when processing theresource file.

The attribute names in Table 4-4 are the attribute names provided inthe sample resource file included in your Adaptive Serverdistribution.

Using srvbuildres

To execute srvbuildres from the UNIX prompt:

$SYBASE/bin/srvbuildres -r resource_file

where resource_file specifies the resource file containing the attributesthat describe the server to build.

➤ NoteUnlike srvbuild, the srvbuildres utility does not require any X libraries.

Table 4-4: Resource file attributes for Backup Server


sybinit.release_directory $SYBASE

sybinit.product bsrv

bsrv.server_name server_name_back

bsrv.do_add_backup_server(to interfaces file)

yes [no]

bsrv.network_protocol_list tcp [spx]

bserv.network_hostname_list hostname

bsrv.network_port_list port_number

bsrv.language us_english [chinese, french, german,japanese, spanish]

bsrv.character_set [iso_1, cp850, cp437, deckanji, ascii_8,eucgb, eucjis, mac, roman8, sjis, utf8]

bsrv.tape_config_file $SYBASE/backup_tape.cfg

bsrv.errorlog $SYBASE/server_name_back.log


Post-Installation Tasks Adaptive Server Enterprise Version 11.9.2

Resource File Installation Complete

You have completed resource file installation. Go to “Post-Installation Tasks” on page 4-36.

Post-Installation Tasks

After installing your servers, complete the tasks in this section.

Verifying That Servers Are Running

To determine whether the servers you installed are running:

1. Do either of the following:

- For each server, enter the following command at the UNIXprompt:

$SYBASE/bin/isql -Usa -P -S server_name

where server_name is the name of the server you want to check.If the server is running, you will see the isql prompt:

1>


$SYBASE/install/showserver

showserver shows how many Adaptive Server-related processesare on the system.

Setting the Sybase System Administrator Password

A user account called “sa” is created for the Sybase SystemAdministrator when the Sybase software is installed. (See “UserRoles” on page 1-1.) A user logged in as “sa” can use any database onAdaptive Server, including master, with full privileges.

Immediately after a new installation, there is no password on the“sa” account. The initial default value for the password is NULL. Ina production environment, the Sybase System Administrator shouldalways use a non-default password.


Adaptive Server Enterprise Version 11.9.2 What’s Next?

The Sybase System Administrator should log in to the new AdaptiveServer as “sa” and set a password with the sp_password systemprocedure:

$SYBASE/bin/isql -Usa -P -S server_name1> sp_password null, new_password2> go

Information Required for XP Server

If you install Adaptive Server and XP Server in the same buildsession, srvbuild automatically adds information about the XP Serverto the sysservers table of Adaptive Server. If you install XP Server in adifferent build session than the Adaptive Server installation, you areprompted during the XP Server installation process to supply thename of the related Adaptive Server and the System Administrator’sname and password. This information is required by AdaptiveServer to start XP Server.

If you do not supply this required information during the installationprocess, XP Server cannot run. When you execute an extended storedprocedure (ESP), you will see an error message similar to thefollowing:

Msg 11018, Level 16, State 1:Procedure 'xp_cmdshell', Line 2XP Server must be up for ESP to execute.

To add this required information to the sysservers table manually:

1. Run the following system procedure:

sp_addserver servername _XP, NULL, servername _XP

where servername is the name of the Adaptive Server.

What’s Next?

For information on the using the servers you installed, see thefollowing sections:

Adaptive Server

You have a running server, as well as various system databases andsystem tables. Some references that may help you get started usingyour new Adaptive Server are as follows:



• For an overview of Adaptive Server, see Introducing SybaseAdaptive Server for UNIX Platforms.

• To create an Adaptive Server user database and its devices, see“Initializing Database Devices” and “Creating User Databases”in the System Administration Guide.

• To write queries, see the Transact-SQL User’s Guide.

Backup Server

For information on developing a backup and recovery plan andbacking up and restoring user databases, see the SystemAdministration Guide.

Monitor Server

Monitor Server requires some additional configuration afterinstallation. See the Adaptive Server Enterprise Monitor Server User’sGuide.

XP Server

For information on using extended stored procedures, see theTransact-SQL User’s Guide.


5 Installing Sybase PC-ClientProducts 5.

Your UNIX-based Adaptive Server also includes PC-client productsthat you install on a PC and connect, via the interfaces file, with yourAdaptive Server.

This chapter describes how to install client products on Windows 95and Windows NT 4.0.


• Preinstallation Task 5-1

• Installing PC Clients 5-1

• Configuring Network Connections for Client Products 5-4

• Installing the Adaptive Server Plug-In for Sybase Central 5-6


Preinstallation Task

Before starting the installation process for PC-client products, be surethat the drive on which you install the products has at least an extra2.4MB of disk space, and includes the \temp directory and TEMPenvironment variable.

The installation program uses the extra space and directory to writefiles temporarily during the installation. The installation programfrees this space after installation is complete.

Installing PC Clients

To install client products on Windows NT or Windows 95:

1. Verify that your computer has sufficient RAM for each product.See Chapter 2, “Installation Requirements.”

2. If you are installing on Windows NT, log in using an accountwith Windows NT administrator privileges.

3. Close any open applications or utilities to free memory andsystem resources.

4. Insert the CD containing the PC-client products into theCD-ROM drive.

5-2 Installing Sybase PC-Client Products

Installing PC Clients Adaptive Server Enterprise Version 11.9.2

5. Start the installation program by using one of the followingmethods:

- Click the Start button, choose Run, and enter:

n:\setup.exe

where n is your CD-ROM drive.

- Click the Start button, choose the Windows Explorer, selectyour CD-ROM drive, and then double-click the setup.exe file.

The Welcome window is displayed.

6. Click Next.

The Select Installation Type window is displayed:

7. Choose Licensed Products, and click Next.

The Select Sybase Installation Directory is displayed.

Do not change the default Sybase Installation Directory value.The default directory is either the value of the SYBASEenvironment variable, if set, or c:\sybase. This directory shouldnot be located on a network drive. You can specify another localdisk drive if it has at least 15MB space more than the amountrequired for installation.

The installation program will download files to this directory.

8. Click Next.

The Select a Program Folder window is displayed.


Adaptive Server Enterprise Version 11.9.2 Installing PC Clients

Do not change the default Program folder. The installationprogram will create a program folder, named Sybase, in which toplace icons.

Click Next.

The Product Selection window is displayed:

9. Click the box next to each product to be installed.

The installation program will install each product you select.The Product Selection window provides the followinginformation:

- Available disk space.

- Disk space required for all products selected.

- Product description for each highlighted product, as it isselected.

- Options for products that have a plus sign (+) to the left. Toexpand the tree, click the plus sign.

10. Click Next.

The Installation Summary window is displayed.

11. Check the Installation Summary window to be sure the productsselected are correct.


Configuring Network Connections for Client Products Adaptive Server Enterprise Version 11.9.2

To change entries, click Back to access previous windows, makechanges, and then press Next to access the Installation Summarywindow again.

12. In the Installation Summary window, click Install to completethe installation.

The installation program downloads files from the CD to thecomputer. The Verification window is displayed when thedownload process is completed.

This completes the installation process for all clients.

To configure client network connections to Adaptive Server, see“Configuring Network Connections for Client Products” onpage 5-4.

13. When the installation is complete, choose Yes to exit theinstallation program.

14. Reboot your PC.

If you do not reboot the PC immediately, do so before you useyour Sybase products. Restarting the PC updates theenvironment variables and Registry keys so that applicationscan find the Sybase products on your computer.

Configuring Network Connections for Client Products

Network connections between clients and servers are defined in thesql.ini file on the PC. Sybase client products use the sql.ini file to findthe network addresses of available servers.

Before any client product can access a Sybase server, each server towhich you want to connect must be included in the sql.ini file on theclient computer.

By default, connections from client products to Adaptive Server areenabled through the Named Pipes and Winsock network protocols.

Adding a Server to the sql.ini File

To add a server entry to the sql.ini file on your PC-client computer:

1. Double-click the dsedit icon in your Sybase folder.

2. In the Input Server Name box, enter the name of the server forwhich you are creating an entry.


Adaptive Server Enterprise Version 11.9.2 Configuring Network Connections for Client Products

3. In the Connection Information/Network Address box, enter theserver’s listening network address:

server_machine-hostname_or_ip_address , server_listen_port_number

where:

- server_machine-hostname_or_ip_address is the name of the UNIXmachine or the IP address of the machine where the server youwant to connect to is located.

- server_listen_port_number is the port number the server is usingto “listen” for clients.

To find the IP address for the server machine to which you wantto connect:

"ypmatch ’ hostname ’ hosts"

where hostname is the name of the machine to which you want toconnect.

➤ NoteTo connect to a UNIX server, the entries you add to the sql.ini file must

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

Make sure the name of the Monitor Server in the sql.ini file in the client PC

is the same name as the server name that you are trying to get the

monitoring information from.

To find the server’s listener service port number:

a. View the $SYBASE/interfaces file on the server machine.

b. Find the name of the server to which you want to connect. Forexample:

testsolaris

master tli tcp /dev/tcp \x0002100482d63ce70000000000000000query tli tcp /dev/tcp \x0002100482d63ce70000000000000000

testlinux

master tcp ether testlinux 4100query tcp ether testlinux 4100

c. In the server’s master entry line for solaris , the port numberconsists of the 4–5 hexadecimal digits following “\x0002”. Inthis example, the port number is 1004 (hexadecimal). When1004 is converted to decimal, the port number is 4100. The portnumber must be between the decimal value of 1025 and 65535.


Installing the Adaptive Server Plug-In for Sybase Central Adaptive Server Enterprise Version 11.9.2

d. In the server’s master entry line for linux , the last field is theport number. For testlinux , the port number is 4100.

4. From the Service Type drop-down list, choose Query.

5. From the Net-Library Driver drop-down list, chooseNLWNSCK.

6. Click Add.

For additional information on using dsedit on the client computer, seethe Open Client/Server Configuration Guide for Desktop Platforms andthe Open Client/Server Supplement.

For specific information about entries for connections to MonitorServer and Historical Server, see:

• Adaptive Server Enterprise Monitor Server User’s Guide

• Adaptive Server Enterprise Monitor Historical Server User’s Guide

For information about using dsedit on the server machine or for moreinformation on the components of an interfaces file entry, seeConfiguring Adaptive Server for UNIX Platforms.

Enabling TCP Connections

To connect through TCP instead of Named Pipes and Winsocknetwork protocols, you must enable the TCP connections:

1. Double-click the OC OS Config icon in the Sybase folder.

2. Click the NetLibrary tab.

3. Select Windows NT/95 as the platform and TCP as the protocol.

4. Click OK.

This maps NLWNSCK to TCP in your Sybase network configurationfile (libtcl.cfg).

Installing the Adaptive Server Plug-In for Sybase Central

Sybase Central is a graphical framework management tool formanaging Adaptive Server and other Sybase servers. You canmanage Adaptive Server running on any platform from a PC that isrunning Windows 95 or Windows NT.


Adaptive Server Enterprise Version 11.9.2 Installing the Adaptive Server Plug-In for Sybase Central

Installing the Plug-In

To install the Adaptive Server plug-in on your Windows NT orWindows 95 system:

1. Select setup.exe from the root directory of the Sybase product CD.

2. Install your PC clients as described in “Installing PC Clients” onpage 5-1.

3. Choose Sybase Central ASE Plug-in from the Product Selectionwindow.

4. Restart your PC.

The Adaptive Server plug-in installation process adds thefollowing path names to your CLASSPATH environmentvariable:

- ase_install_path\Monclass.zip

- ase_install_path\3pclass.zip

where ase_install_path is the path name where you installed theplug-in (usually C:\sybtools\asep).

Installing the Required Microsoft DLL on Windows 95

After installing the plug-in for Sybase Central on a computer that isrunning Windows 95, check the version of the comctl32.dll systemfile. This file provides common graphical controls for windows anddialog boxes. If your system has an older version of this file, someAdaptive Server plug-in dialog boxes may not display properly.

Checking the Current File Version

To check the file comctl32.dll:

1. Open the Windows NT Explorer to the d:\windows\systemdirectory.

2. Locate the file comctl32.dll.

3. If the Modified date is earlier than 4/30/97, replace the file.

You can check the modified date by opening the property sheetfor the file or putting the right pane of the Windows NT Explorerin Details view and looking in the Modified column.



Replacing the File

To replace the file comctl32.dll:

1. Access the Microsoft Web site at:

http://support.microsoft.com/support/kb/articles/Q165/4/87.asp

2. Get the file com32upd.exe from the Microsoft Web site. Follow theinstructions for installation provided by Microsoft, but do notuse the -d parameter.

3. After you install the update, restart your computer.

Running the Japanese Version of the Plug-In

To run the Japanese version of the plug-in:

1. Move the sjis.uct file

- For Windows 95 and NT:

Move \sybtools\charsets\unicode\sjis.uct to\sybase\charsets\unicode\sjis.uct.

2. Set the LANG environment variable to Japanese.

- For Windows 95:

In the autoexec.bat file, add the following line:

set LANG=japanese

- For Windows NT:

a. In the Control Panel, open the Systems applet.

b. Select the Environment tab.

c. In the Variable text box, enter “LANG”.

d. In the Value text box, enter “japanese”.

e. Click Set.

f. Click OK.

Installing the Java Runtime Environment

To use the monitoring features of the Adaptive Server plug-in, youneed to install the Java Runtime Environment (JRE) 1.1.6 (or later)



from Sun Microsystems. The JRE is also required by jisql and ribo. Youcan get the JRE from:

http://java.sun.com/

or from other sites.

JRE 1.1.6 for NT is available on the PC Client CD. To install the JREprovided on the CD:

1. In the Windows Explorer, navigate to the \java directory on thePC Client CD.

2. Double-click the jre116i.exe file. The installation program starts.

3. Follow the instructions in the installation window.

You do not have to reboot your computer after you install the JRE.

➤ NoteAs an alternative to installing the JRE, you can install the Java Development

Kit. For information, see “Installing the Java Development Kit” on page 5-10.

Installing Java Utilities

The PC Client CD includes two java utilities called jisql and Ribo.These are compressed in Zip format files called jisql.zip and ribo.zip.Instructions on how to use jisql and Ribo are available in both htmland pdf formats, and are included in these compressed files.

Before installing jisql and Ribo, you need to download and install theJava Development Kit (JDK) or the Java Runtime Environment(JRE).

➤ Notesybsetup does not list jisql and ribo as products available for installation.

Installing jisql and ribo

To extract the jisql.zip and ribo.zip files, you need WinZip® or asimilar file extraction program. To run jisql, you also need Swingversion 1.1 Beta 3 or later and JRE 1.1.6 or later. You can get these filesfrom http://java.sun.com/ or from other sites.

For the latest information on jisql and ribo, visit the Sybase web site:http://www.sybase.com/products/internet/jconnect/utilities



To load the utilities:

1. When the Sybase installation program displays, click Exit to quitthe installer.

2. Start the Windows NT Explorer.

3. Click the CD-ROM drive name to display the CD’s contents inthe Explorer.

4. In the Windows Explorer, navigate to the \jutils directory on theCD.

5. Double-click jisql.zip or ribo.zip, which will invoke WinZip if youhave the .zip extension associated with that application. If youdon’t, start WinZip and open the jisql or ribo .zip archive.

6. Extract jisql.zip and/or ribo.zip to the desired location on yourhard drive.

7. Exit WinZip.

➤ NoteAlthough the programs on this CD are designed to run on NT only, ribo and

jisql can run on any platform that is able to read this CD and has a Java VM

and a program to extract the .zip file.

Installing the Java Development Kit

The Java Development Kit (JDK) includes files and features thatsupport development of Java applets and applications. Sybase doesnot distribute the JDK. The Java Development Kit (JDK) requiresmore disk space than the JRE.

To install the Java Development Kit:

1. Download the JDK for your operating system from the JavaSoftWeb site:

http://java.sun.com/products/index.html

2. Double-click the file you downloaded.

3. Follow the instructions in the installation window.

4. Add install_path\lib\CLASSES.ZIP to your CLASSPATHenvironment variable, where install_path is the location whereyou installed the JDK; for example, C:\javasoft.

5. Add install_path\bin to your PATH environment variable.



System Requirements

Table 5-1 and Table 5-2 list the system requirements for installing jisqland Ribo:.

Table 5-1: System requirements for Windows NT and Windows 95

Hardware PC with 486 or greater Intel processor

Operating system Windows NT 3.5.1 or later, or Windows 95(supporting Java VM version 1.1)

Memory 16MB

Free disk space 6MB for default options

Java Developer’s Kit Sun’s JDK 1.1.x or later, or Microsoft’s jView

Database • Adaptive Server Enterprise (SQL Server System10, version 10.0.2, through Adaptive ServerEnterprise 11.9.x); or

• Sybase SQL Anywhere 5.5.03 or later, runningOpen Server Gateway™ dbos50; or

• Sybase SQL Anywhere Studio 6.0*

Other Sybase products(optional)

Adaptive Server IQ, OmniConnect™,DirectConnect™

IDE (optional) Any Java application development environment,such as PowerJ™, Visual J++, Symantec Cafe, orBorland Latte, etc.

Web server (optional) For jConnect’s TDS-tunnelling servlet, any Webserver, such as HotJava, that supports the HTTPSprotocol and javax.servlet interfaces

*A free evaluation version of SQL Anywhere Studio 6.0 (includes Adaptive ServerAnywhere 6.0) is available from Sybase at:

http://www.sybase.com/products/system11/workplace/sqlanyform.html

The Open Server Gateway and the required DLLs are no longer needed with SybaseSQL Anywhere Studio version 6.0 and later.

Table 5-2: System requirements for UNIX

Hardware Any UNIX platform that supports Java VM 1.1.x

Operating system Sun Solaris, HP UX, IBM AIX, DEC Digital Unix,SGI IRIX, etc.

Memory 16MB



What’s Next?

For information about configuring and administering your clientproducts, see the following manuals:

Free disk space 6MB for default options

Java Developer's Kit Sun’s JDK 1.1.x or later

Database • Adaptive Server Enterprise, from SQL ServerSystem 10, version 10.0.2, through AdaptiveServer Enterprise 11.9.x; or

• Sybase SQL Anywhere 5.5.03 or later, runningOpen Server Gateway™ dbos50; or

• Sybase SQL Anywhere Studio 6.0*

Other Sybase products(optional)

Adaptive Server IQ, OmniConnect, DirectConnect

Web server (optional) For jConnect’s TDS-tunnelling servlet, any Webserver that supports the HTTPS protocol andjavax.servlet interfaces

*A free evaluation version of SQL Anywhere Studio 6.0 (includes Adaptive ServerAnywhere 6.0) is available from Sybase at:

http://www.sybase.com/products/system11/workplace/sqlanyform.html

The Open Server Gateway and the required DLLs are no longer needed with SybaseSQL Anywhere Studio version 6.0 and later.

Product ManualAdaptive Server EnterpriseMonitor Client Library

Adaptive Server Enterprise Monitor ClientLibrary Programmer's Guide

Adaptive Server plug-in forSybase Central

Managing and Monitoring Sybase AdaptiveServer

Open Client Open Client/Server Supplement (for theclient platform)

Table 5-2: System requirements for UNIX (continued)


6 Upgrading Sybase Servers 6.

This chapter describes how to upgrade approved versions ofAdaptive Server, SQL Server, Backup Server, Monitor Server, and XPServer to version 11.9.2.


• Overview 6-1

• Pre-Upgrade Tasks 6-1

• Upgrading Adaptive Server 6-11

• Post-Upgrade Tasks 6-17

• Upgrading Backup Server, Monitor Server, and XP Server 6-21


Overview

You can upgrade to Adaptive Server 11.9.2 from version 11.0.3.3.

The upgrade process includes:

• Performing generic pre-upgrade tasks to prepare your siteenvironment and your current server for the upgrade

• Performing specific pre-upgrade tasks if your current serversupports auditing or replicated databases

• Upgrading to the new release level

• Performing post-upgrade tasks

➤ NoteBefore you begin the upgrade process, unload Adaptive Server 11.9.2

product files onto your system. The unloading process is described in

Chapter 3, “Unloading Server Products from Distribution Media.”

Pre-Upgrade Tasks

Before beginning any upgrade tasks, read the “Special UpgradeInstructions” section in the release bulletin for Adaptive Server.

6-2 Upgrading Sybase Servers

Pre-Upgrade Tasks Adaptive Server Enterprise Version 11.9.2

To ensure a successful upgrade, review the following pre-upgradetasks and perform them as necessary. Depending on your currentAdaptive Server configuration, it may not be necessary to performall pre-upgrade tasks.

Pre-upgrade tasks include:

• “Verifying Your Adaptive Server Environment” on page 6-2

• “Preparing Your Server for Upgrade” on page 6-3

• “Increasing the Size of the sybsystemprocs Database” on page 6-7

• “Upgrading a Database That Uses Auditing” on page 6-10

• “Preparing to Upgrade with Replicated Databases” on page 6-11

Verifying Your Adaptive Server Environment

To verify that your system environment is configured correctly:

1. Verify that you unloaded Adaptive Server 11.9.2 in a differentdirectory from your previous Adaptive Server (or SQL Server)installation.

If you overwrote your previous server installation:

a. Restore it from your most recent backup.

b. Reload the product files for Adaptive Server in a differentdirectory.

c. Continue with the upgrade.

For details on unloading server products, see Chapter 3,“Unloading Server Products from Distribution Media.”

2. Verify that your operating system is at the proper release leveland has all operating system patches needed for AdaptiveServer.

For the minimum operating system level on which you can runthis version of Adaptive Server, see “System Requirements” inChapter 2, “Installation Requirements.” If the operating systemon which your current server is running is at a earlier releaselevel than required, upgrade your operating system to therequired level before upgrading Adaptive Server.

3. Verify the name and location of the runserver file.

Be sure the runserver file for your current server is located in theold $SYBASE/install directory and is still namedRUN_server_name, where server_name is the name of the current


Adaptive Server Enterprise Version 11.9.2 Pre-Upgrade Tasks

server. The server_name must appear exactly as it appears in theinterfaces file.

4. Test your current applications and stored procedures.

If you have critical applications and stored procedures, performan upgrade in a test environment, so that you can determine anyadjustments you may need to make in your productionenvironment before upgrading it.

5. Determine which Sybase products should be running.

If you are upgrading Adaptive Server (or SQL Server), thepreviously installed version of the server must be running.

If you are upgrading Backup Server, Historical Server, MonitorServer, or XP Server, those servers must not be running.

If you install any other Adaptive Server products in the samedirectory as the previously installed release, stop the currentversion of the product that is running before installing the newversion in the same directory.

Preparing Your Server for Upgrade

To prepare your server for upgrade:

1. Determine whether your server supports an upgrade toAdaptive Server.

To determine the release level of your current Adaptive Server(or SQL Server), enter the following command in isql:

1> select @@version2> go

You can upgrade to Adaptive Server 11.9.2 from version 11.0.3.3.

2. Verify that all server users are logged off:

a. Log in to your current server as the Sybase SystemAdministrator:

isql -Usa -P password -S server_name

b. Enter:

1> sp_who2> go

This command returns a list of all users and processescurrently on the server.

c. Log off all users on the server.



The upgrade will not work if you boot the server in single-usermode.

3. Check for reserved word conflicts.

If you plan to use sqlupgrade to perform the upgrade process, youdo not have to check for reserved words as a separate step. Insqlupgrade, you can check for reserved words at the start of theupgrade process, and then continue with the upgrade if noproblems are found.

If you plan to use sqlupgraderes to perform the upgrade processusing a resource file, you can run sqlupgrade first to identifyreserved word conflicts and other potential upgrade eligibilityproblems. You can specify that you do not want the upgrade toproceed even if no problems are found.

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

➤ NoteIf you change an object name, be sure to change applications and stored

procedures that refer to that object.

Checking for reserved words generates a list of identifiers thatconflict with reserved words, and the owners of those identifiers,in the file $SYBASE/init/logs/sqlupgradeMMDD.nnn. Review thisfile to determine which identifiers must be changed.

For a list of reserved words in 11.9.2, see New Functionality inAdaptive Server Enterprise 11.9.2. For more information onresolving reserved word conflicts, see sp_checkreswords in theAdaptive Server Reference Manual.

4. Check logical and physical database consistency by running thefollowing commands in each database:

- dbcc checkalloc

- dbcc checkdb

- dbcc checkcatalog

If you encounter any errors while running these commands,resolve them before continuing the upgrade. For help withresolving errors, see the Troubleshooting and Error Messages Guide.



If a database is marked “suspect,” drop that database with thedbcc dbrepair (database_name, dropdb) command. If a database ismarked “read only,” change its status by setting the read onlyoption of the sp_dboption system procedure to false.

5. Use the dump database command to back up all databases on yourcurrent server. If you encounter any problems during theupgrade, you may need these dumps to recover the previousinstallation. Be sure to also dump the master database.

6. The upgrade process may consume substantial space in thetransaction log. Before beginning the upgrade process, run thedump tran command in each database to free up log space.

7. Make sure that master is the default database for the “sa” user.

The upgrade cannot complete successfully with a differentdatabase as your default. For information about specifying thedefault database, see the System Administration Guide.

8. Verify that the master database is large enough. The minimumsize for upgrading master is 7MB.

If you are upgrading a server on which multiple languages areinstalled, make sure that you have at least 2–7MB of free spacefor each language in the master database. sqlupgrade requires thisspace so that it can remove and reinstall those languages as partof the upgrade.

9. Verify that the tempdb database is large enough. The minimumsize for upgrading tempdb is 3MB.

10. Verify that the model database is large enough. The minimumsize for upgrading model is 3MB.

11. Verify that the sybsystemprocs database is large enough. Theminimum size for sybsystemprocs is 45MB. The recommendedsize is 60MB. You may need more space if you are adding user-defined stored procedures. The recommended partition type is araw partition.

If your sybsystemprocs database is smaller than 45MB, and youhave room on the device that contains this database, use the alterdatabase command to increase the database size. For moreinformation, see “Increasing the Size of the sybsystemprocsDatabase” on page 6-7.

12. Run the sp_helpdb system procedure to display the options thatare set on your current server databases.



Run the sp_dboption system procedure to turn off all optionsexcept select into/bulk copy on tempdb.

For more information on using sp_helpdb and sp_dboption, see theAdaptive Server Reference Manual.

13. Use the disk unmirror command to disable disk mirroring for yourcurrent Adaptive Server. For more information about diskunmirror, see the Adaptive Server Reference Manual.

14. Adaptive Server 11.9.2 uses more memory for code and internalstructures than previous versions. If you have limited memoryassigned for your Adaptive Server, you may encounterproblems starting the new Adaptive Server during the upgradeprocess.

To avoid this problem, reconfigure your current Adaptive Serverto provide sufficient memory for the upgrade process tocomplete successfully.

Make a note of the current values so that you can reset them afterthe upgrade.

You can accomplish this task in either of two ways:

- Raise the memory allocated to Adaptive Server, or

- Lower other configuration parameters that consume memory.

For example, use sp_configure to set user connections to thedefault value of 25. For more information about sp_configure, seethe Adaptive Server Reference Manual.

15. Restart Adaptive Server when you have finished configuringmemory resources.

16. Record the current cache size to use after you complete theupgrade.

Check the boot sequence in the error log for your currentAdaptive Server for the size of your caches. Values are listed inpages of 2K each in the following lines:

Number of proc buffers allocated: nnn

where nnn is the number of 2K pages in the data cache.

Number of blocks left for proc headers: nnn

where nnn is the number of 2K pages in the procedure cache.



Increasing the Size of the sybsystemprocs Database

sysprocsdev is the default system name for the device that stores thesybsystemprocs database. However, the device is frequently referredto as the sybsystemprocs device, since it stores the sybsystemprocsdatabase.

The sybsystemprocs database stores system procedures and must be atleast 45MB (60MB is recommended). Before you upgrade toAdaptive Server, you must determine whether you need to increasethe size of the sybsystemprocs database.

To determine whether sysprocsdev and sybsystemprocs are largeenough:

1. Log in to Adaptive Server using isql.

2. Use sp_helpdb to determine the size (in megabytes) of thesybsystemprocs database:

1> sp_helpdb sybsystemprocs2> go

If the db_size setting is less than 45MB, increase the size of thedatabase using the alter database command, as explained in“Increasing the Size of sybsystemprocs Only” on page 6-7 or“Increasing sybsystemprocs Beyond the Capacity ofsysprocsdev” on page 6-8.

3. If you have added your own stored procedures to sybsystemprocs,calculate how much space they use and be sure yoursybsystemprocs database is large enough for them.

4. After you have determined how large the sybsystemprocsdatabase needs to be, check to see how much space is availableon your device:

- If you have enough space on the device, follow the instructionsin “Increasing the Size of sybsystemprocs Only” on page 6-7.

- If there is not enough space on sysprocsdev, follow theinstructions in “Increasing sybsystemprocs Beyond theCapacity of sysprocsdev” on page 6-8.

Increasing the Size of sybsystemprocs Only

Use the procedure in this section if:

• The sybsystemprocs database is less than 45MB, and



• The sysprocsdev device is large enough to accommodate anincrease in the size of the sybsystemprocs database to at least45MB.

If you cannot increase the size of sysprocsdev to 45MB, use theprocedure in “Increasing sybsystemprocs Beyond the Capacityof sysprocsdev” on page 6-8.

To increase the size of the sybsystemprocs database:

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

1> use master2> go1> alter database sybsystemprocs on sysprocsdev=292> go

In this example, “sysprocsdev” is the logical name of the existingsybsystemprocs database and “29” is the number of megabytes ofincreased space needed to bring the size up to 45MB.

2. Verify that Adaptive Server has allocated more space tosybsystemprocs by issuing the command:

1> sp_helpdb sybsystemprocs2> go

Increasing sybsystemprocs Beyond the Capacity of sysprocsdev

If the sysprocsdev device is too small, you may receive a messagesimilar to the following when you attempt to increase the size of thesybsystemprocs database:

Couldn’t find enough space on disks to extenddatabase sybsystemprocs

If you cannot fit the enlarged sybsystemprocs database on thesysprocsdev device, use the following procedure.

◆ WARNING!This procedure removes all stored procedures you have created atyour site. Before you begin, back up your local stored procedures orrelocate them to a safe storage area, using the defncopy utility.



To increase sybsytemprocs beyond the capacity of sysprocsdev:

1. Run sp_helpdevice to obtain the physical name of your sysprocsdevdevice.

2. Use drop database to drop the existing sybsystemprocs database,using the name you assigned to sysprocsdev:

1> sp_configure "allow update", 12> go1> reconfigure with override2> go1> use master2> go1> drop database sybsystemprocs2> go1> begin transaction2> delete from sysdevices3> where name = "sysprocsdev"4> go

➤ NoteIf this command affects only one row, commit the transaction. If it affects

more than one row, roll back the transaction and call Sybase Technical

Support.

3. Shut down the server.

4. If your sysprocsdev device was a UNIX file, delete the file at theoperating system level.

For more information on the drop database command, see theAdaptive Server Reference Manual.

5. Reboot the server.

6. Find another device that has 45–60MB of additional free space,or use the disk init command to create an additional device forsybsystemprocs. For example:

1> use master2> go1> disk init2> name = "sysprocsdev2",3> physname = "/mydir/data/sysproc2.dat",4> vdevno = 9,5> size = 307206> go

where /mydir/data is the path to your sysprocsdev device.



The number for vdevno must be available. For information onhow to determine if the vdevno is available, see the SystemAdministration Guide.

The size you provide should be the number of additionalmegabytes of space needed for the device multiplied by 512,because disk init requires the size to be specified in 2K pages. Inthe preceding example, the size is 60MB (60 x 512 = 30720).

For more information on disk init, see the Adaptive Server ReferenceManual.

7. Create a sybsystemprocs database of the appropriate size on thatdevice.

8. Run the installmaster command in the old Sybase installationdirectory, as follows:

isql -Usa -Ppassword -i/old_dir/scripts/installmaster-oinstallmaster.out

where old_dir is the path to the old Sybase installation directory.

Upgrading a Database That Uses Auditing

To upgrade a server that contains a database in which auditing isactivated:

1. Turn off auditing before upgrading:

a. Verify that all Adaptive Server users are logged off.

b. Disable auditing with the following Transact-SQL command:

sp_auditoption 'enable auditing', 'off'

2. Record system procedure audit options before upgrading.

When upgrading, all previous versions of system procedures areoverwritten when sybsystemprocs is populated. Be sure to recordthe audit options for all system procedures. After the upgrade iscomplete, you can reenter the audit options, using sp_audit.

Adaptive Server 11.5.x and later versions include the followingglobal audit options for sp_audit:

- security

- dbcc

These options are turned off by default. To turn these options on,use the following commands:

- sp_audit security on


Adaptive Server Enterprise Version 11.9.2 Upgrading Adaptive Server

- sp_audit dbcc on

The functionality provided by the following obsoletesp_auditoption options are now covered by the new sp_audit securityglobal audit option:

- server boot

- role toggle

The security option is turned off by default. Therefore, if any ofthese options are turned on, reset the security option to on toresume the same auditing actions.

After the upgrade is complete, you must enable auditing again.For more information, see the Security Administration Guide.

Preparing to Upgrade with Replicated Databases

If you have a version of Replication Server running on a system thatwill use Adaptive Server version 11.9.2, follow the instructions inAppendix A, “Preparing to Upgrade Servers with ReplicatedDatabases,” before beginning the upgrade process.

Upgrading Adaptive Server

Use either of the following methods to upgrade Adaptive Server:

• sqlupgrade – provides an X-Windows or Motif GUI for the upgradeprocess. For details, see “Using sqlupgrade” on page 6-12.

• sqlupgraderes – provides a noninteractive, file-based interface forthe upgrade process. sqlupgraderes allows you to upgradeAdaptive Server using a resource file. This is useful if you areupgrading sites with identical servers. For details, see “Usingsqlupgraderes” on page 6-15.

➤ NoteYou cannot use resource files to upgrade Backup Server, Monitor Server,

and XP Server.


Upgrading Adaptive Server Adaptive Server Enterprise Version 11.9.2

Using sqlupgrade

To upgrade to the new release of Adaptive Server using sqlupgrade:

1. Make sure your current server is running.

2. Verify that your SYBASE environment variable points to thelocation of the new Adaptive Server software files you justunloaded.

You also can set the OLDSYBASE environment variable to thelocation of the server you are upgrading, to avoid typing thispath when you run sqlupgrade.

3. Execute sqlupgrade in either of the following ways:

- If you copied sybsetup to your system from the distributionmedia, click Upgrade Adaptive Server in the sybsetup mainmenu.

◆ WARNING!Do not access sqlupgrade from sybsetup on the CD.


$SYBASE/bin/sqlupgrade

A sqlupgrade screen is displayed.

4. Verify that you have performed the tasks mentioned on thescreen, before beginning the upgrade.

➤ Notesqlupgrade automatically copies the interfaces file entry of the server you are

upgrading from the old interfaces file to the new interfaces file.

5. Click OK.



The Specify Sybase Directories screen of sqlupgrade is displayed:

6. Provide the installation directory location for both the newserver release and your current server.

If the SYBASE environment variable is set, sqlupgrade displays thevalue of the SYBASE environment variable as the directorylocation for the new server release.

If the OLDSYBASE environment variable is set, sqlupgradedisplays that value as the directory location for your currentserver.

7. Click OK.

The Adaptive Server Selection screen is displayed.

8. From the list of server names provided, select the server youwant to upgrade.

If the server you are upgrading is not running, sqlupgrade willprompt you to start the server. Click Yes. The server you areupgrading must be running. See “Verifying Your AdaptiveServer Environment” on page 6-2.

9. Click OK.

The SA Password screen is displayed.

10. Enter the password for the System Administrator (SA) login.

11. Click OK.

The Specifying Upgrade Options screen is displayed.



12. Specify an upgrade option.

You can run the upgrade eligibility tests before performing theactual upgrade or you can upgrade immediately after theupgrade eligibility tests run successfully.

The upgrade eligibility tests verify that your current servermeets the requirements for upgrading to the new version. (Theonline help provides a partial list of what the upgrade eligibilitytests check.) If your current server fails the upgrade eligibilitytest, you must fix the problem. Depending on the nature of theproblem, you can either specify an upgrade option from thecurrent screen or restart sqlupgrade.

If sqlupgrade encounters database object names that use Transact-SQL keywords reserved by Sybase, it does not continue untilyou rename the database objects with names that are notreserved words.

After the eligibility tests complete successfully, click OK.sqlupgrade redisplays the Specify Sybase Directories screen.Follow the same steps as you did before. At the SpecifyingUpgrade Options screen, select the option to upgrade the server.

13. Click OK to upgrade your server.

sqlupgrade displays the Status Output screen.

14. View the Status Output screen for the completion status andinformational messages about the upgrade process.



◆ WARNING!Do not interrupt the upgrade, and do not try to connect to AdaptiveServer or run any stored procedures while the upgrade is in progress.

You can also check the progress of the upgrade by viewing thesqlupgrade log in $SYBASE/init/logs/sqlupgradeMMDD.NNN.

If the upgrade is successful, a “Done” message is displayed inthe Status Output screen.

15. When the upgrade completes successfully, you can:

- Click OK to upgrade another server, or

- Exit sqlupgrade, and go to “Post-Upgrade Tasks” on page 6-17.

Using sqlupgraderes

You can upgrade Adaptive Server in noninteractive mode by usingvalues from a resource file that defines the attributes for the server tobe upgraded.

➤ NoteYou cannot upgrade Backup Server, Monitor Server, or XP Server using

resource files.

To upgrade an Adaptive Server using a resource file:

1. Use an ASCII text editor to edit the resource file as described in“Editing a Resource File” on page 6-15.

2. Execute sqlupgraderes using the edited resource file as described in“Upgrading using sqlupgraderes” on page 6-17.

Editing a Resource File

There are two ways to edit a resource file:

• Edit a sample resource file, described in “Editing a SampleResource File” on page 6-16, or

• Edit the resource file created by the sqlupgrade utility described in“Editing a Resource File Created by sqlupgrade” on page 6-16.

For details on the attributes used in a resource file, see “Resource FileAttributes for Upgrading Adaptive Server” on page 6-16



Editing a Sample Resource File

A sample resource file is included in your Adaptive Serverdistribution in $SYBASE/init/sample_resource_files/upgrade.rs. Use anyASCII editor to modify this file to specify the attributes for yourupgrade.

Editing a Resource File Created by sqlupgrade

When you run the sqlupgrade utility, a new file containing the valuesyou specified for that upgrade session is written to:

$SYBASE/init/logs/sqlupgradeMMDD.NNN- server_name.rs

where server_name is the name of the upgraded server. You can createa new resource file by using an ASCII editor to modify this file.

◆ WARNING!Be sure to change device names in the resource file, if necessary,before executing the resource file using sqlupgraderes.

Resource File Attributes for Upgrading Adaptive Server

Table 6-1 on page 6-16 shows the resource file attribute names, theirdefault values, and other options, which you use in the resource filefor upgrading Adaptive Server. The sample resource file included inyour Adaptive Server distribution shows examples of theseattributes.

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

If the resource file you are modifying was created by sqlupgrade, theprefix of the attribute name may vary. sqlupgraderes ignores this prefixwhen processing the resource file.

Table 6-1: Resource file attributes for upgrading Adaptive Server


sybinit.release_directory $SYBASE [path_name_of_old_srv]

sybinit.product sqlsrv

sqlsrv.server_name server_name

sqlsrv.new_config no (required value)

sqlsrv.sa_login current_login


Adaptive Server Enterprise Version 11.9.2 Post-Upgrade Tasks

Upgrading using sqlupgraderes

When you have finished editing your resource file, you can run thefile using sqlupgraderes.

➤ Notesqlupgraderes is a command line tool; therefore, unlike sqlupgrade, it does not

require any X libraries.

To execute sqlupgraderes, at the UNIX prompt, enter:

$SYBASE/bin/sqlupgraderes -r resource_file

where resource_file specifies the resource file containing the attributesthat describe the server to upgrade.

Post-Upgrade Tasks

After you have upgraded to the new version of Adaptive Server,perform the following tasks to make sure your new Adaptive Serveris up and running.

Verifying That Servers Are Running

1. Verify that Adaptive Server and/or Backup Server is running.

To find out whether Adaptive Server or Backup Server iscurrently running, try to log in to the server, using isql:

isql -Usa -P -S server_name

If the server is running, you see the isql prompt:

1>

You can also use the showserver command to determine whetherany Adaptive Server or Backup Server processes are running.For example:

$SYBASE/install/showserver

sqlserv.sa_password current_password

sqlsrv.do_upgrade yes (required value)

Table 6-1: Resource file attributes for upgrading Adaptive Server (continued)



Post-Upgrade Tasks Adaptive Server Enterprise Version 11.9.2

2. Verify the version level of Adaptive Server.

To verify that you are at the new version level, connect to isql andrun the following commands:

1> select @@version2> go

Look for “11.9.2” in the version string.

1> sp_configure "upgrade version"2> go

sp_configure should return the Run Value “11920”.

Restoring Functionality in Adaptive Server

To reset or enable options or functionality you had to change beforethe upgrade:

1. Reset the configuration parameters.

If you changed any configuration parameters before the upgradeto ensure enough memory, such as reducing user connections,use the sp_configure command to set them back to their previousvalues.

2. Determine the effect of upgrade on your caches.

When preparing for your upgrade, you saved the number ofpages for your data and procedure cache, as recorded in theerror log of your previous Adaptive Server version (see“Preparing Your Server for Upgrade” on page 6-3).

Compare the previous values to the 11.9.2 error log values to seewhat effect the upgrade had on your caches. Increase totalmemory, using sp_configure, to add enough memory to yourAdaptive Server to raise your caches back to the previous values.Otherwise, you may see performance degradation in theupgraded Adaptive Server.

For more information on sp_configure and sp_sysmon, see theAdaptive Server Reference Manual and the Performance and TuningGuide.

3. Reset the database options.

Using the sp_dboption command, reset any database options youdisabled before the upgrade.

4. Update your scripts.


Adaptive Server Enterprise Version 11.9.2 Post-Upgrade Tasks

After you complete the upgrade, but before you use theupgraded Adaptive Server, verify that all scripts developed atyour site point to Adaptive Server 11.9.2.

5. Increase the procedure cache memory.

The size of query plans has increased between releases. You maywant to increase both the total memory and the percent ofmemory allocated to the procedure cache.

Stored procedures, triggers and other compiled objects requiremore memory to run than in older versions. The memoryrequired to run a stored procedure increased by almost 100percent between versions 4.9.x and 11.5 and approximately 20percent between versions 10.x and 11.5. Adaptive Server 11.9.2may need more procedure cache for the server to maintain thesame performance.

To increase the procedure cache size, increase the total memoryor the procedure cache percentage using sp_configure. Use thesystem procedure sp_sysmon to monitor procedure cache usage.

For more information on sp_configure and sp_sysmon, see theAdaptive Server Reference Manual and the Performance and TuningGuide. For more information on configuring memory, see theSystem Administration Guide.

6. Remirror devices.

If you unmirrored devices, remirror them, using the disk remirrorcommand.

7. If applicable, enable auditing with the following Transact-SQLcommand:

sp_configure auditing, 1

8. If applicable, enable two-phase commit.

Prior to 11.5, information to track two-phase committransactions was stored in system tables in the master database.These tables are removed during the upgrade to AdaptiveServer 11.9.2. To continue running applications that use two-phase commit, you must create the new sybsystemdb databaseand install the two-phase commit tables in sybsystemdb.

To create the sybsystemdb database:

a. Create a new device in isql, as shown in this example session:


Post-Upgrade Tasks Adaptive Server Enterprise Version 11.9.2

1> disk init2> name = "sybsystemdb_dev",3> physname= " path_to_file ",4> vdevno= 8,5> size = 25606> go

b. Create the new database:

1> create database sybsystemdb on sybsystemdb_dev=52> go

c. From the UNIX prompt, run the script to install the two-phasecommit tables:

isql -Usa -P sa_password -i$SYBASE/scripts/installcommit

9. If you are using Replication Server, you must reenable it afterupgrading to Adaptive Server.

If you are upgrading from 10.0.2.7, grant the replication role toeach login account that the LTM uses to scan transaction logsfrom the SQL Server (SQL_user in the LTM configuration file)and to each maintenance user login account:

1> sp_role "grant", replication_role , login_name2> go

To reenable replication for each primary RSSD being upgraded:

a. Connect to the primary RSSD, and execute the followingcommand to clear the locator for the database:

1> use rssd2> go1> rs_zeroltm dataserver , RSSD2> go

b. Connect to the primary database and enable the truncationpoint for the database:

1> use database2> go1> dbcc settrunc (‘ltm’,’valid’)2> go

To restart replication:

a. Restart the Replication Servers and LTMs.

b. Execute the following Replication Server command for eachsuspended database to resume the Data Server Interface (DSI)connections that were suspended before the upgrade:


Adaptive Server Enterprise Version 11.9.2 Upgrading Backup Server, Monitor Server, and XP Server

1> resume connection to dataserver.database2> go

10. Configure connections for client products.

If you installed any Sybase client products, such as Open Client,use the dsedit utility to edit your interfaces file and to specify theservers to which you want to connect. Start dsedit at the UNIXprompt or from the sybsetup menu.

For more information about establishing client/serverconnections, see the Open Client Configuration Guide orConfiguring Adaptive Server for UNIX Platforms.

Upgrading Backup Server, Monitor Server, and XP Server

Backup Server, Monitor Server, and XP Server do not have a formalupgrade process. To upgrade these products, unload the new serversoftware (using sybsetup) and create the new server (using srvbuild).

➤ NoteInstall a new Backup Server before you dump and load databases on the

upgraded Adaptive Server. Back up all databases, including master, after

successfully upgrading Adaptive Server and Backup Server.

To unload the new release of Backup Server, Historical Server,Monitor Server, and XP Server, follow the instructions in Chapter 3,“Unloading Server Products from Distribution Media.”

To create the new Backup Server, Monitor Server, and XP Serverservers, follow the instructions in Chapter 4, “Installing SybaseServers.”

To create the new Historical Server, see the Historical Serverdocumentation.

What’s Next?

You have completed the upgrade to Adaptive Server 11.9.2.

To add extra functionality to your server, see Chapter 7, “AddingOptional Functionality to Adaptive Server.”

To read about new features and tuning mechanisms for yourupgraded Adaptive Server, see New Functionality in Sybase AdaptiveServer Enterprise 11.9.2.




7 Adding Optional Functionalityto Adaptive Server 7.

This chapter provides instructions for adding optional functionalityto Adaptive Server:

• Installing Auditing 7-1

• Installing Two-Phase Commit 7-9

• Installing Online Help for Transact-SQL Syntax 7-12

• Installing Sample Databases 7-16

Installing Auditing

Auditing is an important part of security in a database managementsystem. Security-related system activity is recorded in an audit trail,which can be used to detect penetration of the system and misuse ofresources. By examining the audit trail, the System Security Officercan inspect patterns of access to objects in databases and can monitorthe activity of specific users. Audit records can be traced to specificusers, enabling the audit system to act as a deterrent to users who areattempting to misuse the system.

A System Security Officer manages the audit system and is the onlyuser who can start and stop auditing, set up auditing options, andprocess audit data.

Audit System Devices and Databases

The audit system is composed of several components including:

• The sybsecurity device and database, which stores auditinformation

• The audit trail, which is composed of a number of audit devicesand tables that you determine at configuration time

• The syslogs transaction log device, which stores transaction logs

The sybsecurity Device and Database

The sybsecurity device stores the sybsecurity database, which iscreated as part of the auditing configuration process. It contains allthe system tables in the model database as well as a system table for

7-2 Adding Optional Functionality to Adaptive Server

Installing Auditing Adaptive Server Enterprise Version 11.9.2

keeping track of server-wide auditing options and system tables forthe audit trail.

Tables and Devices for the Audit Trail

Adaptive Server stores the audit trail in system tables namedsysaudits_01 through sysaudits_08. For example, if you have twoaudit tables, they are named sysaudits_01 and sysaudits_02. At anygiven time, only one of the audit tables is current. Adaptive Serverwrites all audit data to the current audit table. A System SecurityOfficer can use sp_configure tospecify the current audit table.

When you configure Adaptive Server for auditing, you determinethe number of audit tables for your installation. You can specify up toeight system tables (sysaudits_01 through sysaudits_08). Plan to use atleast two or three system tables for the audit trail and to put eachsystem table on its own device, separate from the master device. Ifyou do this, you can use a threshold procedure that archives thecurrent audit table automatically, before it fills up and switches to anew, empty table for subsequent audit records.

Device for syslogs Systems Table

When you configure for auditing, you must specify a separate devicefor the syslogs systems table, which contains the transaction log. Thesyslogs table, which exists in every database, contains a log oftransactions that are executed in the database.

Overview of Audit Installation

To install auditing for the first time in Adaptive Server, you can:

• Use the installsecurity script. For information on using theinstallsecurity script, see the Security Administration Guide.

• Using the auditinit utility. This section includes instructions forusing auditinit.

Pre-Installation Tasks

Determine the location of the raw devices you need for thesybsecurity, syslogs, and sysaudits table devices. You will need toprovide this information later. For information on device selection,see “Pre-Installation Tasks” on page 4-3.


Adaptive Server Enterprise Version 11.9.2 Installing Auditing

It is recommended that you configure your system with theminimum number of auditing devices you require—you mustconfigure for at least three devices. You can add more auditingdevices later with sp_addaudittable. See the Adaptive Server ReferenceManual for information about sp_addaudittable.

Sybase recommends that you:

• Install auditing tables and devices in a one-to-one ratio

Tables that share the same device will share the same upperthreshold limit. These tables cannot be used sequentially when adevice fills up, because they both reside on the same device.

• Install each auditing table on its own device

This enables you to set up a smoothly running auditing systemwith no loss of auditing records.

With two auditing tables, when one fills up, you can switch tothe other. With a third auditing table, if one device fails, theSystem Security Officer can install a new threshold procedurethat changes the device rotation to skip the broken device untilthe device is repaired.

• Make the device larger than the table

When you use only three auditing tables and devices, the size ofthe table and the size of the device can be similar, because youcan obtain more auditing capacity by adding more auditingtables and devices (up to eight). When you are working towardthe upper table and device limit (six to eight), you may want tomake the device considerably larger than the table. Then, youcan expand the table size later towards the upper size of thedevice when a larger auditing capacity is desired, and few or nodevice additions are available.

Audit Installation

To configure Adaptive Server for auditing:

1. Log in to your machine using your Sybase System Administrator(“sa”) user account.

2. Start auditinit at the UNIX prompt:

$SYBASE/install/auditinit

3. When the auditinit menu appears, elect Configure a ServerProduct.



4. Select Adaptive Server.

5. Select Configure an Existing Sybase Server.

6. Select the server you want to configure.

7. Provide the SA Password for the server you selected.

8. From the Sybase Server Configuration screen, select ConfigureAuditing.

As you proceed through the series of menus in auditinit, you canchange the default values, if provided. As you finish with eachmenu, press Ctrl-a to accept the defaults or changed values andmove to the next menu.

CONFIGURE AUDITING

1. Configure auditing: no2. Add a device for audit table(s)3. Add a device for the audit database transaction log4. Delete a device entry5. Change a device entry

List of devices for the audit tables:Logical name Physical name Segment name Table name Size

Device for the audit datbase transaction log:Logical name Physical name Segment name Table name Size

9. From the Configure Auditing screen, select Configure Auditing.

auditinit redisplays the Configure Auditing menu with the value“yes” displayed for Configure Auditing.

CONFIGURE AUDITING1. Configure auditing: yes2. Add a device for audit table(s)3. Add a device for the audit database transaction log4. Delete a device entry5. Change a device entry



Creating a Device for an Audit Table

To create a device for an audit table:



1. From the Configure Auditing screen, select Add a Device forAudit Table(s).

auditinit displays the following menu:

ADD/CHANGE A NEW DEVICE FOR AUDITING1. sybsecurity physical device name:2. Logical name of the device:3. Size of the device (Meg):4. Device size for auditing:

2. Select Sybsecurity Physical Device Name.

3. Enter the full path of the physical device (raw partition) that youlocated in “Pre-Installation Tasks” on page 7-2.

Enter the physical name of the device to use for the auditdatabase (default is''):

/dev/ path_to_partition

where path_to_partition is the path to the raw partition for thedevice.

If you specify an operating system file, the following warningappears:

WARNING: '/secret1/sybase_dr/install/aud1.dat' is a regular filewhich is not recommended for a Server device.

4. Press Return to acknowledge the warning.

auditinit redisplays the Add/Change a New Device for Auditingmenu, which displays the physical name of the device:

ADD/CHANGE A NEW DEVICE FOR AUDITING

1. sybsecurity physical device name:/secret1/sybase_dr/install/aud1.dat

2. Logical name of the device:3. Size of the device:4. Device size for auditing:

5. Proceed through the remaining items on this menu. As you doso, be aware of that the Size of the Device value must be equal toor greater than the Device Size for Auditing value. The DeviceSize for Auditing must be equal to the device size. If you arefollowing Sybase auditing guidelines, you need not change thevalue displayed in Device Size for Auditing.

6. Press Ctrl-a to accept the settings. auditinit returns to theConfigure Auditing menu and displays the device you havecreated.



CONFIGURE AUDITING1. Configure auditing: yes2. Add a device for audit table(s)3. Add a device for the audit database transaction log4. Delete a device entry5. Change a device entryList of devices for the audit tables:

Logical name Physical name Segment name Table name Size6.Audit_01' /secret1/sybase_dr/install/aud1.dat’sysaudits_01 5

7. To add multiple audit devices, repeat steps 1–6.

You can add as many as eight devices. Sybase recommendsadding three or more audit table devices.

After adding a device, auditinit returns to the Configure Auditingmenu and displays all the devices you have created.

CONFIGURE AUDITING1. Configure auditing: yes2. Add a device for audit table(s)3. Add a device for the audit database transaction log4. Delete a device entry5. Change a device entryList of devices for the audit tables:

Logical name Physical name Segment name Table name Size6.Audit_01' /secret1/sybase_dr/install/aud1.dat’sysaudits_01 57.Audit_02' /secret1/sybase_dr/install/aud2.dat'sysaudits_02 5

Creating a Device for the Audit Database Transaction Log

To create a device for the audit database transaction log:

1. From the Configure Auditing menu, select Add a Device for theAudit Database Transaction Log.

auditinit displays the Add/Change a New Device for Auditingmenu.


1. sybsecurity physical device name:2. Logical name of the device:3. Size of the new device (Meg):4. Device size for auditing:

2. Select Sybsecurity Physical Device Name.

auditinit prompts for the physical name and supplies you with adefault, if available:



Enter the physical name of the device to use for the sybsecuritydatabase (default is''):/dev/ path_to_partition

where path_to_partition is the path to the raw partition for thedevice.

3. Enter the full path name of a physical device.

If you enter an operating system file name, the followingwarning appears:

WARNING: '/secret1/sybase_dr/install/audlog'is a regular file, which is not recommended for a Server device.

4. Press Return to acknowledge this warning.

auditinit displays the Add/Change a New Device for Auditingmenu and the value you selected for the physical name of thedevice.


1.sybsecurity physical device name/secret1/sybase_dr/install/auditlog.dat2.Logical name of the device:3.Size of the device:4.Device size for auditing:

5. Proceed through the remaining items on this menu. As you doso, be aware of the following:

- Sybase recommends a minimum size of 2MB for the size of thetransaction log.

- auditinit displays the size in both Size of the Device and inDevice Size for Auditing in the Add/Change a New Device forAuditing menu.

- The Device Size for Auditing default value is equal to the sizeof the device, based on the assumption that you may want todevote the entire device to log for the auditing task. If you wantto use only a subset of the device, you can edit the Size of theDevice value.

6. Press Ctrl-a to accept the settings displayed in the Add/Changea New Device for Auditing menu.

auditinit returns to the Configure Auditing menu and displays allthe devices you have created.



CONFIGURE AUDITING1. Configure auditing: yes2. Add a device for audit table(s)3. Add a device for the audit database transaction log4. Delete a device entry5. Change a device entry


6.Audit_01' /secret1/sybase_dr/install/aud1.dat’sysaudits_01 57.Audit_02' /secret1/sybase_dr/install/aud2.dat'sysaudits_02 5


8.auditlog /secret1/.../auditlog.dat logsegment syslogs 2

7. When you are ready to execute the audit configuration, pressCtrl-a. auditnit returns you to the Sybase Server Configurationscreen.

8. Press Ctrl-a again. auditinit prompts with:

Execute the Sybase Server Configuration now?

9. Enter “y” (yes).

auditinit executes the tasks to install auditing. When theinstallation completes successfully, the following messages aredisplayed:

Running task: install auditing capabilities.....................DoneAuditing capability installed.Task succeeded: install auditing capabilities.

Configuration completed successfully.Press <return> to continue.

Enabling Auditing

After auditing is installed, no auditing occurs until a System SecurityOfficer enables auditing with the sp_configure procedure. For moreinformation, see the Security Administration Guide.

Deleting a Device Entry

To delete a device entry:


Adaptive Server Enterprise Version 11.9.2 Installing Two-Phase Commit

1. Select Delete a Device Entry from the Configure Auditing menu.

2. Enter the number of the device you want to delete.

3. Press Return to delete the entry.

Changing a Device Entry

To change a device entry:

1. Select Change a Device Entry from the Configure Auditingmenu.

2. Enter the number of the device you want to change.

auditinit displays the Add/Change a New Device for Auditingmenu with information on the device you selected:


1. sybsecurity physical device name:/secret1/sybase_dr/install/audlog2. Logical name of the device: aud.log3. size of the new device (Meg): 54. Device size for auditing:5

3. Select each remaining entry you want to change.

4. Press Ctrl-a to save the new entries.

Installing Two-Phase Commit

This section provides instructions for installing two-phase commitfunctionality on Adaptive Server.

Read this section if:

• You did not install two-phase commit at installation time, andyou want to add this functionality.

• Your upgraded Adaptive Server is not configured for two-phasecommit, and you want to add this functionality.

For information on how the upgrade process handles a pre-11.5server that is configured for two-phase commit, see the appropriatestep in “Restoring Functionality in Adaptive Server” on page 6-18.

About Two-Phase Commit

The two-phase commit functionality allows client applications tocoordinate transaction updates across two or more Adaptive Servers


Installing Two-Phase Commit Adaptive Server Enterprise Version 11.9.2

and treats these transactions, which may be on different AdaptiveServers, as though they are a single transaction. Two-phase commitguarantees that either all or none of the databases on theparticipating Adaptive Servers are updated.

For additional background and configuration information on two-phase commit transactions, see the Open Client DB-Library/CReference Manual.

Enhancements to Two-Phase Commit

This section describes the enhancements made to two-phase committransactions in version 11.5.

The enhancements are:

• Improved space and log management by relocating thespt_committab table from the master database to a new systemdatabase, sybsystemdb. For details, see “spt_comittab Moved tosybsystemdb” on page 7-10.

• Improved performance by using a random value for the commitidentifier, commid. For details, see “Improved Performance for theCommit Identifier” on page 7-10.

spt_comittab Moved to sybsystemdb

The spt_committab table in Adaptive Server stores information aboutand tracks the completion status of each two-phase committransaction. All activities made against spt_committab are logged.Prior to 11.5, spt_committab resided in the master database. However,it has been moved to a different database (sybsystemdb) because thelogging activity against spt_committab for two-phase committransactions can fill up the master transaction log, causing frequentspace management problems.

Moving spt_committab makes space management and recovery oftwo-phase commit transactions easier for two reasons:

• The dump tran command can be used against sybsystemdb.

• Unlike the master database, the sybsystemdb database is extensible.

Improved Performance for the Commit Identifier

In 11.5 Adaptive Server and later versions, the value of the commitidentifier, commid, in the spt_committab table, becomes a random


Adaptive Server Enterprise Version 11.9.2 Installing Two-Phase Commit

value between 1 and 2147483647 (231-1), instead of a monotonicallyincreasing value. This reduces page lock contention on the rowwhere the maximum commid resides when several distributedtransactions try to insert an entry into the spt_committab table. Thespt_committab table still has a unique, clustered index.

Configuring for Two-Phase Commit

After installing or upgrading Adaptive Server, you must create thesybsystemdb database and run the installcommit script as described inthe following procedures.

To create sybsystemdb:

1. Determine the location of the raw partition device where youwill be storing the sybsystemdb database. You will need toprovide this information in step 2.

Allocate at least 5MB for the size of sybsystemdb and itstransaction log file.

For information on device selection, see “Pre-Installation Tasks”on page 4-3.

2. Use the disk init command to create the data and log devices forsybsystemdb.

For example:

disk init name="sybsysdb_dat",physname="/dev/ path_to_partition ",vdevno=5, size=1536

disk init name="sybsysdb_log",physname="/dev/ path_to_partition ",vdevno=5, size=1024

For detailed information on disk init, see the Adaptive ServerReference Manual.

3. Use the create database command to create the sybsystemdbdatabase on the devices you created in step 2:

use mastercreate database sybsystemdb on sybsysdb_dat = 5 log onsybsysdb_log = 5

For details on using create database, see the Adaptive ServerReference Manual.

4. Use sp_adduser to create the “guest” user for the sybsystemdbdatabase.


Installing Online Help for Transact-SQL Syntax Adaptive Server Enterprise Version 11.9.2

For more information about sp_adduser, see the Adaptive ServerReference Manual.

The installcommit script performs the following tasks:

- Creates the spt_committab table in the sybsystemdb database.

- Stores two-phase commit system procedures in sybsystemprocs(except for sp_probe_xact, which is stored in the master database).

If necessary, installcommit also performs the following tasks:

- Modifies pre-11.5 two-phase commit stored procedures topoint to sybsystemdb.

- Copies the contents of spt_committab, located in the masterdatabase, to sybsystemdb.

- Drops the spt_committab table from the master database.

- Increases the value of the sp_configure number of open databasesparameter by 1.

To run the installcommit script, enter the following command at theUNIX prompt:

isql < $SYBASE/scripts/installcommit

You can now execute two-phase commit applications.

Installing Online Help for Transact-SQL Syntax

This section provides instructions for installing online help forTransact-SQL syntax.

Online Syntax Help: sp_syntax

The $SYBASE/scripts directory contains scripts for installing thesyntax help database, sybsyntax. You can retrieve this data with thesp_syntax system procedure. For more information on sp_syntax, seethe Adaptive Server Reference Manual.


Adaptive Server Enterprise Version 11.9.2 Installing Online Help for Transact-SQL Syntax

The scripts directory contains one or more of the sp_syntax scriptsshown in Table 7-1, depending on which Sybase products areincluded with your server:

All Adaptive Server installations receive the ins_syn_sql script. Thisscript includes syntax information for Transact-SQL, the systemprocedures, and the Sybase utilities. When you execute this script,you install the SQL portion of the sybsyntax database.

You can install any of these scripts, depending on the need for Sybaseinformation on your server. The first script you execute creates thesybsyntax database and the needed tables and indexes. Any scriptsthat you execute after the first one add to the existing information inthe database. If you execute a script that was executed previously, thepreviously installed rows of information will be deleted from thetable in the database and then reinstalled.

Default Device for the sybsyntax Database

The sybsyntax database requires 2MB on your database device. Bydefault, the sybsyntax installation scripts install the sybsyntaxdatabase on the device that is designated as the default databasedevice. The default database device is the master device.

If you have not changed the status of the master device (which isinstalled as the default disk) or specified another default device, thescripts install sybsyntax on the master device. This configuration isnot recommended because sybsyntax uses valuable space, which isbest used for the system tables.

To avoid installing sybsyntax on the master device, do one of thefollowing:

• Use sp_diskdefault to specify a default device other than the masterdevice. See the Adaptive Server Reference Manual for informationon sp_diskdefault.

Table 7-1: sp_syntax installation scripts

Script Product

ins_syn_cl Open Client Client-Library™

ins_syn_esql Embedded SQL™

ins_syn_os Open Server

ins_syn_sql Transact-SQL


Installing Online Help for Transact-SQL Syntax Adaptive Server Enterprise Version 11.9.2

• Modify each sybsyntax installation script that you plan to executeto specify a different device, as explained in the following section.

Installing sybsyntax

For each sybsyntax installation script that you want to execute:

1. Determine the type (raw partition, logical volume, operatingsystem file, and so on) and location of the device where you planto store the sybsyntax database. You will need to provide thisinformation later.


2. Make a copy of the original script. Be sure you can access thiscopy, in case you experience problems with the edited script.

3. Use a text editor to edit the script, if necessary, to change thedefault device from the master device to the device created instep 1. For information on the default device, see “DefaultDevice for the sybsyntax Database” on page 7-13.

- Comment out the following section, which specifies the defaultdevice:

/* create the database, if it does not exist */if not exists (select name from sysdatabaseswhere name = "sybsyntax")begin

/* create the sybsyntax table if it doesn’t exist *//* is the space left on the default databasedevices > size of model? */if (select sum (high-low +1) from sysdevices where status& 1 = 1) - (select sum(size) from sysusages, sysdevices

where vstart >= sysdevices.lowand vstart <= sysdevices.highand sysdevices.status &1 = 1) >(select sum(sysusages.size) from sysusageswhere dbid = 3)


Adaptive Server Enterprise Version 11.9.2 Installing Online Help for Transact-SQL Syntax

begincreate database sybsyntax

endelsebegin

print "There is not enough room on the defaultdevices to create the sybsyntax database."

returnend

end

- After you have commented out this entire section, add a linelike this to the script:

create database sybsyntax on device_name

where device_name is the name of the device where you want toinstall sybsyntax.

4. Execute the script with a command like the following:

isql -U sa -P password -S servername < $SYBASE/scripts/ins_syn_sql

where sa is the user ID of the System Administrator, password isthe System Administrator’s password, and servername is thename of the Adaptive Server on which you plan to install thedatabase.

If you have set the DSQUERY environment variable to theservername, you can replace the server name with DSQUERY. Forexample:

isql -U sa -P password -S$DSQUERY < $SYBASE/scripts/ins_syn_sql

5. To ensure that you have installed the sybsyntax database and thatit is working correctly, use isql to log in to the server on whichyou installed the database, and execute sp_syntax. For example:

isql -Usa -Ppassword -Sservername1> sp_syntax "select"2> go

Adaptive Server displays a list of commands that contain theword or word fragment “select.”

◆ WARNING!The ins_syn_cl and ins_syn_os scripts conflict. If you execute bothscripts, errors occur.


Installing Sample Databases Adaptive Server Enterprise Version 11.9.2

Installing Sample Databases

This section describes how to install the U.S. English andinternational language sample databases. For installationinstructions specific to each sample database, see the followingsections:

• “Installing the pubs2 and pubs3 Databases” on page 7-17

• “Installing the interpubs Database” on page 7-18

• “Installing the jpubs Database” on page 7-19

Default Devices for Sample Databases

The $SYBASE/scripts directory contains scripts for installing theus_english sample database, foreign language sample databases,and the image data associated with the U.S. English pubs2 sampledatabase.

Each sample database requires 2MB on your database device. Bydefault, the sample database installation scripts install the sampledatabases on the device that is designated as the default databasedevice, which is the master device.

If you have not changed the status of the master device or specifiedanother default device, the scripts install the sample databases on themaster device. This configuration is not recommended because ituses valuable space that is best used for system tables.

To avoid installing sample databases on the master device, do one ofthe following:

• Use sp_diskdefault to specify a default device other than the masterdevice. See the Adaptive Server Reference Manual for informationon sp_diskdefault.

• Modify each sample database installation script to specify adifferent device.

pubs2 and pubs3 Databases

The U.S. English sample databases are pubs2 and pubs3. The pubs3sample database is an updated version of pubs2 and is useful forreferential integrity examples. These databases are used for most ofthe examples in the Transact-SQL User’s Guide.


Adaptive Server Enterprise Version 11.9.2 Installing Sample Databases

Installing the pubs2 and pubs3 Databases

To install pubs2 and pubs3:

1. Determine the type (raw partition, logical volume, operatingsystem file, and so on) and location of the device where you willbe storing the pubs2 and pubs3 databases. You will need toprovide this information later.


2. Make a copy of the original installpubs2 and installpubs3 scripts. Besure you can access the copies, in case you have problems withthe edited scripts.

3. Use a text editor to edit the script, if necessary, to specify adefault device other than the master device, or use sp_diskdefault.For information on the default device, see “Default Devices forSample Databases” on page 7-16.

4. Execute the script with a command like the following:

isql -U sa -P password -S servername < $SYBASE/scripts/installpubs2

or

isql -U sa -P password -S servername < $SYBASE/scripts/installpubs3

where sa is the user ID of the System Administrator, password isthe System Administrator’s password, and servername is theserver on which you want to install pubs2 and pubs3. If either ofthe databases currently exists, the script drops it and then re-creates it.

5. To install the image data associated with pubs2 (pubs3 does notuse image data), repeat steps 1–3 with the script installpix2 afteryou have installed pubs2.

➤ NoteThe image data requires a fair amount of space—there are six pictures, two

each in the PICT, TIF, and Sun raster file formats. Run installpix2 only if you

want to use or test the image datatype. Sybase does not supply any tools

for displaying image data. You must use appropriate screen graphics tools

to display the images, after you have extracted them from the database.



interpubs Database

interpubs is a database similar to pubs2 that contains French andGerman data. This data contains 8-bit characters and is available foruse at Adaptive Server installations using the ISO 8859-1 (iso_1) orRoman8 (for HP-UX) character set. To display the French andGerman data correctly, you must set up your terminal to display 8-bitcharacters.

Installing the interpubs Database

To install interpubs:

1. Be sure iso_1 or Roman8 is installed as the default character setor as an additional character set.

2. Determine the type (raw partition, logical volume, operatingsystem file, and so on) and location of the device where you willbe storing the interpubs database. You will need to provide thisinformation later.


3. Make a copy of the original installintpubs script. Be sure you canaccess this copy, in case you experience problems with the editedscript.

4. Use a text editor to edit the script, if necessary, to specify adefault device other than the master device, or use sp_diskdefault.See “Default Devices for Sample Databases” on page 7-16.

5. Execute the installintpubs script, using the -J flag to ensure that thedatabase is installed with the correct character set:

See Utility Programs for UNIX Platforms for more information onthe -J option in isql.

jpubs Database

If you installed the Japanese Language Module with your AdaptiveServer, $SYBASE/scripts contains the installjpubs script for installingthe jpubs database. jpubs is a database similar to pubs2 that containsJapanese data. installjpubs uses either the EUC-JIS (eucjis) or theShift-JIS (sjis) character set.


Adaptive Server Enterprise Version 11.9.2 Installing Sample Databases

Installing the jpubs Database

To install the jpubs database:

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

2. Verify that the EUC-JIS or Shift-JIS character set (depending onwhich characters you want for jpubs) is installed as AdaptiveServer’s default character set or as an additional character set.

3. Determine the type (raw partition, logical volume, operatingsystem file, and so on) and location of the device where you willbe storing the jpubs database. You will need to provide thisinformation later.


4. Make a copy of the original installjpubs script. Be sure that you canaccess this copy, in case you experience problems with the editedscript.

5. Use a text editor to edit the script, if necessary, to specify adefault device other than the master device, or use sp_diskdefault.See “Default Devices for Sample Databases” on page 7-16.

6. Execute the installjpubs script, using the -J flag to ensure that thedatabase is installed with the correct character set:

isql -U sa -P password -S servername -Jeucjis \< $SYBASE/scripts/eucjis/installjpubs

or:

isql -U sa -P passwor d -S servernam e -Jsjis \< $SYBASE/scripts/sjis/installjpubs

See Utility Programs for UNIX Platforms for more information onthe -J option in isql.

➤ NoteSince you may want to refresh or make new copies of the sample

databases, back up the original and edited versions of the installation

scripts and store the copies in a safe place.

Maintaining the Sample Databases

The sample databases contain a “guest” user that allows access to thedatabase 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 aboutthe “guest” user and a list of “guest” permissions, see the SecurityAdministration Guide.

If possible, and if space allows, give each new user a clean copy of thesample 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 begintransaction command before updating a sample database. After theuser has finished updating one of the sample databases, he or she canissue the rollback transaction command to undo the changes.


8 Starting and Stopping Servers 8.

This chapter describes how to start and stop Adaptive Server,Backup Server, Monitor Server, and XP Server.

Topics include:

• Overview 8-1

• Starting Servers From the UNIX Command Line 8-1

• Starting Servers When the Operating System Restarts 8-3

• Stopping Servers 8-3

Overview

After you create or upgrade Adaptive Server (using srvbuild orsqlupgrade), Adaptive Server, Backup Server, and Monitor Server arerunning.

XP Server is not started by the installation process. XP Server isstarted only when any XP command is issued through isql.

The methods described here are used to start Adaptive Server,Backup Server, and Monitor Server after a shutdown for databasemaintenance, because of an operating system crash, or for someother reason.

You can start Adaptive Server, Backup Server, and Monitor Server onUNIX in two ways:

• Entering commands from the UNIX command line

• Configuring your operating system so that the servers startautomatically when the operating system starts

Starting Servers From the UNIX Command Line

You can start Adaptive Server, Backup Server, Monitor Server, orfrom the UNIX command line by using runserver files and startserver commands. You can move the Adaptive Server sharedmemory files by adding a flag to the runserver file.

8-2 Starting and Stopping Servers

Starting Servers From the UNIX Command Line Adaptive Server Enterprise Version 11.9.2

Using the Runserver File

Each time a new Adaptive Server, Monitor Server, or Backup Server,is installed, the srvbuild program creates a runserver file that containsthe information required to restart that server. Runserver files arecreated in the $SYBASE/install directory. For Adaptive Server, therunserver file is named RUN_servername, where servername is thename of the server.

For example, the runserver file name for an Adaptive Server namedTEST is RUN_TEST.

For Backup Server, the runserver file name is RUN_servername_back.The runserver file name for Monitor Server is RUN_servername_mon,where servername is the name of the server.

➤ NoteDo not delete the runserver file that is created in $SYBASE/install. This file

is used to restart servers when you customize your installation. If you need

the runserver file in another location, make a copy of the original runserver

file in the new location.

The runserver file for a server named SYBASE is namedRUN_SYBASE. If the runserver file for your current Adaptive Serveris named RUNSERVER, you must change the name to RUN_SYBASEduring the upgrade process.

Using the startserver Command

To start an Adaptive Server or Backup Server from the commandline, enter:

$SYBASE/install/startserver [ -f runserverfile ]

where $SYBASE/install/startserver is the full path name of thestartserver utility, and runserverfile is the full path name of therunserver file (usually $SYBASE/install/RUN_servername).

If your Adaptive Server is named SYBASE, the runserver filespecification is optional.

You must have read and write permissions on the master device foran Adaptive Server in order to start it with startserver. See UtilityPrograms for UNIX Platforms for more information about startserver.


Adaptive Server Enterprise Version 11.9.2 Starting Servers When the Operating System Restarts

Although startserver runs Adaptive Server in the background, it doesnot return to the operating system prompt after restarting. AfterAdaptive Server has been restarted, press Return to return to theoperating system prompt.

Using the monserver Command

Use the monserver command to start Monitor Server from the UNIXcommand line. For details, see the Adaptive Server Enterprise MonitorServer User’s Guide.

Starting Servers When the Operating System Restarts

The $SYBASE/install/sybinstall.sh script sets up a correct shellenvironment and installs a system run-level script in a Sybase useraccount. The script allows the automatic boot and automaticshutdown of configured Sybase Server products such as AdapativeServer Enterprise, Backup Server, and Open Server.

To run sybinstall.sh:

1. Log in as root.

2. Use the RPM query command to set the SYBASE environmentvariable. For example:

# export SYBASE=‘rpm -q --queryformat ’%{installprefix}’ sybase-common‘

3. Run the sybinstall.sh script to perform the post-installation.Enter:

# $SYBASE/install/sybinstall.sh

4. Create the correct runtime links for shutdown and boot. Enter:

# /sbin/chkconfig sybase on

Stopping Servers

The preferred method of stopping Adaptive Server or Backup Serveris to use the Transact-SQL shutdown command. For Monitor Server,use the sms_shutdown command.

Only the System Administrator has permission to issue a shutdowncommand. Using a shutdown command minimizes the amount ofwork that automatic recovery needs to do when the servers arerestarted.


Stopping Servers Adaptive Server Enterprise Version 11.9.2

Stopping Adaptive Server

To shut down Adaptive Server:

1. Use isql to log in to an Adaptive Server account with SystemAdministrator privileges:

isql -Usa -P password -S server_name

2. Enter:

1> shutdown2> go

The default for the shutdown command is with wait. The with wait optionallows Adaptive Server to finish executing SQL statements orprocedures, perform a checkpoint in each database, disable newlogins, and perform other shutdown tasks.

Issuing the shutdown command prints a message like this to sterr:

SQL Server SHUTDOWN by request.The SQL Server isterminating this process.CT-Library error:

This is normal behavior. If the message indicates that AdaptiveServer is waiting for processes to complete, and you need to stopAdaptive Server immediately, you can use the shutdown with nowaitcommand. shutdown with nowait does not wait for currently executingstatements to finish and does not perform checkpoints in everydatabase.

Stopping Backup Server

Use the following procedure to stop Backup Server.

To shut down a Backup Server:

1. Use isql to log in to a Sybase account with System Administratorprivileges:

isql -U sa -P password -S server_name

2. Enter:

1> shutdown SYB_BACKUP2> go

After you shut down a Backup Server, you must wait at least 30seconds before restarting it.

Issuing the shutdown command prints a message similar to thefollowing to the stderr file:


Adaptive Server Enterprise Version 11.9.2 Stopping Servers

Backup Server: 3.48.1.1: The Backup Server will godown immediately.Terminating sessions.

This is normal behavior. If a message indicates that Adaptive Serveror Backup Server is waiting for processes to complete, and you needto stop Adaptive Server or Backup Server immediately, you can usethe shutdown with nowait command. shutdown with nowait does not wait forcurrently executing statements to finish and does not performcheckpoints in every database.

Using shutdown with nowait for Backup Server can cause inconsistent orincomplete dumps and loads. Use this command only whennecessary.

For more information on the shutdown command, see the AdaptiveServer Reference Manual.

Stopping Monitor Server

You must shut down Monitor Server before restarting AdaptiveServer. If Adaptive Server stops, make sure that Monitor Server isshut down before you restart Adaptive Server. Monitor Server mustbe shut down to release resources. Otherwise, Adaptive Server maynot be able to allocate enough resources to restart.

For more information on stopping Monitor Server, see the AdaptiveServer Enterprise Monitor Server User’s Guide.

Using the kill Command

◆ WARNING!Use the kill command in Adaptive Server and Backup Server only as alast resort.

When possible, use the Transact-SQL shutdown or shutdown with nowaitcommand. Do not use kill with the -9 flag because it exits the serverwithout running a checkpoint to ensure that all database changes arewritten to the database device. Adaptive Server may also exitwithout removing associated shared memory files and networkhandlers.



Because Adaptive Server and Backup Server are backgroundprocesses, they can be killed from the operating system by theirowner or by “root” with the UNIX kill command. The syntax is:

kill pid

where pid is the process identification of any dataserver or backupserverprocess, as determined by the showserver command. Killing oneengine for a particular Adaptive Server kills all engines for thatserver.

If more than one Adaptive Server is running on the same system, youmust be careful that the engine you kill is associated with the correctAdaptive Server. The following example from a multiprocessing(SMP) machine shows how to using showserver to determine whichserver processes are running. (The output has been reformatted forclarity; it looks different when displayed on a monitor.)

showserver

This example shows four running dataserver processes with operatingsystem process identifications 3320, 3321, 3322, and 3323. (dataserver isthe executable form of the Adaptive Server program.) AdaptiveServer running on a unprocessed has one dataserver process. A singleAdaptive Server running on a multiprocessor may have more thanone dataserver process.

showserver shows how many Adaptive Server-related processes areon the system. For SMP Adaptive Server running multiple engines,showserver shows as many dataserver processes as there are enginescurrently running. In the preceding example, three engines arerunning in a single Adaptive Server. Child engine processes for thedataserver have the -ONLINE: argument.

Each child engine has a parent process identification (PPID) that isequal to the process identification (PID) of the parent. In the exampleabove, the PID of the parent server is 3320. The other three enginesspawned by the parent process have the same PPID.

If the PPIDs appear to be unrelated, and there is more than onedataserver process, then more than one Adaptive Server is running onthe system.

UID PID PPID C STIME TTY TIME COMDjorge 3320 1 80 10:31:40 pts/4 302:15 dataserverjorge 3321 3220 80 10:31:45 pts/4 324:47 dataserver -ONLINE:1 -d teamsterjorge 3322 3320 80 10:31:45 pts/4 326:02 dataserver -ONLINE:2 -d teamsterjorge 3323 3320 80 10:31:45 pts/4 328:56 dataserver -ONLINE:3 -d teamster


Adaptive Server Enterprise Version 11.9.2 Stopping Servers

Shutdown and Shared Memory Files

When Adaptive Server starts, it creates the following files in$SYBASE to store information about the shared memory segmentsthat it uses:

When Adaptive Server is shut down in a normal manner, the sharedmemory files are automatically removed. If Adaptive Server crashesor is stopped with the kill -9 command, these files are not deleted. Youneed read and write permissions on these files to restart AdaptiveServer after a crash or a kill -9 command, as Adaptive Server must beable to overwrite the previously created shared memory files.

Please consult the Linux ipcs(1) options for stale shared memorysegment removal.

# ipcs -a

# ipcrm -m <ID>




9 Troubleshooting 9.

This chapter provides instructions for troubleshooting installationerror messages.

If this chapter does not describe the error message you areencountering, see the Troubleshooting and Error Messages Guide.


• Overview 9-1

• Error Log Locations 9-1

• Solutions to Common Installation Problems 9-2

Overview

For Sybase server products, there are two categories of errors:

• Errors generated by the installation, upgrade, and setup utilities

• Errors generated by the server (Adaptive Server, Backup Server,and so on)

To determine the cause of an error, first look in the log file of theutility being used, to identify the task the utility was performingwhen it failed. Then check the server error log. See “Error LogLocations” on page 9-1 for the location of the error log files for theinstallation utilities and the servers.

Error Log Locations

The information in the error logs will help you determine the reasonand possible solution for an error message.

9-2 Troubleshooting

Solutions to Common Installation Problems Adaptive Server Enterprise Version 11.9.2

For Installation Utilities

Table 9-1 lists the default error log locations for the installation,upgrade, and setup utilities.

For Sybase Servers

Table 9-2 lists the default error log locations for each Sybase server.

Solutions to Common Installation Problems

If this section does not describe the problem you are experiencing,see the Troubleshooting and Error Messages Guide.

Table 9-1: Error log locations for installation utilities

Utility Error Log Location

srvbuildsrvbuildres

$SYBASE/init/logs/srvbuildMMDD.NNN

where MM is the month, DD is the date, and NNN is a 3-digit number identifying the srvbuild session

sqllocsqllocres

$SYBASE/init/logs/sqllocMMDD.NNN

sqlupgradesqlupgraderes

• $SYBASE/init/logs/sqlupgradeMMDD.NNN

• $SYBASE/upgrade/upgrade.NNN (a temporary filecreated by the upgrade process)

Table 9-2: Error log locations for Sybase servers

Server Default Error Log Path and File Name

Adaptive Server $SYBASE/install/servername.log

Backup Server $SYBASE/install/servername_back.log

Monitor Server The directory from which Monitor Server is started. Theerror log file name is ms.log.

XP Server Writes to the Adaptive Server error log.


Adaptive Server Enterprise Version 11.9.2 Solutions to Common Installation Problems

You Do Not Have a 17-Inch Monitor

If you do not have a 17-inch monitor, you may need to change to asmaller font size to enable the X-Windows/Motif GUI installationand setup utilities (srvbuild, sybsetup) to be displayed properly.

To change to a smaller font size, issue these UNIX commands:

% cd $SYBASE% chmod +w xappdefaults% cd xappdefaults% chmod +w *% foreach i(*)? cat $i | sed -e "s/140/100/g" | sed -e "s/^#D/D/g" | sed -e"s/^#S/S/g" > p? mv p $i? end%

The installation utilities will use approximately 25 percent lessscreen space.

If sybsetup Prompts for a Customer Authorization String (CAS)

Contact Technical Support or an authorized support representative ifyou receive a prompt from sybsetup for a CAS.

Cannot Eject the CD from the Drive

If you cannot eject the CD from the drive:

• Check to see whether the CD drive path (/cdrom) is the currentdirectory (pwd) in a UNIX terminal window. If it is, change (cd) toanother directory.

• Check for sybhelp processes (by invoking help screens withinsybsetup). If these processes exist, kill them using the UNIX killcommand.

DISPLAY Environment Variable Not Set Correctly

If you run a command, such as sybsetup or sybupgrade, and you get thiserror message:

The DISPLAY environment variable is not setcorrectly.

9-4 Troubleshooting


it means that the DISPLAY environment variable on the remotemachine is not set correctly to display the sybsetup user interface toyour local machine.

To correct the problem, enter this command at the UNIX prompt ofthe remote machine:

For C shell:

setenv DISPLAY host_name:0.0

For Bourne shell:

DISPLAY=host_name:0.0; export DISPLAY

where host_name is the name of the machine on which you wantthe sybsetup interface to appear (that is, on your local machine).

Connection Refused; Client Not Authorized to Connect to Server

If you run sybsetup and you get this error message:

Xlib: connection to "host_name" refused by serverXlib: Client is not authorized to connect to Serverxhost: unable to open display "host_name"

it means the remote machine does not have permissions to displaythe user interface on the local machine where you are working.

To correct the problem:

1. Enter the following command at the UNIX prompt of your localmachine:

xhost + remote_machine

where remote_machine is the machine on which you are runningsybsetup.

2. Restart sybsetup.

Address Already in Use

If you receive the following message from srvbuild:

kernel: ninit: bind, Address already in use

it means you entered a port number that is already in use.

To correct the problem, enter a different port number on the srvbuildscreen. The command netstat -a produces a list of port numbers in use.


Adaptive Server Enterprise Version 11.9.2 Solutions to Common Installation Problems

Adaptive Server Failed to Boot

The shared memory of the operating system may not be set highenough.

To correct the problem:

1. See Chapter 4, “Installing Sybase Servers,” for instructions onadjusting the shared memory value.

2. Start the installation or upgrade process again.

Cannot Start XP Server

You may receive the following message from XP Server, when it isinvoked by xp_cmdshell or some other extended stored procedure:

Msg 11018, Level 16, State 1:Procedure "xp_cmdshell", Line 2:XP Server must be up for ESP to execute.(return status = -6)

Verify that there is an XP Server entry in Adaptive Server’s sysserverstable. If you created XP Server separately (in a different srvbuildsession) from Adaptive Server and you did not specify a relatedAdaptive Server, srvbuild cannot update the sysservers table.

Use sp_addserver to add an entry to the sysservers table.

Pre-Upgrade Eligibility Test Failed

Check to see whether the name of the runserver file and the servername in the interfaces file are the same. If they are not, correct therunserver file name, and rerun the upgrade.

9-6 Troubleshooting


Installation Guide for Linux/Intel A-1

A Preparing to Upgrade Serverswith Replicated Databases A.

If you have a version of Replication Server running on a system thatwill use Adaptive Server version 11.9.2, follow the instructions inthis appendix before beginning the upgrade process.

You must disable replication, or the upgrade may fail.

➤ NoteThe procedures described here do not upgrade Replication Server itself.

For information on upgrading Replication Server, see your Replication

Server documentation.

To determine whether your existing server contains replicateddatabases:

1. In isql, connect to the Adaptive Server you are upgrading.

2. Run the following command in each database (including systemdatabases):

1> dbcc gettrunc2> go

3. If the command returns “1” for “ltm_trunc_state” in anydatabase, replication is enabled in that database.

◆ WARNING!As a safeguard, perform a dump database and a dump transaction beforeexecuting the procedures in the following sections.

Suspend Transaction Activity in the Databases and Suspend Replication

To suspend replication of and transaction activity in the databases:

1. Verify that subscriptions you have created have reached a“valid” state at the primary Replication Server and that no useris creating subscriptions for the data in the database you areupgrading.

2. Run rs_helproute in each Replication Server System Database(RSSD) being upgraded to determine each RSSD’s status.

A-2 Preparing to Upgrade Servers with Replicated Databases

Drain Transaction Logs for Primary Databases Adaptive Server Enterprise Version 11.9.2

The status of all routes should be “Active.” Refer to theReplication Server documentation to resolve route problems.

3. Shut down applications using the databases you are upgrading.

4. Use the admin who command in Replication Server to identifyexisting Data Server Interface (DSI) connections to the dataserver being upgraded.

5. While leaving DSI connections for RSSDs running, suspend DSIconnections to non-RSSD databases you are upgrading by usingthe following command for each database:

1> suspend connection to dataserver.database2> go

Drain Transaction Logs for Primary Databases

Use the logmon script located in the $SYBASE/upgrade directory on thedataserver you are upgrading to drain the logs. You will beprompted to start and stop Replication Servers and LTMs, as the logsare being drained.

➤ NoteBefore running the logmon command, set your SYBASE environment

variable to the location of your current Adaptive Server. You must execute

logmon using the full pathname of your current Adaptive Server installation.

After running the logmon command, set the SYBASE environment variable

back to the location for your new Adaptive Server.

The syntax for logmon is:

logmon -S server_name -U user_name -P password[-l file_name ] [-help] [-version]

where server_name is the SQL Server to be upgraded and file_name isthe file into which the LTM restoration scripts are to be written. Youuse this file to reenable replication after the upgrade, as described in“Restoring Functionality in Adaptive Server” on page 6-18.

The -help option displays the help screen, and the -version optiondisplays the version of the logmon script.

When the transaction logs are drained, logmon displays the full pathname of the file logmon.server_name, which you will need later toreenable replication after upgrading.


Adaptive Server Enterprise Version 11.9.2 Drain Transaction Logs for Primary Databases

Manually Draining the RSSD Transaction Log

Manually drain the transaction log of each primary RSSD in the dataserver you are upgrading.

If Replication Server has routes to other Replication Servers, youmust make sure that Replication Server processes all transactions inthe RSSD transaction log before you upgrade the databases.

You can make sure the transaction log is completely processedcreating a replication definition in the primary Replication Serverand then watch for it to appear in the replicate Replication Sever’sRSSD. When the replication definition is in the replicate RSSD, thelog is fully processed.

To create a replication definition for ensuring the RSSD log isprocessed:

1. In the primary Replication Server, create a temporary replicationdefinition:

1> create replication definition rep_def_name2> with primary at dataserver.database3> (column_a int)4> primary key (column_a)5> go

The data server and database names must be valid, but thereplication definition does not have to reference an actual table.

2. In the replicate RSSD, execute the following query to seewhether the replication definition has arrived from the primaryRSSD:

1> select * from rs_objects2> where objname = ‘rep_def_name’3> go

When the replication definition has arrived in the replicate RSSD, theRSSD transaction log has been drained.


Disable the LTM Truncation Point Adaptive Server Enterprise Version 11.9.2

Disable the LTM Truncation Point

Before you upgrade databases, disable the LTM truncation point foreach primary RSSD in your data server by completing the followingsteps:

1. Make sure that you have shut down the LTMs for the databasesyou are upgrading and that you have shut down ReplicationServers for the RSSDs you are upgrading.

2. In each primary RSSD, execute the following commands to turnoff the LTM truncation point:

1> use database2> go3> dbcc settrunc (‘ltm’, ‘ignore’)4> go

If the dbcc settrunc command fails, execute the followingcommands to allow SQL Server to recognize that the LTM isdisconnected:

1> begin tran2> commit tran3> go 500

To turn off the LTM truncation point, enter the followingcommand:

1> dbcc settrunc (‘ltm’,’ignore’)2> go

Drain Each Replicated Primary

Manually drain the transaction log of each replicated primary in thedata server you are upgrading:

1. Note the timestamp of the last log page:

1> use database2> go

1> dbcc traceon (3604)2> go

This sends trace output to the terminal.

1> select root from sysindexes where name =‘syslogs’2> go

The value returned is the last log page.


Adaptive Server Enterprise Version 11.9.2 Drain Each Replicated Primary

1> dbcc page (<database>, <last_log_pageid>, 0)2> go

The timestamp is a 6-byte hexadecimal number. Save this valuefor reference in step 3.

2. Append to the log:


1> begin tran2> commit tran3> go 500

3. Check the LTM truncation point:


1> dbcc gettrunc2> go

The value in the ltm_trunc_page column is the LTM truncationpoint.

1> dbcc traceon (3604)2> go

This forces trace output to the terminal.

1> dbcc page (<database>, <ltm_trunc_page>, 0)2> go

Note the timestamp. Continue this step until the timestamp ofthe LTM truncation page is greater than the timestamp valueyou saved in step 1.

Shut down the LTM for this replicated database, and thendisable the LTM truncation point.


1> dbcc settrunc (‘ltm’, ‘ignore’)2> go

Suspend the connection to the RSSD databases from ReplicationServer.

1> suspend connection to dataserver.database2> go


Restore Replication After Upgrade Adaptive Server Enterprise Version 11.9.2

Restore Replication After Upgrade

1. Zero out the locator in the RSSD for each replicated primary.

2. Using isql, connect to the RSSD and execute the followingcommands:

1> use RSSD2> go

1> rs_zeroltm dataserver, RSSD2> go

3. Set the LTM truncation point to “valid” in each replicatedprimary. Using isql, connect to the replicated primary, andexecute the following commands:

1> use <database>2> go

1> dbcc settrunc (‘ltm’, ‘valid’)2> go

Shut Down Replication Servers and LTMs

Shut down Replication Servers and LTMs for the database you areupgrading.

Upgrade Adaptive Server

Follow the instructions in “Upgrading Adaptive Server” on page6-11 to complete the upgrade of your replicated databases.

Installation Guide for Linux/Intel Index-1

Index

AAdaptive Server

character set, changing 4-31clients 1-3, 5-1communicating with Backup

Server 4-25database device requirements 4-4described 1-2disk space requirements 2-2installation directory structure 1-6installing multiple 4-32installing via resource file 4-32Japanese version of plug-in to Sybase

Central 5-8language, changing 4-38localizing 4-20, 4-31minimum platform requirements 4-3more information about 4-37multiprocessing 8-6network protocol for 2-1performance statistics for 1-3plug-ins 5-6preparing to upgrade 6-3RAM required by 2-1shutting down 8-4starting from UNIX command line 8-

1starting with operating system 8-3System Administrator 4-36verifying environment for upgrade 6-

2Address, IP 5-5Administrator

operating system 1-1Sybase system 1-2

alter database command 6-5Applets, Java 5-10Applications

changing after renaming objects 6-4developing Java 5-10testing current 6-3

Auditingdevice for 7-1global options 7-2installing using the auditinit utility 7-2installing using the installsecurity

script 7-2process 7-2recommended database device size 4-

5tables for tracking 7-2

auditinit utility 1-10Audit system 7-1Audit trail

overview 7-1system audit tables 7-2

BBackup Server

character set for 4-24communicating with Adaptive

Server 4-25default language for 4-24described 1-3when to install 1-3installing via resource file 4-32more information about 4-38network connections for 4-24server connections 4-24shutting down 8-4specifying message language for 4-24starting from UNIX command line 8-

1unloading 3-8using tape with 1-3

Batch installation of servers 4-32Binary sort order 4-32Buffer specifications 2-5

Index-2


CCD-ROM

image name 3-7unmount command 3-9

Changingcharacter sets 4-31server language 4-31

Character deviceslocated in /dev directory 4-5

Character setschanging 4-31for Backup Server 4-24

Checking database integrity 6-4CLASSPATH environment variable 5-

10Client products

description of 1-2installing 3-10

Configuration file, network 5-6Conflicting object names 6-4Connection problems, analyzing 4-3Conventions, used in this manual xviiicreate database command, system tables

created by 1-9Current applications, testing 6-3

DDatabase devices 7-13, 7-16

See also individual device namesmaster 1-9raw partitions for, preparing 4-5sysprocsdev 1-9, 1-10

Database integrity, checking 6-4Databases

backing up, during installation 6-5dbccdb 1-11image data for sample 7-17interpubs 2-4, 7-18jpubs 2-4, 7-18master 1-9, 1-10, 2-3model 1-9, 2-3pubs2 2-4, 7-16, 7-17pubs3 2-4, 7-17

read-only, changing 6-5sample 1-11, 2-4, 7-16, 7-19sizes of 2-3, 2-4specifications 2-3suspect 6-5sybsecurity 1-10sybsyntax 1-11sybsystemdb 1-11sybsystemprocs 1-10, 2-4tempdb 1-9, 2-4

dataserver utility 8-6dbcc checkalloc command 6-4dbcc checkcatalog command 6-4dbcc checkdb command 6-4dbcc checkstorage, database for 1-11dbccdb database 1-11Default

character sets installed by 4-32installation directory 5-2language for Backup Server 4-24network protocols 5-4program folder 5-3

Directoriesinstallation 1-6, 5-1specifying new, for installation 6-2

Disabling, LTM truncation point A-4disk init command 4-5DISPLAY environment variable 3-2DLL file required for Sybase Central 5-7Documents

Adaptive Server xivavailable on the Web xviHistorical Server 3-10Monitor Client 5-12Monitor Server xiv, xvi, 3-10ODBC 5-12Open Client 5-12security xvSQL Advantage 5-12Sybase Central xiv, 5-12utilities xv

dscp utility 1-5, 1-8dsedit utility 1-5, 1-8, 6-21DSLISTEN environment variable 1-6



DSQUERY environment variable 1-6dump database command, backing up

with 6-5Dump requests 1-3dump tran command 6-5DynaText xvi

EEnvironment variables

CLASSPATH 5-10DISPLAY, setting of 3-2DSLISTEN 1-6DSQUERY 1-6LANG 5-8PATH 1-6, 5-10shared library 1-6SYBASE 1-6TEMP 5-1

Errors, resolving 6-4Extended stored procedures (ESPs) 1-4,

4-38

FFiles

runserver 8-2shared memory 8-7

French sample database 1-11

GGerman sample database 1-11Guest user

for sybsystemdb database 7-11in pubs2 and pubs3 databases 7-19

HHardware requirements 2-3Historical Server

configuring and using 3-10description of 1-3

documentation 3-10Host name 4-25

IIdentifiers, conflicting with reserved

words 6-4Installation directory

default, Windows 5-2for unloading products 3-2restrictions 5-2structure of 1-6

Installation utilities 1-4Installing client products 3-10, 5-1installintpubs script 7-18installjpubs script 7-18installpix script 7-17installpubs2 script 7-17installpubs3 script 7-17interfaces file 1-7, 5-5, 6-21Interfaces File Entry attribute for custom

installation 4-25, 4-28interpubs sample database 1-11, 7-18IP address, finding 5-5isql

checking for replicated databases A-1determining Adaptive Server release

level 6-3verifying which servers are

running 4-36

JJapanese sample database 1-11Japanese version of Adaptive Server

plug-in to Sybase Central 5-8Java Development Kit, installing 5-10Java Runtime Environment,

installing 5-8jpubs sample database 1-11, 7-18

Kkeywords, reserved by Sybase 6-14

Index-4


kill command 8-5, 8-7

LLANG environment variable 5-8Language functions, procedural 1-4Language Modules

description of 1-4disk space required for 2-2for Backup Server 4-24sizes of 2-2

Languages 3-8Library, technical xviListen port number, finding 5-5Load requests 1-3Localization

changing languages 4-31disk space needed for 3-8, 4-20, 4-24

Loginadministrator, Windows NT 5-1“root” 1-1, 3-5“sa” 1-2superuser 1-1“sybase” 1-2

logmon command A-2Log space, freeing up 6-5Loopback mode 4-3LTMs

truncation points, disabling A-4

MMapping NLWNSCK to TCP 5-6master database 1-9Master device 1-9, 4-4Master entry line, server 5-5Microsoft DLL required for Sybase

Central 5-7model database 1-9Monitor Client Library

configuring and using 3-10description of 1-3RAM required by 2-1

Monitor Historical Server. See HistoricalServer

Monitoring with Adaptive Server plug-in for Sybase Central 5-8

Monitor Serverdescribed 1-3description of 1-3disk space required for 2-2monserver command 8-3more information about 4-38shutting down 8-5starting from UNIX command line 8-

1monserver command 8-3Mounting the CD-ROM 3-5

NNetwork configuration file 5-6Network connections

Backup Server 4-24between clients and servers 5-4Monitor Server 4-27

Network-mounted devices 4-5Network problems, and Adaptive

Server data integrity 4-5Network protocols

Named Pipes 5-4, 5-6SPX 1-8, 2-1TCP 5-6TCP/IP 1-8, 2-1Winsock 5-4, 5-6

Network software configuration,verifying 4-3

OObjects

conflicting names of 6-4renaming 6-4

Online syntax help 7-12Open Client

applications 1-4disk space requirements 2-2



Open Server applications 1-3Operating system

administrator 1-1kernel patches 4-3RAM requirements 2-1starting servers 8-3

PParent process identification (PPID) 8-6Partition map, avoiding damage to 4-5Password, setting System

Administrator 4-36PATH environment variable 1-6, 5-10PC client

before installing 5-1product descriptions 5-3

PID. See Process identificationPlug-ins

Adaptive Server 5-6DLL file required for Sybase

Central 5-7Japanese version of 5-8Java Runtime Environment required

for 5-8Port number, specifying 4-25, 5-5PPID. See Parent process

identification 8-6Preparing

Adaptive Server for upgrading 6-3for PC-client product installation 5-1

Privileges 4-6Procedural language functions 1-4Procedure specifications 2-5Process identification (PID) 8-6Product descriptions 5-3, 5-6Product Selection screen 5-3Program folder for Sybase 5-3pubs2 sample database 1-11, 7-16pubs3 sample database 1-11, 7-16, 7-17

QQuery specifications 2-5

RRAM, requirements for

client products 2-1servers 2-1

Raw partitions 4-4availability of 4-6choosing for database devices 4-5minimum size for database devices 4-

6Read-only databases, changing 6-5Referential integrity constraint 2-5Related documents xivRenaming objects 6-4Replicated databases

checking for A-1draining A-4restoring A-6

Replication, disabling A-1Reserved word conflicts

checking for 6-4resolving 6-4

Resource files 6-15installation using 4-32

RSSDs A-3RUN_server_name file 6-2Runserver file 6-2, 8-2

SSample databases 7-16, 7-19“sa” user 4-36Scripts

installintpubs 7-18installjpubs 7-18installpix 7-17installpubs2 7-17installpubs3 7-17

Security. See Auditingserver_name entry in runserver file 6-2Server connections for Backup Server 4-

24Servers, including in sql.ini files 5-4setenv 3-2Setup utilities 1-4

Index-6


Shared library environment variable 1-6Shared memory files 8-7showserver command 4-36, 6-17shutdown command 8-4, 8-5Size

interpubs database, minimum 2-4jpubs database, minimum 2-4language module 2-2master database, minimum for new

installation 2-3model database, minimum for new

installation 2-3pubs2 database, minimum 2-4pubs3 database, minimum 2-4recommended for database devices 6-

5required for installing PC-client

products 5-1sybsystemprocs database, minimum

required for upgrade 2-4tempdb database, minimum for new

installation 2-4Software, manuals for xviSort order

Adaptive Server default 4-32sp_checkreswords 6-4sp_dboption 6-5SPX network protocol 1-8, 2-1sql.ini file 5-4sqllocres utility 1-5sqlloc utility 1-5SQL Server

Monitor Server for version 11.0.x 1-3sqlupgraderes utility 1-5, 6-15sqlupgrade utility 1-5, 6-14srvbuildres utility 1-5srvbuild utility 1-5, 1-8, 4-7, 4-16, 4-31Starting servers

from UNIX command line 8-1with operating system 8-3

startserver utility 8-2Stored procedures

changing after renaming objects 6-4testing 6-3

Suspect databases 6-5Sybase Central, Adaptive Server plug-in

to 1-2, 5-6, 5-7SYBASE environment variable 1-6, 3-6Sybase installation directory 1-6, 3-2, 5-

2Sybase products

running during installation 6-3Sybase Technical Library xvisybload utility 3-4sybsecurity

database 1-10device 1-10, 4-5

sybsetup utility 1-5sybsyntax database 1-11, 7-12sybsystemdb

database 1-11device for 4-4

sybsystemprocsdatabase 1-10preparing for upgrade 6-8 to 6-9

Syntaxconventions for, in this manual xixdatabase of 1-11online help for 1-11

sysprocsdev deviceminimum size for 4-4preparing for upgrade 6-8 to 6-9purpose of 1-9, 1-10

System Administratorsetting password 4-36

System audit tables 7-2System databases

where stored 4-4System procedures

storage location of 1-10

TTable specifications 2-4Tape, using with Backup Server 1-3TCP/IP network protocol 1-8, 2-1Technical Library xvitempdb database 1-9



TEMP environment variable 5-1Transaction log, space in 6-5Transaction logs

draining A-2Transport type menu 4-25Two-phase commit 4-22, 7-9

UUNIX

system requirements 5-11Unloading

Backup Server 3-8server products 3-1XP Server 3-8

us_english language 4-31Utilities

dsedit 6-21

WWindows 95 and NT

available disk space 5-3client product installation on 5-1plug-in installation on 5-7product descriptions 5-3required disk space 5-3

Windows NT and Windows 95system requirements 5-11

Xxhost 3-2xp_cmdshell command 8-1XP Server

described 1-4installing 4-29more information about 4-38related Adaptive Server name 4-29starting 8-1unloading 3-8

Index-8
