Oracle SQL/Services Server Configuration Guide

Oracle Rdb7^(tm)

Oracle SQL/Services^(tm) Server Configuration Guide

Release 7.0

Part No. A41983-1

Corporate Copyright Notice

IMPORTANT - READ CAREFULLY BEFORE VIEWING AND/OR USING THIS DOCUMENTATION IN ANY WAY. NO PART OF THIS DOCUMENTATION MAY BE REPRODUCED OR TRANSMITTED IN ANY FORM OR BY ANY MEANS, ELECTRONIC OR MECHANICAL, FOR ANY PURPOSE, WITHOUT THE EXPRESS WRITTEN PERMISSION OF ORACLE CORPORATION.

This software contains proprietary information of Oracle Corporation; it is provided under a license agreement containing restrictions on use and disclosure and is also protected by copyright law. Reverse engineering of the software is prohibited.

The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. Oracle Corporation does not warrant that this document is error free.

Restricted Rights Legend Programs delivered subject to the DOD FAR Supplement are 'commercial computer software' and use, duplication and disclosure of the programs shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement. Otherwise, programs delivered subject to the Federal Acquisition Regulations are 'restricted computer software' and use, duplication and disclosure of the programs shall be subject to the restrictions in FAR 52.227-14, Rights in Data---General, including Alternate III (June 1987). Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065.

The programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, back up, redundancy and other measures to ensure the safe use of such applications if the programs are used for such purposes, and Oracle disclaims liability for any damages caused by such use of the programs.

Oracle and SQL*Net are registered trademarks of Oracle Corporation, Redwood City, California. Rdb7, Oracle Rdb, Oracle RMU, and Oracle SQL/Services are trademarks of Oracle Corporation, Redwood City, California.

All other company or product names are used for identification purposes only and may be trademarks of their respective owners.

Send Us Your Comments

Oracle Corporation welcomes your comments and suggestions on the quality and usefulness of this publication. Your input is an important part of the information used for revision.

You can send comments to us in the following ways:

Electronic mail --- nedc_doc@us.oracle.com
FAX --- 603-897-3334 Attn:Oracle Rdb Documentation

Postal service

Oracle Corporation 
Oracle Rdb Documentation 
One Oracle Drive
Nashua, NH  03062
USA

If you like, you can use the following questionnaire to give us feedback. (Edit the online release notes file, extract a copy of this questionnaire, and send it to us.)

Did you find any errors?
Is the information clearly presented?
Do you need more information? If so, where?
Are the examples correct? Do you need more examples?
What features did you like most about this manual?

If you find any errors or have any other suggestions for improvement, please indicate the chapter, section, and page number (if available).

Preface

Oracle Rdb is a general-purpose database management system based on the relational data model.

Oracle SQL/Services, a client/server component of Oracle Rdb, enables a client application program, invoked on a remote client computer running on a supported operating system or transport, to access Oracle Rdb databases and other databases supported by SQL on a Digital UNIX or OpenVMS server system. See the Guide to Using the Oracle SQL/Services Client API for a complete list of supported clients.

This manual describes how to maintain and tune an Oracle SQL/Services server system.

Intended Audience

This manual is written for the system manager responsible for maintaining and fine-tuning Oracle SQL/Services. System managers should refer to the Oracle SQL/Services Installation Guide, which provides information important to the installation of an Oracle SQL/Services system.

Operating System Information

You can find information about the versions of the operating system and optional software that are compatible with this release of Oracle Rdb and Oracle SQL/Services in the Oracle Rdb7 Installation and Configuration Guide, the Oracle SQL/Services Installation Guide, and the Oracle SQL/Services Release Notes.

Contact your Oracle representative if you have other questions about compatibility.

Structure

This manual contains the following chapters.

Chapter 1 Introduces the Oracle SQL/Services system.

Chapter 2 Describes how to manage an Oracle SQL/Services system.

Chapter 3 Describes how to maintain an Oracle SQL/Services system.

Chapter 4 Describes the Oracle SQL/Services system management commands.

Related Manuals

For more information, see the other manuals in this documentation set, especially the following:

Oracle Rdb7 Guide to SQL Programming
Oracle Rdb7 SQL Reference Manual
Guide to Using the Oracle SQL/Services Client API
Oracle Rdb7 Release Notes
Oracle SQL/Services Release Notes
Oracle Rdb7 Installation and Configuration Guide
Oracle SQL/Services Installation Guide
Oracle Rdb7 Guide to Database Maintenance

The Oracle SQL/Services Release Notes and the Oracle Rdb7 Release Notes are provided only as part of the software kit. The Oracle Rdb release notes are at /usr/lib/dbs/rdb/v70/doc. The Oracle SQL/Services release notes PostScript and .TXT source files are available in SYS$HELP on OpenVMS systems and /usr/lib/dbs/sqs/v70/doc on Digital UNIX systems.

Conventions

In this manual, Oracle Rdb refers to Oracle Rdb for OpenVMS and software. Release 7.0 of Oracle Rdb software is often referred to as V7.0.

The SQL interface to Oracle Rdb is referred to as SQL. This interface is the Oracle Rdb implementation of the SQL standard ANSI X3.135-1992, ISO 9075:1992, commonly referred to as the ANSI/ISO SQL standard or SQL92.

Oracle ODBC Driver for Rdb software is referred to as the ODBC driver.

Variant file names and names of utilities are used for a multiversion installation. That is, the file name or utility may have a two-digit version number appended as the last two characters of its name. For example, the management client is SQLSRV_MANAGE70 and its log files are *70.log, and so forth, if Oracle SQL/Services V7.0 is installed as a multiversion on the same node as a previous version of Oracle SQL/Services. For a standard installation, file names and names of utilities are not variant. This manual assumes you have a standard installation and uses the nonvariant names of files and utilities unless use of variant names makes the meaning clearer.

OpenVMS means both the OpenVMS Alpha and the OpenVMS VAX operating systems.

This manual uses icons to identify information specific to an operating system or platform. Where material pertains to more than one platform or operating system, combination icons or generic icons are used. For example:

[OpenVMS Alpha]

The Alpha icon denotes the beginning of information specific to the OpenVMS Alpha operating system.

[OpenVMS VAX]

The VAX icon denotes the beginning of information specific to the OpenVMS VAX operating system.

[Digital UNIX]

The Digital UNIX icon denotes the beginning of information specific to the Digital UNIX operating system.)

The diamond symbol denotes the end of a section of information specific to an operating system or platform.

These icons do not appear in the .TXT version of this document but are replaced by character icons enclosed by angle brackets (<>). For example, <OpenVMS>.

The following conventions are also used in this manual:

.
.
. Vertical ellipsis points in an example mean that information not directly related to the example has been omitted.

[ ] In text, brackets enclose optional information from which you can choose to use or not.

$ The dollar sign represents the DIGITAL Command Language prompt in OpenVMS and the Bourne shell prompt in Digital UNIX.

> The right angle bracket represents the :MS--DOS command prompt. This symbol indicates that the :MS--DOS command language interpreter is ready for input.

% The percent sign represents the ULTRIX default user prompt.

boldface text Boldface type in text indicates a term defined in the text.

monospaced boldface text Monospaced boldface type text indicates user input.

e, f, t Index entries in the printed manual may have a lowercase e, f, or t following the page number; the e, f, or t is a reference to the example, figure, or table, respectively, on that page.

Terminology

Some Oracle SQL/Services terminology in this manual has changed effective with release 7.0 of Oracle SQL/Services. The revised terminology reflects changes in the current server architecture compared to the original Oracle SQL/Services architecture, and makes terminology consistent on Digital UNIX and OpenVMS platforms.

The term dispatcher replaces all instances of the phrase communications server.
The term executor or executors replaces all instances of the phrase execute server process or execute server processes.
The term service replaces all instances of the term class.
The term universal replaces all instances of the term generic when referring to a service type. For example, the phrase session reusable generic service becomes session reusable universal service and generic service becomes universal service.

These terminology changes are made throughout this manual.

Technical Changes and New Features

The Oracle SQL/Services Release Notes and Oracle Rdb7 Release Notes provide information on all the new features and technical changes included in release 7.0. The major new features and technical changes described in this manual include the following:

A new server on OpenVMS systems.
The new server has a system management command line interface to manage the server components from OpenVMS and Digital UNIX server systems, and an Oracle SQL/Services Manager graphical user interface (GUI) to manage server components from Windows clients.
The server can be managed either on line or off line. See Section 1.2 for more information.
See the Oracle SQL/Services Installation Guide for installation information. See Chapter 2 for information on configuring the server.
[Digital UNIX]
The following commands are new:
- ALTER DISPATCHER
- ALTER SERVICE
- DROP SERVER
- KILL EXECUTOR
- RESTART SERVER
- SET CONFIRM
- SHOW VERSION
- SHUTDOWN DISPATCHER
- SHUTDOWN SERVICE
- START DISPATCHER
- START SERVICE
<>
[Digital UNIX]
The following commands are obsolete:
- ALTER EXECUTORS FOR SERVICE
- CREATE EXECUTORS FOR SERVICE
- DROP EXECUTORS FOR SERVICE
- SHOW EXECUTORS FOR SERVICE
- SHOW PRIVILEGES FOR SERVICE
- SHUTDOWN EXECUTORS FOR SERVICE
- START MONITOR
<>
[Digital UNIX]
The following commands are changed:
- ALTER SERVER
  - New default values for: PROCESS_STARTUP_TIMEOUT and PROCESS_SHUTDOWN_TIMEOUT arguments.
  - Obsolete argument: SERVER_VERSION.
- CONNECT TO SERVER [USER <user-name> USING <password>]
  If you are using DECnet or TCP/IP with sufficient privileges to manage a server on the local node (OpenVMS or Digital UNIX systems), you do not need to enter a user name and password. Using DECnet, Oracle SQL/Services uses an implicit local proxy to connect to a server on the local node. Using TCP/IP, Oracle SQL/Services uses a trusted local user mechanism to connect to a server on the local node; the user must also have the SYSPRV privilege. The syntax of this command is changed to indicate this change.
  If you are connecting to a local server using the configuration file you currently have open, SQLSRV_MANAGE attempts to connect to any network port defined for the server.
- CREATE DISPATCHER
  New arguments: AUTOSTART, MAX_CLIENT_BUFFER_SIZE.
  Changed argument: CONNECTION_TIMEOUT renamed to IDLE_USER_TIMEOUT.
  Supports SQL*Net and NetWare (OpenVMS only) as transport options.
- CREATE SERVER
  Obsolete arguments: SERVER_VERSION, NODE, DEFAULT_SERVER
  The CREATE SERVER command now creates the configuration file.
- CREATE SERVICE
  New arguments: AUTOSTART, SQL_VERSION, PROCESS_INITIALIZATION, APPLICATION_TRANSACTION_USAGE, IDLE_USER_TIMEOUT, IDLE_EXECUTOR_TIMEOUT, MIN_EXECUTORS, MAX_EXECUTORS, CLIENTS_PER_EXECUTOR
  The following arguments are obsolete for the CREATE SERVICE command and are replaced with these new arguments:
  - Obsolete argument: AUTHORIZE UNKNOWN USERS AS <user-string>
  - Replaced by: DEFAULT_CONNECT_USERNAME <user-string>
  - Obsolete argument: IMPERSONATE {ON | OFF}
  - Replaced by: DATABASE_AUTHORIZATION {[SERVICE] OWNER | [CONNECT] USERNAME}
- DROP SERVICE: Now deletes the services' executors.
- GRANT USE ON SERVICE
  New keyword: PRIVILEGED_USER for the <grant-element> argument.
  New optional keyword: USER[S] grants access to use the service to the specified user name.
- REVOKE USE ON SERVICE
  New keyword: PRIVILEGED_USER for the <grant-element> argument.
  New optional keyword: USER[S] revokes user access to the specified service.
  If use of a service by a specific user name is revoked, that user will still be able to access the service if the user holds an identifier that has been granted use of the service. Likewise, if use of a service by a specific identifier is revoked, a user who holds that identifier will still be able to access the service if the user's name has been granted use of the service. <>
- SHOW CLIENTS
  New keywords: FULL, USERNAME, and PID.
  This command shows the location of executor log files, error files, and the eventual location of the dump file when one is created.
  By default, it displays one line per client.
- SHOW DISPATCHER, SHOW SERVER
  This command shows all new and changed arguments previously described as well as the location of log files, error files, and the eventual location of the dump file when one is created. It shows differences for values of attributes between the running server and its configuration file. This information displays at the end of the show output. This command shows the state of the object as well as its network ports.
- SHOW SERVICE
  New keywords: FULL and PRIVILEGED_USER.
  This command shows all new and changed arguments previously described and the user's USE descriptor privileges. This command shows the services' executor information and the differences for values of attributes between the running server and its configuration file. This information displays at the end of the show output.
  By default, the command displays one line per service.
- SHUTDOWN SERVICE: Now shuts down the service's executor processes.
- START SERVER
  New arguments:
  - AUTOSTART {ON | OFF}, determines if other server objects automatically start up after you issue a START SERVER command if each object's AUTOSTART attribute is also set to ON.
  - USER <user-name> USING <password>, provides an optional user name and password for connecting to a local server.
  - AUTOCONNECT {ON | OFF}, now connects to the server after it is started and tries each network port defined for the server in a round-robin fashion up to three times each to establish a management connection. The network port used for the management connection is the first one that is successful.
- START SERVICE: Now starts the services' executor processes.
<>
[Digital UNIX]
Values of some arguments of ALTER SERVER, ALTER DISPATCHER, and ALTER SERVICE commands can change dynamically when run in the indirect (SQLSRV_MANAGE) environment.
A change to a value for an ALTER SERVER, ALTER DISPATCHER, and ALTER SERVICE command argument that is dynamic takes effect immediately. Changes to arguments of commands that are not dynamic do not take effect until that object is restarted. The following commands and arguments are dynamic:
- ALTER DISPATCHER
  - IDLE_USER_TIMEOUT
- ALTER SERVER
  - PROCESS_STARTUP_TIMEOUT
  - PROCESS_SHUTDOWN_TIMEOUT
- ALTER SERVICE
  - DEFAULT_CONNECT_USERNAME
  - APPLICATION_TRANSACTION_USAGE
  - IDLE_USER_TIMEOUT
  - IDLE_EXECUTOR_TIMEOUT
  - MIN_EXECUTORS
  - MAX_EXECUTORS
  - CLIENTS_PER_EXECUTOR
<>
[Digital UNIX]
Order of arguments of management commands is no longer important.
Beginning with V7.0, the order of arguments of management commands is no longer important. If you enter a command using the command line interface that contains two or more arguments, the arguments no longer must appear in the order presented in the format description of that command. <>

Next | Contents

Library
Product

Chapter 1	Introduces the Oracle SQL/Services system.
Chapter 2	Describes how to manage an Oracle SQL/Services system.
Chapter 3	Describes how to maintain an Oracle SQL/Services system.
Chapter 4	Describes the Oracle SQL/Services system management commands.

. . .	Vertical ellipsis points in an example mean that information not directly related to the example has been omitted.
[ ]	In text, brackets enclose optional information from which you can choose to use or not.
$	The dollar sign represents the DIGITAL Command Language prompt in OpenVMS and the Bourne shell prompt in Digital UNIX.
>	The right angle bracket represents the :MS--DOS command prompt. This symbol indicates that the :MS--DOS command language interpreter is ready for input.
%	The percent sign represents the ULTRIX default user prompt.
boldface text	Boldface type in text indicates a term defined in the text.
monospaced boldface text	Monospaced boldface type text indicates user input.
e, f, t	Index entries in the printed manual may have a lowercase e, f, or t following the page number; the e, f, or t is a reference to the example, figure, or table, respectively, on that page.

Oracle Rdb7(tm)

Oracle SQL/Services(tm) Server Configuration Guide