Oracle9i Personal Edition Installation Guide
Release 1 (9.0.1.1.0) for Windows 98

Part Number A95905-01


Contents

Index

Go to previous page Go to next page


Glossary

automatic undo management mode

A mode of the database in which undo data is stored in a dedicated undo tablespace. Unlike in manual undo management mode, the only undo management that you must perform is the creation of the undo tablespace. All other undo management is performed automatically.

cluster

A cluster generally comprises two or more computers, or "nodes." Oracle Real Application Clusters software and a collection of hardware, known as a "cluster," unite the processing power of each component to become a single, robust computing environment. Oracle Real Application Clusters is a robust computing environment that harnesses the processing power of multiple, interconnected computers.

connect descriptor

A specially formatted description of the destination for a network connection. A connect descriptor contains destination service and network route information.

The destination service is indicated by using its service name for the Oracle9i Database or its Oracle system identifier (SID) for Oracle release 8.0, or version 7 databases. The network route provides, at a minimum, the location of the listener through use of a network address.

connect identifier

A name, net service name, or service name that resolves to a connect descriptor. Users initiate a connect request by passing a username and password along with a connect identifier in a connect string for the service to which they want to connect, for example:

SQL> CONNECT username/password@connect_identifier 
default domain

The network domain within which most client requests take place. It can be the domain where the client resides, or a domain from which the client often requests network services. The default domain is also the client configuration parameter that determines what domain to append to unqualified network name requests. A name request is unqualified if it does not have a "." character within it.

Directory Information Tree (DIT)

A hierarchical tree-like structure in a directory server of the Distinguished Names (DNs) of the entries.

directory naming context

A subtree that is of significance within a directory server. It is usually the top of some organizational subtree. Some directories only allow one such context that is fixed; others allow none to many to be configured by the directory administrator.

directory naming

A naming method that specifies a directory server to resolve a net service name into a connect descriptor. The net service name is stored centrally in a directory server.

directory server

An Lightweight Directory Access Protocol (LDAP)-compliant directory server. A directory can provide centralized storage and retrieval of database network components, user and corporate policies preferences, user authentication, and security information, replacing client-side and server-side localized files.

external procedures

A PL/SQL routine executing on an Oracle server can call an external procedure or function that is written in the C programming language and stored in a shared library. In order for the Oracle9i Database to connect to external procedures, the server must be configured with a net service name and the listener must be configured with protocol address and service information.

global database name

The full database name that uniquely distinguishes it from any other database in your network domain. For example:

sales.us.acme.com

where sales is the name you want to call your database and us.acme.com is the network domain in which the database is located.

Interprocess Communication (IPC)

A protocol used by client applications that resides on the same node as the listener to communicate with the database. IPC can provide a faster local connection than TCP/IP.

installation type

An installation type is a predefined component set that automatically selects which components to install. See "Oracle9i Products for Installation" for a list of installation types available with each top-level component.

listener

A process that resides on the server whose responsibility is to listen for incoming client connection requests and manage the traffic to the server.

When a client requests a network session with a database server, a listener receives the actual request. If the client information matches the listener information, then the listener grants a connection to the database server.

listener.ora file

A configuration file for the listener that identifies the:

The listener.ora file resides in ORACLE_BASE\ORACLE_HOME\network\admin.

An Oracle9i Database does not require identification of the database service because of service registration. However, static service configuration is required for an Oracle9i Database if you plan to use Oracle Enterprise Manager.

local naming

A naming method that resolves a net service name into a connect descriptor. This name is configured and stored in the tnsnames.ora file on each individual client.

manual undo management mode

A mode of the database in which undo blocks are stored in user-managed rollback segments. In automatic undo management mode, undo blocks are stored in system-managed, dedicated undo tablespaces.

naming method

A resolution method used by a client application to resolve a connect identifier to a network address when attempting to connect to a database service. Oracle Net Services supports the following naming methods:

net service name

A simple name for a service that resolves to a connect descriptor. Users initiate a connect request by passing a username and password along with a net service name in a connect string for the service to which they want to connect:

SQL> CONNECT username/password@net_service_name

Depending on your needs, net service names can be stored in a variety of places, including:

Oracle Context

The root of a directory subtree with a relative distinguished name of cn=OracleContext, under which all Oracle software information is kept. There may be one (or more than one) Oracle Context in a directory. An Oracle Context can be associated with a directory naming context.

The Oracle Context can contain the following Oracle entries:

Oracle home name

The name of the current Oracle home. Each Oracle home has a home name that distinguishes it from all other Oracle homes on your computer. During installation, you are prompted to enter an Oracle home name in the Name field of the Oracle Universal Installer's File Locations window.

Oracle home

The directory path in which to install Oracle components (for example, D:\oracle\ora90). You are prompted to enter an Oracle home in the Path field of the Oracle Universal Installer's File Locations window.

Oracle schema

A set of rules that determine what can be stored in an LDAP-compliant directory server. Oracle has its own schema that is applied to many types of Oracle entries, including Oracle Net Services entries. The Oracle schema for Oracle Net Services entries includes the attributes the entries may contain.

Oracle9i Database Online Documentation CD-ROM

The CD-ROM in your kit that include the Oracle9i Database Online Documentation. The Oracle9i Database Online Documentation CD-ROM are separate from the component CD-ROM.

The Oracle9i Database Online Documentation CD-ROM do not include this installation guide or Oracle9i Release Notes for Windows. These documents are only included on the first component CD-ROM.

Oracle9i Personal Edition

The complete database type.

protocol address

An address that identifies the network address of a network object.

When a connection is made, the client and the receiver of the request, such as the listener is configured with identical protocol addresses. The client uses this address to send the connection request to a particular network object location, and the recipient "listens" for requests on this address. It is important to install the same protocols for the client and the connection recipient, as well as configure the same addresses.

sqlnet.ora file

A configuration file for the client or server that specifies the:

The sqlnet.ora file resides in ORACLE_BASE\ORACLE_HOME\network\admin.

instance registration

A feature by which the PMON process (an instance background process) automatically registers information with a listener. Because this information is registered with the listener, the listener.ora file does not need to be configured with this static information.

Instance registration provides the listener with the following information:

This information allows the listener to determine how best to service a client connection request.

SID

The Oracle system identifier that uniquely distinguishes the database from any other database on your computer. The SID automatically defaults to the database name portion of the global database name (sales in the example sales.us.acme.com) until you reach eight characters or enter a period. You can accept or change the default value.


Note:

For Oracle Real Application Clusters, the SID you enter is automatically appended with an identifier. For example, if DB is entered, the first instance in the cluster is given a SID of DB1, and the second instance is given a SID of DB2.  


system identifier

See SID.

tnsnames.ora file

A configuration file that contains net service names mapped to connect descriptors. This file is used for the local naming method. The tnsnames.ora file resides in ORACLE_BASE\ORACLE_HOME\network\admin.

top-level components

When you run Oracle Universal Installer from the component CD-ROM, you are prompted in the Available Products window to install a top-level component. Each installation type contains a predefined set of individual components. See "Oracle9i Products for Installation" for a list of installation types available with each top-level component.

UNC

See Universal Naming Convention (UNC)

undo tablespace

A dedicated tablespace that stores only undo information when the database is run in automatic undo management mode. An undo tablespace contains one or more undo segments. The creation of any other types of segment (for example, tables, indexes) in undo tablespaces is not allowed.

In the automatic mode, each Oracle instance is assigned one and only one undo tablespace. Each undo tablespace is composed of a set of undo files. Undo blocks are grouped in extents. At any point in time, an extent is either allocated to (and used by) a transaction table, or is free.

Blocks in undo tablespaces are grouped into the following categories:

unqualified name

A net service name that does not contain a network domain.

Universal Naming Convention (UNC)

The Universal Naming Convention provides a means to access files on a network without mapping the network drive to a drive letter. UNC names are constructed in the following manner:

\\computer name\share name\filename


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

All Rights Reserved.


Contents

Index