D
Alpha OpenVMS Supplement to the Generic Documentation Set

This appendix is designed to be used as a supplement to the following documents:

Oracle8i Server Administrator's Guide

Oracle8i Application Developer's Guide

Oracle8i Server Concepts

Oracle8i Server Migration Guide

Oracle8i Server Utilities

This Appendix is not intended for use on its own. It is a supplement, and chiefly contains references to specific topics covered in your Oracle8i for Alpha OpenVMS documentation set.

The following topics are covered in this chapter:

• Server Guides

• Utilities Guide

Server Guides

This section lists and explains the server guides.

Archiver Process (ARCH)

Background processes are created automatically when an instance is started.

Archiving Mode

For more information about log archiving, see Chapter 6, "Backing Up and Archiving Your Database"

enabling auto	Valid option on Alpha OpenVMS
initial mode	The value of the LOG_ARCHIVE_START parameter is FALSE by default, which means the archiver is off until this value is changed by editing the INIT.ORA file.
specific steps	For more information about archiving redo files, see Chapter 6, "Backing Up and Archiving Your Database"

Audit Trail

creation of views	On Alpha OpenVMS, the Oracle8i database and its data dictionary are created with the audit trail views defined by the CATAUDIT.SQL script.
O/S audits	Operating system audits are not currently used with Oracle8i for Alpha OpenVMS.
directing records	Operating system audits are not currently used with Oracle8i for Alpha OpenVMS. .

Authentication through OS

A user can be authenticated in many different ways. For example, you can use the OS_AUTHENT_PREFIX initialization parameterto set a prefix that is concatenated to the beginning of the account name when a user logs in ORACLE without a user name or password.

You can also limit user control over a database through the ORA_DBA, ORA_<sid>_DBA, ORA_OPER, ORA_<sid>_OPER, and ORA_<sid>_<rolename>_<A/D> rights identifiers.

To control access by remote clients, use REMOTE_OS_AUTHENT and REMOTE_OS_ROLES. If REMOTE_OS_AUTHENT is set to TRUE, then remote clients can perform OPS$ logons. If REMOTE_OS_ROLES is set to TRUE, then remote clients can use OS ROLES and roles that are identified externally. For security reasons, the default for both parameters is FALSE.

Background Processes

For more information about background processes, see Chapter 1, "Introduction to Oracle8i on Alpha OpenVMS".

ARCH	For more information about archiving mode, see "Archiver Process (ARCH)" and "Archiving Mode."
DBWR	Oracle8i on Alpha OpenVMS does not support multiple DBWR processes.
names	The prefix ORA_<sid> is concatenated to the beginning of every background process. The <sid> is the value of thelogical name ORA_SID. For example, if the value of the logical name ORA_SID is MIS, then the DBWR process is identified as ORA_MIS_DBWR.
creating	Background processes are created automatically when an instance is started. For more information about setting up server processes, see Chapter 3, "Starting Up and Shutting Down Oracle8i".

Backups

A set of sample database backup scripts are included to aid database administrators in their duties. For more information, please see

ORA_DB_BACKUP_DEMO:README_BACKUP.DOC.

For more information about your backup options, see Chapter 6, "Backing Up and Archiving Your Database".

Client/Server Communication

For more information about communication links, see the SQL*Net documentation.

Clusters, Estimating Size

Use the following figures for calculating cluster size in the Oracle8i Enterprise Edition guides:

• Fixed header size = 86 bytes

• Variable transaction header = 24 (INITRANS value for the table)

• Row header = 4 bytes per row of a clustered table

Configuring Oracle8i

Alpha OpenVMS supports both multithreaded and dedicated server configurations.

Control Files

default name	The default names of the two control files are ORA_DB:ORA_CONTROL1.CON and ORA_DB:ORA_CONTROL2.CON. The logical names ORA_CONTROL1 and ORA_CONTROL2 point to the two control files, which are created at installation.
specifying names	You can make copies of the default control file using any legal Alpha OpenVMS file names, such as ORA_DB:ORA_CONTROL3.CON or DISK$MIS:[BACKUP]ORA_CNTRL3_MIS.CON.
minimum size	The minimum size is 2500 blocks (1250 Kb) For more information about the Alpha OpenVMS block size, see the Oracle8i for OpenVMS Installation Guide.
specification	Refer to the paragraph in this section on specifying names for information about filename specification.

Creating a Database During Installation

You must use ORACLEINS to request the creation of a new database.

Data Dictionary Creation

The CATALOG.SQL script is run for the default database during the installation process. If you create a database with the create database command, you must run CATALOG.SQL manually.

Data Files

The default value of the DATAFILE parameter of the CREATE DATABASE command is:

'ORA_DB:ORA_SYSTEM.DBS', SIZE 60M REUSE

The maximum size of each data file is 4095Mb.

Database

admin O/S account	On Alpha OpenVMS, the Oracle8i DBA must possess at least one of the ORA_DB, ORA_<sid>_DBA, ORA_OPER, or ORA_<sid>_OPER process rights identifiers, and have a UIC group number larger than the SYSGEN parameter MAXSYSGROUP.
background, server processes	For more information, see "Introduction to Oracle8i on Alpha OpenVMS," in Chapter 1 of this guide.
block size	The default value of the INIT.ORA parameter DB_BLOCK_SIZE is listed in the section on the initialization parameters below. The current value on your system can be found by entering the following command: SVRMGR> SHOW PARAMETERS
datafiles	The installation process creates one default database file, ORA_DB:ORA_SYSTEM.DBS. It is not necessary to create the database files before installation. For more information about adding datafiles, see Chapter 8, "Optimizing Oracle8i" and the section on database and tablespace files in the Oracle8i Server Concepts Manual.
limit on connections	No information is currently available.
database limits	For the equation given in the Oracle8i Enterprise EditionOracle8i Enterprise Edition guides, use the following figures: minimum database file size = 5 MB for the first file. database files= 1022 or value of DB_FILES in the INIT.ORA parameter file or value of MAXDATAFILES in CREATE DATABASE.
redo log files	Maximum number of files=255
connect string	Refer to the SQL*Net Release 8.1.7 for Alpha OpenVMS Configuration and User's Guide for information about database string specification.
SQL files to run at startup	Oracle8i for Alpha OpenVMS does not require you to run any SQL files at startup.

For specific information on the ADDRESS = portion of the connect descriptor, refer to the SQL*Net Release 8.1.7 for Alpha OpenVMS Configuration and User's Guide.

Files

locations	For more information about designating archive destination devices, see Chapter 6, "Backing Up and Archiving Your Database", of this guide.
names	ORA_DB:INIT.ORA is the name of the parameter file shared by all instances of a given database. ORA_DB:<setup_node>_<sid>_INIT.ORA is the name of the parameter file used by each individual instance. Refer to Chapter 5, "Managing the Database", in this guide for more information on file names.

Indexes

overhead of index blocks	The overhead for an index block consists of KCBH, KTBBH, KTBIT, KDXLE, or KDXBR. To find out the overhead on your machine, enter the following query:
SQL> SELECT * FROM v$type_size 2 WHERE type IN ('KCBH','KTBBH','KTBIT','KDXLE','KDXBR');
space required	No information is currently available for these calculations.

Installing Products

Refer to the instructions in the Oracle8i for Alpha OpenVMS Installation Guide for complete information about installation.

Instance

check identifier	A database instance is identified by the value of the logical name ORA_SID. Use the commands SET INSTANCE and SHOW INSTANCE to display the connect string used to connect to the remote instance.
initial default	The logical name ORA_SID sets the value of the initial local default instance. Use the SET INSTANCE command to change the value. You can return to the default value using the SET INSTANCE LOCAL command or by using SET INSTANCE without a qualifier.
startup	Use the STARTUP command.

Latches

No Alpha OpenVMS-specific information is currently available.

Listener Process

For information on TNS listener processes, refer to the SQL*Net for Alpha OpenVMS Configuration and User's Guide.

Log Files

The default value of the LOGFILE parameter of the CREATE DATABASE command is:

'ORA_DB:ORA_LOG1.RDO', 'ORA_DB:ORA_LOG2.RDO' SIZE 2000K REUSE

MAXLOGFILES, MAXLOGMEMBERS

When using ORACLEINS, the Alpha OpenVMS install procedure, the default value for MAXLOGFILES is 32 and the default value for

MAXLOGMEMBERS is 2. The maximum value of MAXLOGFILES is 255 and the maximum value of MAXLOGMEMBERS is 5.

Monitors

content of fields	There are no Alpha OpenVMS-specific elements in the contents of the monitor fields.
interrupt	No information is currently available on the interrupt mechanism.
running MONITOR.SQL	No Alpha OpenVMS-specific information is currently available.

Multiple Instances

Oracle8i for Alpha OpenVMS supports multiple instances.

Parameter Files

case sensitive	OpenVMS is not case sensitive.
creating and editing	The ORA_DB: INIT.ORA parameter file and ORA_DB:<setup_node>_<sid>_INIT.ORA file for each instance are created upon initial installation, and can be edited as text files on OpenVMS using a system editor.
format	Refer to the ORA_RDBMS:INIT.ORA file for the default INIT.ORA file.
global cache values	For more information about global cache values, see the Oracle8i for Alpha OpenVMS Installation Guide.
location	The INIT.ORA, and <setup_node>_ <sid>_INIT.ORA files are located in the ORA_DB directory of every database.
names	You can use any legal OpenVMS filename with the PFILE option. The INIT.ORA file referenced throughout this guide refers to any of the various INIT.ORA files such as ORA_DB:INIT.ORA, and ORA_DB:<setup_node>_<sid>_INIT.ORA.
O/S parameters	Refer to the following section in the guide on initialization parameters for more information.
tuning	Refer to Chapter 8, "Optimizing Oracle8i" and Chapter 9, "Trace Files" in this guide for more information on tuning.

Program Global Area (PGA)

No information is currently available on PGA parameters.

Protocol Adapters

For more information about SQL*Net Oracle Protocol Adapters, refer to the SQL*Net documentation.

Recovery

Refer to Chapter 6, "Backing Up and Archiving Your Database", in this guide for information about recovery procedures.

Redo Log Files

Refer to Chapter 6, "Backing Up and Archiving Your Database", in this guide for information about redo log files.

archived file name format	Refer to the chapter on backing up and recovering your database in this guide for information on the LOG_ARCHIVE_FORMAT and LOG_ARCHIVE_DEST parameters.
destination search path	This is the value of the ORACLE_PATH variable.
default location	The redo log files are located by default in ORA_DB.
default size	The default value of the LOG_SIZE variable is 2000 KB (4000 Alpha OpenVMS blocks).
limited by LOG_FILES	The default value of LOG_FILES is 255, which is also its maximum value.

Resource Costs

No information is currently available on setting resource costs.

Roles

For the role specification syntax given in the Oracle8i Enterprise Server Guides, <ID> refer to your SID (defined by the logical name ORA_SID).

Refer also to the sections in this appendix on authentication through OS and the database administration O/S account for information on how to limit roles via the operating system.

For more information about groups, see the Oracle8i for Alpha OpenVMS Installation Guide.

OSOPER and OSDBA

On Alpha OpenVMS, the OSOPER role is controlled by the ORA_OPER and ORA_<sid>_OPER process rights identifiers. The OSDBA role is limited to users with the ORA_DBA and ORA_<sid>_DBA rights identifiers. As with ORA_DBA, if an ORA_<sid>_OPER rights identifier exists for the OSOPER role on a given database, then users with the ORA_OPER process rights identifier have insufficient privileges to perform the duties authorized by the OSOPER role. For more information about the ORA_DBA limitation, see the Oracle8i for Alpha OpenVMS Installation Guide

using the O/S for security

OpenVMS verifies that you have the necessary rights identifiers for your role when you log in.

Script File Names

Script file names are not case dependent in OpenVMS.

Segments Extents

No Alpha OpenVMS-specific information is currently available on extents.

SQL Scripts, Names, and Locations

CATAUDIT.SQL	ORA_RDBMS_ADMIN
UTLCHAIN.SQL	ORA_RDBMS_ADMIN
DIT scripts	These scripts are not provided for Alpha OpenVMS.
UTLEXCPT.SQL	ORA_RDBMS_ADMIN
UTLLOCKT.SQL	ORA_RDBMS_ADMIN
to run initially	If you create your database with the CREATE DATABASE command, you must run CATALOG.SQL, CATEXP.SQL, and ULVIEW.SQL after the CREATE DATABASE command completes. If you are also using the procedural option, you must run STANDARD.SQL, DBMSSNAP.SQL, DBMSSNAP.SQL, DBMSUTIL.SQL, DIO.SQL, and DBMSPIPE.SQL. All of these scripts are run for you automatically by the database creation and upgrade scripts provided in the Alpha OpenVMS Oracle8i installation scripts.
STANDARD & DBMSSTDX.SQL	ORA_RDBMS_ADMIN
DBSMSNAP.SQL	ORA_RDBMS_ADMIN

SQL*Net and Networking

For a thorough explanation of SQL*Net and networking, refer to the SQL*Net manuals.

choosing	For information on networking in your environment, refer to the SQL*Net manuals.
integrated into RDBMS	The RDBMS listener process has been merged with the SQL*Net V8 listener process. You access the SQL*Net V8 listener process when you use the Multi-Threaded Server configuration of Oracle8i.
installing	Refer to the Oracle8i for Alpha OpenVMS Installation Guide for more information on installing SQL*Net.
O/S comm. software	Refer to the Oracle8i for Alpha OpenVMS Installation Guide for all software and hardware requirements.
specifying links	Refer to the Oracle8i for Alpha OpenVMS Installation Guide and the SQL*Net Release 8.1.7 for Alpha OpenVMS Configuration and User's Guide for host string specifications.

System Global Area (SGA)

The SGA is described in Chapter 1, "Introduction to Oracle8i on Alpha OpenVMS", in this guide.

Table Size, Estimating

Clustered	No Alpha OpenVMS-specific information is currently available.
non-clustered	No Alpha OpenVMS-specific information is currently available.

Tuning Information

Refer to Chapter 8, "Optimizing Oracle8i", in this guide.

Trace Files

Refer to Chapter 9, "Trace Files", in this guide.

Transaction Entries, Space Required

No Alpha OpenVMS-specific information is currently available.

Initialization Parameters

Parameter Name	DefaultValue
BACKGROUND_DUMP_DEST	ORA_DUMP
COMMIT_POINT_STRENGTH	1
DB_BLOCK_CHECKSUM	FALSE
DB_BLOCK_SIZE	2048
DB_FILES	80
DB_FILE_MULTIBLOCK_READ_COUNT	8 (Range of 1-65536/DB_BLOCK_SIZE)
DB_FILE_SIMULTANEOUS_WRITES	4
DISTRIBUTED_TRANSACTIONS	16
INSTANCE_NUMBER	0
LOG_ARCHIVE_BUFFER_SIZE	127
LOG_ARCHIVE_BUFFERS	4
LOG_ARCHIVE_DEST	ORA_ARCHIVE:
LOG_ARCHIVE_FORMAT	ARCH%T_%S.ARC
LOG_BUFFER	8192(4xDB_BLOCK_SIZE)
LOG_CHECKPOINT_INTERVAL	10000
LOG_SMALL_ENTRY_MAX_SIZE	80
OS_AUTHENT_PREFIX	ops$
PROCESSES	50
SHARED_POOL_SIZE	5000000 bytes
SORT_AREA_SIZE	65536
SORT_READ_FAC	20
SORT_SPACEMAP_SIZE	512
TEMPORARY_TABLE_LOCKS	60
TRANSACTIONS_PER_ROLLBACK_SEGMENT	11
USER_DUMP_DEST	ORA_DUMP

Utilities Guide

This section lists and explains information about the utilities guide.

Creating or Initializing a Database

No information is currently available.

Default Buffer Size

No information is currently available.

Default RECORDLENGTH

No information is currently available.

Error Messages

Refer to Appendix B, "Messages and Codes" of this guide for a complete list of messages for Oracle8i on Alpha OpenVMS.

Installing Export Views

Export views are automatically installed by the Oracle8i installation scripts. If they must defined at another time, run the script called

ORA_RDBMS_ADMIN:CATEXP.SQL.

Redirecting I/O

No information is currently available.

Backslash Escape

No information is currently available.

Sizes of Data

No information is currently available.

Size of SMALLINT Data Type

No information is currently available.

Length Subfield in VARCHAR Data

No information is currently available.

Length Subfield in VARGRAPHIC Data

No information is currently available.

File Processing Options

Current options available for Alpha OpenVMS are "FIXED=<n>", "STREAM=<n>", and"VAR" where n represents the number of bytes in the resulting file. You must put one of these options in double quotes (") on the command line.

For example, to declare a file in SQL*Loader named MYDATA.DAT as a file containing 80-byte records, use the following clause:

INFILE MYDATA.DAT "FIXED=80"

For example, to declare a file in SQL*Loader named MYDATA.DAT as a file containing variable length records, use the following clause:

INFILE MYDATA.DAT "VAR"

Examples of records in MYDATA.DAT that include first name, last name, and hire date are:

0025JOHN, SMITH, 09-JUNE-1981
0032ROBERT, MILLER, 20-FEBRUARY-1976

Note that in Alpha OpenVMS you cannot specify the number of I/O buffers to be used in an operation