Oracle8i Client Installation Guide
Release 3 (8.1.7) for Windows

Part Number A85303-01

Top

Contents

Index

Go to previous page Go to next page


Glossary

administrative context

A directory entry under which an Oracle Context resides. An administrative context can be a directory naming context. During directory access configuration, clients are configured with an administrative context in the directory configuration file (LDAP.ORA). The administrative context specifies the location of the Oracle Context in the directory whose entries a client expects to access. On Windows 2000, your domain is your administrative context.

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 Oracle8i 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 user name 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 which 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 method

A naming method that resolves a database service or net service name to a connect descriptor, stored in a central directory server.

A directory provides central administration of database services and net service names, reducing the work effort associated with adding or relocating services. Although net service names can be configured to alias a service, the directory can refer to a database service directly without using a net service name. To further aid with configuration ease, the database service is automatically added as an entry to the directory during installation.

directory server

An LDAP-compliant directory server that is accessed with the Lightweight Directory Access Protocol (LDAP). 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.

IPC

A protocol used by client applications that reside on the same node as the listener to communicate with the database.

installation types

When you run Oracle Universal Installer from the component CD-ROM, you are prompted to install an installation type. Each installation type contains a series of individual components. The following installation types are available for installation:

LDAP.ORA file

A file created by the Net8 Configuration Assistant that contains the following directory access information:

The LDAP.ORA file resides in ORACLE_BASE\ORACLE_HOME\NETWORK\ADMIN.

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.

Every time a client requests a network session with a server, a listener receives the actual request. If the client's information matches the listener's information, the listener grants a connection to the 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 Oracle8i database does not require identification of the database service because of service registration. However, static service configuration is required for an Oracle8i database if you plan to use Oracle Enterprise Manager.

local naming method

A naming method that resolves a net service name, stored in a client's TNSNAMES.ORA file, to the network address and identification of the service. Local naming is most appropriate for simple distributed networks with a small number of services that change infrequently.

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. Net8 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 user name 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:

operating system authenticated connections

Windows NT login credentials can be used to authenticate users connecting to an Oracle8i database. The benefits of Windows NT native authentication include:

OPS$

The initialization file parameter OS_AUTHENT_PREFIX enables users to specify a prefix that Oracle uses to authenticate users attempting to connect to the database. Oracle concatenates the value of this parameter to the beginning of the user's operating system account name and password. When a connection request is attempted, Oracle compares the prefixed user name with Oracle user names in the database.

The default value of this parameter is "" (a null string), thereby eliminating the addition of any prefix to operating system account names. In earlier releases, OPS$ (short for operating system specific) was the default setting.

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\Ora81). 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 Net8 entries. The Oracle schema for Net8 entries includes the attributes the entries may contain.

Oracle8i Client Online Documentation CD-ROM

The CD-ROM in your kit that includes the Oracle8i Client Online Documentation. The Oracle8i Client Online Documentation CD-ROM is separate from the component CD-ROM. The Oracle8i Client Online Documentation CD-ROM does not include this installation guide or the Oracle8i Release Notes for Windows NT. Those documents are only included on the component CD-ROM.

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, Oracle Names Server, or Oracle Connection Manager, are 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.

A protocol used by client applications that reside on the same node as the listener to communicate with the database.

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.

service registration

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

Service registration provides the listener with the following information:

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.

unqualified name

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


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

All Rights Reserved.

Top

Contents

Index