Release 2 (8.1.6) for Windows NT
A73010-01
 Library |
 Product |
 Contents |
 Index |
| Oracle8i Installation Guide Release 2 (8.1.6) for Windows NT A73010-01 |
|
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 NT, your domain is your administrative context.
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.
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> CONNECTUSERNAME/PASSWORD@CONNECT_IDENTIFIER
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 requests network services often. The default domain is also the client configuration parameter that determines what domain should be appended to unqualified network name requests. A name request is unqualified if it does not have a "." character within it.
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 which is fixed; others allow none to many to be configured by the directory administrator.
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.
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.
A PL/SQL procedure 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 Oracle8i 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.
IPC
A protocol used by client applications that reside on the same node as the listener to communicate with the database.
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.
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.
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.
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.
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:
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> CONNECTUSERNAME/PASSWORD@NET_SERVICE_NAME
Depending on your needs, net service names can be stored in a variety of places, including:
TNSNAMES.ORA, on each client
Windows NT login credentials can be used to authenticate users connecting to an Oracle8i database. The benefits of Windows NT native authentication include:
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 username with Oracle usernames 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.
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:
The CD-ROM in your kit that includes the Oracle8i Online Documentation. The Oracle8i Online Documentation CD-ROM is separate from the product CD-ROM.
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.
The CD-ROM in your kit that includes the Oracle8i server, client, and management infrastructure software. The product CD-ROM is separate from the Oracle8i Online Documentation CD-ROM.
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.
A set of database tables used as a back-end store for the middle-tier Oracle Management Server(s). A repository can be located in any Oracle database. A repository is shared by administrators and stores the state and history of registered events and scheduled jobs. A repository also contains accounts of all administrators, including information such as administrator passwords and privileges, and the current view of the network including all system data, application data, and information about the state of managed nodes.
A configuration file for the client or server that specifies the:
The SQLNET.ORA file resides in ORACLE_BASE\ORACLE_HOME\NETWORK\ADMIN.
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.
Service registration provides the listener with the following information:
This allows the listener to direct a client's request appropriately.
This allows the listener to determine which dispatcher can best handle a client connection's request. If all dispatchers are blocked, the listener can spawn a dedicated server for the connection.
This information allows the listener to determine how best a client connection request should be serviced.
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.
A net service name that does not contain a network domain.
|
 Copyright © 2000 Oracle Corporation. All Rights Reserved. |
|