advertisement
Configuration Guide
Adaptive Server
®
Enterprise
15.0
[ UNIX ]
DOCUMENT ID:
DC35823-01-1500-04
LAST REVISED:
March 2007
Copyright © 1987-2007 by Sybase, Inc. All rights reserved.
This publication pertains to Sybase software and to any subsequent release until otherwise indicated in new editions or technical notes.
Information in this document is subject to change without notice. The software described herein is furnished under a license agreement, and it may be used or copied only in accordance with the terms of that agreement.
To order additional documents, U.S. and Canadian customers should call Customer Fulfillment at (800) 685-8225, fax (617) 229-9845.
Customers in other countries with a U.S. license agreement may contact Customer Fulfillment via the above fax number. All other international customers should contact their Sybase subsidiary or local distributor. Upgrades are provided only at regularly scheduled software release dates. No part of this publication may be reproduced, transmitted, or translated in any form or by any means, electronic, mechanical, manual, optical, or otherwise, without the prior written permission of Sybase, Inc.
Sybase, SYBASE (logo), ADA Workbench, Adaptable Windowing Environment, Adaptive Component Architecture, Adaptive Server, Adaptive Server
Anywhere, Adaptive Server Enterprise, Adaptive Server Enterprise Monitor, Adaptive Server Enterprise Replication, Adaptive Server Everywhere, Advantage
Database Server, Afaria, Answers Anywhere, Applied Meta, Applied Metacomputing, AppModeler, APT Workbench, APT-Build, APT-Edit, APT-Execute,
APT-Translator, APT-Library, ASEP, Avaki, Avaki (Arrow Design), Avaki Data Grid, AvantGo, Backup Server, BayCam, Beyond Connected, Bit-Wise,
BizTracker, Certified PowerBuilder Developer, Certified SYBASE Professional, Certified SYBASE Professional Logo, ClearConnect, Client-Library, Client
Services, CodeBank, Column Design, ComponentPack, Connection Manager, Convoy/DM, Copernicus, CSP, Data Pipeline, Data Workbench, DataArchitect,
Database Analyzer, DataExpress, DataServer, DataWindow, DataWindow .NET, DB-Library, dbQueue, Dejima, Dejima Direct, Developers Workbench,
DirectConnect Anywhere, DirectConnect, Distribution Director, Dynamic Mobility Model, e-ADK, E-Anywhere, e-Biz Integrator, E-Whatever, EC Gateway,
ECMAP, ECRTP, eFulfillment Accelerator, EII Plus, Electronic Case Management, Embedded SQL, EMS, Enterprise Application Studio, Enterprise Client/
Server, Enterprise Connect, Enterprise Data Studio, Enterprise Manager, Enterprise Portal (logo), Enterprise SQL Server Manager, Enterprise Work
Architecture, Enterprise Work Designer, Enterprise Work Modeler, eProcurement Accelerator, eremote, Everything Works Better When Everything Works
Together, EWA, ExtendAssist, Extended Systems, ExtendView, Financial Fusion, Financial Fusion (and design), Financial Fusion Server, Formula One, Fusion
Powered e-Finance, Fusion Powered Financial Destinations, Fusion Powered STP, Gateway Manager, GeoPoint, GlobalFIX, iAnywhere, iAnywhere Solutions,
ImpactNow, Industry Warehouse Studio, InfoMaker, Information Anywhere, Information Everywhere, InformationConnect, InstaHelp, Intelligent Self-Care,
InternetBuilder, iremote, irLite, iScript, Jaguar CTS, jConnect for JDBC, KnowledgeBase, Legion, Logical Memory Manager, M2M Anywhere, Mach
Desktop, Mail Anywhere Studio, Mainframe Connect, Maintenance Express, Manage Anywhere Studio, MAP, M-Business Anywhere, M-Business Channel,
M-Business Network, M-Business Suite, MDI Access Server, MDI Database Gateway, media.splash, Message Anywhere Server, MetaWorks, MethodSet, mFolio, Mirror Activator, ML Query, MobiCATS, MobileQ, MySupport, Net-Gateway, Net-Library, New Era of Networks, Next Generation Learning, Next
Generation Learning Studio, O DEVICE, OASiS, OASiS logo, ObjectConnect, ObjectCycle, OmniConnect, OmniQ, OmniSQL Access Module, OmniSQL
Toolkit, OneBridge, Open Biz, Open Business Interchange, Open Client, Open ClientConnect, Open Client/Server, Open Client/Server Interfaces, Open
Gateway, Open Server, Open ServerConnect, Open Solutions, Optima++, Partnerships that Work, PB-Gen, PC APT Execute, PC DB-Net, PC Net Library,
Pharma Anywhere, PhysicalArchitect, Pocket PowerBuilder, PocketBuilder, Power++, Power Through Knowledge, power.stop, PowerAMC, PowerBuilder,
PowerBuilder Foundation Class Library, PowerDesigner, PowerDimensions, PowerDynamo, Powering the New Economy, PowerScript, PowerSite,
PowerSocket, Powersoft, PowerStage, PowerStudio, PowerTips, Powersoft Portfolio, Powersoft Professional, PowerWare Desktop, PowerWare Enterprise,
ProcessAnalyst, Pylon, Pylon Anywhere, Pylon Application Server, Pylon Conduit, Pylon PIM Server, Pylon Pro, QAnywhere, Rapport, Relational Beans,
RemoteWare, RepConnector, Report Workbench, Report-Execute, Replication Agent, Replication Driver, Replication Server, Replication Server Manager,
Replication Toolkit, Resource Manager, RFID Anywhere, RW-DisplayLib, RW-Library, SAFE, SAFE/PRO, Sales Anywhere, Search Anywhere, SDF, Search
Anywhere, Secure SQL Server, Secure SQL Toolset, Security Guardian, ShareSpool, ShareLink, SKILS, smart.partners, smart.parts, smart.script, SOA
Anywhere Trademark,SQL Advantage, SQL Anywhere, SQL Anywhere Studio, SQL Code Checker, SQL Debug, SQL Edit, SQL Edit/TPU, SQL Everywhere,
SQL Modeler, SQL Remote, SQL Server, SQL Server Manager, SQL SMART, SQL Toolset, SQL Server/CFT, SQL Server/DBM, SQL Server SNMP
SubAgent, SQL Station, SQLJ, Stage III Engineering, Startup.Com, STEP, SupportNow, S.W.I.F.T. Message Format Libraries, Sybase Central, Sybase Client/
Server Interfaces, Sybase Development Framework, Sybase Financial Server, Sybase Gateways, Sybase IQ, Sybase Learning Connection, Sybase MPP, Sybase
SQL Desktop, Sybase SQL Lifecycle, Sybase SQL Workgroup, Sybase Synergy Program, Sybase Virtual Server Architecture, Sybase User Workbench,
SybaseWare, Syber Financial, SyberAssist, SybFlex, SybMD, SyBooks, System 10, System 11, System XI (logo), SystemTools, Tabular Data Stream, The
Enterprise Client/Server Company, The Extensible Software Platform, The Future Is Wide Open, The Learning Connection, The Model For Client/Server
Solutions, The Online Information Center, The Power of One, TotalFix, TradeForce, Transact-SQL, Translation Toolkit, Turning Imagination Into Reality,
UltraLite, UltraLite.NET, UNIBOM, Unilib, Uninull, Unisep, Unistring, URK Runtime Kit for UniCode, Viafone, Viewer, VisualWriter, VQL,
WarehouseArchitect, Warehouse Control Center, Warehouse Studio, Warehouse WORKS, Watcom, Watcom SQL, Watcom SQL Server, Web Deployment Kit,
Web.PB, Web.SQL, WebSights, WebViewer, WorkGroup SQL Server, XA-Library, XA-Server, XcelleNet, XP Server, XTNDAccess and XTNDConnect are trademarks of Sybase, Inc. or its subsidiaries. 01/06
Unicode and the Unicode Logo are registered trademarks of Unicode, Inc.
All other company and product names used herein may be trademarks or registered trademarks of their respective companies.
Use, duplication, or disclosure by the government is subject to the restrictions set forth in subparagraph (c)(1)(ii) of DFARS 52.227-7013 for the DOD and as set forth in FAR 52.227-19(a)-(d) for civilian agencies.
Sybase, Inc., One Sybase Drive, Dublin, CA 94568.
Contents
About Adaptive Server ..................................................................... 1
System-specific issues ..................................................................... 2
System user roles ............................................................................ 3
Environment variables...................................................................... 3
Adaptive Server devices and system databases.............................. 5
The master device ..................................................................... 5
The sybsystemdb device ........................................................... 6
The sysprocsdev device ............................................................ 6
Optional devices and databases ............................................... 6
dsync option on by default for database device files ................. 8
Determining the location, type, and size of a database device . 9
Client/server communication .......................................................... 11
Changing Adaptive Server configuration........................................ 12
Languages other than U.S. English ............................................... 13
Adaptive Server specifications ....................................................... 13
CHAPTER 2 Starting and Stopping Servers .................................................... 17
Overview ........................................................................................ 17
Requirements for starting servers ........................................... 17
Starting servers .............................................................................. 18
Server start-up parameters ..................................................... 18
Using a RUN_server_name file ............................................... 19
Using the startserver command .............................................. 20
Using the monserver and backupserver commands ............... 20
Starting servers when the operating system restarts ..................... 20
For HP-UX ............................................................................... 21
For IBM RS/6000..................................................................... 21
For Sun Solaris and Linux ....................................................... 22
Starting XP Server after initial installation ...................................... 24
Stopping servers ............................................................................ 24
Configuration Guide
iii
Contents
iv
Stopping Adaptive Server........................................................ 24
Stopping Backup Server.......................................................... 25
Stopping Monitor Server.......................................................... 26
Using the kill command ........................................................... 26
Shutdown and shared memory files ........................................ 27
Configuring the Operating System .............................................. 29
Setting environment variables ........................................................ 29
Configuring new servers with srvbuild............................................ 30
Using the stty setting ...................................................................... 33
Restoring correct permissions........................................................ 34
File descriptors and user connections............................................ 34
For HP-UX............................................................................... 34
For AIX .................................................................................... 34
For Linux ................................................................................. 35
For Sun Solaris........................................................................ 35
Displaying current soft and hard limits .................................... 35
Increasing the soft limit............................................................ 35
Increasing the hard limit .......................................................... 36
Sample program...................................................................... 37
Enabling asynchronous disk I/O..................................................... 38
Adjusting the client connection timeout period............................... 41
For HP-UX............................................................................... 41
For IBM RS/6000..................................................................... 41
For Sun Solaris........................................................................ 42
For Linux ................................................................................. 42
Checking for hardware errors......................................................... 42
For HP-UX............................................................................... 42
For IBM RS/6000..................................................................... 43
For Sun Solaris........................................................................ 43
For Linux ................................................................................. 43
Monitoring the use of operating system resources ........................ 43
For HP-UX............................................................................... 43
For IBM RS/6000..................................................................... 44
For Sun Solaris and Linux ....................................................... 44
A sample C shell maintenance script ............................................. 45
Adaptive Server Default Configuration........................................ 47
Default settings .............................................................................. 47
Setting Up Communications Across the Network ...................... 49
How Adaptive Server determines which directory service entry to use
Adaptive Server Enterprise
Configuration Guide
Contents
How a client uses directory services .............................................. 51
Creating a directory services entry................................................. 51
Supported directory drivers ............................................................ 52
Contents of an interfaces file.......................................................... 52
Heterogeneous and homogeneous environments ......................... 53
Understanding the format of the interfaces file .............................. 55
Components of an interfaces file entry .................................... 56
Creating a master interfaces file .................................................... 58
Using dsedit or dscp to create a master interfaces file............ 58
Using a text editor to create a master interfaces file ............... 58
Configuring interfaces files for multiple networks ........................... 59
Configuring the server for multiple network handlers .............. 59
Configuring the client connections .......................................... 60
Configuring for query port backup ........................................... 62
IPv6 support ................................................................................... 63
Understanding IPv6 ................................................................. 63
IPv6 infrastructure ................................................................... 64
Starting Adaptive Server Enterprise as IPv6-aware ................ 65
Troubleshooting ............................................................................. 66
Server fails to start .................................................................. 66
Error when executing an ESP ................................................. 67
Using the Lightweight Directory Access Protocol as a Directory
Service..................................................................................... 69
Overview ........................................................................................ 69
LDAP directory services versus the Sybase interfaces file ............ 70
The libtcl*.cfg file ............................................................................ 73
Enabling LDAP directory services .................................................. 74
Adding a server to the directory services ....................................... 76
Multiple directory services .............................................................. 77
Encrypting the password ................................................................ 78
Performance................................................................................... 78
Migrating from the interfaces file to LDAP...................................... 79
Customizing Localization for Adaptive Server........................... 81
Overview of localization support .................................................... 81
Language modules .................................................................. 82
Default character sets for servers ........................................... 83
Supported character sets ........................................................ 84
Character set conversion ............................................................... 89
Conversions between server and client .................................. 89
Sort orders ..................................................................................... 90
v
Contents
Available sort orders................................................................ 90
Language modules......................................................................... 93
Installing a new language module ........................................... 93
Message languages ................................................................ 93
Localization .................................................................................... 94
Localization directories............................................................ 94
About the directory .................................................................. 95
About the charsets directory.................................................... 95
About the locales.dat file ......................................................... 95
Changing the localization configuration ......................................... 97
Adaptive Server localization .................................................... 98
Backup Server localization ...................................................... 99
Sort orders............................................................................. 100
Character sets ....................................................................... 101
charset utility ......................................................................... 102
Logging Error Messages and Events ........................................ 105
Adaptive Server error logging ...................................................... 105
Enabling and disabling error logging ..................................... 106
Setting error log paths .................................................................. 106
Setting the Adaptive Server error log path ............................ 106
Managing messages .................................................................... 107
Logging user-defined messages ........................................... 107
Logging auditing events ........................................................ 108
CHAPTER 9 Managing Adaptive Server Databases....................................... 109
Managing database devices ........................................................ 109
Device requirements ............................................................. 109
Creating files for database devices ....................................... 110
CHAPTER 10 Adding Optional Functionality to Adaptive Server................... 113
Adding auditing ............................................................................ 113
Audit system devices and databases .................................... 113
Overview of audit installation................................................. 114
Pre-installation tasks for auditing devices ............................. 115
Installing auditing................................................................... 115
Installing online help for Transact-SQL syntax............................. 121
Online syntax help: sp_syntax............................................... 121
Default device for the sybsyntax database............................ 122
Installing sybsyntax ............................................................... 122
vi
Adaptive Server Enterprise
About This Book
Audience
How to use this book
Configuration Guide
This manual, the Configuration Guide, provides instructions for performing specific configuration tasks for Sybase® Adaptive Server®
Enterprise on UNIX platforms.
The operating system release levels for the UNIX platforms on which
Adaptive Server is certified to execute is in the installation documentation or release bulletin for your platform.
This manual covers the following topics:
• Instructions for reconfiguring certain attributes of your existing
Sybase Adaptive Server Enterprise, Backup Server™, Adaptive
Server Enterprise Monitor™, and XP Server™ to meet your specific needs.
• Creating network connections.
• Configuring optional functionality.
• Performing operating system administration tasks.
• Working with system administration issues that are relevant to
Adaptive Server running on UNIX platforms. This manual supplements the System Administration Guide and the Performance
and Tuning Guide.
Note
Before configuring Adaptive Server according to the instructions in this book, you should have a newly installed or upgraded Adaptive Server on your system. If you do not, follow the installation and upgrade instructions in the installation documentation for your platform.
This manual is for System Administrators or other qualified installers who are familiar with their system’s environment, networks, disk resources, and media devices.
This manual contains the following chapters:
•
Chapter 1, “Introduction” is an overview of Adaptive Server and the
configuration changes you might want to make to Adaptive Server after installing or upgrading the server.
vii
Related documents
•
Chapter 2, “Starting and Stopping Servers” describes how to start and
stop Adaptive Server, Backup Server, Monitor Server, and XP Server.
•
Chapter 3, “Configuring the Operating System” describes how to set up
your operating system to work with Adaptive Server.
•
Chapter 4, “Adaptive Server Default Configuration” provides
information about the default parameter settings of Adaptive Server.
•
Chapter 5, “Setting Up Communications Across the Network” describes
how to use the interfaces file to establish network connections for servers and clients.
•
Chapter 6, “Using the Lightweight Directory Access Protocol as a
Directory Service” provides information about using LDAP directory
services to establish connections.
•
Chapter 7, “Customizing Localization for Adaptive Server” provides
background information about Sybase’s localization support as well as task information for reconfiguring character sets, sort orders, and language modules.
•
Chapter 8, “Logging Error Messages and Events” describes how to use
the error logging features of Adaptive Server.
•
Chapter 9, “Managing Adaptive Server Databases” provides information
about the administration of Adaptive Server databases, including both routine tasks and performance and tuning considerations.
•
Chapter 10, “Adding Optional Functionality to Adaptive Server”
provides instructions for adding optional functionality, such as auditing and the sample databases.
The Sybase
®
Adaptive Server
®
Enterprise documentation set consists of the following:
• The release bulletin for your platform – contains last-minute information that was too late to be included in the books.
A more recent version of the release bulletin may be available on the
World Wide Web. To check for critical product or document information that was added after the release of the product CD, use the Sybase
Technical Library.
• The Installation Guide for your platform – describes installation, upgrade, and configuration procedures for all Adaptive Server and related Sybase products.
viii
Adaptive Server Enterprise
Configuration Guide
About This Book
• What’s New in Adaptive Server Enterprise? – describes the new features in Adaptive Server version 15.0, the system changes added to support those features, and changes that may affect your existing applications.
• ASE Replicator User’s Guide – describes how to use the Adaptive Server
Replicator feature of Adaptive Server to implement basic replication from a primary server to one or more remote Adaptive Servers.
• Component Integration Services User’s Guide – explains how to use the
Adaptive Server Component Integration Services feature to connect remote Sybase and non-Sybase databases.
• The Configuration Guide for your platform – provides instructions for performing specific configuration tasks for Adaptive Server.
• Full-Text Search Specialty Data Store User’s Guide – describes how to use the Full-Text Search feature with Verity to search Adaptive Server
Enterprise data.
• Glossary – defines technical terms used in the Adaptive Server documentation.
• Java in Adaptive Server Enterprise – describes how to install and use Java classes as data types, functions, and stored procedures in the Adaptive
Server database.
• Messaging Service User’s Guide – describes how to useReal Time
Messaging Services to integrate Java Message Service and IBM
WebSphere MQ messaging services with all Adaptive Server database applications.
• Monitor User's Guide, Historical Server – describes how to use Historical
Server to obtain performance information for SQL Server
®
and Adaptive
Server.
• Monitor Client Library Programmer’s Guide – describes how to write
Monitor Client Library applications that access Adaptive Server performance data.
• Monitor Server User’s Guide – describes how to use Monitor Server to obtain performance statistics from SQL Server and Adaptive Server.
• Performance and Tuning Guide – is a series of four books that explains how to tune Adaptive Server for maximum performance:
• Basics – the basics for understanding and investigating performance questions in Adaptive Server.
ix
x
• Locking – describes how the various locking schemas can be used for improving performance in Adaptive Server.
• Optimizer and Abstract Plans – describes how the optimizer processes queries and how abstract plans can be used to change some of the optimizer plans.
• Monitoring and Analyzing – explains how statistics are obtained and used for monitoring and optimizing performance.
• Quick Reference Guide – provides a comprehensive listing of the names and syntax for commands, functions, system procedures, extended system procedures, datatypes, and utilities in a pocket-sized book.
• Reference Manual – is a series of four books that contains the following detailed Transact-SQL
®
information:
• Building Blocks – Transact-SQL datatypes, functions, global variables, expressions, identifiers and wildcards, and reserved words.
• Commands – Transact-SQL commands.
• Procedures – Transact-SQL system procedures, catalog stored procedures, system extended stored procedures, and dbcc
stored procedures.
• Tables – Transact-SQL system tables and dbcc
tables.
• System Administration Guide – provides in-depth information about administering servers and databases. This manual includes instructions and guidelines for managing physical resources, security, user and system databases, and specifying character conversion, international language, and sort order settings.
• System Tables Diagram – illustrates system tables and their entity relationships in a poster format. Available only in print version.
• Transact-SQL User’s Guide – documents Transact-SQL, Sybase’s enhanced version of the relational database language. This manual serves as a textbook for beginning users of the database management system.
This manual also contains descriptions of the pubs2
and pubs3
sample databases.
• Using Adaptive Server Distributed Transaction Management Features – explains how to configure, use, and troubleshoot Adaptive Server DTM features in distributed transaction processing environments.
Adaptive Server Enterprise
Other sources of information
About This Book
• Using Sybase Failover in a High Availability System – provides instructions for using Sybase’s Failover to configure an Adaptive Server as a companion server in a high availability system.
• Unified Agent and Agent Management Console – Describes the Unified
Agent, which provides runtime services to manage, monitor and control distributed Sybase resources.
• Utility Guide – documents the Adaptive Server utility programs, such as isql
and bcp
, which are executed at the operating system level.
• Web Services User’s Guide – explains how to configure, use, and troubleshoot Web Services for Adaptive Server.
• XA Interface Integration Guide for CICS, Encina, and TUXEDO – provides instructions for using the Sybase DTM XA interface with
X/Open XA transaction managers.
• XML Services in Adaptive Server Enterprise – describes the Sybase native
XML processor and the Sybase Java-based XML support, introduces
XML in the database, and documents the query and mapping functions that comprise XML Services.
Use the Sybase Getting Started CD, the SyBooks CD, and the Sybase Product
Manuals Web site to learn more about your product:
• The Getting Started CD contains release bulletins and installation guides in PDF format, and may also contain other documents or updated information not included on the SyBooks CD. It is included with your software. To read or print documents on the Getting Started CD, you need
Adobe Acrobat Reader, which you can download at no charge from the
Adobe Web site using a link provided on the CD.
• The SyBooks CD contains product manuals and is included with your software. The Eclipse-based SyBooks browser allows you to access the manuals in an easy-to-use, HTML-based format.
Some documentation may be provided in PDF format, which you can access through the PDF directory on the SyBooks CD. To read or print the
PDF files, you need Adobe Acrobat Reader.
Refer to the SyBooks Installation Guide on the Getting Started CD, or the
README.txt file on the SyBooks CD for instructions on installing and starting SyBooks.
Configuration Guide
xi
• The Sybase Product Manuals Web site is an online version of the SyBooks
CD that you can access using a standard Web browser. In addition to product manuals, you will find links to EBFs/Maintenance, Technical
Documents, Case Management, Solved Cases, newsgroups, and the
Sybase Developer Network.
To access the Sybase Product Manuals Web site, go to
Product Manuals at http://www.sybase.com/support/manuals/
.
Technical documentation at the Sybase Web site is updated frequently.
Sybase certifications on the Web
v
Finding the latest information on product certifications
1 Point your Web browser to
Technical Documents at http://www.sybase.com/support/techdocs/
.
2 Select Products from the navigation bar on the left.
3 Select a product name from the product list and click Go.
4 Select the Certification Report filter, specify a time frame, and click Go.
5 Click a Certification Report title to display the report.
v
Finding the latest information on component certifications
1 Point your Web browser to
Availability and Certification Reports at http://certification.sybase.com/
.
2 Either select the product family and product under Search by Product; or select the platform and product under Search by Platform.
3 Select Search to display the availability and certification report for the selection.
v
Creating a personalized view of the Sybase Web site (including support pages)
Set up a MySybase profile. MySybase is a free service that allows you to create a personalized view of Sybase Web pages.
1 Point your Web browser to
Technical Documents at http://www.sybase.com/support/techdocs/
.
2 Click MySybase and create a MySybase profile.
xii
Adaptive Server Enterprise
About This Book
Sybase EBFs and software maintenance
Conventions
v
Finding the latest information on EBFs and software maintenance
1 Point your Web browser to the Sybase Support Page at http://www.sybase.com/support
.
2 Select EBFs/Maintenance. If prompted, enter your MySybase user name and password.
3 Select a product.
4 Specify a time frame and click Go. A list of EBF/Maintenance releases is displayed.
Padlock icons indicate that you do not have download authorization for certain EBF/Maintenance releases because you are not registered as a
Technical Support Contact. If you have not registered, but have valid information provided by your Sybase representative or through your support contract, click Edit Roles to add the “Technical Support Contact” role to your MySybase profile.
5 Click the Info icon to display the EBF/Maintenance report, or click the product description to download the software.
The following sections describe conventions used in this manual.
SQL is a free-form language. There are no rules about the number of words you can put on a line or where you must break a line. However, for readability, all examples and most syntax statements in this manual are formatted so that each clause of a statement begins on a new line. Clauses that have more than one part extend to additional lines, which are indented. Complex commands are formatted using modified Backus Naur Form (BNF) notation.
Table 1 shows the conventions for syntax statements that appear in this manual:
Table 1: Font and syntax conventions for this manual
Element Example
Command names, procedure names, utility names, and other keywords display in sans serif font.
select sp_configure
Database names and datatypes are in sans serif font.
master
database
Book names, file names, variables, and path names are in italics.
System Administration Guide
sql.ini file
column_name
$SYBASE/ASE directory
Configuration Guide
xiii
Element Example
Variables—or words that stand for values that you fill in—when they are part of a query or statement, are in italics in Courier font.
Type parentheses as part of the command.
Double colon, equals sign indicates that the syntax is written in BNF notation. Do not type this symbol.
Indicates “is defined as”.
Curly braces mean that you must choose at least one of the enclosed options. Do not type the braces.
Brackets mean that to choose one or more of the enclosed options is optional. Do not type the brackets.
The comma means you may choose as many of the options shown as you want. Separate your choices with commas as part of the command.
The pipe or vertical bar( | ) means you may select only one of the options shown.
An ellipsis (...) means that you can repeat the last unit as many times as you like.
select
column_name
from
table_name
where
search_conditions
compute
::=
row_aggregate
(
column_name
)
{cash, check, credit}
[cash | check | credit] cash, check, credit cash | check | credit buy thing = price [cash | check | credit]
[, thing = price [cash | check | credit] ]...
You must buy at least one thing and give its price. You may choose a method of payment: one of the items enclosed in square brackets. You may also choose to buy additional things: as many of them as you like. For each thing you buy, give its name, its price, and (optionally) a method of payment.
• Syntax statements (displaying the syntax and all options for a command) appear as follows: sp_dropdevice [device_name]
For a command with more options: select column_name from table_name where search_conditions
In syntax statements, keywords (commands) are in normal font and identifiers are in lowercase. Italic font shows user-supplied words.
• Examples showing the use of Transact-SQL commands are printed like this: select * from publishers
xiv
Adaptive Server Enterprise
About This Book
• Examples of output from the computer appear as follows: pub_id pub_name city state
-----------------------------------------
0736
0877
1389
New Age Books
Binnet & Hardley
Algodata Infosystems
Boston
Washington
Berkeley
MA
DC
CA
Terms
(3 rows affected)
In this manual, most of the examples are in lowercase. However, you can disregard case when typing Transact-SQL keywords. For example,
SELECT
,
Select
, and
select
are the same.
Adaptive Server’s sensitivity to the case of database objects, such as table names, depends on the sort order installed on Adaptive Server. You can change case sensitivity for single-byte character sets by reconfiguring the Adaptive
Server sort order. For more information, see the System Administration Guide.
Accessibility features
The following terms appear repeatedly throughout this book. For more detailed information about these and other terms, see the Glossary.
• /work/sybase – is given as an example of the Sybase installation directory.
• Text editor – refers to an ASCII text editor or any editor that can save files to text format.
This document is available in an HTML version that is specialized for accessibility. You can navigate the HTML with an adaptive technology such as a screen reader, or view it with a screen enlarger.
Adaptive Server Enterprise and the HTML documentation have been tested for compliance with U.S. government Section 508 Accessibility requirements.
Documents that comply with Section 508 generally also meet non-U.S. accessibility guidelines, such as the World Wide Web Consortium (W3C) guidelines for Web sites.
The online help for this product is also provided in HTML, which you can navigate using a screen reader.
Note
You might need to configure your accessibility tool for optimal use.
Some screen readers pronounce text based on its case; for example, they pronounce ALL UPPERCASE TEXT as initials, and MixedCase Text as words. You might find it helpful to configure your tool to announce syntax conventions. Consult the documentation for your tool.
Configuration Guide
xv
If you need help
For information about how Sybase supports accessibility, see
Sybase
Accessibility at http://www.sybase.com/accessibility
. The Sybase Accessibility site includes links to information on Section 508 and W3C standards.
Each Sybase installation that has purchased a support contract has one or more designated people who are authorized to contact Sybase Technical Support. If you cannot resolve a problem using the manuals or online help, please have the designated person contact Sybase Technical Support or the Sybase subsidiary in your area.
xvi
Adaptive Server Enterprise
C H A P T E R 1
Introduction
Sybase Adaptive Server Enterprise for UNIX is a full-featured Adaptive
Server that runs on the following platforms:
• HP-UX
• IBM AIX
• Sun Solaris
• Linux 32-bit
Note
The instructions in this book assume that Adaptive Server is installed and running. For information about installing and starting
Adaptive Server, as well as for an overview of Adaptive Server, see the
Adaptive Server Installation Guide for your platform.
This chapter provides an overview of how to configure Adaptive Server and the steps you need to take to customize it for your use.
Topic
Adaptive Server devices and system databases
Changing Adaptive Server configuration
Languages other than U.S. English
Adaptive Server specifications
Page
About Adaptive Server
Adaptive Server performs data management and transaction functions, independent of client applications and user interface functions.
Configuration Guide
1
System-specific issues
Adaptive Server also:
• Manages multiple databases and multiple users
• Keeps track of the data’s location on disks
• Maintains the mapping of logical data description to physical data storage
• Maintains data and procedure caches in memory
Adaptive Server uses these auxiliary programs to perform dedicated tasks:
• Backup Server manages database load, dump, backup, and restoration activities.
• Monitor Server keeps track of performance data.
• Historical Server obtains performance data from Monitor Server and saves the data in files for use at a later time.
• XP Server stores the extended stored procedures (ESPs) that allow
Adaptive Server to run operating-system and user-defined commands.
2
System-specific issues
Adaptive Server runs on a variety of hardware and operating system platforms.
System-specific issues do not affect the basic functionality of Adaptive Server, but there are differences among platform implementations. These differences may include:
• Adaptive Server configuration
• Changes to the operating system that enable or enhance Adaptive Server performance
• The structure of entries in the interfaces file
• Options for selecting database devices
• Operating system commands or utilities that simplify or automate routine system administration tasks
• Operating system utilities for monitoring Adaptive Server performance
System-specific issues are described in this document. For more information about system-specific issues, see the Installation Guide and release bulletin for your platform.
Adaptive Server Enterprise
CHAPTER 1 Introduction
System user roles
The Adaptive Server installation and setup process defines various user roles.
Different user roles have different responsibilities and privileges. These user roles clarify the way Adaptive Server is to be integrated into your system:
• Operating system administrator – the individual who maintains the operating system. This individual has superuser or “root” privileges.
• System Administrator – the individual in charge of Adaptive Server system administration, creating user accounts, assigning permissions on databases, and creating new databases. At installation time, the System
Administrator’s login name is “sa”. The “sa” login is not a UNIX login.
The “sa” login is specific to Adaptive Server and is used to log in to
Adaptive Server using the isql
command.
• “sybase” login – the “sybase” login is a UNIX login that owns all the
Sybase installation directories and files, sets permissions on those directories and files, and performs the installation and upgrading of
Adaptive Server. This login is preferred, but not required.
Environment variables
It is crucial to the operation of Sybase products that the system environment variables be set correctly.
Environment variables are set in the user’s environment either interactively or by including them in the user’s .login and .cshrc files (for C shell) or .profile file (for Bourne shell). The installation instructions in this guide explain when to set these variables.
Note
As part of the installation, the installer setup these environment variables in SYBASE.csh and SYBASE.sh files. You can source the file to set their environment.
• DSLISTEN – defines the name Adaptive Server uses to listen for client connections if no name is given during the Adaptive Server start-up. If
DSLISTEN is not set, and no name is given during the Adaptive Server start-up, the Adaptive Server name defaults to SYBASE.
Configuration Guide
3
Environment variables
• DSQUERY – defines the Adaptive Server name that client programs attempt to connect to if no Adaptive Server is specified with a command line option. If DSQUERY is not set, and you do not supply the Adaptive
Server name with a command line option, clients attempt to connect to
SYBASE.
• SYBASE – defines the path of the Sybase installation directory. The installation program sets up the variable SYBASE to point to the release directory specified during installation.
• SYBASE_ASE – defines the subdirectory of the Adaptive Server component.
• SYBASE_OCS – defines the subdirectory to which Open Client™ is set.
• SYBASE_ FTS – defines the subdirectory for the full-text search components.
• SYBASE_SYSAM – points to the license-management software directory.
• PATH – specifies directory path to search for executables. The Sybase executables are located in the installed_components /bin directory. When using the source files SYBASE.csh or SYBASE.sh, the following paths are prepended to PATH:
$SYBASE/$SYBASE_ASE/bin:$SYBASE/$SYBASE_OCS/bin
• LD_LIBRARY_PATH – this variable specifies the directory to search for shared libraries. The Sybase shared libraries are located in the installed component’s /lib directory.
When using the source files: SYBASE.csh or SYBASE.sh, the following paths are prepended to the LD_LIBRARY_PATH environment variable:
$SYBASE/$SYBASE_ASE/lib:$SYBASE/$SYBASE_OCS/ lib:$SYBASE/SYBASE_FTS/lib,etc.
• LIBPATH – on the IBM RS/6000 platform, this variable specifies which directory to search for libraries.
When using the source files: SYBASE.csh or SYBASE.sh, the following paths are prepended to the LIBPATH environment variable:
$SYBASE/$SYBASE_ASE/lib:$SYBASE/$SYBASE_OCS/ lib: $SYBASE/SYBASE_FTS/lib, etc.
• SHLIB_PATH – on HP-UX platforms, this variable specifies which directory to search for libraries.
4
Adaptive Server Enterprise
CHAPTER 1 Introduction
When using the source files: SYBASE.csh or SYBASE.sh, the following paths are prepended to the LIBPATH environment variable:
$SYBASE/$SYBASE_ASE/lib:$SYBASE/$SYBASE_OCS/ lib: $SYBASE/SYBASE_FTS/lib, etc.
Adaptive Server devices and system databases
Devices are files or portions of a disk that are used to store databases and database objects. You can initialize devices using raw disk partitions or operating system files.
Adaptive Server requires the following devices:
• master
– to store system databases.
• sybsystemdb
– to store information about distributed transaction.
• sysprocsdev
– to store system procedures.
The master, sybsystemdb, and sysprocsdev devices are created when you create a new Adaptive Server.
The master device
The master device contains the following databases:
• master
– controls the operation of Adaptive Server as a whole and stores information about all users, user databases, devices, objects, and system table entries. The master
database is contained entirely on the master device and cannot be expanded onto any other device.
• model
– provides a template for new user databases. The model
database contains required system tables, which are copied into a new user database with the create database
command.
• tempdb
– the work area for temporary databases in Adaptive Server.
Adaptive Server supports multiple tempdb s. See “create temporary database” in the T-SQL User’s Guide. Each time Adaptive Server is started, the tempdb
database is cleared and rebuilt from the model database.
Configuration Guide
5
Adaptive Server devices and system databases
• The sample databases, pubs2
and pubs 3
, are stored on the master device at installation, but should be moved to a user-defined device after installation.
Note
For recovery purposes, Sybase recommends that you do not create other system or user databases or user objects on the master device.
The sybsystemdb device
For new installations the master
device also contains the sybsystemdb database. The sybsystemdb
device stores the sybsystemdb database, which stores information about transactions in progress, and which is also used during recovery.
The sybsystemdb
database is required to support distributed transaction management (DTM) features. Before installation, make sure you have enough space available on the default segment to support sybsystemdb
.
The sysprocsdev device
The sybprocsdev devices stores the sybsystemprocs
database, which contains most of the Sybase-supplied system procedures. System procedures are a collection of SQL statements and flow-of-control statements that perform system tasks, for example, sp_configure
.
The system procedures that are needed during recovery situations are stored in the master database.
Note
sysprocsdev
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 devices and databases described in the following sections are optional.
The sample databases
The sample databases are:
6
Adaptive Server Enterprise
CHAPTER 1 Introduction
The sybsecurity device and database dbccdb database sybmgmtdb database
• pubs2
and pubs3
– provided as learning tools for Adaptive Server. pubs2 is used for most of the examples in the Adaptive Server documentation; other examples use the pubs3
database. Both are available in U.S. English versions of Adaptive Server.
• interpubs
– contains French and German data.
• jpubs
– contains Japanese data.
For information about installing the sample databases, see the Installation
Guide for your platform, Chapter 3, “Post-Installation Tasks.”
For information about the contents of the sample databases, see the
Transact-SQL User’s Guide.
The sybsecurity
device is created as part of the auditing installation process.
The sybsecurity
device stores the sybsecurity
database and the auditing system procedures with which you can configure auditing for your system.
The auditing system records system security information in an Adaptive Server audit trail. You can use this audit trail to monitor the use of Adaptive Server or system resources.
For instructions on configuring Adaptive Server for auditing, see Chapter 10,
“Adding Optional Functionality to Adaptive Server.” For information about
installing and using the auditing system, see Chapter 12, “Auditing,” in the
System Administration Guide.
The database consistency checker ( dbcc
) provides commands for checking the logical and physical consistency of a database. The dbccdb
database stores the results of dbcc
when dbcc checkstorage or dbcc
check verifying is used.
dbcc checkstorage
records consistency information for the target database, operation activity, and the results of the operation in the dbccdb
database.
Stored in the database are dbcc
stored procedures for creating and maintaining dbccdb
and for generating reports on the results of dbcc checkstorage operations.
For information on installing and using dbccdb
, see Chapter 25, “Checking
Database Consistency,” in the System Administration Guide.
sybmgmtdb
is a Job Scheduler database.
Configuration Guide
7
Adaptive Server devices and system databases
All the job, schedule, and scheduled job information, and data needed by the
Job Scheduler task for internal processing is stored in the sybmgmtdb
database.
Most access to data in the sybmgmtdb
database is via stored procedures. The stored procedures make the data available to the GUI, the JS Agent and the command-line interface. Only the Job Scheduler task accesses data directly from the sybmgmtdb
database.
For more information about sybmgmtdb
and Job Scheduler, see Job Scheduler
User’s Guide.
dsync option on by default for database device files
The dsync option ensures Adaptive Server can recover data from devices on the file systems. By default, Adaptive Server enables dsync
for file system devices.
However, dsync may cause performance degredation for file system devices that experience high write activity. The dsync option can be set or reset using the disk init, disk reinit, and sp_deviceattr
commands.
Note
The dsync option is ignored for raw devices.
When installing a new Adaptive Server, by default dsync is set on for all file system devices.
When upgrading from ASE 12.0 or earlier releases on a UNIX server that stored databases on UNIX file system devices, by default dsync is set:
• on for the master device
• off for all other devices
Immediately after upgrade, set the dsync option for the file system devices. See also sp_deviceattr
and sp_helpdevice
in the Reference Manual
Warning!
Data corruption may occur if
dsync option is not set immediately after upgrade.
8
Adaptive Server Enterprise
CHAPTER 1 Introduction
Determining the location, type, and size of a database device
Adaptive Server
requires several database devices. Table 1-1 below shows baseline values for each of the devices. See the release bulletin for any last minute changes to these values.
Device
Table 1-1: Adaptive Server database devices
Purpose
Minimum
size
master
Stores databases
45MB for 4K pages
89MB for 8K pages
177MB for 16K pages
120MB sysprocsdev
(also called the sybsystemprocs device)
Stores the sybsystemprocs database
Minimum recommended size
30MB
60MB
120MB
240MB
120MB (plus any space for holding stored procedures that you have created) sybsystemdb
3MB for 2K pages processing
6MB for 4K pages
12MB for 8K pages sybsecurity
(optional) Required for auditing
24MB for 16K pages
5MB
5 – 24MB
7MB; more for specialized auditing
For Solaris, HP-UX, IBM AIX, and Linux
For all databases you can use either a raw partition or a file.
Sybase Adaptive Server supports the database devices on NFS- and
CIFS-mounted devices with Network Appliance Filers for storing data.
Network appliance filers provide the same performance and data integrity as raw devices. There are no changes needed to the operating system or to Sybase
Adaptive Server to use network appliance filers.
NFS mounted devices have been tested on Solaris, HP-UX, IBM AIX, and
Linux.
For All Platforms
You may need to repartition the disk you choose. Contact your operating system administrator for assistance.
Configuration Guide
9
Adaptive Server devices and system databases
When preparing a raw partition device, follow these guidelines:
• Do not initialize a database device on the partition that contains your
Sybase installation software. Doing so destroys all existing files on that partition.
• A raw partition designated for use by Sybase cannot be mounted for use by the operating system for any other purpose, such as for file systems or swap space.
• After a Sybase configuration utility or the disk init
command has initialized a portion of a partition as a database device, the entire partition cannot be used for any other purpose. Any space left on the partition beyond the size specified for the device becomes inaccessible, unless you drop and recreate the device.
• For best performance, place the Sybase software and all disk devices, including the master
device, on the same machine.
• To avoid any possibility of using a partition that contains the partition map, do not use cylinder 0.
v
Choosing 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 for each device, based on the size recommendations in Table 1-1 on page 9.
4 Verify with the operating System Administrator that the partition you have chosen is available.
5 Make sure the “sybase” user has read and write privileges to the raw partition.
Note
For more information on choosing a raw partition, see your operating system documentation.
10
Adaptive Server Enterprise
CHAPTER 1 Introduction
Client/server communication
Adaptive Server communicates with other Adaptive Servers, Open Server™ applications (such as Backup Server), and client software on your network.
Clients can talk to one or more servers, and servers can communicate with other servers by remote procedure calls.
For Sybase products to interact with one another, each product needs to know where the others reside on the network. Names and addresses of every known server are listed in a directory services file. This information can be stored in a directory services file two different ways:
• In an interfaces file, named interfaces on UNIX platforms, located in the
$SYBASE installation directory, or
• In an LDAP server
After your Adaptive Server or client software is installed, it can connect with any server on the network that is listed in the directory services.
When you are using a client program, and you want to connect with a particular server, the client program looks up the server name in the directory services and connects to that server, as shown in Figure 1-1. You can supply the name of the server by using the DSQUERY environment variable.
On TCP/IP networks, the port number gives clients a way to identify the
Adaptive Server, Open Server, Backup Server, or Monitor Server to which they want to connect. It also tells the server where to listen for incoming connection attempts from clients. The server uses a single port for these two services
(referred to as query service and listener service).
Configuration Guide
11
Changing Adaptive Server configuration
Figure 1-1: Communicating with a server using interfaces file
During installation, you use the srvbuild utility to create and configure a new server. The srvbuild
process adds entries to the interfaces file for your new
Adaptive Server, Backup Server, Monitor Server, and XP Server.
For instructions on how to modify existing interfaces file entries using dsedit and dscp
or to create new interfaces file entries for existing servers, Chapter 6,
“Using the Lightweight Directory Access Protocol as a Directory Service.”
Changing Adaptive Server configuration
Use sp_configure
to change the configuration of Adaptive Server. To change the configuration of several servers, enter the sp_configure
information in a script. For details on using sp_configure
, see the System Administration Guide and the Reference Manual.
For information about configuring languages, character sets, and sort orders,
see Chapter 7, “Customizing Localization for Adaptive Server.”
For information about configuring Adaptive Server to use high availability features, see Using Sybase Failover in a High Availability Environment.
For information about configuring Adaptive Server for distributed transaction management (two-phase commit), see the Using Adaptive Server Distributed
Transaction Management Features.
12
Adaptive Server Enterprise
CHAPTER 1 Introduction
Languages other than U.S. English
If you are running srvbuild
in a language other than U.S. English, verify that any input you provide uses a character set that is supported by the us_english character set.
Note
The us_english character set does not support accent marks, such as tildes (~) and umlauts (ü). This prevents srvbuild
from supporting the character sets that use these characters.
For more information about languages, character sets, and sort orders, see the
Installation Guide for your platform. For more information on srvbuild, see the
Utility Guide.
Adaptive Server specifications
Database specifications
Databases per Adaptive
Server
Maximum database size
Minimum allowable sybsystemprocs
database
Maximum size of a database device (disk partition)
A maximum of 32,767 databases per server
• 2K page server – 4TB
• 4K page server – 8TB
• 8K page server – 16TB
• 16K page server – 32TB
124MB Required for an upgrade
2
24
(4TB)
If the Operating System supports file sizes up to 4TB, then Adaptive
Server supports file system devices up to 4TB
Maximum number of database devices per server
Maximum number of devices or device pieces per database
Maximum number of segments per database
Maximum number of login
IDs per server
2
31
Unlimited
31
2147516416
Limited by available memory
Configuration Guide
13
Adaptive Server specifications
Maximum number of users per database
Maximum number of groups per database
2146484223
1032193
Table specifications
User objects per database 2
31
– 255
Indexes per table 250 (one clustered index)
Rows per table Limited by available storage
31 Columns per composite index
Creation of clustered index 1.2*(x + y)
Maximum size of object name x = total data space in table, y = sum of space of all nonclustered indexes on table, and 20 percent overhead for logging
255
Maximum 2
32
For sorted data, approximately 20 percent of the table size needed
Query specifications
Maximum number of tables participating in a query, for a query without a union, or for each side of a union in a query
64
Maximum number of tables in a
“union” query
256
Maximum number of databases participating in one transaction
Unlimited
Maximum of 50 user tables, including result tables, tables referenced by views (the view itself is not counted) correlations and self-joins; maximum of 14 worktables
Includes up to 50 user tables and 14 work tables on every side of the union, for a total of up to 256 tables across all sides of the union.
Includes database where transaction began, all databases changed during transaction, and tempdb
, if it is used for results or worktables
14
Adaptive Server Enterprise
Practical number of databases participating in one query
16
Maximum number of tables with referential integrity constraints for a query
192
CHAPTER 1 Introduction
Includes each occurrence of each database queried and tempdb
, if it is used for results or worktables
Procedure specifications
Number of buffers and procedure buffers
Configurable Limited by amount of RAM and maximum size of shared memory segment
Minimum memory required per stored procedure
Maximum number of parameters per stored procedure
2K
2048
Maximum APL table limits
Fixed-length column
Variable-length column
Adaptive Server extended-limit capabilities vary by type of table and the database logical page size. Table 1-2 lists the column and row limits for allpages-locked (APL) tables.
Table 1-2: Allpages-locked (APL) tables
Number of columns
Column size
2K page
Column size
4K page
1024
254
1960 bytes
1948 bytes
4008 bytes
3988 bytes
Column size
8K page
8104 bytes
8068 bytes
Column size
16K page
16296 bytes
16228 bytes
Maximum DOL table limits
Fixed-length column
Variable-length column
Table 1-3 lists the column and row limits for data-only-locked (DOL) tables.
Table 1-3: Data row and data page tables.
Number of columns
Column size
2K page
Column size
4K page
1024
1024
1958 bytes
1954 bytes
4006 bytes
4002 bytes
Column size
8K page
8102 bytes
8089 bytes
Column size
16K page
16294 bytes
16290 bytes
Databases
master
database
Database space requirements depend upon the logical page size of the server.If your model
database is larger than the minim size listed below, then the minimum size of the database is equal to the model
database. Table 1-4 lists the minimum size for each database.
Table 1-4: Database requirements for varying page sizes
2K page 4K page 8K page 16K page
13MB 26MB 52MB 104MB
Configuration Guide
15
Adaptive Server specifications
Databases
model database tempdb
database sybsystemdb
database
Tables
Bytes per index key
User-visible row length
DOL table
User-visible row length
APL table
2K page
3MB
4MB
3MB
4K page
6MB
6MB
6MB
8K page
12MB
12MB
12MB
16K page
24MB
24MB
24MB
Larger logical page sizes can contain more data. Table 1-5 lists the maximum data for each logical page size.
Table 1-5: Data limits for tables according to page size
2K page 4K page 8K page 16K page
600
1958
1250
4006
2600
8102
5300
16294
1960 4008 8104 16296
16
Adaptive Server Enterprise
C H A P T E R 2
Starting and Stopping Servers
This chapter describes how to start and stop Adaptive Server, Backup
Server, Monitor Server, and XP Server.
Topic
Starting servers when the operating system restarts
Starting XP Server after initial installation
Page
Overview
The methods described in this chapter are used to start Adaptive Server,
Backup Server, and Monitor Server after a shutdown for database maintenance, because of an operating system crash, or for other reasons.
XP Server is not started by the installation process. XP Server is started by
Adaptive Server when an XP command is issued through isql
.
You can use Sybase Central to start and stop servers manually or automatically. For more information about Sybase Central, see “Chapter
1, Overview of System Administration,” in the System Administration
Guide.
Requirements for starting servers
To start a server, your user account must have:
• Anyone with access to the database servers (execute privileges) and database devices (read/write privileges).
• Access to Adaptive Server distribution files
Configuration Guide
17
Starting servers
•
The system environment variables discussed in Chapter 1, “Introduction”
• Access to SySAM licenses. For more information, see the Sybase Software
Asset Management User’s Guide.
The installation program creates the interfaces file and system environment variables when you install servers on your computer.
Starting servers
You can start Adaptive Server, Backup Server, or Monitor Server from the command line by using RUN_server_name files and startserver
commands.
You can customize the starting options.
You can also customize the start up options by editing the RUN_server_name.
Server start-up parameters
The default start-up parameters are stored under
$SYBASE/$SYBASE_ASE/install/RUN_server_name, where server_name is the name of the server you installed.
Backup Server, Monitor Server, and Historical Server server names are appended with “_back”, “_mon”, and “_hs”, respectively.
Table 2-1 lists the default start-up parameters for Adaptive Server.
Switch
Table 2-1: Default Adaptive Server start-up parameters
Description
-d
$SYBASE/data/master.dat
-s
server_name
-e
$SYBASE/$SYBASE_ASE
/install/errorlog
-M
$SYBASE/$SYBASE_ASE
-N
$SYBASE/$SYBASE_ASE/sysam/
<srv_name>.properties
Location of the master device file
Name of the Adaptive Server
Location and name of the error log file
Directory that stores shared memory files
Location and name of license cache file.
18
Adaptive Server Enterprise
CHAPTER 2 Starting and Stopping Servers
Changing start-up parameters
You cannot change any of these default start-up parameters unless you directly edit the $SYBASE/$SYBASE_ASE/install/RUN_ server_name file. You can also specify additional start-up parameters within the
$SYBASE/$SYBASE_ASE/install/RUN_ server_name file.
Additional start-up parameters include any valid server command line options listed for the databaserver
and backupserver
descriptions in the Utility Guide.
For a description of start-up parameters for Monitor Server and Historical
Server, see the Adaptive Server Enterprise Monitor documentation.
Using a RUN_server_name file
Each time a new Adaptive Server, Backup Server, or Monitor Server is created, the srvbuild program creates a RUN_server_name file that contains the information required to restart that server. RUN_server_name files are created in the $SYBASE/$SYBASE_ASE/install directory. For Adaptive Server, the
RUN_server_name file is named RUN_server_name, where servername is the name of the server.
For example, the RUN_server_name file name for an Adaptive Server named
TEST is RUN_TEST.
For Backup Server and Monitor Server, the RUN_server_name files are named
RUN_servername_back and RUN_servername_mon, respectively, where
servername is the name of the server.
Warning!
Do not delete the RUN_server_name file that is created in
$SYBASE/$SYBASE_ASE/install. This file is used to restart servers when you customize your installation. If you need the RUN_server_name file in another location, make a copy of the original RUN_server_name file in the new location.
The RUN_server_name file for a server named SYBASE is named
RUN_SYBASE. If the RUN_server_name file for your current Adaptive Server is named RUN_server_name, you must change the name to RUN_SYBASE during the upgrade process.
Configuration Guide
19
Starting servers when the operating system restarts
Using the startserver command
To start a server from the command line, enter:
$SYBASE/$SYBASE_ASE/install/startserver [ -f RUN_server_name file ] where $SYBASE/$SYBASE_ASE/install/startserver is the full path name of the startserver
utility, and RUN_server_name file is the full path name of the
RUN_server_name file (usually
$SYBASE/$SYBASE_ASE/install/RUN_server_name).
If your Adaptive Server is named SYBASE, the RUN_server_name file specification is optional.
You must have read and write permissions on the master device for an Adaptive
Server to start it with startserver
. For more information about startserver
, see the Adaptive Server Utility Guide.
Using the monserver and backupserver commands
Use the monserver
command to start Monitor Server from the UNIX command line. For details, see the Adaptive Server Enterprise Monitor Server User’s
Guide.
Starting servers when the operating system restarts
This section describes how to configure your operating system for automatic restart of Adaptive Server and Backup Server.
On production systems, Adaptive Server, Backup Server, and Monitor Server should restart automatically when the UNIX operating system starts. This is accomplished by making an entry for the server in the operating system startup script. Monitor Server must be listed after Adaptive Server in the start-up script.
For more information on starting Monitor Server at operating system restart, see the Monitor Server User’s Guide.
Note
The startup script must set up all the required Sybase environment variables, or source SYBASE.csh or SYBASE.sh, before starting the server.
20
Adaptive Server Enterprise
CHAPTER 2 Starting and Stopping Servers
For HP-UX
In HP-UX versions 10.0 and later, you cannot edit commands in the /etc/rc file, so the System Administrator must create a script that executes when the operating system starts or shuts down.
For more information about rc (1M)
, see the HP-UX manual page. You can model your script after the HP-UX template file /sbin/init.d/template.
After creating the start-up and shutdown script, place it in the directory
/sbin/init.d. Execution scripts placed in this directory have symbolic links to directories /sbin/rcn.d where n is the system run level. The linked scripts in
/sbin/rcn.d are used to control the sequencing order of the execution scripts.
For IBM RS/6000
On production systems, you can restart Adaptive Server automatically whenever the UNIX operating system restarts. To have Adaptive Server restart automatically, place the startserver
command in the /etc/inittab file.
Here is a suggested format for an Adaptive Server start-up command to add to
/etc/inittab:
"sybase:2:wait:/release_directory/install/startserver -f \ RUN_servername
/dev/console 2>&1"
Where release_directory is the full path to the Sybase installation directory
(specified as the SYBASE environment variable), and RUN_servername is the
RUN_server_name file for the server you are starting.
Make sure that the entry for starting Adaptive Server follows any entry for
/etc/rc.tcpip and /etc/rc.nfs in the /etc/inittab file. All network resources must be available before you start Adaptive Server; otherwise, Adaptive Server does not start. Also, your server does not start if the network is not running.
Slow start-up of network operations can also prevent Adaptive Server from starting, even when the commands in the /etc/rc.tcpip file are in the correct order. You can designate a period of time for Adaptive Server to wait before starting by inserting a sleep
command before the server start-up command in the RUN_server_name file. The sleep
command is in the form:
Configuration Guide
21
Starting servers when the operating system restarts
sleep seconds_of_rest
Note
To enable restart of a Backup Server when the operating system starts, add a Backup Server start-up command to /etc/inittab. Use the path of the
Backup Server RUN_server_name file in this command.
For Sun Solaris and Linux
Before you set Adaptive Server or Backup Server to start automatically, make sure that all network resources are available. Your server does not start if the network is not running. Be sure that the entry for restarting the server follows any commands in the rc directory for starting network operations. Slow startup of network operations may prevent servers from starting, even if commands are in the correct order in the rc directory. You may want to designate a period of time for your server to wait before starting by inserting a sleep
command at the beginning of the linked RUN_server_name file you created.
To configure your operating system for automatic restart of Adaptive Server and Backup Server:
1 Create a start-up script file with contents like the following:
$SYBASE/$SYBASE_ASE/install/startserver
-f
$SYBASE/$SYBASE_ASE/install/RUN_servername where $SYBASE/$SYBASE_ASE/install/startserver is the full path name of the startserver
utility, and
$SYBASE/$SYBASE_ASE/install/RUN_servername is the full path name of the RUN_server_name file for the server.
2 Copy the script to the /etc/init.d directory, using syntax like the following: cp script_name /etc/init.d/script_name
3 Review the contents of the /etc/inittab file to determine the default run level for your operating system. The initdefault
entry specifies the default run level, which is usually 2 or 3 for Sun Solaris and 5 for Linux
4 Use the ln
command to create a hard link from the RUN_server_name file to the appropriate run control (rc) directory, rc#, where # is the default run level obtained in step 2.
Use syntax like the following for Sun Solaris:
22
Adaptive Server Enterprise
CHAPTER 2 Starting and Stopping Servers
ln /etc/init.d/script_name /etc/rc#.d/S##script_name
For Linux:
Use ln -s
to create symbolic links from the script name to the appropriate run control (rc) directory, rc# where # is the run level. Use syntax like the following: ln -s /etc/init.d/script_name /etc/rc#.d/S##script_name
When you type the command to create this link, add an uppercase “S” and a two-digit sequence number preceding the name of the script file. “S” indicates a start-up file. The sequence number is necessary because files in the rc directory are executed in order of their numbers. This file should be executed last, so you should use a sequence number that follows all existing numbers in ASCII order.
You can perform an ls
command on the rc directory to view existing sequence numbers. For example: ls /etc/rc3.d/S* returns:
/etc/rc3.d/S10syslog
/etc/rc3.d/S15nfs.server
/etc/rc3.d/S21rfs
If your script is named sybstart
, type the following: ln /etc/init.d/sybstart /etc/rc3.d/S77sybstart
In this example, you can use any number greater than 27 in place of 77.
For Linux:
You can perform an ls command on the rc directory to view existing sequence numbers. For example: ls /etc rc5.d/S* returns:
/etc/rc5.d/S12syslog
/etc/rc5.d/S14nfslock
/etc/rc5.d/S27ypbind and so on. If your script is named sybstart, type the following: ln -s /etc/init.d/sybstart /etc/rc5.d/S99sybstart
In this example, you can use any number greater than 27 in place of 99.
Configuration Guide
23
Starting XP Server after initial installation
Starting XP Server after initial installation
If you install Adaptive Server and XP Server in the same build session, srvbuild automatically adds information about the XP Server to the sysservers
table of
Adaptive Server. If you install XP Server in a different build session than the
Adaptive Server installation, you are prompted during the XP Server installation process to supply the name of the related Adaptive Server and the
System Administrator’s name and password. This information is required by
Adaptive Server to start XP Server.
If you do not supply this information during the installation process, XP Server cannot run. When you execute an extended stored procedure (ESP), you see an error message similar to the following:
Msg 11018, Level 16, State 1:
Procedure 'xp_cmdshell', Line 2
XP Server must be up for ESP to execute.
To add this required information to the sysservers
table manually, enter: sp_addserver servername_XP, NULL, servername_XP where servername is the name of the Adaptive Server.
Stopping servers
Only the System Administrator has permission to issue a shutdown command.
Using a shutdown command minimizes the amount of work that automatic recovery needs to do when the servers are restarted.
The preferred method of stopping Adaptive Server or Backup Server is to use the Transact-SQL shutdown
command. For Monitor Server, use the sms_shutdown
command.
Stopping Adaptive Server
To shut down Adaptive Server:
1 Use isql
to log in to an Adaptive Server account with System
Administrator privileges: isql -Usa -Ppassword -Sserver_name
24
Adaptive Server Enterprise
CHAPTER 2 Starting and Stopping Servers
2 Enter:
1> shutdown
2> go
The default for shutdown
uses the with wait
option
, which allows Adaptive
Server to finish executing SQL statements or procedures, perform a checkpoint in each database, disable new logins, and perform other shutdown tasks.
Issuing the shutdown
command prints a message like this to the sterr file:
Server SHUTDOWN by request.The SQL Server is terminating this process.
CT-LIBRARY error:
This is normal behavior. If the message indicates that Adaptive Server is waiting for processes to complete, and you must stop Adaptive Server immediately, you can use shutdown with nowait
which neither waist for currently executing statements to finish, nor performs checkpoints in every database.
Note
Using the shutdown with nowait
command is not recommended; use it only when necessary.
Stopping Backup Server
To shut down a Backup Server:
1 Use isql
to log in to a server with System Administrator privileges.
2 Enter:
1> shutdown SYB_BACKUP
2> go
After you shut down a Backup Server, you must wait at least 30 seconds before restarting it.
Issuing the shutdown
command prints a message similar to the following to the
stderr file:
Backup Server: 3.48.1.1: The Backup Server will go down immediately.
Terminating sessions.
Configuration Guide
25
Stopping servers
This is normal behavior. If a message indicates that Adaptive Server or Backup
Server is waiting for processes to complete, and you must stop Adaptive Server or Backup Server immediately, use shutdown with nowait
, which neither waits for currently executing statements to finish, nor performs checkpoints in every database.
Using shutdown with nowait
for Backup Server can cause inconsistent or incomplete dumps and loads. Use this command only when necessary.
For more information on the shutdown
command, see the Reference Manual.
Stopping Monitor Server
To release resources, you must shut down Monitor Server before you restart
Adaptive Server. If Adaptive Server stops, make sure that Monitor Server is shut down before you restart Adaptive Server. Otherwise, Adaptive Server may not be able to allocate enough resources to restart.
If the Monitor Server heartbeat feature is in effect, Monitor Server automatically detects the termination of Adaptive Server within the specified period and shuts itself down. Therefore, before attempting to restart Adaptive
Server after a shutdown, either wait for the automatic shutdown of Monitor
Server to occur, or explicitly stop Monitor Server.
For more information on stopping Monitor Server, see the Monitor Server
User’s Guide.
Using the kill command
Warning!
Use the kill
command to stop Adaptive Server and Backup Server only as a last resort.
When possible, use the Transact-SQL shutdown
or shutdown with nowait command. Do not use kill
with the
-9
flag, because it exits the server without running a checkpoint to ensure that all database changes are written to the database device. Adaptive Server may also exit without removing associated shared memory files and network handlers.
Because Adaptive Server and Backup Server are background processes, they can be killed from the operating system by their owner or by “root” with the
UNIX kill
command. The syntax is:
26
Adaptive Server Enterprise
CHAPTER 2 Starting and Stopping Servers
kill pid where pid is the process identification of any dataserver
or backupserver process, as determined by the showserver
command. Killing one engine for a particular Adaptive Server kills all engines for that server.
If more than one Adaptive Server is running on the same system, be careful that the engine you kill is associated with the correct Adaptive Server. If your
Adaptive Server is configured to use multiple engines (CPUs), each engine has an associated operating system process. The correct way to kill a multi-engine server is to specify the process ID for engine 0.
This showserver
output shows the processes for a four-engine server: showserver
UID PID PPID C STIME TTY TIME COMD jorge 3320 1 80 10:31:40 pts/4 302:15 dataserver -dteamster jorge 3321 3320 80 10:31:45 pts/4 324:47 dataserver -ONLINE:1 jorge 3322 3320 80 10:31:45 pts/4 326:02 dataserver -ONLINE:2 jorge 3323 3320 80 10:31:45 pts/4 328:56 dataserver -ONLINE:3
This example shows four running
dataserver
processes with operating system process identifications (PID) 3320, 3321, 3322, and 3323 ( dataserver
is the executable form of the Adaptive Server program.)
Child engine processes for the dataserver have the
-ONLINE:
argument.
Each child engine has a parent process identification (PPID) that is equal to the process identification (PID) of the parent. In the example above, the PID of the parent server is 3320. The other three engines spawned by the parent process have the same PPID.
If the PPIDs appear to be unrelated, and there is more than one dataserver process, then more than one Adaptive Server is running on the system.
Shutdown and shared memory files
When Adaptive Server starts, it creates SERVER_NAME.krg file in
$SYBASE/$SYBASE_ASE directory to store information about shared memory segments that it uses.
Configuration Guide
27
Stopping servers
If Adaptive Server is configured with a memory size that is greater than the
MAXSHMSEGSIZE parameter in the operating system then Adaptive Server may create additional shared memory segments and for every additional shared memory segment that it creates, an additional file with
SERVER_NAME.srg[N] (where N ranges from 0 – N), is created under
$SYBASE/$SYBASE_ASE.
When Adaptive Server is shut down in a normal manner, the shared memory files are automatically removed. If Adaptive Server crashes or is stopped with the kill -9
command, these files are not deleted. You need read and write permissions on these files to restart Adaptive Server after a crash or a kill -9 command, because Adaptive Server must be able to overwrite the previously created shared memory files.
If Adaptive Server or Backup Server is killed abnormally it also leaves shared memory segments. Use the ipcs
and ipcrm
commands to identify and remove these shared memory segments that have “NATTACH” count as “0”.
See the UNIX man pages for more information about ipcs
and ipcrm
.
28
Adaptive Server Enterprise
C H A P T E R 3
Configuring the Operating
System
This chapter discusses the operating system configuration settings that you can adjust after installing or upgrading Adaptive Server. Unless stated otherwise, the information pertains to all supported UNIX platforms.
Topic
Configuring new servers with srvbuild
File descriptors and user connections
Enabling asynchronous disk I/O
Adjusting the client connection timeout period
Monitoring the use of operating system resources
A sample C shell maintenance script
Page
Setting environment variables
Note
As part of the installation, the installer creates SYBASE.sh and
SYBASE.csh files in $SYBASE directory for user to source to setup all the environment variables.
It is crucial to the operation of Sybase products that the system environment variables be set correctly. Environment variables are set in the user’s environment either interactively or by including them in the user’s .login and .cshrc files (for C shell) or .profile file (for Bourne shell).
Only the file owner or the “root” user can edit a user’s .login, .cshrc, or
.profile file.
Configuration Guide
29
Configuring new servers with srvbuild
You may want to verify that the Adaptive Server environment variables in
Table 3-1 are set correctly.
To check the current value of environment variables, enter the following command at the operating system prompt: env
Table 3-1 describes the system environment variables for Adaptive Server.
Table 3-1: System environment variables
Variable Sample value Function
DSLISTEN TEST
DSQUERY
PATH
TEST
/usr/bin:/etc:
/usr/sbin:
Used at Adaptive Server start-up; enables the specified Adaptive Server to listen for input from front-end software.
Defines the Adaptive Server to which local client applications connect.
Appends the full path to the Adaptive Server bin subdirectories.
/usr/ucb:
/usr/bin/X11:/sbin
Configuring new servers with srvbuild
To configure new servers with srvbuild
:
1 Source SYBASE.csh or SYBASE.sh file in $SYBASE to setup the environment variables.
2 Run $SYBASE/$SYBASE_ASE/bin/srvbuild.
3 The Select Servers to Build window displays. Choose the servers you want to configure by clicking the boxes on the left. When you select each of the boxes, the server name text field is enabled where you can enter the server name.
Note
The list of “Server type” available for you to choose depends on what you have installed in $SYBASE.
4 When you have selected the servers you want to build, click OK The next screen or screens displays information depending on what you chose to configure.
30
Adaptive Server Enterprise
Configuration Guide
CHAPTER 3 Configuring the Operating System
5 In the Adaptive Server type screen, select the:
• Server page size
• Master device path
• Master device size
• Master database size
• Sybsystemprocs device path
• Sybsystemprocs device size
• Sybsystemprocs database size
• Error log
• Transport type
• Host name
• Port number
In the Edit Advance Adaptive Server Attributes tab, enter:
• Adaptive Server configuration file
• Sybsystemdb device path
• Sybsystemdb device size
• Sybsystemdb database size
• Share memory file directory
• Default backup server
6 To configure Backup Server, in the Backup Server configuration screen, select the:
• Error log
• Tape configuration file
• Language
• Character set
• Maximum number of network connections
• Maximum number of server connections
• Transport type
• Host name
31
Configuring new servers with srvbuild
• Port number
7 To configure Monitor Server, select the following information in the
Monitor Server screen:
• Maximum number of connections
• Error log
• Configuration file
• Shared memory directory
• Transport type
• Host name
• Port number
8 In the XP Server type screen, select:
• Transport type
• Host name
• Port number
9 In the Full-Text Search SDS type screen, select:
• Error log
• Collection directory
• Default database
• Language
• Character set
• Minimum number of sessions
• Maximum number of sessions
• Transport type
• Host name
• Port number
10 To configure Job Scheduler, enter the following information in the Job
Scheduler type screen”
• Sybmgmtdb device path
• Sybmgmtdb device size
32
Adaptive Server Enterprise
CHAPTER 3 Configuring the Operating System
• Sybmgmtdb database size
• Transport type
• Host name
• Port number
11 In the “Configure Self Management...” screen, you can enter:
• Enable Self Management
• Self Management user name
• Self Management user password
If you change the Self Management user password after configuring the
Self Management, you need to rerun: sp_addexternlogin loopback, <Self Management user name>, <Self Management user name>, <new Self
Management user password>
12 Click Build Servers! to proceed with the servers configuration. srvbuild displays the configuration status as it builds the servers you selected.
13 After the server configuration completes, click Exit to quit srvbuild
.
Using the stty setting
Setting the stty tostop
option causes a background Adaptive Server to stop as soon as it tries to write to the terminal. To avoid this error, execute the following command before starting Adaptive Server: stty -tostop
If you are redirecting all Adaptive Server output to files, you do not have to change the stty
setting.
Configuration Guide
33
Restoring correct permissions
Restoring correct permissions
Sybase software files and directories are installed with the correct access permissions. If you notice that the permissions are no longer correct, you can restore the correct permissions with the script setperm_all
, located in the
$SYBASE/$SYBASE_ASE/install directory.
File descriptors and user connections
The number of user connections used by Adaptive Server cannot exceed the number of file descriptors available to Adaptive Server on the operating system. When configuring user connections on Adaptive Server, the System
Administrator should take into account the number of file descriptors available per process. Although most of the open file descriptors are available for user connections, a few are used by Adaptive Server for opening files and devices.
For HP-UX
The kernel parameters maxfiles
and maxfiles_lim
control the number of file descriptors available to any one process. The limit is 10,000 for HP-UX on a
32-bit system, and 60,000 on a 64-bit system.
To obtain the current values on the file descriptors use the Korn or Bourne shell ulimit
command: ulimit -n
For AIX
The number of file descriptors per process is determined by the operating system parameter open_max
. The default value of open_max
is 32767.
Adaptive Server can use a maximum of 2000 file descriptors per engine, regardless of the value of open_max
. For more information on setting open_max
, see the AIX operating system documentation.
To obtain the current value of the open_max
parameter, use the Korn or Bourne shell ulimit command: ulimit -n
34
Adaptive Server Enterprise
CHAPTER 3 Configuring the Operating System
For Linux
The number of file descriptors per process is limited to 10,000. You can set the number of file descriptors using ulimit
.
For Sun Solaris
For Sun Solaris, you can set both soft and hard limits for file descriptors. The soft limit can be increased up to the hard limit by the user, but the hard limit can be increased only by someone with “root” permissions. The soft limit determines the number of open file descriptors available to an Adaptive Server engine. The limit is 10,000.
Although most of the open file descriptors are available for user connections, a few are used by Adaptive Server engines for opening files and devices.
See the System Administration Guide for additional information on user connections.
Displaying current soft and hard limits
To display the current soft limit, for C shells, enter: limit descriptors
For Bourne shells, enter: ulimit -n
To display the current hard limit for C shells, enter: limit -h descriptors
For Bourne shells, enter: ulimit -Hn
Increasing the soft limit
To increase the soft limit for C shells, enter: limit descriptors n
For Bourne shells, enter:
Configuration Guide
35
File descriptors and user connections
ulimit -Sn new_value where n is the current value for the soft limit, and new_value is the value to which you want to increase the soft limit.
Note
You can use the preceding commands in your RUN_server_name file to increase the hard and soft limits. The RUN_server_name file is a Bourne shell script, be sure to use the Bourne shell versions of these commands in the
RUN_server_name file.
Increasing the hard limit
To increase the hard limit, use a program like the sample program shown in
v
Setting up the sample program to increase the hard limit
1 Create file_name.c (where file_name is the name you give the file), by
using an ASCII text editor. Type the text shown in the sample in “Sample program” on page 37.
2 Compile the file: cc file_name.c -o program_name where file_name is the name of the source file you created, and
program_name is the name you want to give the program.
3 Change the program’s permissions and ownership so that it will execute as
“root”: chmod 755 program_name chown root program_name where program_name is the name of the compiled program.
4 The “root” user can use the program to start Adaptive Server with increased user connections by typing the following command at the operating system prompt:
# program_name dataserver -d master_device_name
36
Adaptive Server Enterprise
CHAPTER 3 Configuring the Operating System
where program_name is the name of the compiled program, and
master_device_name is the full path of Adaptive Server’s master device.
Instead of typing the command at the operating system prompt, you can add program_name preceding the dataserver command line in the
Adaptive Server RUN_server_name file.
Sample program
Note
This is an sample script; modify it as necessary.
The following example shows the source code that you can use to increase the hard limit:
#include <sys/time.h>
#include <sys/resource.h>
#include <sys/types.h>
/*
** define MAX_CONNECTIONS to a number less than
** 10000. The number defined will then become the maximum
** number of connections allowed by an Adaptive Server.
*/
#define MAX_CONNECTIONS 9999
extern int errno;
main(argc,argv)
char **argv;
{ struct rlimit rlp; rlp.rlim_cur = MAX_CONNECTIONS; rlp.rlim_max = MAX_CONNECTIONS;
/* set the number of open file desriptors to if (setrlimit (RLIMIT_NOFILE,&rlp) == -1)
{
perror("setrlimit");
exit(1);
}
/* reset the user id to disable superuser
Configuration Guide
37
Enabling asynchronous disk I/O
setuid(uid);
/* run the program indicated as arguments to
}
For additional information on user connections, see the System Administration
Guide.
Enabling asynchronous disk I/O
For HP-UX
This step is mandatory for HP users.
To improve I/O performance on character or raw and block devices, enable asynchronous I/O by installing the HP asynchronous I/O driver from SAM. For help with installing this driver, contact your operating system administrator or
HP technical support.
Note
Before executing the following instructions, shut down Adaptive Server
(or SQL Server).
To enable asynchronous I/O:
1 From the SAM Kernel Configuration menu, choose Drivers and set the
Pending State for asyncdisk to In by adding the driver.
An alternate step could be done by adding the asyncdsk subsystem keyword to /stand/system.
2 Rebuild the kernel, and reboot the system.
3 Execute the following commands using the userid
root:
#/etc/mknod/dev/async c 101 4
#chmod 0660/dev/async
#chown <uid> /dev/async
#/etc/setprivgrp <ugrp> MLOCK
Where:
<uid> is the identification (user ID)used by the user that is booting
Adaptive Server.
<ugrp> is the user group for the <uid> user ID.
38
Adaptive Server Enterprise
HP-UX 11.23
HP-UX on Itanium
Configuration Guide
CHAPTER 3 Configuring the Operating System
4 At the UNIX prompt, execute the following statements as “root”. The user
ID of the user who is starting Adaptive Server and Backup Server must be the owner of the /dev/async directory.
This step is mandatory for HP users.
To improve I/O performance on character or raw block devices, enable asynchronous I/O by installing the HP asynchronous I/O driver from SAM. For help with installing this driver, contact your operating system administrator or
HP technical support.
Note
Before executing the following instructions, shut down Adaptive Server
(or SQL Server).
1 To launch the Kernel Configuration use kcweb -F
.
2 Select Modules.
3 Select asyncdsk
and change the next boot
to static
.
4 Rebuild the kernel, and reboot the system.
5 Execute the following commands using the userid
root:
#/etc/mknod/dev/async c 101 4
#chmod 0660/dev/async
#chown <uid> /dev/async
#/etc/setprivgrp <ugrp> MLOCK
Where:
<uid> is the identification (user ID) used by the user that is booting
Adaptive Server.
<ugrp> is the user group for the sybase userid.
6 At the UNIX prompt, execute the following statements as “root”. The user
ID of the user who is starting Adaptive Server and Backup Server must be the owner of the /dev/async directory.
To verify that the async
I/O is active on the Itanium machine:
1 Log in as root.
2 Issue the command:
# kcmodule -a | grep aync
Result: asyncdsk static required or you can also use the following:
39
Enabling asynchronous disk I/O
For IBM AIX
# ls /dev/asyn* idev/async /dev/asyncdsk
Enable asynchronous disk I/O.
This step is mandatory for IBM users.
Enable asynchronous I/O by adjusting the kernel parameters, using the System
Management Interface Tool (SMIT):
1 Enter “smit” at the UNIX prompt.
2 From the Devices menu, select Asynchronous I/O.
3 Select Change/Show Characteristics of Asynchronous I/O.
4 Enter the values from Table 3-2:
Table 3-2: SMIT parameters for asynchronous I/O
SMIT parameter
Values for RS/6000 AIX
4.3.3
MINIMUM number of servers 1
MAXIMUM number of REQUESTS I/O
4096
ASYNC I/O STATE
(to be configured at system restart)
Available
If your system uses more than seven disks at the same time for Asynchronous
I/O, increase the MAXIMUM number of servers value by 1 for every active device.
Note
Setting the minor device number on /dev/async to 4 reduces or eliminates transient 605 errors in Adaptive Server.
If you are using LVM mirroring, set the minor device number to 0x0.
40
Adaptive Server Enterprise
CHAPTER 3 Configuring the Operating System
Adjusting the client connection timeout period
Adaptive Server uses the
KEEPALIVE
option of the TCP/IP protocol to detect clients that are no longer active. When a connection to a client is inactive for a period of time (the timeout period), the operating system sends
KEEPALIVE packets at regular intervals. If it does not receive a response from the client machine for any of these packets, the operating system notifies Adaptive
Server that the client is no longer responding. Adaptive Server then terminates the client’s connection.
The
KEEPALIVE
default timeout period is 2 hours (7,200,000 ms). To display the current time value, use the command for your platform as shown in the following sections.
For HP-UX
To display the current timeout period, enter:
/usr/contrib/bin/nettune -l
Note
The switch is a lowercase “L”, not the number one (1).
The tcp_keepstart
parameter specifies the length of time (measured in seconds) to keep an idle connection active before the system checks to see if the connection died.
To change the timeout period, use the nettune -s
command.
For IBM RS/6000
To display the current timeout value, enter:
/usr/sbin/no -o tcp_keepidle
The tcp_keepidle
parameter specifies the length of time (measured in half seconds) to keep an idle connection active before the system checks to see if the connection died. The default is 14,400 half seconds (7200 seconds, or 2 hours).
IBM recommends a value of at least 15 minutes.
Configuration Guide
41
Checking for hardware errors
For Sun Solaris
To display the timeout value, enter:
/usr/sbin/ndd -get /dev/tcp tcp_keepalive_interval
To reduce the timeout period to 15 minutes (900,000 ms.), enter:
/usr/sbin/ndd -set /dev/tcp tcp_keepalive_interval 900000
For Linux
To display the timeout value, enter:
/sbin/sysctl -e net.ipv4.tcp_keepalive_time
To reduce the timeout period to 15 minutes (900 seconds,) enter:
/sbin/sysctl -w net.ipv4tcp_keepalive_time=900
Checking for hardware errors
The following types of hardware error messages indicate problems that may lead to database corruption:
• Disk read, write, or retry errors
• Timeouts
• System panics
• Memory problems of any type
For HP-UX
Check the /var/adm/syslog/syslog.log file on a regular basis. You can view the file directly, or you can use the HP-UX dmesg
command. See your operating system documentation for more information.
42
Adaptive Server Enterprise
CHAPTER 3 Configuring the Operating System
For IBM RS/6000
The errpt
command includes several options for limiting the report to events that match certain criteria. Use the errpt
command on a regular basis. If errors appear, use the diagnostic tool diag
to check your memory and disks. Or use the
System Management Interface Tool (SMIT) to run the errpt
command. This command may produce a lot of output.
For Sun Solaris
Check the /var/adm/messages file on a regular basis. If any of the types of hardware errors described in the beginning of this section appear, use the Sun
Microsystems diagnostic tool, sundiag
, to check memory and disks. See the operating system documentation for more information.
For Linux
Check the /var/log/messages file on a regular basis. See the operating system documentation for more information.
Monitoring the use of operating system resources
The System Administration Guide discusses maintaining the optimal number of
Adaptive Server engines for your workload and system configuration. To determine the optimal number, monitor system and CPU usage.
For HP-UX
Configuration Guide
HP-UX supplies many tools to help monitor performance, some of which are described as follows:
• The sar
command reports relative and absolute I/O throughput rates to each disk and controller.
• The vmstat
command monitors virtual memory usage.
• The netstat
command monitors network status.
43
Monitoring the use of operating system resources
• The ps
command provides a snapshot of accumulated CPU time and usage for individual processes.
• The time
command can be useful in determining the various user, system, and real-time resources used over a complete run.
For details about these tools, see your operating system documentation.
For IBM RS/6000
IBM RS/6000 supplies the following tools for monitoring performance:
• The iostat
command reports the amount of I/O on terminals and hard disks and how CPU time is spent.
• The vmstat
command monitors virtual memory usage.
• The netstat
command monitors network status.
• netstart -v
displays Transmit/Receive Statistics. It is also used to determine if enough buffers have been configured for network traffic.
• no -a
command displays current network options. It is also used for tuning mbuf pools.
• The ps
command provides a snapshot of accumulated CPU time and usage for individual processes.
• The time
command determines the various user, system, and real-time resources during a complete run.
For details about these tools, see your operating system documentation.
For Sun Solaris and Linux
Sun Solaris and Linux supplies the following tools to help monitor performance:
• The iostat
command reports the amount of I/O on terminals and hard disks and how CPU time is spent.
• The vmstat
command monitors virtual memory usage.
• The netstat
command monitors network status.
44
Adaptive Server Enterprise
CHAPTER 3 Configuring the Operating System
• The ps
command gives you an accurate snapshot of accumulated CPU time and usage for individual processes. This can be very helpful in determining the dataserver-, engine-, and process-specific loading.
• The time
command can be useful in determining the various user, system, and real-time resources used over a complete run.
For details about these tools, see your operating system documentation.
A sample C shell maintenance script
Running dbcc
checks and performing database backups protect the integrity and recoverability of your Adaptive Server databases. The following sample C shell script calls several isql
scripts to help you do this:
#!/bin/csh -f
if ( -e dbcc_mail.out) then rm dbcc_mail.out
endif
foreach i (*.dbcc)
isql -Usa -Ppassword < $i > dbcc_out
if ( ‘grep -c ‘Msg 25[0-9][0-9]’ dbcc_out’ ) then echo "There are errors in" $i >> dbcc_mail.out
cat dbcc_out >> dbcc_mail.out
else echo "Backing up " $i:r >> dbcc_mail.out
isql -Usa -Ppassword < $i:r.backup
endif
end
mail -s "Backup Report" jjones < dbcc_mail.out
The first set of scripts (one for each database with a file name appended with
.dbcc) runs dbcc checkalloc
and dbcc checkdb
for each database and sends the messages to an output file called dbcc_out.
For example, the script master.dbcc
runs dbcc
to check the master
database: dbcc checkalloc (master) go dbcc checkdb (master) go
The C shell script then runs the grep
command to find 2500-level error messages in the dbcc
output. The results of the grep
command go into an output file called dbcc_mail.out.
Configuration Guide
45
A sample C shell maintenance script
Next, the script invokes an isql
backup script for each database for which no
2500-level errors occurred and adds the “Backing up database_name” line to
dbcc_mail.out. For example, the script
master.backup
backs up the master database: use master go dump database master to master_dump go
You may want to add appropriate dump transaction
commands to your scripts.
If there are 2500-level error messages, the script does not back up the database.
At the end of the script, dbcc_mail.out is mailed to the System Administrator
“jjones,” who then has a record of fatal dbcc
errors and successful backups.
You can tailor the sample shell and isql
scripts to suit the needs of your installation.
To have the scripts execute automatically, edit the crontab file, and add an entry similar to this:
00 02 * * * /usr/u/sybase/dbcc_ck 2>&1
This example executes a C shell script called dbcc_ck
every morning at 2:00 a.m.
46
Adaptive Server Enterprise
C H A P T E R 4
Adaptive Server Default
Configuration
When you install or upgrade Adaptive Server, it includes some default parameter settings and a few of its auxiliary programs.
After installing and testing this “default” Adaptive Server, you can configure it to your system’s needs and install other optional features.
For information about configuring Adaptive Server, Backup Server, and
Monitor Server see the System Administration Guide.
For information about configuring languages, character sets, and sort orders, as well as optional features, see the System Administration Guide.
Topic
Page
Default settings
After installation, Adaptive Server default settings are as listed in Table 4-
1. You may need to configure these settings to suit your computer and database needs.
Table 4-1: Defaults for Adaptive Server parameter settings
Item
Name
Transport Type
Default value
Servername
TCP/IP
Port number
Error log path
5000
$SYBASE/$SYBASE_ASE/install/servername.log
Event logging Not configured
International support (Localization)
• Language us_english
Configuration Guide
47
Default settings
Item
• Character set
• Sort order
Login security mode
Default value
HP – Roman8
IBM – ISO 8859-1
Sun – ISO 8859-1
Linux – iso_1
Linux – Binary ordering
Standard
Table 4-2 lists the default settings for the Backup Server, Monitor Server, and
XP Server. For more information about these servers, see “Introduction” on page 1.
Table 4-2: Defaults for Backup, Monitor, and XP Servers
Server Item Default value
Backup Server Name AdaptiveServername_back
Network support (TCP/IP)
Socket number
Error log path
5001
$SYBASE/$SYBASE_ASE/install/AdaptiveS ervername_back.log
Monitor Server
XP Server
Name AdaptiveServername_mon
Network support (TCP/IP)
Socket number
Error log path
5002
$SYBASE/$SYBASE_ASE/install/AdaptiveS ervername_back.log
Name
$SYBASE/$SYBASE_ASE/ADAPTIVESER
VERNAME_XP
Network support (TCP/IP)
Socket number 5003
Error log path N/A
48
Adaptive Server Enterprise
C H A P T E R 5
Setting Up Communications
Across the Network
Configuration Guide
Adaptive Server can communicate with other Adaptive Servers, Open
Server applications, and client software across a network. Clients can communicate with one or more servers, and servers can communicate with other servers via remote procedure calls.
Page
Topic
How Adaptive Server determines which directory service entry to use
How a client uses directory services
Creating a directory services entry
Contents of an interfaces file
Heterogeneous and homogeneous environments
Understanding the format of the interfaces file
Creating a master interfaces file
Configuring interfaces files for multiple networks
Directory services contains information about the network locations of servers. Directory services contain entries for all Adaptive Servers,
Backup Servers, and other server products on the network.
In the Sybase client/server environment, a client can connect with
Adaptive Server if it knows where the server resides on the network and if the server supports the client’s language or character set. When a client initiates a connection, it looks in its directory services for the network location of the target server.
Directory services list the name and address of every server, including
Backup Server, Monitor Server, and XP Server. When you are using a client program, and you want to connect with a particular server, the client program looks up the server name in the directory services and connects to that server.
49
How Adaptive Server determines which directory service entry to use
Servers also need network information. When a server starts up, it looks in its interfaces file to determine where to listen for client connection requests. In addition, Adaptive Server can take on a client role when it makes remote procedure calls to other Adaptive Servers.
Table 5-1 shows where to find more information on server and client interfaces file tasks and topics.
Table 5-1: Where to find interfaces file tasks and topics
Type of interfaces file
UNIX server or client
PC-client
Task or topic See
Adding entries for multiple
Adaptive Server installations
Creating a master interfaces file for multiple installations
Chapter 7, “Customizing Localization for Adaptive
“Creating a master interfaces file” on page 58
Configuring for multiple networks
“Configuring interfaces files for multiple networks” on page 59.
Reference information
“Understanding the format of the interfaces file” on page 55.
Configuring a client Installation Guide for your platform instructions for advanced tasks
Client platforms not listed
Configuring, reference information, and instructions for advanced tasks for your PC-client platform, or the appropriate Open
Client documentation
Open Client and Open Server Programmer’s Supplement for your PC-client platform, or the appropriate Open
Client documentation
How Adaptive Server determines which directory service entry to use
Adaptive Server uses directory services to determine the address at which it should listen for clients. When you start Adaptive Server, it performs the following steps:
1 It looks for the server name supplied in the command line
-s
option. If the server name is not supplied in the command line:
2 It determines its own name by checking the value of the DSLISTEN environment variable. If the DSLISTEN environment variable is not set, then it assumes that the server name is SYBASE.
50
Adaptive Server Enterprise
CHAPTER 5 Setting Up Communications Across the Network
3 Looks in directory services for an entry whose name matches the name found in the steps above.
4 It uses the network information provided by the directory services entry it has found to listen for client connections.
How a client uses directory services
When a client connects to a server it:
• Determines the name of the server either programmatically or by referring to the DSQUERY environment variable. If the application user has not set
DSQUERY, the runtime value for the server name defaults to the SYBASE environment variable.
• Looks in directory services for an entry whose name matches the name of the server.
• Uses the network information provided by the directory services entry to connect to the server. If the client cannot connect the first time, it makes additional attempts according to the delay and retry numbers indicated in directory services. If no matching entry is found, an error message is written to the client’s standard error file. If multiple networks are supported, the client attempts to connect using the information in the second network address entry for the server.
The Open Client documentation discusses client connections in much greater detail. See the Open/Client Programmer’s Supplement for your client platform or the appropriate Open/Client documentation.
Creating a directory services entry
The installation program, srvbuild
, automatically creates a directory services entry for each server installation. You can also use the following Sybase utilities to edit the network information in directory services:
• dsedit
– an X-Windows GUI utility.
• dscp
– a UNIX command line utility.
For details on using these utilities, see the Adaptive Server Utility Guide.
Configuration Guide
51
Supported directory drivers
Supported directory drivers
There are three supported drivers:
• interfaces driver
• Lightweight Directory Services driver.
• Cell Directory Service (CDS) provided by Distributed Computing
Environment (DCE)
This remainder of this chapter describes the interfaces file and provides specific configuration information for each supported UNIX platform. For information about LDAP drivers, Cell Directory Services, and for a comparison between interfaces files and LDAP directory services, see the
Open Client/Server Configuration Guide for your platform.
Contents of an interfaces file
An interfaces file contains network information about all servers on your network, including Adaptive Server, Backup Server, and XP Server, plus any other server applications such as Monitor Server, Replication Server, and any other Open Server applications.
The network information in the file includes the server name, network name or address of the host machine, and the port, object, or socket number (depending on the network protocol) on which the server listens for queries. See
“Understanding the format of the interfaces file” on page 55 for the specific
makeup of the interfaces file entry.
Each entry in an interfaces file can contain two types of lines:
• Master lines, which are used by server applications to listen for queries over the network. This information is called a listener service.
• Query lines, which are used by client applications to connect to servers over the network. This information is called a query service.
The network information contained in the master and query lines for a server is identical because a server listens for connection requests on the same port that clients use to request connections.
A server needs both master and query lines in its interfaces file, since servers sometimes act as clients to other servers.
52
Adaptive Server Enterprise
If your site has multiple installations
CHAPTER 5 Setting Up Communications Across the Network
A client’s interfaces file does not need a master line. It functions correctly with only a query line.
If you have more than one Adaptive Server installation, each server’s interfaces file should contain information about all servers on the network.
If all of your server products are running on the same platform, you can create one master interfaces file and copy that file to each machine. For more
information, see “Creating a master interfaces file” on page 58.
Heterogeneous and homogeneous environments
You can run Adaptive Server and clients on the same platform or on different platforms.
If the platforms are different, each platform may require a different format and configuration for its interfaces file. Figure 5-1 illustrates how a PC client uses network information in its interfaces file (sql.ini) to connect to Adaptive Server running under UNIX, and how Adaptive Server uses its interfaces file to connect to another server during a remote procedure call.
Configuration Guide
53
Heterogeneous and homogeneous environments
Figure 5-1: Establishing network connections in a heterogeneous environment
PC clients
PC clients
sql.ini
Get Harpo’s address and connect.
[Harpo] xxxxx
[Chico]
Harpo SQL
server
Make a remote procedure call to
Chico.
interfaces
Chico SQL server
Harpo xxxxx
Chico xxxxx
Get Chico’s address and connect.
xxxxx
If both a client and a server are running under UNIX, the same interfaces file is valid for both. Figure 5-2 illustrates how clients and Adaptive Servers running in a homogeneous environment can use copies of the interfaces file to establish connections. Because the two Adaptive Servers are running under the same operating system, they can use the same interfaces file or exact copies of the same file.
54
Adaptive Server Enterprise
CHAPTER 5 Setting Up Communications Across the Network
Figure 5-2: Establishing network connections in a homogeneous environment
Harpo SQL server
Get Chico’s address and make an RPC.
Homogeneous clients
Get Harpo’s address and connect.
Harpo xxxxx
Chico xxxxx
Chico SQL server
Get Chico’s address and connect.
Understanding the format of the interfaces file
The following rules apply to the format of interfaces file entries:
• Each Adaptive Server has only one entry, although there may be multiple lines in the entry.
• Each line that follows the servername line must begin with a space or a character tab.
• Each element on the line must be separated by a single space.
• Each entry is separated by a blank line.
• You can add comments to an interfaces file by adding a pound sign (#) at the beginning of the line and a line break at the end.
There are two interfaces file entry formats, TLI and TCP.
A TLI style entry looks like:
Configuration Guide
55
Understanding the format of the interfaces file
servername retry_attempts delay_interval<newline>
<tab>service_type api protocol device address filter<newline>
<tab>ha_failover servername<newline>
A TCP style entry looks like:
servername retry_attempts delay_interval<newline>
<tab>service_type protocol network machine port filter<newline>
<tab>ha_failover servername<newline>
Components of an interfaces file entry
Table 5-2 describes the components of an interfaces file entry.
Component
servername
retry_attempts (optional)
delay_interval (optional)
service_type api protocol network host
Table 5-2: Components of an interfaces file
Value
Name of Adaptive Server or Backup Server. Requirements for a server name are:
• The name cannot be more than 30 characters long.
• The first character must be a letter (ASCII a through z, A through Z).
• The characters that follow must be letters, numbers, or underscores (_).
Number of times you want the client to try to connect to a server after initial failure. Default is 0.
Number of seconds between connection attempts. Default is 0.
Type of service defined by entry. Must be one of the following:
• master
• query
Application programming interface available to the network.The supported value is tli.
Name of the network protocol. Protocol types available are:
• TCP/IP, represented by the letters “tcp”
Name of the network; not currently used by Adaptive Server. srvbuild enters
“ether” as a placeholder.
Network name or address of server’s host machine.
• For TCP/IP, use either the host name or Internet address. Maximum size of entry is 32 bytes.
To determine the host name of a machine, log in to that machine and enter:
/bin/hostname
56
Adaptive Server Enterprise
CHAPTER 5 Setting Up Communications Across the Network
Component
machine device
address for a TLI protocol entry
port ha_failover filter
Value
Network name or address of server’s host machine.
You can use either the host name or Internet address. Maximum size of entry is 32 bytes.
To determine the host name of a machine, log in to that machine and enter:
/bin/hostname
The network device endpoint.
For TCP networks, the device varies according to the vendor supplying the networking software. Check the vendor-specific documentation for the name of the device. Your network may provide multiple stream devices corresponding to different protocols in the TCP protocol suite. Choose the TCP streams device.
Common TCP streams devices is /dev/tcp.
Address consists of:
• Address prefix, “\x” for TLI.
• Network type, always 0002.
• Port number converted to four digits, hexadecimal. Must be a unique number between 1025 and 65535. Check the /etc/services file on each machine on the network to see what port numbers are in use. Enter the Adaptive Server port number in a new section of /etc/services labeled “Sybase specific services.”
You do not have to make this entry for the operating system to function properly, but the presence of the port number in the file may prevent other users from using the port number.
• IP network node address of the host machine converted to 8 digits, hexadecimal.
• Trailing zeros, optional, 16 digits.
A unique port number between 1025 and 65535. Check the /etc/services file on each machine on the network to see what port numbers are in use. Enter the
Adaptive Server port number in a new section of /etc/services labeled “Sybase specific services.” You do not have to make this entry for the operating system to function properly, but the presence of the port number in the file may prevent other users from using that port number.
An entry created in directory services or the interfaces file for high availability.
Adaptive Server supports Secure Socket Layers (SSL) as a filter which is appended to the master and query lines of the directory services. SSL is the standard for securing the transmission of sensitive information.
Configuration Guide
57
Creating a master interfaces file
Creating a master interfaces file
A master interfaces file contains entries for all Sybase servers on the network.
It can be used with every server and client connected to the network. By distributing copies of a master interfaces file, you can ensure that all Sybase products on the network interact with one another.
Distributing copies of one interfaces file (a master file) with entries for all
Adaptive Servers is the easiest way to maintain consistency in the interfaces files in a homogeneous environment on a network.
You can make all changes to one version of the file and then copy the updated master file to all appropriate Sybase directories.
You can make a master file in one of two ways:
• Using dsedit
or dscp
• Using a text editor
Using dsedit or dscp to create a master interfaces file
You can use the dsedit
or dscp
utility to create a master interfaces file, which you can then distribute to all servers. If you are not an experienced Sybase user, you may find that using dsedit
or dscp
is easier than using a text editor. Using dsedit
or dscp
also ensures that your interfaces file is consistent in format.
To create a master interfaces file with dsedit
or dscp
:
1 Select the interfaces file that contains the most complete, up-to-date information.
2 Begin a dsedit
or dscp
session in your latest Sybase installation to edit this interfaces file.
3 Add entries for any Adaptive Servers or Backup Servers that are not listed in this file.
For details on using these utilities, see the Adaptive Server Utility Guide.
Using a text editor to create a master interfaces file
To construct a single master interfaces file from several individual interfaces files:
58
Adaptive Server Enterprise
CHAPTER 5 Setting Up Communications Across the Network
1 Concatenate the individual interfaces files.
2 Make a copy of the file.
3 Use an ASCII text editor to modify the copy of the concatenated file.
Note
When you manually edit an interfaces file, be sure that, for each entry, each line following the first line begins with a <tab> character.
The following elements must be correct and unique in the resulting file:
• servername – each server entry in the interfaces file must be unique.
During the srvbuild
session, you had the choice of entering a server name or accepting the default server name, SYBASE, for those servers. If you accepted the default name, find any duplicate
SYBASE entries in your merged file, and rename them.
• A combination of the host machine’s network name or address and
Adaptive Server’s port or object number.
• If the original interfaces file was created when there was only one machine on the network, its entries may have the word “loghost” in place of the machine name (address). If loghost is present, replace it with the machine name.
Configuring interfaces files for multiple networks
On some platforms, Adaptive Server can accommodate multiple networks.
This allows Adaptive Server to listen for clients over multiple network interfaces. You must add an entry for each network interface to the interfaces file.
Configuring the server for multiple network handlers
To configure multiple network listeners:
1 Define a unique host name for each network interface in your operating system’s host database.
Configuration Guide
59
Configuring interfaces files for multiple networks
2 In your interfaces file, use a text editor to add copies of the “master” line for your Adaptive Server; one for each additional interface you want the server to listen on.
3 Include a unique host name on each line to configure a network handler for each network interface.
4 Port numbers within the interface need not be the same, but they can be.
They fall under the same rules for naming and numeric range as the primary network interface.
Sample interfaces files for multiple network handlers
The following example shows an interfaces file for an Adaptive Server with two network interfaces. The server host machine is known as
SERV_CORPNET on the corporate network and SERV_ENGNET on the engineering network.
# PRODUCTION server with two network listeners
PRODUCTION<tab>3<tab>3<newline>
<tab>master tcp ether SERV_CORPNET 4559
<tab>master tcp ether SERV_ENGNET 5479
<tab>query tcp ether SERV_CORPNET 4559
When Adaptive Server restarts, it spawns a network handler process for each master line in the entry that corresponds to the server’s DSLISTEN value.
Connections made on each interface are handled equally, as peers.
Configuring the client connections
When an Adaptive Server client scans the interfaces file for a server name, the client uses the first “query” entry it encounters for the server’s entry. This makes configuring clients to use multiple network connections less straightforward than configuring the server ports. You have two choices:
• Use the same DSQUERY name for all clients. The interfaces files on the different machines contain different network names.
• Use different DSQUERY names for the clients. The interfaces files on all the machines are the same, but they contain multiple DSQUERY names.
60
Adaptive Server Enterprise
CHAPTER 5 Setting Up Communications Across the Network
Using one network-independent DSQUERY name
If uniform client DSQUERY naming is important, you can make the necessary changes in the network addressing of the clients in the interfaces file. You can install separate Sybase installation directories and distinct interfaces files on client file servers on each network to allow users to connect to the correct network address. Instead of altering the DSQUERY name the clients use, you maintain one DSQUERY name for all clients, on all networks, and alter each network’s interfaces file accordingly.
This method assumes that:
• You have complete control over what the Sybase installation clients see on each network.
• The interfaces file (at the very least) is not shared or copied among Sybase installations on different networks.
The interfaces file looks like the following example on the “engineering” network:
PRODUCTION<tab>3<tab>3<newline>
<tab>query tcp ether SERV_ENGNET 5470
<tab>master tcp ether SERV_CORPNET 4559
<tab>master tcp ether SERV_ENGNET 5479
The interfaces file looks like the following example on the “corporate” network:
PRODUCTION<tab>3<tab>3<newline>
<tab>query tcp ether SERV_CORPNET 4559
<tab>master tcp ether SERV_CORPNET 4559
<tab>master tcp ether SERV_ENGNET 5479
The “query” line in each file name is different, depending on the network to be used.
The full “master” entry is present in both files. This is allowed because only
Adaptive Server will use the “master” lines. Assuming that the server host machine can see both networks (both host names are interchangeable), it does not matter which interfaces file is used for Adaptive Server start-up.
Using different DSQUERY names
To use different DSQUERY names for each network listener:
1 Choose an additional server name.
Configuration Guide
61
Configuring interfaces files for multiple networks
You can concatenate the original server name and the network name. For example, if your server is named PRODUCTION, you could choose the names PRODUCTION_network1 and PRODUCTION_network2.
2 Do one of the following:
• For PC clients, use sqledit
to create multiple sql.ini file entries for the server, one for each network. In the following example, you create one entry for PRODUCTION_network 1 and one for
PRODUCTION_network2. For more information, see the Open
Client documentation for your client platform.
• For UNIX clients, you can edit the interfaces files with an ASCII text editor. From the server’s interfaces files, copy the server name line and the “master” line for each network into the client interfaces file.
Add the appropriate server name for each entry, and change “master” to “query.”
Clients on each network must use the DSQUERY value that corresponds to the network the client is on. In the following example, either PRODUCTION_network1 or PRODUCTION_network2 can be used.
# Client entry for PRODUCTION on network1
PRODUCTION_network1<tab>3<tab>3<newline>
<tab>query tcp ether serv_corpnet 4559
# Client entry for PRODUCTION on network2
PRODUCTION_network2<tab>3<tab>3<newline>
<tab>query tcp ether serv_engnet 5479
Configuring for query port backup
Another use for multiple network interfaces is to provide a backup in case of network failure. If a client is connected to a server via two networks, the client can establish a connection via the second network if the first one goes down.
To configure Adaptive Server for query port backup:
1 Install multiple “master” and “query” lines in a server entry in the interfaces file.
2 Adaptive Server listens for connections at both ports. Clients looking for a host name and a port number for a connection to an Adaptive Server try the port on each “query” line in order, until they establish a connection.
62
Adaptive Server Enterprise
CHAPTER 5 Setting Up Communications Across the Network
The following example shows how to configure a backup network that will be used only if the normal connection fails. The primary network is
“corporate network” and backup is “engineering network.”
# PRODUCTION server with two network listeners
PRODUCTION<tab>3<tab>3<newline>
<tab>master tcp ether SERV_CORPNET 4559
<tab>master tcp ether SERV_ENGNET 5479
<tab>query tcp ether SERV_CORPNET 4559
<tab>query tcp ether SERV_ENGNET 5479
3 Configure PC-client interfaces files with the appropriate multiple “query” entries, as described in the Open Client documentation. For client interfaces files in a homogeneous environment, you can copy the entire interfaces file entry for the Adaptive Server into the client interfaces file.
4 A connection on the secondary port occurs only if the corporate network is disabled, or if the corporate network interface on the host machine fails or is shut down due to a network-related failure.
IPv6 support
Adaptive Server supports IPv6 technology.
Understanding IPv6
IPv6 addressing terminology:
• Link-local address – an IPv6 address that is usable only over a single link.
• Site-local address – an IPv6 address that can be used within a single-site.
• Global address – an IPv6 address that can be used across the global
Internet.
IPv6 application types:
• IPv6-unaware – an application that cannot handle IPv6 addresses.
• IPv6-aware – an application that can communicate with nodes that do not have IPv4 addresses. In some cases, this might be transparent to the application, for instance when the API hides the content and format of the actual addresses.
Configuration Guide
63
IPv6 support
• IPv6-enabled – an application that, in addition to being IPv6-aware, takes advantage of some IPv6 features.
• IPv6-required – an application that requires some IPv6 features and cannot operate over IPv4.
IPv6 Infrastructure:
IPv6 infrastructure
Dual Stack infrastructure implements both IPv4 and IPv6. This is the recommended infrastructure implementation for using Adaptive Server
Enterprise as an IPv6-aware server.
Sybase applications are IPv6-aware. All code to turn Sybase™ Adaptive
Server and the Open Client/Server components IPv6-aware was done using the
IETF designed primitives, see “Creating or converting for IPv6-aware applications.” The following matrix lists the platform run-time requirements and the specific product and its release version:
Table 5-3: IPv6 support
Platform
Sun Solaris 8 32- and 64- bit
HP-UX 11i(v1) 32- and
64-bit
Microsoft Server 2003
Linux RHEL 3.0
Adaptive Server IPv6 awareness
12.5.3a and 15.0
12.5.3a and 15.0
12.5.3a and 15.0
15.0
Open Client/Server
IPv6 awareness
12.5 and 15.0
12.5 and 15.0
12.5 and 15.0
12.5 and 15.0
Many Sybase products that are Open Client/Server based like XP Server,
Backup Server, Replication Server and Open Switch became automatically
IPv6-aware due to the layered Open Client Transport Control Layer (CTlib-
>NETlib) which is IPv6-aware for network-socket operations. An important note is that any DBlib based Open Client product is not IPv6-aware.
For Adaptive Server Enterprise being IPv6-aware is a complex issue because some components within the ASE are 3rd party components and are not yet
IPv6-aware. To understand how this impacts Adaptive Server Enterprise the following list shows all functional mechanisms of Adaptive Server Enterprise that are IPv6-aware with respect to the platform / release matrix above:
• Connection Handler
64
Adaptive Server Enterprise
CHAPTER 5 Setting Up Communications Across the Network
• RPC mechanisms
• Job Scheduler Task / Agent session connection
• Network Host API
• UDP Message support for sybsendmsg
• Component Integration Services connectivity
• Host / name resolving
• XML URL connection handler
• Auditing for client address data
The following functional mechanisms in Adaptive Server Enterprise do not support IPv6. These mechanisms in Adaptive Server Enterprise are IPv6unaware. They will gradually (over time) be become IPv6-aware in follow-on releases:
• Java support
• License Management Server
• LDAP driver
Starting Adaptive Server Enterprise as IPv6-aware
Adaptive Server is IPv6-unaware, by default. To make Adaptive Server IPv6aware, you must start Adaptive Server with trace flag 7841. This causes
Adaptive Server to determine IPv6 availability and makes Adaptive Server
IPv6-aware.
See your Network or IT specialist to configure your platforms and Network
Infrastructure correctly for IPv6 support.
A second trace flag, 7815 can be set when you start Adaptive Server which captures and logs address connection requests and host / name lookups.
The IPv6 Adaptive Server traceflags:
• T7841 – Enable Adaptive Server IPv6-awareness
• T7815 – Report all Adaptive Server IPv4 & IPv6 Client address connect requests
Configuration Guide
65
Troubleshooting
Before starting Adaptive Server for IPv6-aware operations, make sure that your infrastructure is correctly set up. Once your operating system is correctly configured, an IPv6 connection handler
can be configured and enabled.
Configuring and enabling the IPv6 connection handler
requires adding an additional DCL entry. A single Adaptive Server configuration can typically carry up to 32 connection handler assignments within the DCL.
For example if you have a Site-local setup with two domains administrated under the nameserver setup: sybase.com - being responsible for all IPv4 networking applications v6.sybase.com - being responsible for all IPv6 networking applications
The DCL entry for Adaptive Server to start named “SYBASE” on the host
“revival” for port 17100 would typically look like:
SYBASE master tcp ether revival.sybase.com 17100 query tcp ether revival.sybase.com 17100 master tcp ether revival.v6.sybase.com 17100 query tcp ether revival.v6.sybase.com 17100
In the above example, when Adaptive Server is started with IPv6-awareness it creates two connection handlers
. One listens on port 17100 for incoming IPv4
Clients connection requests, and the other listens on port 17100 for incoming
IPv6 Clients connection requests.
Troubleshooting
This section describes how to correct some common situations that may cause a server to not start.
Server fails to start
If a server fails to start with the following message, the port number specified in the interfaces file may be in use:
00:00000:00002:2003/09/22 12:37:23.63 kernel network name SERV_CORPNET, type ether, port 4559, filter NONE
00:00000:00002:2003/09/22 12:37:23.65 kernel ninit: bind, Address already in use
00:00000:00002:2003/09/22 12:37:23.68 server Error: 1602, Severity: 18, State:
66
Adaptive Server Enterprise
CHAPTER 5 Setting Up Communications Across the Network
2
00:00000:00002:2003/09/22 12:37:23.68 server Unable to initialize network 0
00:00000:00002:2003/09/22 12:37:23.68 kernel ninit: All master network listeners have failed. Shutting down.
00:00000:00002:2003/09/22 12:37:23.68 kernel ueshutdown: exiting
00:00000:00016:2003/09/22 16:11:35.46 server SQL Server shutdown by request.
v
Investigating the port assignment
1 Look in the interfaces file to identify the port number assigned to the server.
2 Determine whether another process is using the same port number by entering: netstat -a
If the port number is presented as a local address in the netstat
output, you cannot use that port for the server. Another process is already using that port.
3 To verify that the server port is in use, start the server manually.
The server does not start if its assigned port number is already in use.
For information on starting servers manually, see the installation documentation for your platform and the Adaptive Server Utility Guide.
v
If a stale server process is retaining use of the port number
1 Do one of the following:
• Use the operating system kill command to terminate the process.
• Use another port number for the server by modifying the interfaces file.
2 Start the server manually to confirm that the port number is available.
For information on starting servers manually, see the installation documentation for your platform and the Utility Guide.
Error when executing an ESP
If you attempt to execute an ESP (extended stored procedure), you may see the following error:
00:00000:00008:1997/09/10 12:52:53.03 kernel XP Server failed to start. Try bringing up XP Server manually. Check SQL Server documentation for more
Configuration Guide
67
Troubleshooting
information on how to bring XP Server up.
XP Server cannot start because the port number may be in use by another process. Use the netstat
command described in the previous section to determine if the port number specified for XP Server is in use.
If you find no processes using the same port number:
1 Restart Adaptive Server.
2 Execute the ESP that you attempted earlier.
XP Server should start automatically.
If you find a process using the same port number, you can do one of the following:
• Change the interfaces file to use a new port number for the XP Server.
• Stop the process using the port number allotted to XP Server.
Restart Adaptive Server, and execute the ESP that you attempted earlier. XP
Server should start automatically.
68
Adaptive Server Enterprise
C H A P T E R 6
Using the Lightweight Directory
Access Protocol as a Directory
Service
Adaptive Server uses directory services to establish client and RPC connections over the Internet. This chapter provides information about using LDAP directory services to establish connections.
Topic
LDAP directory services versus the Sybase interfaces file
Enabling LDAP directory services
Adding a server to the directory services
Migrating from the interfaces file to LDAP
Page
Overview
Configuration Guide
Lightweight Directory Access Protocol (LDAP) is an industry standard for accessing directory services. Directory services allow components to look up information by a distinguished name (DN) from an LDAP server that stores and manages server, user, and software information that is used throughout the enterprise or over a network.
The LDAP server can be located on a different platform from the one on which Adaptive Server or the clients are running. LDAP defines the communication protocol and the contents of messages exchanged between clients and servers. Messages are operators, such as client requests for read, write and query, and server responses, including data-format information.
69
LDAP directory services versus the Sybase interfaces file
The LDAP server stores and retrieves information about:
• Adaptive Server, such as IP address, port number, and network protocol
• Security mechanisms and filters
• High availability companion server name
The LDAP server can be configured with these access restrictions:
• Anonymous authentication – all data is visible to any user.
• User name and password authentication – Adaptive Server uses the default user name and password for UNIX platforms:
• $SYBASE/$SYBASE_OCS/config/libtcl.cfg on 32-bit platforms
• $SYBASE/$SYBASE_OCS/config/libtcl64.cfg on 64-bit platforms
User name and password authentication properties establish and end a session connection to an LDAP server.
Note
The user name and password that are passed to the LDAP server for user authentication purposes are distinct and different from those used to access
Adaptive Server.
Note
LDAP user authentication is not supported on IBM AIX.
When an LDAP server is specified in the libtcl.cfg or libtcl64.cfg file
(collectively the libtcl*.cfg file) the server information is accessible only from the LDAP server. Adaptive Server ignores the interfaces file.
If multiple directory services are supported in a server, then the order in which they are searched is specified in libtcl*.cfg. You cannot specify the search order with the dataserver
command-line option. See “Multiple directory services” on page 77.
LDAP directory services versus the Sybase interfaces file
The LDAP driver implements directory services for use with an LDAP server.
LDAP directories are an infrastructure that provide:
70
Adaptive Server Enterprise
CHAPTER 6 Using the Lightweight Directory Access Protocol as a Directory Service
• A network-based alternative to the traditional Sybase interfaces file
• A single, hierarchical view of information, including users, software, resources, networks, files, and so on
Table 6-1 highlights the differences between the Sybase interfaces file and an
LDAP server.
Table 6-1: interfaces file versus LDAP directory services
interfaces file
Platform-specific
Specific to each Sybase installation
Directory services
Platform-independent
Centralized and hierarchical
Contains separate master and query entries One entry for each server that is accessed by both clients and servers
Cannot store metadata about the server Stores metadata about the server
LDAP directory services support more attributes than the Sybase interfaces file. These attributes can include server version, server status, and so on. See
Table 6-2 for a list of attributes.
Note
LDAP is only supported with reentrant libraries. You must use isql_r
, instead of isql
, when connecting to a server using LDAP directory services.
Attribute name
ditbase dn sybaseVersion sybaseServername sybaseService sybaseStatus
Table 6-2 lists the Sybase LDAP directory entries.
Table 6-2: Sybase LDAP directory definitions
Value type Description
interfaces file or libtcl.cfg
DIT base for object tree. If the libtcl.cfg file is specified, the
interfaces file is ignored. The libtcl.cfg file can be overridden with ct_con_prop
() for a specified connection.
Distinguished name. Must be unique name that identifies the object.
Character string
Integer
Character string
Character string
Integer
Server version number.
Server name.
Service type: Sybase Adaptive Server, or Sybase SQL Server.
Status: 1 = Active, 2 = Stopped, 3 = Failed, 4 = Unknown.
Configuration Guide
71
LDAP directory services versus the Sybase interfaces file
Attribute name
sybaseAddress sybaseSecurity (optional) sybaseRetryCount sybaseRetryDelay sybaseHAservername
(optional)
Value type
String
String
Integer
Integer
String
Description
Each server address includes:
• Protocol: TCP, NAMEPIPE, SPX DECNET (entry is case sensitive).
• Address: any valid address for the protocol type.
Note
dscp splits this attribute into Transport type and Transport address.
Security OID (object ID).
This attribute is mapped to CS_RETRY_COUNT, which specifies the number of times that ct_connect retries the sequence of network addresses associated with a server name.
This attribute is mapped to CS_LOOP_DELAY, which specifies the delay, in seconds, that ct_connect waits before retrying the entire sequence of addresses.
A secondary server for failover protection.
The traditional interfaces file with TCP connection and a failover machine looks like: master tcp ether huey 5000 query tcp ether huey 5000 hafailover secondary
An example of an LDAP entry with TCP and a failover machine looks like: dn: sybaseServername=foobar, dc=sybase,dc=com objectClass: sybaseServer sybaseVersion: 1500 sybaseServername: foobar sybaseService: ASE sybaseStatus: 4 sybaseAddress: TCP#1#foobar 5000 sybaseRetryCount: 12 sybaseRetryDelay: 30 sybaseHAServernam: secondary
All entries in the LDAP directory service are called entities. Each entity has a distinguished name (DN) and is stored in a hierarchical tree structure based on its DN. This tree is call the directory information tree (DIT). Client applications use a DIT base to specify where entities are stored. See
“The libtcl*.cfg file” on page 73
.
72
Adaptive Server Enterprise
CHAPTER 6 Using the Lightweight Directory Access Protocol as a Directory Service
In the example above, the entry describes an Adaptive Server named “foobar” listening on a TCP connection with a port number of 5000. This entity also specifies a retry count of 12 (times) and a retry delay of 30 (seconds). Once a client has found an address where a server responds, the login dialog between the client and the server begins.
You can find a complete list of Sybase’s LDAP directory schema in UNIX
$SYBASE/$SYBASE_OCS/config.
In the same directory, there is also a file called sybase-schema.conf, which contains the same schema, but uses a Netscape-specific syntax.
Since LDAP supports multiple entries for each attribute, each address attribute must contain the address of a single server, including protocol, access type, and address. See sybaseAddress
in Table 6-2.
For example, this is an LDAP entry for an Windows server listening on two addresses, with different connection protocols: sybaseAddress = TCP#1#TOEJAM 4444 sybaseAddress = NAMEPIPE#1#\pipe\sybase\query
Note
Each entry in the address field is separated by the # character.
You can edit these entries with dsedit
. See “Adding a server to the directory services” on page 76.
To ensure cross-platform compatibility for all Sybase products, the protocol and address attribute fields should be in a platform- and product-independent format.
The libtcl*.cfg file
You use the libtcl*.cfg file to specify the LDAP server name, port number, DIT base, user name, and password to authenticate the connection to an LDAP server.
The purpose of the libtcl*.cfg file is to provide configuration information such as driver, directory, and security services for Open Client/Open Server and
Open Client/Open Server-based applications. 32-bit utilities such as dsedit
and srvbuild
, look up the libtcl.cfg, while 64-bit applications use the libtcl64.cfg file for configuration information
Configuration Guide
73
Enabling LDAP directory services
You should edit both the libtcl.cfg and the libtcl64.cfg files to ensure compatibility between 32- and 64-bit applications.
The default libtcl.cfg file is located in $SYBASE/$SYBASE_OCS/config.
If LDAP is specified in the libtcl.cfg file, the interfaces file is not used.
Note
Open Client/Open Server applications that use the
-I
option at start-up override the libtcl.cfg file and use the interfaces file.
In its simplest form, the libtcl.cfg file is in this format:
[DIRECTORY] ldap=libsybdldap.dll ldapurl where the ldapurl is defined as: ldap://host:port/ditbase
The following LDAP entry, using these same attributes, is an anonymous connection and only works only if the LDAP server allows read-only access. ldap=libsybdldap.dll ldap://seashore/d=sybase,dc=com
You can specify a user name and password in the libtcl.cfg file as extensions to the LDAP URL to enable password authentication at connection time.
Enabling LDAP directory services
To use a directory service, you must:
1 Configure the LDAP server according to the vendor-supplied documentation.
2 Add the location of the LDAP libraries to the Unix load library path environment variable for your platform.
3 Configure the libtcl.cfg file to use directory services.
Use any standard ASCII text editor to:
• Remove the semicolon (;) comment markers from the beginning of the LDAP URL lines in the libtcl.cfg file under the [DIRECTORY] entry.
74
Adaptive Server Enterprise
CHAPTER 6 Using the Lightweight Directory Access Protocol as a Directory Service
• Add the LDAP URL under the [DIRECTORY] entry. See Table 6-3 for supported LDAP URL values.
Warning!
The LDAP URL must be on a single line.
libtcl.cfg
ldap+libsydblad.so ldap://host:port/ditbase??scope??bindname=username password libtcl64.cfg
ldap=libsydbldap64.so ldap://host:port/ditbase??scope??bindname=username password
For example:
[DIRECTORY] ldap=libsydbldap.so ldap:///huey:11389/dc=sybase,dc=com??one??
bindname=cn=Manager,dc=sybase,dc=com secret
“one” indicates the scope of a search that retrieves entries one level below the DIT base.
Table 6-3 defines the keywords for the ldapurl variables.
Keyword
Table 6-3: ldapurl variables
Description Default
host (required) The host name or IP address of the machine running the LDAP server
None
port
The port number that the LDAP server is listening on 389
ditbase (required) The default DIT base None
username
Distinguished name (DN) of the user to authenticate NULL (anonymous authentication)
password
Password of the user to be authenticated NULL (anonymous authentication)
4 Verify that the appropriate environment variable points to the required third-party libraries. The Netscape LDAP SDK libraries are located in
$SYBASE/$SYBASE_OCS/lib3p or lib3p64.The Unix load library path environment variable must point to this directory.
5 Add your server entry to the LDAP server using dscp
or dsedit
. See
“Adding a server to the directory services” on page 76.
Configuration Guide
75
Adding a server to the directory services
Adding a server to the directory services
Warning!
Most LDAP servers have an ldapadd
utility for adding directory entries. Sybase recommends you use dsedit
instead since it has built-in semantic checks that generic tools do not provide.
Each server entry is made up of a set of attributes. When you add or modify a server entry, you are prompted for information about server attributes. Some attributes are provided by default, others require user input. When a default value is provided, it appears in brackets “[ ]”. See Table 6-2 for accepted values.
You can use srvbuild
to add entries, but not modify or delete them. v
Adding a server entry to the directory service using dsedit
Before you can add, delete, or modify an LDAP server entry, you must add the
LDAP URL to the libtcl.cfg file. See “The libtcl*.cfg file” on page 73.
Use dsedit
to add a server to the directory service:
1 Source SYBASE.csh or SYBASE.sh to set the environment variables.
2 cd
to $SYBASE/$SYBASE_OCS/bin.
3 Execute dsedit
.
4 Select LDAP from the list of servers, and click OK.
5 Click Add New Server Entry.
6 Enter:
• The server name – this is required.
• The security mechanism – optional. This is the name of the highavailability failover server, if you have one.
7 Click Add New Network Transport and:
• Select the transport type from the drop-down list.
• Enter the host name.
• Enter the port number
8 Click OK two times to edit dsedit
.
To view the server entries, enter the following URL in Netscape http://host:port/ditbase??one.
76
Adaptive Server Enterprise
CHAPTER 6 Using the Lightweight Directory Access Protocol as a Directory Service
For example: ldap://huey:11389/dc=sybase,dc=com??one
Note
Microsoft Internet Explorer does not recognize LDAP URLs.
For more information about dscp
, see the Open Client/Server Configuration
Guide, in the 11.1.x Generic Collection
at http://www.sybase.com/support/manuals
.
Multiple directory services
Any type of LDAP service, whether it is an actual server or a gateway to other
LDAP services, is called an LDAP server.
You can specify multiple directory services for high-availability failover protection. Not every directory service in the list needs to be an LDAP server.
For example:
[DIRECTORY] ldap=libsydbladp.so ldap://test:389/dc=sybase,dc=com ldap=libsybdldap.so ldap://huey:11389/dc=sybase,dc=com
In this example, if the connection to test:389 fails, the connection fails over to the DCE driver with the specified DIT base. If this also fails, a connection to the LDAP server on huey:11389 is attempted. Different vendors employ different DIT base formats.
Note
For more information, see the Open Client Client-Library/C
Programmer’s Guide and the Open Client Client-Library/C Reference Manual at http://www.sybase.com/support/manuals.
Configuration Guide
77
Encrypting the password
Encrypting the password
Entries in the libtcl.cfg file are in human-readable format. Sybase provides a pwdcrypt
utility for basic password encryption. pwdcrypt
is a simple algorithm that, when applied to keyboard input, generates an encrypted value that can be substituted for the password. pwdcrypt
is located in
$SYBASE/$SYBASE_OCS/bin.
From the $SYBASE/$SYBASE_OCS directory, enter: bin/pwdcrypt
Enter your password twice when prompted.
pwdcrypt
generates an encrypted password. For example:
0x01312a775ab9d5c71f99f05f7712d2cded2i8d0ae1ce78868d0e8669313d1bc4c706
Copy and paste the encrypted password into the libtcl.cfg file using any standard ASCII-text editor. Before encryption, the file entry appears as: ldap=libsybdldap.so
ldap://seashore/dc=sybase,dc=com??one??bindname=uid=Manager,dc=sybase, dc=com?password
Replace the password with the encrypted string: ldap=libsybdldap.so
ldap://seashore/dc=sybase,dc=com??one??bindname=uid=Manager,dc=sybase,dc=com
0x01312a775ab9d5c71f99f05f7712d2cded2i8d0ae1ce78868d0e8669313d1bc4c706
Warning!
Even if your password is encrypted, you should still protect it using file-system security.
Performance
Performance when using an LDAP server may be slower than when using an interfaces file because the LDAP server requires time to make a network connection and retrieve data. Since this connection is made when Adaptive
Server is started, changes in performance will be seen at login time, if at all.
During normal system load, the delay should not be noticeable. During high system load with many connections, especially repeated connections with short duration, the overall performance difference of using an LDAP server versus the traditional interfaces file might be noticeable.
78
Adaptive Server Enterprise
CHAPTER 6 Using the Lightweight Directory Access Protocol as a Directory Service
Migrating from the interfaces file to LDAP
There is no direct method to upgrade an existing server using the interfaces file to one that uses lightweight directory services. To upgrade a previous release of Adaptive Server to Adaptive Server version 15.0, see the Installation Guide
for Windows.
Once you have upgraded the server, you can configure your server to use
LDAP service.
1
Shut down the server. See Chapter 2, “Starting and Stopping Servers.”
2 Edit the $SYBASE/$SYBASE_OCS/config/libtcl.cfg or libtcl64.cfg file to
add the directory service. See “Enabling LDAP directory services” on page 74.
3 Use dsedit
4 Restart your server.
Configuration Guide
79
Migrating from the interfaces file to LDAP
80
Adaptive Server Enterprise
C H A P T E R 7
Customizing Localization for
Adaptive Server
This chapter provides information about Sybase localization support for international installations, including configuring languages, character sets, and sort order. For more information, see the System Administration
Guide.
Topic
Overview of localization support
Changing the localization configuration
Page
Overview of localization support
Localization is the process of setting up an application to run in a particular language or country environment, including translated system messages and correct formats for date, time, and currency. Adaptive
Server supports localization for international customers and for customers with heterogeneous environments.
This support includes:
• Data processing support – Adaptive Server comes with character set and sort order definition files it uses to process the characters used in different languages.
Sybase provides support for the major languages in:
• Western Europe
• Eastern Europe
• Middle East
Configuration Guide
81
Overview of localization support
• Latin America
• Asia
• Translated system messages – Adaptive Server includes language modules for:
• Brazilian Portuguese
• Chinese (Simplified)
• French
• German
• Japanese
• Korean
• Polish
• Spanish
• Thai
• Translated documentation – translated documentation is available in:
• Chinese (Simplified)
• French
• German
• Japanese
• Korean
Language modules
Adaptive Server stores its localized software messages in separate language modules.
When you install a language module, the installation program loads the messages, character set, and sort-order files that support the new language in the correct locations.
When you install Adaptive Server and Backup Server, system messages in
English are installed by default.
82
Adaptive Server Enterprise
CHAPTER 7 Customizing Localization for Adaptive Server
Default character sets for servers
The default character set is the character set in which data is encoded and stored on the Adaptive Server databases.
Changing the default language and character set
Warning!
Make all changes to the character set and sort order for a new
Adaptive Server before creating any user databases or making any changes to the Sybase-supplied databases. Changing the character set and sort order after data or data structures have been added to Adaptive Server may require additional steps. To change the character set or sort order after you have added data, see the System Administration Guide.
After srvbuild
configures a new Adaptive Server, it displays a message box asking if you want to localize your Adaptive Server to a language other than us_english and if you want to use a character set or sort order other than the default.
srvbuild
creates an Adaptive Server with the following defaults:
• us_english language
• iso_1 character set (on HP-UX platforms, use Roman8)
• Binary sort order
Valid language options depend on what language modules were unloaded from the distribution media onto your system.
All character sets are copied from the distribution media by default.
You can:
• Click No to accept the defaults.
• Click Yes to change the defaults.
The sqlloc
menu is displayed. sqlloc
is the GUI utility used to change default languages, character sets, and sort orders.
By default, when Adaptive Server and Backup Server are installed on IBM, and SUN Solaris systems, the installation installs the character set files for ISO
8859-1, which supports the Western European languages.
Configuration Guide
83
Overview of localization support
By default, when Adaptive Server and Backup Server are installed on HP systems, the installation installs the character set files for ROMAN8, which supports the Western European languages.
Changing the default character set for servers
You can select any character set as the default on Adaptive Server, including character sets that are not the platform default character sets. Keep the following guidelines in mind when selecting a new default character set:
• To avoid conversion errors or overhead, determine the default character set based on the character set used by your clients.
For example, if most of your clients use ISO 8859-1, you can minimize the amount of data conversion that has to occur by specifying ISO 8859-1.
• If your server is operating in a heterogeneous language environment, choose a character set that works with all the character sets needed. Often, this is Unicode (UTF-8).
Warning!
Make all changes to the default character set and sort order for a new
Adaptive Server before creating any user databases or making any changes to the Sybase-supplied databases. Changing the character set and sort order after data or data structures have been added to Adaptive Server can cause incorrect behavior. To change the character set or sort order after you have added data, see the System Administration Guide.
Supported character sets
The following language, scripts and character sets are supported by Adaptive
Server:
• Arabic – see Table 7-1 on page 85.
• Baltic – see Table 7-2 on page 85.
• Chinese, Simplified – see Table 7-3 on page 86.
• Chinese, Traditional – see Table 7-4 on page 86
• Cyrillic – see Table 7-5 on page 86.
• Eastern European – see Table 7-6 on page 86.
• Greek – see Table 7-7 on page 87.
84
Adaptive Server Enterprise
Configuration Guide
CHAPTER 7 Customizing Localization for Adaptive Server
• Hebrew – see Table 7-8 on page 87.
• Japanese – see Table 7-9 on page 87.
• Korean – see Table 7-10 on page 87.
• Thai – see Table 7-11 on page 87.
• Turkish – see Table 7-12 on page 88.
• Unicode (which supports over 650 languages) – see Table 7-13 on page 88.
• Vietnamese – see Table 7-14 on page 88.
• Western European – see Table 7-15 on page 88.
The tables define each character set and indicate information on whether it requires Unilib conversion (Unilib Required column).
• Check mark (x) – the character set requires Unilib conversion.
• No check mark – the character set may use either the Unilib conversion or the built-in conversion.
For more information see “Character set conversion” on page 89.
Table 7-1 lists the Arabic character set:
Table 7-1: Arabic character sets
Character set Unilib required Description
cp864 cp1256 iso88596
X
X
X
PC Arabic
Microsoft Windows Arabic
ISO 8859-6 Latin/Arabic
Table 7-2 lists the Baltic character set:
Table 7-2: Baltic character sets
Character set Unilib required Description
cp1257 X Microsoft Windows Baltic
Table 7-3 lists the simplified Chinese character set:
85
Overview of localization support
Table 7-3: Simplified Chinese character sets
Character set Unilib required Description
eucgb cp936 gb18030
X
X
X
EUC GB encoding = Simplified Chinese character sets
Microsoft Simplified Chinese character sets
PRC 18030 standard
Table 7-4 lists the traditional Chinese character set:
Table 7-4: Traditional Chinese character set
Character set Unilib required Description
cp950 euccns big5 big5hk
X
X
X
X
PC (Microsoft) Traditional Chinese
EUC CNS encoding = Traditional Chinese with extensions
Big 5 Traditional Chinese
Big 5 with HKSCS extensions
Table 7-5 lists the Cyrillic character set:
Table 7-5: Cyrillic character sets
Character set Unilib required Description
cp855 IBM PC Cyrillic cp866 cp1251 iso88595 koi8
PC Russian
Microsoft Windows 3.1 Cyrillic
ISO 8859-5 Latin/Cyrillic
KOI-8 Cyrillic
Table 7-6 lists the Eastern European character set:
Table 7-6: Eastern European character sets
Character set Unilib required
cp852
Description
PC Eastern Europe cp1250 iso88592
Microsoft Windows 3.1 Eastern European
ISO 8859-2 Latin-2
Table 7-7 lists the Greek character set:
86
Adaptive Server Enterprise
Configuration Guide
CHAPTER 7 Customizing Localization for Adaptive Server
Table 7-7: Greek character sets
Character set Unilib required Description
cp869 cp1253 greek8 iso88597
IBM PC Greek
MS Windows Greek
HP GREEK8
ISO 8859-7 Latin/Greek
Table 7-8 lists the Hebrew character set:
Table 7-8: Hebrew character sets
Character set Unilib required Description
cp1255 iso88598
X
X
Microsoft Windows Hebrew
ISO 8859-8 Hebrew
Table 7-9 lists the Japanese character set:
Table 7-9: Japanese character sets
Character set Unilib required Description
cp932 eucjis
X IBM J-DBCS:CP897 + CP301 (Shift-JIS)
EUC-JIS encoding sjis Shift-JIS (no extensions)
Table 7-10 lists the Korean character set:
Table 7-10: Korean character sets
Character set Unilib required
eucksc X
Description
EUC KSC Korean encoding = CP949
Table 7-11 lists the Thai character set:
Table 7-11: Thai client character sets
Character set Unilib required Description
tis620 cp874
X
X
TIS-620 Thai standard
Microsoft Windows Thai
Table 7-12 lists the Turkish character set:
87
Overview of localization support
Table 7-12: Turkish character sets
Character set Unilib required
cp857 cp1254 iso88599 turkish8
Description
IBM PC Turkish
Microsoft Windows Turkish
ISO 8859-9 Latin-5 Turkish
HP TURKISH8
Table 7-13 lists the Unicode character set:
Table 7-13: Unicode character set
Character set Unilib required
utf8 X
Description
Unicode UTF-8 encoding
Table 7-14 lists the Vietnamese character set:
Table 7-14: Vietnamese character set
Character set Unilib required Description
cp1258 X Microsoft Windows Vietnamese
Table 7-15 lists the Western European character set:
Table 7-15: Western European character set
Character set Unilib required Description
X ascii8 cp437 cp850 cp860 cp858 cp1252 iso_1
X
X
X
US ASCII, with 8-bit data, ISO 646
IBM CP437 - U.S. code set
IBM CP850 - European code set
PC Portuguese cp850 with Euro support
Microsoft Windows US (ANSI)
ISO 8859-1 Latin-1 roman8 iso15 roman9
X
X
HP ROMAN8
ISO 8859-15 Latin-1 with Euro support
HP ROMAN8 with Euro support
88
Adaptive Server Enterprise
CHAPTER 7 Customizing Localization for Adaptive Server
Character set conversion
Backup Server passes messages to Adaptive Server in the client’s language and in the Adaptive Server character set. Adaptive Server then converts the messages and issues them in the client’s language and character set. Keep the following requirements in mind when selecting a character set:
• In a heterogeneous environment, Adaptive Server and Backup Server may need to communicate with clients running on different platforms and using different character sets. To maintain data integrity, the server converts the code between the character sets.
• To use the built-in conversion, you must install the character set definition files on the server for all the character sets being used by your clients.
Built-in conversion support is available for many character sets.
• Unilib conversion support is available for all character sets supported by
Sybase. To enable Unilib conversion, you must use sp_configure
and turn enable unicode conversions
on. For more information, see the System
Administration Guide.
If either Adaptive Server or Backup Server does not support a client’s language or character set, that server issues a warning message. Errors also occur when the Backup Server character set is not compatible with the Adaptive Server character set.
Character set conversion is supported only between character sets for the same language or between character sets in the same language group.
For example, automatic character set conversion is supported between the character sets for the Western European languages: ASCII 8, CP 437, CP 850,
CP 860, CP 863, CP 1252, ISO 8859-1, ISO 8859-15, and ROMAN8.
Similarly, conversion is supported between the character sets for Japanese: CP
932, EUC-JIS, Shift-JIS, and DEC-Kanji.
However, code conversion is not supported between any of the Western
European language character sets and the Japanese character sets. For more information about supported conversions, see the System Administration
Guide.
Conversions between server and client
If Adaptive Server does not support the client’s language or character set, the client can connect with the server, but no character conversions occur.
Configuration Guide
89
Sort orders
When a localized client application connects to Adaptive Server, the server checks to see if it supports the client’s language and character set.
• If Adaptive Server supports the language, it automatically performs all character set conversions and displays its messages in the client’s language and character set.
• If Adaptive Server does not support the language, it uses the user’s default language or Adaptive Server’s default language.
• If Adaptive Server does not support the character set, it issues a warning to the client, turns conversion off, and sets the language to U.S. English.
Sort orders
Each character set comes with one or more sort orders (collating sequences), which are located in the sort-order definition files (.srt files). These files accompany the character set definition files and can be found in the same directory.
You can select a sort order for your data according to the needs at your site.
However, the server can support only one sort order at a time, so select a sort order that will work for all of your clients.
Warning!
Make all changes to the default character set and sort order for a new
Adaptive Server before creating any user databases or making any changes to the Sybase-supplied databases. Changing the character set and sort order after data or data structures have been added to Adaptive Server may cause incorrect behavior. To change the character set or sort order after you have added data, see the System Administration Guide.
Available sort orders
The sort order determines the collating sequence Adaptive Server uses to order, compare, and index character data. Each character set comes with one or more sort orders.
90
Adaptive Server Enterprise
CHAPTER 7 Customizing Localization for Adaptive Server
Sort orders are located in sort order definition files (.srt files) that accompany your character set definition files.
Note
Available sort orders vary according to the character set installed on
Adaptive Server.
You can see the available sort orders for your character set by looking in the
.srt file for your language. Sort orders are stored in:
$SYBASE/charsets/<charset_name>/*.srt
Sort order name
Binary order
Dictionary order, case sensitive, accent sensitive
Dictionary order, case insensitive, accent sensitive
Dictionary order, case insensitive, accent insensitive
For more information about localization files, see “Localization directories” on page 94.
Table 7-16 describes the sort orders that you can specify at installation time or at a later time using the sqlloc
utility.
Table 7-16: Sort orders available in Adaptive Server
Description
Sorts all data according to numeric byte values for that character set. Binary order sorts all ASCII uppercase letters before lowercase letters. Accented or ideographic
(multibyte) characters sort in their respective standards order, which may be arbitrary.
All character sets have binary order as the default. If binary order does not meet your needs, you can specify one of the other sort orders either at installation or at a later time by, using the sqlloc
utility.
Case sensitive. Sorts each uppercase letter before its lowercase counterpart, including accented characters. Recognizes the various accented forms of a letter and sorts them after the associated unaccented letter.
Case-insensitive dictionary sort order. Uppercase letters are equivalent to their lowercase counterparts and are intermingled in sorting results.
Case-insensitive dictionary sort order. Diacritical marks are ignored.
Configuration Guide
91
Sort orders
Sort order name
Dictionary order, case insensitive with preference
Description
Case-insensitive dictionary sort order, with case preference for collating purposes. A word written with uppercase letters is equivalent to the same word written with lowercase letters.
Uppercase and lowercase letters are distinguished only when you use an order by clause. The order by
clause sorts uppercase letters before it sorts lowercase.
Note
Do not select this sort order unless your installation requires that uppercase letters be sorted before lowercase letters in otherwise equivalent strings for order by clauses.
Using this sort order may reduce performance in large tables when the columns specified in an order by clause match the key of the table’s clustered index.
Alternate dictionary order, case sensitive
Alternate dictionary order, case insensitive, accent insensitive
Alternate dictionary order, case insensitive, uppercase preference
Spanish dictionary order, case sensitive
Spanish dictionary order, case insensitive
Spanish dictionary order case insensitive, accent insensitive
Scandinavian dictionary order, case sensitive
Scandinavian dictionary order, case insensitive, uppercase preference
Case-sensitive alternate dictionary sort order with lowercase variants sorted before uppercase.
Use with several of the Western European languages.
Case-insensitive and accent-insensitive alternate dictionary sort order.
Use with several of the Western European languages.
Case-insensitive alternate dictionary sort order with uppercase preference.
Use with several of the Western European languages.
Case-sensitive Spanish dictionary sort order.
Use with Spanish and for most Latin American locales.
Spanish case-insensitive dictionary sort order.
Use with Spanish and for most Latin American locales.
Spanish case-insensitive and accent-insensitive dictionary sort order.
Use with Spanish and for most Latin American locales.
Case-sensitive dictionary sort order.
Use with Scandinavian languages.
Case-insensitive and accent-insensitive dictionary sorting, with uppercase preference.
Use with Scandinavian languages.
To see the sort orders that are available, use sqlloc
to display the sort orders for the character sets you plan to use. For more information on unicode sort orders for utf_8, see Chapter 7, “Configuring Character Sets, Sort Orders, and
Languages” in the System Administration Guide.
92
Adaptive Server Enterprise
CHAPTER 7 Customizing Localization for Adaptive Server
Language modules
If you want Adaptive Server error messages to be displayed in a language other than U.S. English (us_english), you must install the appropriate language module.
When you install a new language module, installation automatically loads the language into the Sybase installation directory to support the new language.
For information about directories, see “Localization directories” on page 94.
Installing a new language module
A full Adaptive Server installation includes all the language components automatically. If you did not select a full install, you must install additional language modules manually.
To install a new language module:
1 Load the language module software from the distribution media. You must load this software into the same directory in which you loaded Adaptive
Server.
2 Reconfigure the language and, if necessary, the character set and sort order
for Adaptive Server. For instructions, see “Changing the localization configuration” on page 97.
Message languages
For messages, U.S. English is installed as the default language in Adaptive
Server. The following rules apply to language modules:
• During Adaptive Server installation or reconfiguration, you can specify a default language other than U.S. English. However, you must have installed the language module for the language you specify.
• If your clients require Adaptive Server messages in a language other than
U.S. English, you must load the language module for those languages.
Then, you can configure Adaptive Server to the language used by your clients.
• If Adaptive Server does not support messages in a client’s language, these clients receive messages in the server default language.
Configuration Guide
93
Localization
For example, if your client’s language is Latin, the Spanish language module is installed, and Spanish is specified as the Adaptive Server default language, the client receives messages in Spanish.
Localization
By default, the Adaptive Server and Backup Server configurations use the
English locale settings, which include:
• Character set definition files for Western European character sets
• Sort-order definition files for Western European character sets
• U.S. English system message files
During the installation process or through reconfiguration, you can specify a different language, character set, and sort order.
Localization directories
Sybase localization configuration involves the following directories:
•
locales
•
charsets
The table below illustrates the structure of the localization files. It does not show a complete list of all the files.
%SYBASE%\ or
$SYBASE/ charsets locales charset_name charset_name...
unicode language_name
language_name...
locales.dat
message
*.srt files
charset.loc
*.uct files
charset_name charset_name...
language_name language_name...
94
Adaptive Server Enterprise
CHAPTER 7 Customizing Localization for Adaptive Server
About the directory
The $SYBASE/locales directory contains a subdirectory for each available language. Each language subdirectory contains a subdirectory for each character set available with that language.
• The .loc files in these subdirectories enable Adaptive Server or Backup
Server to report errors in a specific language, encoded in a specific character set.
There are a variety of .loc files in each subdirectory. Most of these files contain translated error messages for a specific product or utility.
• The common.loc file in each subdirectory contains localized information, such as local date, time, and currency formatting, that is used by all products.
• The locales.dat file contains entries that associate platform-specific locale names with Sybase language and character set combinations.
About the charsets directory
The files in $SYBASE/charsets/charset_name contain information related to each particular character set, such as the definition of the character set and any sort orders available for that character set.
About the locales.dat file
You can edit the locales.dat file to:
• Change the default language or character set for a platform, or
• Add new associations between platform locale names and Sybase language and character set names.
Format of locales.dat file entries
Each entry in the locales.dat file links a platform-specific locale definition to a
Sybase language and character set combination. Each entry has the following format: locale = platform_locale, syb_language, syb_charset where:
Configuration Guide
95
Localization
• platform_locale is the platform-specific keyword for a locale. For acceptable values, see your operating system documentation.
When the locale being defined as the default for the site, platform_locale is “default.”
• syb_language is the name of the language directory to be used from within
$SYBASE/locales/language_name.
• syb_charset is the character set name that determines the character set conversion method and identifies the directory location of the message files for clients from within
$SYBASE/locales/language_name/charset_name.
For example, the following entry specifies that the default locale uses us_english for the language and iso_1 for the character set: locale = default, us_english, iso_1
How client applications use locales.dat
Client applications use the locales.dat file to identify the language and character set to use. The connection process follows these steps:
1 When a client application starts, it checks the operating system locale setting and then checks the locales.dat file to see if that setting is appropriate for Adaptive Server. For example, a locale entry for French can look like the following: locale = fr_FR, french, iso_1
2 When the client connects to Adaptive Server, the language and character set information is passed to Adaptive Server in the login record.
3 Adaptive Server then uses:
• The character set information, for example, iso_1, to identify the client’s character set and verify whether it can convert character data to this character set
• The language (in the preceding example, French) and character set information to see if it has messages in the client’s language
Note
Adaptive Server software includes some locale entries already defined in the locales.dat file. If these entries do not meet your needs, you can either modify them or add new locale entries.
96
Adaptive Server Enterprise
CHAPTER 7 Customizing Localization for Adaptive Server
Editing the locales.dat file
Before beginning the edit, make a copy of the original file, in case you have problems with the resulting edited version.
To edit the locales.dat file:
1 Open the locales.dat file copy in a text editor.
2 Find the section enclosed in brackets:
• For Sun Solaris, [sun_svr4]
• For HP, [hp ux]
• For IBM, [aix]
3 Make sure the section contains an entry for the language (syb_language) and character set (syb_charset) combination that you want to use.
Note
The value for platform_locale must match the value required by your operating system. If the locales definitions in your system configuration files do not match the Sybase locale definitions, your applications will not run properly.
For example, if you want your Open Client messages to appear in French, and Adaptive Server is using the ROMAN8 character set, you would check the locales.dat entries for your platform and look for the following entry: locale = fr_FR, french, roman8
4 Add the required entry or modify an existing entry.
5 Save the changes, if any, and exit the text editor.
Changing the localization configuration
By default, the Adaptive Server and Backup Server configurations uses the
English locale settings localization, which include:
• Character set definition files for Western European character sets
• Sort order definition files for Western European character sets
• us_english system message files
Configuration Guide
97
Changing the localization configuration
During the installation process and through reconfiguration, you can specify a different language, character set, and sort order.
Adaptive Server localization
Each language uses about 2MB of database space per module. If necessary, use the alter database
command to increase the size of the master
database before adding another language.
Note
If you want to install more than one language on Adaptive Server, and the master
database is not large enough to manage more than one language, the transaction log may become too full. You can expand the master
database only on the master device. For more information, see the System Administration
Guide.
1 Source SYBASE.csh or SYBASE.sh if you have not set up the Sybase environment variables.
2 To configure localization for Adaptive Server on the server, start sqlloc
:
$SYBASE/$SYBASE_ASE/bin/sqlloc
3 Select Localize an Existing Server.
4 From the Adaptive Server selection window, select the server.
5 Supply the user name and password. The user must have “sa” privileges.
6 Next, supply:
• the default language
• the default character set
• default sort order
7 Select any other languages you want to install. You may select only languages that are supported by the default character set.
The Add and Remove Languages window lists all Sybase supported languages.
8 The Localization Summary window summarizes the configuration options you selected. Click OK to confirm your selections.
The Status Output window notifies you upon completing the installation.
98
Adaptive Server Enterprise
CHAPTER 7 Customizing Localization for Adaptive Server
Backup Server localization
You can change the Backup server language and character set by modifying the
RUN_<backup_server_name> file. See the Utility Guide for more information on the backupserver
command arguments.
Configuring Adaptive Server for other character sets
To configure Adaptive Server with the character set and sort order for your language, complete the following steps. Your system messages appear in the default language, English.
1 Use the charset
utility to load the default character set and sort order.
To use charset
, the server must be running and you must have System
Administrator privileges. Use the file name of the sort order:
$SYBASE/$SYBASE_ASE/bin/charset -Usa -Ppassword
-Sserver_name sort_order_file character_set
Replace sort_order_file with the name of the sort order file. See Table 7-
17 on page 100. Replace character_set with the Sybase name for your character set. See Table 7-18 on page 101.
2 Use charset
To use the Adaptive Server built-in character set conversions, you must load the character set definition files for all the characters set on your client platforms. If you are using the Unilib character set conversions, you do not need to do this.
3 Using isql
, log in to your server as “sa” and select the master database.
1> use master
2> go
4 Use the ID of the sort order to configure your server for the new character set and sort order.
1> sp_configure "default sortorder_id",
2> sort_order_id, "character_set"
3> go
Replace sort_order_id with the ID for your sort order. See Table 7-17 on page 100. Replace character_set with the Sybase name for your character set. See Table 7-18 on page 101.
5 Shut down the server to start the reconfiguration process.
Configuration Guide
99
Changing the localization configuration
6 Use your normal process on your UNIX system to reboot the server, usually by invoking one of the RUN_xxx scripts from
$SYBASE/$SYBASE_ASE/install.
7 The server starts, rebuilds all the system indexes, then shuts down. Restart a second time to bring the server up in a stable state.
Sort orders
Table 7-17 describes the available sort orders. If your language does not appear, then there is no language-specific sort order for your language—use a binary sort order.
Language or script
All languages
Cyrillic
English
French
German
These sort orders work with all
Western European character sets.
English
French
German
These sort orders work only with CP
850.
Table 7-17: Available sort orders
Sort orders
Binary order
Dictionary order, case sensitive, accent sensitive
File name
binary.srt
cyrdict.srt
Dictionary order, case sensitive, accent sensitive
Dictionary order, case sensitive, accent sensitive
cyrnocs.srt
dictiona.srt
64
51
Dictionary order, case insensitive, accent sensitive
Dictionary order, case insensitive, accent sensitive, with preference
nocase.srt
nocasepr.srt
52
53
Dictionary order, case insensitive, accent insensitive
noaccent.srt
54
Alternate dictionary order, case sensitive
Alternate dictionary order, case sensitive, accent insensitive
Alternate dictionary order, case sensitive, with preference
altdict.srt
altnoacc.srt
altnocsp.srt
ID
50
63
45
39
46
Greek
This sort order works only with ISO
8859-7.
Hungarian
These sort orders work only with
ISO 8859-2.
Russian
This sort order works with all
Cyrillic character sets except for CP
855.
Dictionary order, case sensitive, accent sensitive
Dictionary order, case sensitive, accent sensitive
Dictionary order, case insensitive, accent sensitive
elldict.srt
hundict.srt
hunnoac.srt
Dictionary order, case insensitive, accent insensitive
hunnocs.srt
Dictionary order, case sensitive, accent sensitive
rusdict.srt
Dictionary order, case insensitive, accent sensitive
rusnocs.srt
65
69
70
71
58
59
100
Adaptive Server Enterprise
CHAPTER 7 Customizing Localization for Adaptive Server
Language or script
Scandinavian
These sort orders work only with CP
850.
Spanish
Thai
Turkish
These sort orders work only with
ISO 8859-9.
Sort orders
Dictionary order, case sensitive, accent sensitive
Dictionary order, case insensitive, with preference
File name ID
scandict.srt
47
scannocp.srt
48
Dictionary order, case sensitive, accent sensitive
espdict.srt
55
Dictionary order, case insensitive, accent sensitive
espnocs.srt
Dictionary order, case insensitive, accent insensitive
espnoac.srt
Dictionary order
Dictionary order, case sensitive, accent sensitive
dictionary.srt
turdict.srt
56
57
51
72
Dictionary order, case insensitive, accent insensitive
turnoac.srt
Dictionary order, case insensitive, accent sensitive
turnocs.srt
73
74
Character sets
Table 7-18 lists the supported character sets and their Sybase name.
Table 7-18: Sybase character set names
Character sets Sybase name
ASCII 8
Big 5
Big 5HK
CP 437
CP 850
CP 852
CP 855 acsii_8 big5 big5hk cp437 cp850 cp852 cp855
CP 857
CP 858
CP 860
CP 864
CP 866
CP 869
CP 874
CP 932
CP 936
CP 950
CP 1250
CP 1251
CP 1252 cp857 cp858 cp860 cp864 cp866 cp869 cp874 cp932 cp936 cp950 cp1250 cp1251 cp1252
Configuration Guide
101
Changing the localization configuration
GREEK8
ISO 8859-1
ISO 8859-2
ISO 8859-5
ISO 8859-6
ISO 8859-7
ISO 8859-8
ISO 8859-9
ISO 8859-15
Koi8
ROMAN8
ROMAN9
Shift-JIS
TIS 620
TURKISH8
UTF-8
Character sets
CP 1253
CP 1254
CP 1255
CP 1256
CP 1257
CP 1258
DEC Kanji
EUC-CNS
EUC-GB
EUC-JIS
EUC-KSC
GB 18030 iso15 koi8 roman8 roman9 sjis tis620 turkish8 utf8 greek8 iso_1 iso88592 iso88595 iso88596 iso88597 iso88598 iso88599
Sybase name
cp1253 cp1254 cp1255 cp1256 cp1257 cp1258 deckanji euccns eucgb eucjis eucksc gb18030
charset utility
Use the charset
utility to load character sets and sort orders into Adaptive
Server. If you are using charset
to load the default character set and sort order, this should be done only at the time of installation.
To change the default character set and sort order of Adaptive Server, see the
System Administration Guide.
102
Adaptive Server Enterprise
CHAPTER 7 Customizing Localization for Adaptive Server
Syntax charset
[ -U username ]
[ -P password ]
[ -S server ]
[ -I interfaces ]
[ -v version ]
sort_order
[ charset ]
Keywords and options Description
-U
Table 7-19: Keywords and options for charsets
-P
-S
-I
-v
sort_order charset
If you are not already logged in to your operating system as “sa”, you must specify “-Usa” or
“/username = sa” in the command line.
Specifies the “sa” password on the command line. If not specified, the user is prompted for the “sa” password.
Specifies the name of the server. If not specified, charset
uses the DSQUERY environment variable to identify the server name. If there is no DSQUERY environment variable, charset attempts to connect to a server named “SYBASE.”
Specifies the interfaces file to use. If not specified, charset
uses the interfaces file in the SYBASE directory.
Causes the Sybase version string to be printed, then exits. Use with no other options specified.
When charset
is used to load the default character set and sort order, sort_order is a mandatory parameter specifying the name of the sort order file to be used by Adaptive Server. When loading additional character sets, use charset.loc to indicate the name of the character set files.
Specifies the directory of the character set to be used by
Adaptive Server
.
Configuration Guide
103
Changing the localization configuration
104
Adaptive Server Enterprise
C H A P T E R 8
Logging Error Messages and
Events
This chapter describes how to use the error logging features of Adaptive
Server.
Topic
Page
Adaptive Server error logging
Each time Adaptive Server starts, it writes information to a local error log file, called the Adaptive Server error log:
$SYBASE/$SYBASE_ASE/install/server_name.log
This file:
• Stores information about the success or failure of each start-up attempt.
• Logs error and informational messages generated by the server during its operations.
• Remains open until you stop the server process.
• Contains startup messages from Adaptive Server
Note
When you want to make more disk space available by reducing the size of the error log, stop Adaptive Server before deleting logged messages. The log file cannot release its memory space until Adaptive
Server has stopped.
Configuration Guide
105
Setting error log paths
Enabling and disabling error logging
Logging to the Adaptive Server error log is always enabled. However, when you create or modify a specific user-defined message, you can set it to be
omitted from the log. See “Logging user-defined messages” on page 107.
Setting error log paths
The installation program sets the error log location in the Sybase installation directory when you configure a new Adaptive Server. Backup Server and
Monitor Server each have their own error logs.
The default location for each server’s error log is:
• Adaptive Server: $SYBASE/$SYBASE_ASE/install/servername.log
• Backup Server: $SYBASE/$SYBASE_ASE/install/servername_back.log
• Monitor Server: $SYBASE/$SYBASE-ASE/install/servername_ms.log
At start-up, you can reset the name and location of the Adaptive Server error log file from the command line. Use the
-e
start-up parameter and value in the dataserver
command to start Adaptive Server.
Note
Multiple Adaptive Servers cannot share the same error log. If you install multiple Adaptive Servers, specify a unique error log file name for each server.
Setting the Adaptive Server error log path
You can change the error log path by editing the
$SYBASE/$SYBASE_ASE/install/RUN_server_name file.
For example, to change the error log path from
$SYBASE/$SYBASE_ASE/bin/dataserver -d/Devices/ASE_2K.dat -sASE_2K -
i/ASE_150 -e$SYBASE/$SYBASE_ASE/install/ASE_2K.log -M/ASE_150 to the $SYBASE directory, type:
$SYBASE/ASE-15_0/bin/dataserver -d/Devices/ASE_2K.dat
-sASE_2K -i/ASE_150 -e$SYBASE/ASE_2K.log -M/ASE_150
For information about using the RUN_server_name file, see “Starting and
106
Adaptive Server Enterprise
CHAPTER 8 Logging Error Messages and Events
Managing messages
When event logging is enabled, you can manage its functions in the following ways:
• Use sp_addmessage
or sp_altermessage
to control whether a specific user-defined message is logged in the Adaptive Server error log.
For the complete syntax for sp_addmessage
and sp_altermessage
, see the
Reference Manual.
• Use configuration parameters to specify whether auditing events are logged. Auditing events pertain to a user’s success, log audit logon success
, or failure, log audit logon failure
, in logging in to Adaptive Server.
Logging user-defined messages
You can specify whether a user-defined message is logged to the Adaptive
Server error log. Adaptive Server lets you make this determination for:
• New messages ( sp_addmessage
).
• Existing messages ( sp_altermessage
).
For more information about these commands and their parameters, see sp_addmessage
and sp_altermessage
in the Reference Manual.
New messages
Include the with_log
option in sp_addmessage
when you add a new userdefined message to sysusermessages
. This parameter sets the Adaptive Server to log the message each time that the message appears.
Existing messages
Include the with_log
option in sp_altermessage
to change an existing userdefined message. This parameter alters the reporting status of that message:
• TRUE – to enable logging.
• FALSE – to disable logging.
Configuration Guide
107
Managing messages
Logging auditing events
By default, Adaptive Server does not log auditing events. However, you can use sp_configure
parameters to specify whether Adaptive Server is to log auditing events, such as logins, to the Adaptive Server error log.
Possible parameters and values are:
• log audit logon success
at 1 – to enable logging of successful Adaptive
Server logins: sp_configure "log audit logon success", 1
• log audit logon failure
at 1 – to enable logging of unsuccessful Adaptive
Server logins: sp_configure "log audit logon failure", 1
• Either parameter at 0 – to disable logging of that message type: sp_configure "log audit logon success", 0 sp_configure "log audit logon failure", 0
For more information about sp_configure
, see the System Administration
Guide.
108
Adaptive Server Enterprise
C H A P T E R 9
Managing Adaptive Server
Databases
The administration of Adaptive Server databases includes both routine tasks and performance and tuning considerations.
• The System Administration Guide discusses most of the administrative tasks in detail.
• The Performance and Tuning Guide provides in-depth explanations of performance issues.
Topic
Page
Managing database devices
The term database device refers to a disk or a portion of a disk that stores
Adaptive Server databases and database objects.
Device requirements
Adaptive Server devices and databases are subject to the following limits:
• The maximum device size is 4TB.
• The minimum usable device size depends on the servers logical page size. Databases manage space in groups of 256 logical pages, and the smallest specifiable disk piece size is 1MB, so the smallest usable device is the larger of 1MB or 256 logical pages:
• The minimum device size for a 2K page server is 1MB
• The minimum device size for a 4K page server is 1MB
• The minimum device size for an 8K page server is 2MB
Configuration Guide
109
Managing database devices
• The minimum device size for a 16K page server is 4MB
• The maximum number of database devices is 2,147,483,647. However,
Adaptive Server must retain a description of each device in memory, so in practice this number is limited by your system’s memory. Your operating system also limits how many devices one program can open simultaneously.
• A database can contain up to 2,147,483,648 logical pages, so its maximum size depends on its logical page size:
• The maximum database size on a 2K page server is 4TB.
• The maximum database size on a 4K page server is 8TB.
• The maximum database size on an 8K page server is 16TB.
• The maximum database size on a 16K page server is 32TB.
• The minimum database size is the size of the installation’s model
database.
• Each database is stored on one or more database devices, in one or more disk pieces. The maximum number of disk pieces in one database is 8,
388,608. However, Adaptive Server must retain a description of all active databases, so in practice this number is also limited by your operating system memory.
Note
By default, srvbuild
creates the devices in $SYBASE/data directory.
Creating files for database devices
You can create new database devices using the disk init
command. You can specify a raw partition or operating system file. When using a raw partition, you must specify the full path to the partition. When using an operating system file, you may use the full path or a relative path. Path names are relative to your server’s current working directory.
Sybase recommends that you specify the full path to all database devices. Do not use environment variables when specifying path names with disk init
.
Here is an example of creating a database device using disk init
: disk init name = "user_device1", physname = "/work/data/device1.dat", size = 2048
110
Adaptive Server Enterprise
Configuration Guide
CHAPTER 9 Managing Adaptive Server Databases
In this example,
"size = 2048"
tells the command to allocate 2048 “virtual” pages to the device. A virtual page is 2048 bytes, so this command creates a
4MB device.
The example command does not specify a device number, instead letting the server choose one. Unless you need to assign a specific number to a given device, Sybase recommends you use this method. If you do need an explicit device number, use the parameter
"vdevno = N"
, where N is the device number you want to use. If you specify a device number, that number must not be in use by any other device on this server. Use sp_helpdevice
to see what device numbers have already been used.
If you find an existing database device is too small, you can make that device larger using the disk resize
command. This command takes the same “name” and “size” parameters as disk init
,except that the “size” parameter specifies how much larger you want the device to be.
Note
Operating system constraints will limit how much larger you can make any given device. For example, you cannot make a device on a UNIX raw partition larger if you have already allocated the full defined size of that partition.
For more information about sp_helpdevice
and disk init
command, see the
System Administration Guide and the Reference Manual.
For more information about device files, see the Performance and Tuning
Guide.
111
Managing database devices
112
Adaptive Server Enterprise
C H A P T E R 1 0
Adding Optional Functionality to
Adaptive Server
This chapter provides instructions for adding optional functionality to
Adaptive Server:
Topic
Installing online help for Transact-SQL syntax
Page
After you have installed the Sybase products on your system, see the product documentation for configuration and administration issues.
Adding auditing
Auditing is an important part of security in a database management system. Security-related system activity is recorded in an audit trail, which can be used to detect penetration of the system and misuse of resources.
By examining the audit trail, the System Security Officer can inspect patterns of access to objects in databases and can monitor the activity of specific users. Audit records can be traced to specific users, enabling the audit system to act as a deterrent to users who are attempting to misuse the system.
A System Security Officer manages the audit system and is the only user who can start and stop auditing, set up auditing options, and process audit data.
Audit system devices and databases
The audit system includes several components. The main components are:
• The sybsecurity
device and the sybsecurity
database, which stores audit information
Configuration Guide
113
Adding auditing
The sybsecurity device and database
Tables and devices for the audit trail
Device for syslogs systems table
• The audit trail, which consists of several audit devices and tables that you determine at configuration time
• The syslogs transaction log device, which stores transaction logs
The sybsecurity device stores the sybsecurity
database. The sybsecurity database is created as part of the auditing configuration process. It contains all the system tables in the model
database, as well as a system table for keeping track of server-wide auditing options and system tables for the audit trail.
Adaptive Server stores the audit trail in system tables, named sysaudits_01 through sysaudits_08
. At any given time, only one of the audit tables is current.
Adaptive Server writes all audit data to the current audit table. A System
Security Officer can use sp_configure
to set or change which audit table is current.
When you configure Adaptive Server for auditing, you determine the number of audit tables for your installation. You can specify up to eight system tables
( sysaudits_01 through
sysaudits_08
). Plan to use at least two or three system tables for the audit trail and to put each system table on its own device, separate from the master device. If you do this, you can use a threshold procedure that archives the current audit table automatically, before it fills up and switches to a new, empty table for subsequent audit records.
During auditing configuration, you must specify a separate device for the syslogs
system table, which contains the transaction log. The syslogs
table, which exists in every database, contains a log of transactions that are executed in the database.
Overview of audit installation
There are two methods for installing auditing for the first time in Adaptive
Server:
• Use the installsecurity
script. For information, see the System
Administration Guide.
• Use the auditinit
utility. Tasks that you must perform before installing auditing and instructions on using the auditinit utility follow.
114
Adaptive Server Enterprise
CHAPTER 10 Adding Optional Functionality to Adaptive Server
Pre-installation tasks for auditing devices
Determine the location of the raw devices for the sybsecurity
, syslogs
, and sysaudits
table devices. You will need to provide this information later.
Sybase recommends that you:
• Configure your system with the minimum number of auditing devices you require—you must configure at least three devices. You can add more auditing devices later with sp_addaudittable
. For information, see the
Reference Manual.
• Install auditing tables and devices in a one-to-one ratio. Tables that share the same device will share the same upper threshold limit. These tables cannot be used sequentially when a device 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 system with no loss of auditing records. With two auditing tables, when one fills up, you can switch to the other. With a third auditing table, if one device fails, the System Security Officer can install a new threshold procedure that changes the device rotation to skip the broken device until the device is repaired.
• Make the device larger than the table. When you use only three auditing tables and devices, the size of the table and the size of the device can be similar, because you can obtain more auditing capacity by adding more auditing tables and devices (up to eight). When you are working toward the upper table and device limit (six to eight), you may want to make the device considerably larger than the table. Then, you can expand the table size later towards the upper size of the device when a larger auditing capacity is desired, and few or no device additions are available.
Installing auditing
v
Configuring Adaptive Server for auditing
1 Source SYBASE.csh or SYBASE.sh file if you have not setup the Sybase environment variables.
2 Start auditinit
at the UNIX prompt:
$SYBASE/$SYBASE_ASE/install/auditinit auditinit displays the following menu:
AUDITINIT
Configuration Guide
115
Adding auditing
116
1. Release directory: /usr/u/sybase
2. Configure a Server product
3 Select Configure a Server Product.
4 Select Adaptive Server.
5 Select Configure an Existing Sybase Server.
6 Select the server to configure.
7 Provide the SA password for the server you selected.
8 From the Sybase Server Configuration screen, select Configure Auditing.
As you proceed through the menus in auditinit
, you can change any default values that appear. As you finish each menu, press Ctrl+A to accept the defaults or changed values and move to the next menu.
CONFIGURE AUDITING
1. Configure auditing: no
2. Add a device for audit table(s)
3. Add a device for the audit database transaction log
4. Delete a device entry
5. Change a device entry
List of devices for the audit tables:
Logical name Physical name Segment name
Device for the audit datbase transaction log:
Logical name Physical name Segment name
Table name
Table name
Size
Size
9 From the Configure Auditing screen, select Configure Auditing.
auditinit redisplays the Configure Auditing menu with the value “yes” displayed for Configure Auditing.
10 Restart Adaptive Server for the changes to take effect.
v
Creating a device for an audit table
1 From the Configure Auditing screen, select Add a Device for Audit
Table(s).
auditinit displays the following menu:
ADD/CHANGE A NEW DEVICE FOR AUDITING
1. sybsecurity physical device name:
2. Logical name of the device:
3. Size of the device (Meg):
4. Device size for auditing:
Adaptive Server Enterprise
CHAPTER 10 Adding Optional Functionality to Adaptive Server
2 Select Sybsecurity Physical Device Name.
To create a device for an audit table:
1 Enter the full path of the physical device (raw partition) that you located
in “Pre-installation tasks for auditing devices” on page 115.
Enter the physical name of the device to use for the audit database (default is " "):
/dev/path_to_partition where path_to_partition is the path to the raw partition for the device.
If you specify an operating system file, the following warning appears:
WARNING: '/secret1/sybase_dr/install/aud1.dat' is a regular file which is not recommended for a Server device.
2 Press Return to acknowledge the warning.
auditinit
redisplays the Add/Change a New Device for Auditing menu, 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:
3 Proceed through the remaining items on this menu.
Note
The Size of the Device value must be equal to or greater than the
Device Size for Auditing value. The Device Size for Auditing must be equal to the device size. If you are following Sybase auditing guidelines, you do not need to change the value displayed in Device Size for Auditing.
4 Press Ctrl+A to accept the settings. auditinit
returns to the Configure
Auditing menu and displays the device you have created.
CONFIGURE AUDITING
1. Configure auditing: yes
2. Add a device for audit table(s)
3. Add a device for the audit database transaction log
4. Delete a device entry
5. Change a device entry
Configuration Guide
117
Adding auditing
List of devices for the audit tables:
Logical name Physical name Segment name Table name Size
6.Audit_01' secret1/sybase_dr/install/aud1.dat’ sysaudits_01 5
5 To add multiple audit devices, repeat steps 1– 6.
You can add as many as eight devices. Sybase recommends adding three or more audit table devices.
After adding a device,
auditinit
returns to the Configure Auditing menu and displays all the devices you have created.
CONFIGURE AUDITING
1. Configure auditing: yes
2. Add a device for audit table(s)
3. Add a device for the audit database transaction log
4. Delete a device entry
5. Change a device entry
List of devices for the audit tables:
Logical name name Size
Physical name Segment name Table
6. Audit_01' /secret1/sybase_dr/install/aud1.dat’ sysaudits_01 5
7. Audit_02' /secret1/sybase_dr/install/aud2.dat' sysaudits_02 5
118
v
Creating a device for the audit database transaction log
1 From the Configure Auditing menu, select Add a Device for the Audit
Database Transaction Log.
auditinit displays the Add/Change a New Device for Auditing menu.
ADD/CHANGE A NEW DEVICE FOR AUDITING
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 a default, if available:
Enter the physical name of the device to use for the sybsecurity database (default is''):
/dev/path_to_partition
Adaptive Server Enterprise
CHAPTER 10 Adding Optional Functionality to Adaptive Server
where path_to_partition is the path to the raw partition for the device.
3 Enter the full path name of a physical device.
If you enter an operating system file name, the following warning 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 Auditing menu and the value you selected for the physical name of the device.
ADD/CHANGE A NEW DEVICE FOR AUDITING
1.sybsecurity physical device name:
/secret1/sybase_dr/install/auditlog.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 do so, be aware of the following:
• Sybase recommends a minimum size of 2MB for the size of the transaction log.
• auditinit displays the size in both Size of the Device and in Device Size for Auditing in the Add/Change a New Device for Auditing menu.
• The Device Size for Auditing default value is equal to the size of the device, based on the assumption that you may want to devote the entire device to log for the auditing task. If you want to use only a subset of the device, you can edit the Size of the Device value.
6 Press Ctrl+A to accept the settings displayed in the Add/Change a New
Device for Auditing menu.
auditinit returns to the Configure Auditing menu and displays all the devices you have created.
CONFIGURE AUDITING
1. Configure auditing: yes
2. Add a device for audit table(s)
3. Add a device for the audit database transaction log
4. Delete a device entry
5. Change a device entry
List of devices for the audit tables:
Configuration Guide
119
Adding auditing
Logical name name Size
Physical name Segment name Table
6. Audit_01' /secret1/sybase_ dr/install/aud1.dat’ sysaudits_01 5
7. Audit_02' /secret1/sybase_ dr/install/aud2.dat' sysaudits_02 5
8. auditlog /secret1/.../auditlog.dat logsegment syslogs 2
Enabling auditing
7 When you are ready to execute the audit configuration, press Ctrl+A. auditinit
returns you to the Sybase Server Configuration screen.
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 the installation completes successfully, the following messages are displayed:
Running task: install auditing capabilities.
....................Done
Auditing capability installed.
Task succeeded: install auditing capabilities.
Configuration completed successfully.
Press <return> to continue.
After auditing is installed, no auditing occurs until a System Security Officer enables auditing with sp_configure
. For more information, see the System
Administration Guide.
v
Deleting a device entry
1 Select Delete a Device Entry from the Configure Auditing menu.
2 Enter the number of the device to delete.
3 Press return.
v
Changing a device entry
1 Select Change a Device Entry from the Configure Auditing menu.
2 Enter the number of the device to change.
auditinit displays the Add/Change a New Device for Auditing menu with information on the device you selected:
ADD/CHANGE A NEW DEVICE FOR AUDITING
1. sybsecurity physical device name:
/secret1/sybase_dr/install/audlog
2. Logical name of the device: aud.log
120
Adaptive Server Enterprise
CHAPTER 10 Adding Optional Functionality to Adaptive Server
3. size of the new device (Meg): 5
4. Device size for auditing:5
3 Select each remaining entry you want to change.
4 Press Ctrl+A to save the new entries.
Installing online help for Transact-SQL syntax
This section provides instructions for installing online help for Transact-SQL syntax.
Online syntax help: sp_syntax
The $SYBASE/$SYBASE_ASE/scripts directory contains scripts for installing the syntax help database,
sybsyntax
. You can retrieve this data with sp_syntax
.
For more information on sp_syntax
, see the Reference Manual.
The scripts directory contains one or more of the sp_syntax
scripts shown in
Table 10-1, depending on which Sybase products are included with your server:
Table 10-1: sp_syntax installation scripts
Script Product
ins_syn_cl ins_syn_esql ins_syn_os ins_syn_sql
Open Client Client-Library™
Embedded SQL™
Open Server
Transact-SQL
All Adaptive Server installations include the ins_syn_sql
script. This script includes syntax information for Transact-SQL, the system procedures, and the
Sybase utilities. When you execute this script, you install the SQL portion of the sybsyntax
database.
Configuration Guide
121
Installing online help for Transact-SQL syntax
You can install any of these scripts, depending on the need for Sybase information on your server. The first script you execute creates the sybsyntax database and the needed tables and indexes. Any scripts that you execute after the first one add to the existing information in the database. If you execute a script that was executed previously, the previously installed rows of information are deleted from the table in the database and then reinstalled.
Warning!
The ins_syn_cl and ins_syn_os scripts conflict. If you execute both scripts, errors occur.
Default device for the sybsyntax database
The sybsyntax
database requires 3MB on your database device. By default, the sybsyntax
installation scripts install the sybsyntax
database on the device that is designated as the default database device.
If you have not used sp_diskdefault to change the status of the master device
(which is installed as the default disk) or to specify another default device, the scripts install sybsyntax on the master device. Sybase does not recommend this configuration because sybsyntax
uses valuable space, which is best left available for future expansion of the master database.
To avoid installing sybsyntax
on the master device, do one of the following:
Use sp_diskdefault
to specify a default device other than the master device. For information about sp_diskdefault
, see the Reference Manual.
• Modify each sybsyntax
installation script that you plan to execute to specify a different device, as explained in the following section.
Installing sybsyntax
For each sybsyntax
installation script you want to execute:
1 Determine the type (raw partition, logical volume, operating system file, and so on) and location of the device where you plan to store the sybsyntax database. You will need to provide this information later.
2 Make a copy of the original script. Be sure you can access this copy, in case you experience problems with the edited script.
122
Adaptive Server Enterprise
Configuration Guide
CHAPTER 10 Adding Optional Functionality to Adaptive Server
3 Use a text editor to edit the script, if necessary, to change the default device from the master device to the device created in step 1. For information on
the default device, see “Default device for the sybsyntax database” on page 122.
• Comment out the following section, which specifies the default device:
/* create the database, if it does not exist */
if not exists (select name from sysdatabases
where name = "sybsyntax")
begin
/* create the sybsyntax table if it doesn’t exist */
/* is the space left on the default database devices > size of model? */ if (select sum (high-low +1) from sysdevices where status
& 1 = 1) - (select sum(size) from sysusages, sysdevices where vstart >= sysdevices.low
and vstart <= sysdevices.high
and sysdevices.status &1 = 1) >
(select sum(sysusages.size) from sysusages where dbid = 3)
begin create database sybsyntax
end
else
begin print "There is not enough room on the default devices to create the sybsyntax database."
return
end
end
• After you have commented out this entire section, add a line like this to the script: create database sybsyntax on device_name where device_name is the name of the device where you want to install sybsyntax
.
4 Execute the script with a command like the following: isql -Usa -Ppassword -Sservername <
$SYBASE/$SYBASE_ASE/scripts/ins_syn_sql where sa is the user ID of the System Administrator, password is the
System Administrator’s password, and servername is the Adaptive Server where you plan to install the database.
123
Installing online help for Transact-SQL syntax
If you have set the DSQUERY environment variable to the servername, you can replace the server name with $DSQUERY.
5 To ensure that you have installed the sybsyntax
database and that it is working correctly, use isql
to log in to the server on which you installed the database, and execute sp_syntax
. For example: isql -Usa -Ppassword -Sservername
1> sp_syntax "select"
2> go
Adaptive Server displays a list of commands that contain the word or word fragment “select.”
124
Adaptive Server Enterprise
Index
Symbols
::= (BNF notation)
, (comma)
{} (curly braces)
() (parentheses)
[ ] (square brackets)
A
Adaptive Server
conversions between, and clients 89
database device requirements 9
starting from UNIX command line 18
starting with operating system 20
address component in interfaces files
administrator
Configuration Guide
API component in interfaces file
asynchronous I/O (AIO)
audit trail
auditing
recommended database device size 9
B
Backup Server
starting from UNIX command line 18
starting with operating system 20
Backup Server, default, for Adaptive Server 48
Backus Naur Form (BNF) notation
BNF notation in SQL statements
brackets. See square brackets [ ]
125
Index
C
case sensitivity
changing
character devices
improving I/O performance on 38, 39
83, 84, 97 client selection of 84
in a heterogeneous environment 89
client interfaces files
difference between client and server versions 52
heterogeneous 53 homogeneous 53
clients
Adaptive Server communications with 49
applications and locales.dat file 96
conversion between, and server 89
code conversion
collating sequences. See sort orders 90
comma (,)
commands
126
communications between client and Adaptive Server
configurations
configuring
conventions
Transact-SQL syntax xiii used in the Reference Manual xiii
conversions, Unicode character 85
converting between character sets 89
create database command, system tables created by 5
creating
interfaces files automatically 50
curly braces ({}) in SQL statements xiv
D
database devices
preparing raw partitions for 10
Adaptive Server Enterprise
dbcc checkstorage, database for 7
default
delay_interval component in interfaces files 56
device component in interfaces files 57
devices
displaying current file descriptors 34
documentation
creating master interfaces files with 58
dsedit
Configuration Guide
Index
creating master interfaces files with 58
DSLISTEN environment variable 3
DSQUERY environment variable 4
multiple networks, using different values 61 naming in 61
E
environment variables
error logging
ESPs. See extended stored procedures (ESPs)
ether placeholder in interfaces files 56
extended stored procedures (ESPs) 2
F
file descriptors
files
127
Index
localized error messages (.loc) 95
sort order definition (.srt) files 90
formatting for local date, time, and currency 95
G
H
described 53 interfaces files and 53
homogeneous environments
described 53 interfaces files and 53
host component in interfaces files 56
host name
HP-UX
I
128
IBM RS/6000
iostat command 44 monitoring systems 44 netstat command 44 netstat -v command 44
no -a command 44 ps command 44 time command 44
installation directory, Sybase xv
interfaces files
client and server versions, differences in 52
heterogeneous environments and 51 homogeneous environments and 51
Adaptive Server Enterprise
query port backup configuration 62
query service type 56 retry_attempt component 56 servername component 56 service_type component 56
spaces in 55 tab characters in 55
international systems
iostat command
J
Japanese sample database 7 jpubs sample database 7
K
L
languages
error reporting in specific 95
Configuration Guide
Index
LD_LIBRARY_PATH environment variable 4
LDAP
multiple directory services 77
LDAP libraries
environment variables 75 location of 75
LDAP server
using dsedit to add and modify 76
ldapurl
LIBPATH environment variable 4
libtcl*cfg
limits for file descriptors 35
loc files 95 local date, time, and currency formatting 95
loghost in interfaces files 59
login
root 3 sa 3 superuser 3 sybase 3
129
Index
M
machine component in interfaces files 57
master
master database 5 master device 5, 9
maxfiles kernel parameters 34 maxfiles_lim kernel parameters 34
messages
messages, selecting language for 93
Monitor Server
starting from UNIX command line 18
starting with operating system 20
monitoring
operating system resources 43 virtual memory usage 43
monitoring systems
multiple directory services
multiple installations
creating one interfaces file for
multiple networks
used as a backup in case of network failure 62
N
named pipes
naming requirements for servers 56
NCR
130
netstart -v command (IBM RS/6000) 44
netstat command
network component in interfaces files 56
network protocols
network support
networks
no -a command (IBM RS/6000) 44
O
operating system
P
parent process identification (PPID) 27
parentheses ()
partition map
password encryption
for libtcl*.cfg 78 pwdcrypt 78
Adaptive Server Enterprise
required in environment variables 29
PID. See process identification
platform-specific locale names 95
port component in interfaces files 57
port numbers and interfaces files 59
PPID. See parent process identification
procedures, Sybase extended stored
process identification (PID) 27
protocol
component in interfaces files 56
ps command
pubs2 sample database 6 pubs3 sample database 6
pwdcrypt
location of 78 password encryption 78
Q
query port backup configuration 62
R
raw block devices
raw partitions
availability of 10 minimum size for database devices 10
referential integrity constraint 15
retry_attempts component in interfaces files 56
Configuration Guide
Index
S
sar command
Scandinavian dictionary sort orders 92
scripts
C shell 45 maintenance 45 sample maintenance 45
servername component in interfaces files 56
servers
service types
master 56 service_type component in interfaces file 56
shells
size
sybsystemprocs database, minimum required for upgrade 13
SMIT
See System Management Interface Tool
Sort order
sort order
default for Adaptive Server 83
Sort orders
131
Index
character sets and 90 databases and 90 definition files 90
Spanish dictionary sort orders 92
square brackets [ ]
starting servers
with operating system 20 startserver utility 20
Sun Solaris
iostat command 44 netstat command 44
sundiag system diagnostic tool 43
$SYBASE environment variable as default server name
Sybase installation directory xv
SYBASE_ASE environment variable 4
SYBASE_FTS environment variable 4
SYBASE_OCS environment variable 4
SYBASE_SYSAM environment variable 4
sybsecurity
sybsystemdb
symbols
syntax conventions, Transact-SQL xiii
sysprocsdev device
system databases
System Management Interface Tool (SMIT) 40
system messages, translated 82
system procedures, storage location of 6
T
tab characters in interfaces files 55
time command
translated messages
U
Unicode
UNIX
UnixWare
132
Adaptive Server Enterprise
Index
utilities
V
vmstat command
W
Windows Sockets
X
XP Server
XP Server, starting 17 xp_cmdshell command 17
Configuration Guide
133
Index
134
Adaptive Server Enterprise
advertisement
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Key Features
- Advanced data management capabilities
- Robust application support
- Scalable architecture
- High availability and disaster recovery
- Comprehensive security features
- Easy to use and manage
Related manuals
Frequently Answers and Questions
What are the benefits of using the Sybase DC35823-01-1500-04?
What types of applications can I run on the Sybase DC35823-01-1500-04?
How can I get started with the Sybase DC35823-01-1500-04?
advertisement