Skip Headers

Oracle8i Server Installation and Database Administration Guide
Release 3 (8.1.7) for Fujitsu Siemens Computers BS2000/OSD

Part Number A95466-01
Go To Table Of Contents
Contents
Go To Index
Index

Go to previous page Go to next page

5
Administering the Oracle Server

This chapter describes how to use the Oracle Server Manager utility to administer Oracle8i Release 3 Server for BS2000/OSD.

Common administration tasks are described in the following sections:

Using the Oracle Server Manager Utility

Oracle Server Manager Modes of Operation

The Oracle Server Manager Utility on Oracle8i Release 3 for BS2000/OSD is available in line mode only. This is the line-by-line oriented approach to entering commands.

Invoking the Oracle Server Manager Utility

To start the Oracle Server Manager, enter the following:

/START-PROGRAM $ORACL817.SVRMGRL
[ENTER]

You can now enter your commands.

Calling the Oracle Server Manager from a Procedure

Set Task Switch 1 to on (/SETSW ON=1). This forces the Oracle Server Manager to read in data from the procedure, rather than prompt you at the terminal.


Note:

If you issue commands that affect control of the Oracle Server software currently being handled, BS2000/OSD may not return control to the Oracle Server Manager Utility upon completion.


Issuing BS2000 Commands from the Oracle Server Manager

The Oracle Server Manager HOST command, or ! command, allows you to enter a BS2000 command, while you are logged on to Oracle Server Manager.

Keep the following points in mind when using the HOST command:

Startup and Background Tasks

Each time you execute the Server Manager utility to start up an Oracle Server database, you also start up the background tasks. When you execute the Oracle Server Manager to shutdown an Oracle Server system, the background jobs are terminated.

Startup and Parameter Files

Oracle Server Manager uses two parameter files when starting and stopping the database:

  1. The ORAENV file (the environment definition file) which contains BS2000-specific information. In the ORAENV file you identify the database to be started up, or shut down, and you can set configuration variables which adapt the Oracle Server to your local operating system and application environment.

  2. The initialization file (INIT.ORA) which exists in all Oracle Server implementations and contains database-specific parameters.

The Environment Definition File ORAENV

The ORAENV file is identified by sid.P.ORAENV, where sid is the database identifier. The same ORAENV file must be used by Server Manager and by all background jobs. This is normally ensured by the installation procedures which create the basic ORAENV file. See Appendix B, "ORAENV Variables" for details of required and optional ORAENV variables.

The Initialization File INIT.ORA

Server Manager requires the INIT.ORA parameter file which contains a list of specifications for the Oracle Server system. These parameters are used to set up filename assignments and to determine the number of entries stored in the System Global Area for each Oracle Server system resource. The SGA resides in shared memory when your Oracle Server system is running and thus allows fast access to any information it contains. See the Oracle8i Administrator's Guide for full descriptions of these parameters.


Note:

We recommend that you always use a question mark (?) to denote the database system-id in initialization files. The "@" character, which is used on other platforms, is the equivalent but is not available on all keyboards and may cause problems in NLS character-set translations.


Using the Correct Initialization File

A default initialization file, called $ORACL817.DEMO.DBS.INIT.ORA, is distributed with your Oracle Server database. During the Database Installation procedure, this file is copied to your $DBA account and renamed, sid.DBS.INIT.ORA, where sid is the 1 to 4 character database ID you specified at the beginning of the Database Installation procedure.

Whenever you use the Oracle Server Manager utility, it looks by default for an initialization file named sid.DBS.INIT.ORA. Oracle Server Manager determines the value of sid by retrieving the ORASID environment variable defined in the ORAENV file for the database. If you wish to use some other initialization file, use the argument PFILE.

For example, to bring up a previously created database using an initialization file called TEST.INIT.ORA, enter the following:

/START-PROGRAM $ORACL817.SVRMGRL

* (type the ENTER key)

At the Server Manager prompt, enter:

SVRMGR> CONNECT INTERNAL
SVRMGR> STARTUP PFILE=TEST.INIT.ORA

Starting a Database Instance from a Remote Machine

In Oracle8i Release 3 Server for Fujitsu Siemens BS2000/OSD you use Server Manager to start up and administer a database instance form a remote machine. You could run Server Manager on a PC, UNIX or another BS2000/OSD system

The Administrator Authentication and startup procedures follow those described in the Oracle8i Administrator's Guide with the following exceptions:

An alternative to using Server Manager is Oracle Enterprise Manager.

Security Considerations

Oracle Server security considerations depend on whether you are using the single-task or the two-task operating environment. The two-task operating environment provides maximum security for the Oracle Server files and the data structures in the SGA. This is because the user task has no direct access to these objects.

The single-task operating environment, on the other hand, requires more attention to security. This is because the user tasks have direct access to:

Checking the Integrity of the Physical Data Structure

To check the data-structure integrity of off-line databases, use the DB_VERIFY external command-line utility. To start DB_VERIFY enter the following command:

/START-PROGRAM $ORACL817.DBV

You can now enter your command, for example:

file=ora7.dbs.database1.dbf blocksize=4096 feedback=100

For more information about the DB_VERIFY program, see the Oracle8i Administrator's Guide and the Oracle8i Utilities book.

Customizing Your Oracle Server System

You can customize your Oracle Server system. The following topics are described in this section:

These procedures are optional and can be performed at any time after the database has been installed. You can perform some or all of them, or decide not to do any of them at all.


Note:

The procedures in the following sections must be performed under the $DBA userid.


Creating a Global SQL*Plus Profile

The DBA can create a global SQL*Plus profile file, GLOGIN.SQL, which will be executed when a user logs in to SQL*Plus. This file is executed before the user's local LOGIN.SQL and is provided to allow sites to set up several defaults useful to all users. You can place any SQL and SQL*Plus statement in GLOGIN.SQL.

The GLOGIN.SQL file must be named as follows:

sid.DBS.GLOGIN.SQL

Adding Database Files

You can add additional files to the existing SYSTEM tablespace, or you can create new tablespaces, according to your needs. You do this from either Oracle Server Manager or SQL*Plus. See your Oracle8i SQL Reference manual for information on the CREATE TABLESPACE, ALTER TABLESPACE and DROP TABLESPACE commands.

Setting Access Rights

You can set up your database system so that users access the Oracle Server in single-task mode under one BS2000 userid (the DBA's userid) or through several userids.

Accessing the Oracle Server in Single-Task under the DBA Userid

Initially, the database is set up by INSTALL.P.DBA so that only tasks executing under the DBA userid can access the database using the single-task driver. All database files are installed as non-sharable.

The Database Administrator can start up or shut down the database only under the DBA userid.

File access does not need any special consideration, as the Database Administrator is the owner of the database files.

Accessing the Oracle Server Through Several Different Userids

Tasks executing under a BS2000 userid different from the DBA userid can access the database as follows:


Go to previous page Go to next page
Oracle
Copyright © 2001 Oracle Corporation.

All Rights Reserved.
Go To Table Of Contents
Contents
Go To Index
Index