GLOSSARY
- address A unique network location used to identify a network object such as a database service, client, Interchange, or Names Server. TNS addresses have a specific format. Addresses must be unique. See TNS address and well known address.
- administrative region An organizational region is an organizational entity for administering SQL*Net network components. Each administrative region includes:
- one or more Oracle Names Servers
- zero or more Interchanges
- network object definitions
- alias An alternate name for an existing network object. Once created, alias resolution is the same as resolving the initial object. For example, if an alias named PAYCHECK.WORLD is created for the database service PAYROLL.WORLD, the following commands are equivalent:
sqlplus scott/tiger@PAYCHECK.WORLD
sqlplus scott/tiger@PAYROLL.WORLD
- authoritative response A Names Server response from the source, or owner, of the data requested. The source is any Names Server in the same administrative region as the requested name.
- backbone data See network data.
- cache The in-memory database within a Names Server where all data is stored. The cache has three basic sections: the system cache, the authoritative data cache, and the non-authoritative data cache, which represent different types of data with different refresh frequencies.
- central administration A SQL*Net network in which all data is administered in one administrative region.
- client profile The properties of a client, often shared by many clients. Includes the protocols used, preferred Interchanges, preferred Names Servers. Also called "client type".
- community A group of network clients and servers using TNS-based software that can communicate using the same industry-standard protocol.
- configuration files Files that are used to identify and characterize the components of a network. Configuration is largely a process of naming network components and identifying relationships among those components.
- connect descriptor A specially formatted description of the destination for a network connection. Connect descriptors are constructed using a set of keywords and values. They are mapped to service names to provide more convenient reference.
- database service name See service name.
- database link A network object stored in the local database or in the network definition that identifies a remote database, a communication path to that database, and optionally, a username and password. Once defined, the database link is used to access the remote database. Also called DB link.
- A public or private database link from one database to another is created on the local database by a DBA or user.
- A global database link is created automatically from each database to every other database in a network with Oracle Names. Global database links are stored in the network definition.
- default domain The domain within which most client requests take place. It could be the domain where the client resides, or it could be a domain from which the client requests network services often. A client configuration parameter 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.
- delegated administration A SQL*Net network where network management is delegated to one or more administrative regions below the root administrative region. Each region is administered through an installation of the Network Manager. Also referred to as "distributed administration" and "decentralized administration".
- delegated administrative region A region that is hierarchically below the root administrative region. Any region other than the root administrative region.
- decentralized administration See delegated administration.
- distributed administration See delegated administration.
- domain A grouping of network objects, such as databases, that simplifies the naming of network services. Within a domain, all the names must be unique.
- domestic domains The set of domains that are managed within a given administrative region. Domains are only domestic relative to a region; they are never domestic in any absolute sense. Also referred to as local domains.
- dynamic discovery The process whereby well-known naming service addresses are hardcoded into both the Oracle Names Server and its clients. Oracle Names Servers are available at these well known addresses, so that clients do not need to be told, by way of configuration files, where to find the server. All listeners and databases register themselves automatically with an Oracle Names Server at a specific well-known name and address.
- flat naming model An Oracle Names infrastructure in which there is only one domain. All names must be unique within that domain.
- foreign domains The set of domains not managed within a given administrative region. Domains are only foreign relative to a region; they are not foreign in any absolute sense. A network administrator typically defines foreign domains relative to a particular region in the Network Manager to optimize Names Server caching performance.
- global database link A database link created automatically by the Network Manager for use with Oracle Names that links each database in a network to all other databases. This enables any user of any database in the network to specify a global object name in a SQL statement or object definition. (The global object name for the DBlink must be the same as the database service name.)
- global database name A unique name that identifies a database in a network. It consists of a database name and its network domain name. For example, HR.US.ORACLE.COM is comprised of a database name component HR and a network domain component US.ORACLE.COM.
- hierarchical naming model An Oracle Names infrastructure in which names are divided into multiple hierarchically-related domains. You can use the hierarchical naming model with either central or delegated administration.
- logging A feature in which client or server errors, service activity, and statistics are written to a log file. See also tracing.
- MultiProtocol Interchange An Oracle network product that allows applications in TNS networks to communicate across different protocols. For example, a TCP/IP client could connect through an Interchange to an Oracle7 server running only DECnet.
- naming model The set and structure of domains within which names can be allocated.
- In a flat naming model, there is a single domain.
- In a hierarchical naming model, the highest level is the root domain, and all other domains are hierarchically related.
- network administrator The person who performs network management tasks such as installing, configuring, and testing network components. The administrator typically maintains the configuration files, TNS connect descriptors and service names, aliases, and public and global database links.
- network data Also called backbone data. Includes all communities and MultiProtocol Interchanges in the entire network, and all Names Servers in the root administrative region. Because backbone data is common to all administrative regions, all delegated administrative regions must have an identical copy of the backbone data. Backbone data is entered identically into each installation of the Network Manager.
- network definition The network configuration created by the Network Manager fully describes one region. When you enter and save information in the Network Manager, it creates a network definition in an operating system file or a database. It generates configuration files from the network definition, and uses it as a data source for Oracle Names.
- Network Manager The graphical tool for configuring and maintaining services in a SQL*Net network, including SQL*Net, MultiProtocol Interchange, and Oracle Names. Each administrative region runs a separate copy of the Oracle Network Manager.
- network objects The types of network names stored in an Oracle Names Server. These includes database service names, global database links, and aliases.
- non-authoritative data If a Names Server returns a name from its foreign cache without asking the authoritative Names Server, this name is termed "non-authoritative". The name is termed "authoritative" if the data source was asked.
- ORACLE_HOME An alternate name for the top directory in the Oracle directory hierarchy on some directory-based operating systems.
- Oracle Names A name resolution system for Oracle7 and SQL*Net networks. Oracle Names includes:
- one or more Oracle Names Servers
- one or more Oracle Network Manager tool installations
- Oracle Names infrastructure A set of initial decisions and policies that govern how names are allocated, and how Oracle Names operates. The infrastructure defines how users and administrators interact with the Oracle Names system.
- Oracle System Identifier (SID) A unique name for an Oracle database instance. To switch between Oracle databases, users must specify the desired SID. The SID is included in the CONNECT DATA parts of the connect descriptors in a TNSNAMES.ORA file, and in the definition of the network listener in the LISTENER.ORA file.
- Oracle Names Server (Names Server) The name resolution software for efficiently answering name requests.
- password A string (word or phrase) used for data security and known only to its owner. Passwords are entered in conjunction with an operating system login ID, Oracle username, or account name, in order to connect to an operating system or software application (such as the Oracle database). Whereas the username or ID is public, the secret password ensures that only the owner of the username can use that name, or access that data.
- preferred Names Server The Names Server(s) preferred by a client for names resolution; usually the Names Server that is physically closest to the client, or available over the least expensive network link.
- private database link A DBlink created by one user for his or her exclusive use. Also see public database link, database link, or global database link.
- public database link A database link created by a DBA on a local database which is accessible to all users on that database. Also see database link and global database link.
- root domain The highest level domain in a hierarchical naming model.
- root administrative region The highest level administrative region in a distributed installation. The root administrative region contains the root domain.
- service name A name for a TNS service
that is easy to use and remember. End users need only know the appropriate service name to make a TNS connection. Each connect descriptor is assigned a service name in the network definition. The service name for a database link must be the same as the global database name.
- service replication A process that fully replicates a directory system on the network. New services need to register with only one Names Server. The service replication process automatically distributes the new registration to to all other active Names Servers on the network.
- SQL*Net An Oracle product that works with the Oracle Server and enables two or more computers that run the Oracle RDBMS or Oracle tools such as SQL*Forms to exchange data through a network. SQL*Net supports distributed processing and distributed database capability. SQL*Net runs over and interconnects many communications protocols.
- system or topology data Data used by the Names Server to control regular functioning or communicate with other Names Servers. Includes communities, Interchanges, root region's Names Servers, and any delegated regions' Names Servers.
- TNS A foundation technology, built into SQL*Net V2.x, the MultiProtocol Interchange, and Oracle Names, that works with any standard network transport protocol. Also called Transparent Network Substrate.
- TNS address An address of a client or network service on a TNS community, which identifies the community to which it belongs, the protocol used by that community, and some protocol-specific values. One TNS client or network service may have multiple TNS addresses if it resides in multiple communities.
- TNS communities A group of Oracle applications running on computers that communicate using the same network protocol.
- TNS network One or multiple TNS communities connected by MultiProtocol Interchanges. All members of a TNS network can communicate regardless of the protocol they run.
- tracing A facility that writes detailed information about an operation to an output file. The trace facility produces a detailed sequence of statements that describe the events of an operation as they are executed. Administrators use the trace facility for diagnosing an abnormal condition; it is not normally turned on.
- username The name by which a user is known to the Oracle Server and to other users. Every username is associated with a password, and both must be entered to connect to an Oracle database.
- well-known address In Dynamic Discovery networks, these are addresses for one or more Names Servers which are hardcoded into both the Oracle Names Server and its clients. Oracle Names Servers then become available at these well known addresses, so that clients do not need to be told, by way of configuration files, where to find the server.
