| |
Home |
![[Table of Contents]](/dwicons/b_toc.gif)
|
Installing Adaptive Server Enterprise on Siemens |
![[-]](/dwicons/i_colpse.gif)
| Chapter 1: Overview |
This chapter introduces important concepts about the installation of Adaptive Server and Adaptive Server products.
Topics covered include:
In this book, these terms are defined as follows:
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:
The individual who maintains the operating system. This individual has superuser or "root" privileges.
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.
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.
Table 1-1 provides a description of the server and client products in your Adaptive Server package.
Product | Description |
|---|---|
Adaptive Server | The relational database server. The default unloading process includes:
|
Adaptive Server Plug-In to Sybase Central | Sybase Central is a common framework for managing servers. It allows you to manage Adaptive Server installations using the Sybase Central graphical management tool. You can manage Adaptive Server running on any platform from a PC that is running Windows 95 or Windows NT. For information on how to use Sybase Central to manage Adaptive Server, see Managing and Monitoring Sybase Adaptive Server Enterprise. |
Adaptive Server Enterprise Monitor | An Open Server application that obtains performance statistics on Adaptive Server and makes those statistics available to Monitor Server client applications. Adaptive Server Enterprise Monitor (also called Monitor Server) includes:
|
Backup Server | Backup Server is an Open Server-based application that manages all database backup (dump) and restore (load) operations for Adaptive Server. Backup Server provides the following features:
|
Language Modules (Server) | Provides system messages and date/time formats to help you localize your applications. Default installation includes the us_english language module and the following character sets:
|
Language Modules (Connectivity) | Provides messages and support files for running Open Client applications in various languages. |
ODBC Driver | Allows Windows NT client applications to access Adaptive Server data. |
Open Client | Provides libraries and utilities for developing any Open Client application. |
SQL Advantage | A graphical isql tool for Adaptive Server. |
XP Server | An Open Server application that manages and executes extended stored procedures (ESPs) from within Adaptive Server. ESPs provide a method for calling procedural language functions from within Adaptive Server. XP Server is unloaded, by default, when you unload Adaptive Server software from the distribution media. Use the srvbuild utility to set up XP Server and to connect XP Server and Adaptive Server through the interfaces file. |
Table 1-2 lists the Adaptive Server installation and setup utilities you can use to unload, install, upgrade, or customize Adaptive Server and its products on UNIX systems.
Utility | Use To | Environment |
|---|---|---|
dscp | Modify the interfaces file. | Interactive, text-based interface |
dsedit | Modify the interfaces file. | X-Windows/Motif GUI |
sqlloc | Modify localization settings, such as language and character set. Use of this utility is not described in this installation guide. For information on using sqlloc, see the sqlloc online help, Configuring Adaptive Server for UNIX Platforms, and Utility Programs for UNIX Platforms. | X-Windows/Motif GUI |
sqllocres | Modify localization settings, such as language and character set, using a resource file. Use of this utility is not described in this installation guide. For information on using sqllocres, see Utility Programs for UNIX Platforms. | Noninteractive, file-based interface |
sqlupgrade | Upgrade Adaptive Server. | X-Windows/Motif GUI |
sqlupgraderes | Upgrade Adaptive Server using a resource file. | Noninteractive, file-based interface |
srvbuild | Build a functional server. | X-Windows/Motif GUI |
srvbuildres | Build a functional server using a resource file. | Noninteractive, file-based interface |
sybsetup |
| X-Windows/Motif Graphic User Interface (GUI) |
sybload | Unload Adaptive Server products from distribution media. | Interactive, text-based interface |
It is crucial to the operation of Sybase products that the system environment variables are 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.
The DSLISTEN environment variable 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 the server name given at installation.
The DSQUERY environment variable defines the Adaptive Server name that client programs try 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 the server name given at installation.
The PATH environment variable specifies which directory path to search for executables. The Sybase executables are located in the $SYBASE/bin directory.
The SYBASE environment variable defines the path of the Sybase installation directory. The installation program uses the SYBASE environment variable during installation.
The name of the shared library environment variable is different for each UNIX platform. Chapter 3, "Unloading Server Products from Distribution Media," defines this environment variable for your platform.
The Sybase installation directory structure is created by the installation process. Adaptive Server is placed in the directory you indicate when you run sybsetup or sybload. Figure 1-1 illustrates a portion of the Adaptive Server installation directory structure.
Figure 1-1: Adaptive Server installation directory structure
The Adaptive Server installation directory contains executable files and administrative tools, which are added as each product is installed.
Adaptive Server communicates with other Adaptive Servers, Open Server(TM) 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. This information is stored in an interfaces file, named interfaces on UNIX platforms, located in the Adaptive Server installation directory. After your Adaptive Server or client software is installed, it can connect with any server on the network that is listed in the interfaces file.
The interfaces file is like an address book. It lists the name and address of every known 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 interfaces file and connects to that server (see Figure 1-2). 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 to which they want to connect. It also tells Adaptive Server where to listen for incoming connection attempts from clients. Adaptive Server uses a single port for these two services (referred to as query service and listener service).
On SPX networks, the socket number gives clients and servers a way to identify each other.
Figure 1-2: Communicating with a server
During installation, you use the srvbuild utility to create a new server. The srvbuild process adds entries to the interfaces file for your new Adaptive Server, Backup Server, Monitor Server, and XP Server.
For instructions on using dsedit or dscp to modify interfaces file entries or to create new interfaces file entries for existing servers, see Configuring Adaptive Server for UNIX Platforms.
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 (for production systems) or operating system files (for nonproduction uses).
Adaptive Server requires the following devices:
The master and sysprocsdev devices are created by srvbuild when you create a new Adaptive Server.
The master device contains the following databases:
The sample databases are stored on the master device at installation, but should be moved to a user-defined device after installation. For information on the sample databases, see "Optional Devices and Databases".
Note: , For recovery purposes, it is recommended that you do not create other system or user databases or user objects on the master device.
The sysprocsdev device 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. System procedure names begin with "sp_".
The system procedures that are needed during difficult 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.
The following devices and databases are needed only if you configure Adaptive Server for optional functionality, like auditing or two-phase commit transactions.
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.
Install auditing using the auditinit utility. The sybsecurity device is created as part of the auditing installation process.
See Chapter 7, "Adding Optional Functionality to Adaptive Server," for instructions on how to configure Adaptive Server for auditing.
The auditing system is discussed in more detail in the Security Administration Guide.
The sybsystemdb device stores the sybsystemdb database, which stores information about two-phase commit transactions.
See Chapter 7, "Adding Optional Functionality to Adaptive Server," for instructions on how to create the sybsystemdb device and database and how to configure Adaptive Server for two-phase commit.
The pubs2 and pubs3 databases are sample databases provided as a learning tool for Adaptive Server. The pubs2 sample database 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.
The interpubs database contain French and German data. jpubs contains Japanese data.
For information about installing the sample databases, see Chapter 7, "Adding Optional Functionality to Adaptive Server."
For information on the contents of these sample databases, see the Transact-SQL User's Guide.
The syntax database, sybsyntax, contains syntax help for Transact-SQL commands, Sybase system procedures, Adaptive Server utilities, and Open Client routines. Users can retrieve this information using the system procedure sp_syntax.
For example, to see the syntax of the Transact-SQL select command, enter:
sp_syntax "select"
Adaptive Server includes scripts for creating the sybsyntax database.
See Chapter 7, "Adding Optional Functionality to Adaptive Server," for instructions on how to install sybsyntax.
See the Adaptive Server Reference Manual for more information about sp_syntax.
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 the dbcc checkstorage command is used.
dbcc checkstorage records configuration 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.
Information on installing dbccdb is located in Chapter 18, "Checking Database Consistency," of the System Administration Guide.
For Adaptive Server product descriptions, and server and database specifications, see Chapter 2, "Installation Requirements."
|
|