4
Understanding Release 8.1 Installation and Net8 Products

Database Instance Registration  

Database instances register themselves with the listener when started. Prior to this release, information about the instance had to be manually configured in the LISTENER.ORA file.

Instance registration is comprised of the following:

• service registration, which provides the listener with instance information, such as database service names and instance names.

• MTS dispatcher registration, which provides dispatcher information to the listener

Database instance registration also permits automatic connect-time failover of a client connect request to a different listener if an instance is down.  

"Database Instance Registration to Listeners"  

Connection Load Balancing  

Instance registration enables connection load balancing. Connection load balancing balances the number of active connections among various instances and dispatchers for the same service. This enables listeners to make their routing decisions based on how many connections each dispatcher has and on how loaded the nodes that the instances run.  

"Connection Load Balancing"  

Service Naming  

Service naming can include multiple services provided by a single database and services that span multiple instances.

Up to this release, the client was configured with the Oracle System Identifier (SID) of a database instance. This SID was then passed to the listener. The listener would then verify this information and permit or deny a connection. The SID was also used internally by the database as pointer to the System Global Area (SGA).

While a SID identified a database instance, it did not identify a database. This limitation caused a database to have no more than one service associated with it.

Because a database can serve multiple services, SID has been replaced with service naming. Service naming allows clients to access:

• a service as a whole through the service name

• an instance of a database (the way SID did) through the instance name

To support services that include multiple instances, use the following new parameters in connect descriptors:

• SERVICE_NAME

• INSTANCE_NAME

• "Connect Operations"

• "Net8 Release 8.1 Configuration File Changes"

• "Setting Service Names and Instance Names"

net_service_name replaces service_name  

In previous releases, an alias for a connect descriptor (listener address and service information) was called a service_name. For example:

service_name=  
(description=  
  (address= (protocol_address_information)) 
  (connect_data=  
     (sid=sid)  
  )  
) 

End users were instructed to connect to a service with it. For example:

sql> CONNECT username/password@service_name

Because service name now refers to a service in the connect descriptor, service_name has been replaced with net_service_name for the connect descriptor and in the connect string. A net_service_name mapped to a connect descriptor looks like:

net_service_name=  
(description=  
  (address=(protocol specific address data)) 
  (connect_data=  
     (service_name=service_name)  
  )  
) 

An end user identifies a service with net_service_name in a connect string:

sql> connect username/password@net_service_name

Chapter 6, "Configuring Naming Methods and the Listener"  

DB_DOMAIN  

DB_DOMAIN in the initialization file (INITSID.ORA) no longer has a default setting of .WORLD. The new setting is NULL. Therefore, service names do not need to include the domain, if the default setting is used. In prior releases of Oracle, the default setting was .WORLD.

If DB_DOMAIN is set to NULL, the service name does not need to be domain-qualified.

If the DB_DOMAIN is not set to NULL, ensure the service name you enter includes the domain. For example, if an Oracle8i database has a service name of SALES and a domain of COM, you specify a service name of SALES.COM to identify the service.  

"Setting Service Names and Instance Names"

Java Option Support  

Prior to this release, Net8 only supported connections that used the Two-Task Common (TTC) presentation layer and Transparent Network Substrate (TNS) Network session (NS) layer to establish client connections.

The Java option allows customers to program the database server using traditional database stored procedures, Enterprise JavaBeans and CORBA Servers. To support clients accessing Enterprise JavaBeans and CORBA Servers in the database, the presentation layer and session layer support have been expanded.  

"Configuring Java Option Connections"  

Net8 Configuration Assistant  

The Net8 Configuration Assistant is post-installation tool that performs basic configuration. After installation, it automatically configures default configuration files.

In addition, the Net8 Configuration Assistant may be run in stand-alone mode to configure various elements of configuration, including the:

• listener

• naming methods

• net service names

• LDAP directory service.

"Net8 Installation and Net8 Products"  

RADIUS (Remote Authentication Dial-In User Service) authentication method  

RADIUS is a lightweight, open protocol for user authentication, authorization, and accounting between a network client and an authentication server. The RADIUS authentication method enables authentication with RADIUS-compliant devices such as token cards. In addition, RADIUS supports challenge-response and accounting.  

Oracle Advanced Security Administrator's Guide  

TCP/IP with SSL Protocol  

The TCP/IP with SSL protocol enables client/server conversation over a network using TCP/IP and the Secure Sockets Layer (SSL).

SSL stores authentication data, such as certificates and private keys, in an Oracle Wallet. When the client initiates a Net8 connection to the server, SSL performs a handshake between the two using the private key and certificate. During the handshake the following processes occur:

• The client and server negotiate a cipher suite, a set of authentication, encryption, and data integrity types, to apply to the messages they exchange.

• Depending on its configuration, the server may then send its own certificate to the client in a message encrypted with the client's public key. The server may also send a request for the client's certificate in the same message. The client decrypts this message by using its own private key, then verifies that the server's certificate bears the certificate authority's signature.

• If required, the client may send the user's certificate to the Oracle server. The certificate ensures that the user's information is correct and that the public key actually belongs to that user.

The server checks the user's certificate to verify that it bears the certificate authority's signature.  

Oracle Advanced Security Administrator's Guide  

Secure Sockets Layer (SSL) authentication method  

Stores authentication data, such as certificates and private keys, in an Oracle Wallet. When the client initiates a Net8 connection to the server, SSL performs a handshake between the two using the private key and certificate. During the handshake the following processes occur:

• The client and server negotiate a cipher suite-a set of authentication, encryption, and data integrity types-to apply to the messages they exchange.

• Depending on how you have configured SSL, the client may send the user's certificate to the Oracle server. The certificate ensures that the user's information is correct and that the public key actually belongs to that user. The server checks the user's certificate to verify that it bears the certificate authority's signature.

• Again, depending on your configuration, the server may then send its own certificate to the client in a message encrypted with the client's public key. The client decrypts this message by using its own private key, then verifies that the server's certificate bears the certificate authority's signature.

Oracle Advanced Security Administrator's Guide  

TCP/IP with SSL Protocol  

Enables client/server conversation over a network using TCP/IP and SSL.  

Oracle Advanced Security Administrator's Guide  

Connecting with service name and instance name rather than system identifier (SID) in TNSNAMES.ORA  

The SID of the database had to be specified in the CONNECT_DATA section of the TNSNAMES.ORA file, as shown below:

service_name= 
 (description=  
  (address_list= 
   (address=...)
   (address=...)
  )
  (connect_data=(sid=sales))

Because a database can include services that span multiple instances, SID has been replaced by service name and, optionally, instance name.

The following entry allows a client to connect to the SALES.COM service:

net_service_name= 
 (description= 
  (address=...)
  (address=...)
  (connect_data=
    (service_name=sales.com)
 ) 

The following entry allows a client to connect to the OP1 instance, which is a part of the OP.COM service:

net_service_name= 
 (description= 
  (address=...)
  (address=...)
  (connect_data=
    (service_name=op.com)
    (instance_name=op1)
 ) 

SERVICE_NAME is typically the global database name, a name comprised of the database name and domain name, entered during installation or database creation. INSTANCE_NAME is typically the SID entered during installation or database creation.

Additional Information: See:

• "Setting Service Names and Instance Names"

• "Configuring the Network with the Local Naming Method"

Client load balancing with DESCRIPTION_LIST and ADDRESS_LIST in TNSNAMES.ORA  

DESCRIPTION_LISTs were used for mapping multiple connect descriptors to net service names and for client load balancing of multiple listeners.

In order to client load balance, the user had to define separate connect descriptors for each listener.  

While client load balancing is still ON by default for DESCRIPTION_LISTs, load balancing can also be explicitly specified with the new LOAD_BALANCE parameter for an ADDRESS_LIST or associated with a set of ADDRESSes or set DESCRIPTIONs. The following entry associates client load balancing with a list of addresses, affecting all listener ADDRESSes:

net_service_name= 
 (description= 
  (load_balance=on)
  (address=...)
  (address=...)
  (connect_data= 
    (service_name=sales.com))
 ) 

Client load balancing works with any version of the client, but requires an Oracle8i release 8.1 server.

Additional Information: See:

• "Configuring Multiple Address Options"

• Figure C-4, "Client Load Balancing for Release 8.1 and Prior to Release 8.1".

Nested addresses within ADDRESS_LIST in TNSNAMES.ORA and LISTENER.ORA  

If there was only one list of addresses, it was required to use an ADDRESS_LIST, as shown below:

service_name= 
(description= 
 (address_list= 
  (address=...)
  (address=...)
 )
 (connect_data=(sid=sales))

Address lists in Net8 do not have to be embedded in an ADDRESS_LIST if there is only one list, as shown below:

net_service_name= 
 (description= 
  (address=...)
  (address=...)
   (connect_data=
     (service_name=sales.com))
 )

Nested addresses work with any version of the client, but requires an Oracle8i release 8.1 server.

Additional Information: See:

• "Configuring the Network with the Local Naming Method"

• "Local Naming Parameters (TNSNAMES.ORA)"

Connect-Time Failover with ADDRESS_LIST in TNSNAMES.ORA  

An ADDRESS_LIST implied connect-time failover, where a client connect fails over to a different listener if the first listener fails. Net8 and SQL*Net proceeded through all the listener addresses until one succeeded.  

Failover is now supported by default for ADDRESS_LISTs, DESCRIPTION_LISTs, and a set of DESCRIPTIONs. Failover can also be explicitly specified with the new FAILOVER parameter for a set of ADDRESSes. The following entry associates connect-time failover with a list of addresses, affecting all listener ADDRESSes:

net_service_name= 
 (description= 
  (failover=on)
  (address=...)
  (address=...)
  (connect_data= 
    (service_name=sales.com))
 ) 

Connect-time failover works with any version of the client, but requires an Oracle8i release 8.1 server.

Additional Information: See:

• "Configuring Multiple Address Options"

• "Local Naming Parameters (TNSNAMES.ORA)"

Routing connections through an Oracle Connection Manager with SOURCE_ROUTE=ON in TNSNAMES.ORA  

The SOURCE_ROUTE parameter, which creates a source route of addresses through an Oracle Connection Manager to the destination service, had to be outside of an ADDRESS_LIST:

service_name= 
(description= 
 (source_route=on)
 (address_list= 
  (address=...)
  (address=...)
 )
 (connect_data=
  (sid=sales))
 )

SOURCE_ROUTE is no longer outside of an ADDRESS_LIST. Instead, it is now associated with a list of ADDRESSes, as shown below:

net_service_name= 
 (description= 
  (source_route=on) 
  (address=...)
  (address=...)
  (connect_data= 
    (service_name=sales.com))
 ) 

Additional Information: See:

• "Configuring the Client for Oracle Connection Manager Features"

• "Local Naming Parameters (TNSNAMES.ORA)"

SID_LIST_listener_name information in the LISTENER.ORA  

The LISTENER.ORA required a definition of the SID of the database served by the listener. The SID of the database had to be specified in the SID_LIST section of the LISTENER.ORA file. For example:

sid_list_listener=(sid_list=
(sid_desc=
 (global_dbname=sales.com)
 (sid_name=db1)
 (oracle_home=/usr/bin/oracle)))

Additional Information: See "Configuring the Listener".  

Because database instances and multi-threaded server dispatchers now register themselves with the listener, it is no longer necessary to explicitly define database information, unless you:

• are connecting to an Oracle 8 release 8.0 or Oracle7 database:

• using a management tool, such as Oracle Enterprise Manager, that requires this information.

Additional Information: See "Configuring the Listener".  

Presentation layer and Session layer information in LISTENER.ORA  

The only type of clients supported by Net8 were those connecting to the database using the Two-Task Common (TTC) presentation layer and theTransparent Network Substrate (TNS) Network Session (NS) session layer. This information was not required in the LISTENER.ORA file.  

Besides traditional Net8 clients, this release also supports IIOP clients connecting to the Java option in the database. These clients use General Inter-Orb Protocol (GIOP) as the presentation layer rather than Two-Task Common (TTC). In addition, no session layering is needed.

TTC and NS are the default and do not need to be explicitly defined in LISTENER.ORA for typical Net8 clients. If you have IIOP clients, the presentation and session layers must be explicitly defined. For example:

listener=
  (description=
   (protocol_stack=
    (presentation=giop)
    (session=raw)
    )
    (address=
     (protocol=tcp)
     (host=sales-pc)
     (port=2481))
  )

Additional Information: See "Configuring Java Option Connections".  

Address for CMADMIN process in CMAN.ORA  

An address was only required for the Oracle Connection Manager gateway process, CMGW. The administrative process, CMADMIN used an internal IPC address.  

A protocol address is required for both CMADMIN and CMGW.

This new address is depicted by the new CMAN_ADMIN parameter, as shown below:

cman=(address=(protocol=tcp)(host=anyh
ost)(port=1630))
    

    cman_
admin=(address=(protocol=tcp)(ho
st= cman-pc)(port=1650))
    

By default the CMADMIN process listens on TCP/IP with a registered port of 1830.

Additional Information: See:

• "Oracle Connection Manager Processes" for conceptual information

• "Enabling Connection Concentration" for configuration information

FAILOVER  

When set to ON, instructs Net8 at connect time to fail over to a different listener if the first listener fails. It determines how many addresses are tried, as shown below:

net_service_name= 
 (description= 
   (failover=on)
   (address=...)
   (address=...)
   (connect_data=
    (service_name=service_name) 
 )

When set to OFF, instructs Net8 to try one address.

By default, this parameter is set to ON for ADDRESS_LISTs, DESCRIPTION_LISTs and a set of DESCRIPTIONs.

Additional Information: See:

• "Configuring Multiple Address Options"

• "Local Naming Parameters (TNSNAMES.ORA)"

INSTANCE_NAME  

In addition to using the SERVICE_NAME parameter, the INSTANCE_NAME parameter can also be used to identify the database instance to access. INSTANCE_NAME is only necessary for an Oracle Parallel server database, where the specific instance to which to connect is important to identify. For example, shown below are descriptions for a service, OP, that spans multiple instances, OP1 and OP2. The end user can connect to the OP service through either instance.

net_service_name=
  (description=
     (address=
       (protocol=tcp) 
       (host=opsnt1) 
       (port=1521))
     (connect_data=
       (service_name=op.com)
       (instance_name=op1))
net_service_name=
  (description=
     (address=
       (protocol=tcp) 
       (host=opsnt1) 
       (port=1521))
     (connect_data=
       (service_name=op.com)
       (instance_name=op2))
    

        

The INSTANCE_NAME is typically the SID entered during installation or database creation.

Additional Information: See "Configuring Multiple Address Options" for information about the instance name string.  

LOAD_BALANCE  

When set to ON, instructs Net8 to progress through the list of listener addresses in a random sequence, balancing the load on the various listeners, as shown below:

net_service_name=
 (description= 
  (load_balance=on)
  (address=...)
  (address=...)
  (connect_data= 
    (service_name=sales.com))
 ) 

When set to OFF, instructs Net8 to try the addresses sequentially until one succeeds.

By default, this parameter is set to ON for DESCRIPTION_LISTs.

Additional Information: See:

• "Configuring Multiple Address Options"

• "Local Naming Parameters (TNSNAMES.ORA)"

SERVICE_NAME  

Identifies the service to which to connect, as shown below:

net_service_name=
 (description= 
  (address=...)
  (address=...)
  (connect_data=
   (service_name=sales.com)
 )

The SERVICE_NAME is typically set to the global database name, a name comprised of the database name and domain name, entered during installation or database creation.

Additional Information: See"Setting Service Names and Instance Names" for information about the service name string.  

PROTOCOL_STACK  

Identifies the presentation and session layer information for a connection:

listener=
  (description_list=
    (description=
      (protocol_stack=
        (presentation=giop)
        (session=raw)
      )
      (address_list=
        (address=...)
      )
    )
  )

It is not necessary to use PROTOCOL_STACK if you are using the default presentation layer of Two-Task Common (TTC) and the default session layer of Network Session (NS).

Additional Information: See "Stack Communications in a Typical Oracle Networking Environment" for a description of the supported presentation and session layers.  

PRESENTATION  

Identifies the presentation layer:

• Typical Net8 clients use a presentation layer of TTC.

• Java clients require a presentation layer of General Inter-Orb Protocol (GIOP).

SESSION  

Identifies the session layer:

• Typical Net8 clients use a session layer of NS.

• Java clients require a presentation layer of RAW for no session layer.

CMAN_ADMIN  

Identifies the address for the administrative process CMADMIN process, as shown below:

cman_admin=
 (address=
  (protocol=tcp)
  (host= cman-pc)
  (port=1650)
 )

When the Oracle Connection Manager Control Utility, CMCTL, is 
run, it locates the CMADMIN protocol address to execute its 
commands.

It is not necessary to explicitly specify CMAN_ADMIN if you are using the default address of TCP/IP on port 1830.

Additional Information: See:

• "Enabling Connection Concentration"

• "Oracle Connection Manager Control Utility (CMCTL)"

AUTOMATIC_IPC  

SQLNET.ORA  

This parameter used to force sessions through IPC addresses. Due to performance issues, this parameter has been removed. You should configure and IPC address instead.  

NAMES.USE_PLUG_AND_PLAY  

NAMES.ORA  

This was used to enable/disable the Dynamic Discovery Option. There are other mechanism available to discover other Oracle Names server.

Additional Information: See "Configuring the Network with the Oracle Names Method".  

NAMES.DOMAIN_CHECKPOINT FILE  

NAMES.ORA  

Name of the file used to checkpoint topology data (domains addresses of servers in the local region).

You should use the NAMES.REGION_CHECKPOINT_FILE parameter to create a checkpoint file with this information.  

NAMES.TOPOLOGY_CHECKPOINT_FILE  

NAMES.ORA  

Name of the file used to checkpoint domain data (all the database addresses and other data in the region).

You should use the NAMES.REGION_CHECKPOINT_FILE parameter to create a checkpoint file with this information.  

Typical  

The Net8 Configuration Assistant runs without user input and configures a default:

• LISTENER.ORA file for a listener named LISTENER listening on the following endpoints:

  -IPC for connections to external procedures

  -TCP/IP for a Net8 client connection to the Oracle database

  -TCP/IP for a IIOP client connection to the Java option

  Static information about external procedures is also configured in the LISTENER.ORA file.

• TNSNAMES.ORA file with a net service name configured for external procedures

• SQLNET.ORA with parameters set for the computer's domain and the naming method order

Minimal  

The Net8 Configuration Assistant runs without user input and configures a default:

• LISTENER.ORA file for a listener named LISTENER listening on the following endpoints:

  -IPC for connections to external procedures

  -TCP/IP for a Net8 client connection to the Oracle database

  -TCP/IP for a IIOP client connection to the Java option

  Static information about external procedures is also configured in the LISTENER.ORA file.

• TNSNAMES.ORA file with a net service name configured for external procedures

• SQLNET.ORA with parameters set for the computer's domain and the naming method order

Custom  

The Net8 Configuration Assistant prompts you to configure the following:

• a listener, including it's name and protocols to use for listener endpoints

• naming methods to resolve net service names to network addresses

When configuring the listener to listen on TCP/IP for typical Net8 clients, you should choose the default port or 1521. If you do not, you must configure the LOCAL_LISTENER parameter in the INITSID.ORA file and resolve the listener name through a naming method. For further information about configuring non-default port numbers in LISTENER.ORA for Net8 clients, see "Configuring a Listener that Uses a Non-Default Port".

When configuring the listener to listen on TCP/IP for IIOP clients, you should choose the default port of 2481. Likewise, you should the default port of 2482 for TCP/IP with SSL for IIOP clients. If you do not, you must configure the LOCAL_LISTENER parameter or the MTS_DISPATCHERS parameter's LISTENER attribute in the INITSID.ORA file, and resolve the listener name through a naming method. For further information about configuring non-default port numbers in LISTENER.ORA for IIOP clients, follow the steps in "Configuring a Non-Default Listener".  

Provides products that allow client connections to databases across a network. A client-side application sends a request to Net8 to be transported across the network to the server.  

server and client  

All  

Provides products that allow the network listener, through protocol, to accept connections from client applications on the network.  

server  

All  

• TCP/IP

Enables client/server conversation over a network using TCP/IP. This combination of Oracle products enables an Oracle application on a client to communicate with remote Oracle databases through TCP/IP (if the Oracle database is running on a host system that supports network communication using TCP/IP).  

server and client  

All  

• TCP/IP with SSL

Enables client/server conversation over a network using TCP/IP and the Secure Sockets Layer (SSL). This combination of Oracle products enables an Oracle application on a client to communicate with remote Oracle databases through TCP/IP and SSL (if the Oracle database is running on a host system that supports network communication using TCP/IP and SSL).  

server and client  

All  

• SPX

Enables client/server conversation over a network using SPX/IPX. This combination of Oracle products enables an Oracle application on a client to communicate with remote Oracle databases through SPX/IPX (if the Oracle database is running on a host system that supports network communication using SPX/IPX). This protocol is predominantly used in Novell Netware environments.  

server and client  

Custom  

• Named Pipes

Enables client/server conversation over a network using Named Pipes. This combination of Oracle products enables an Oracle application on a client to communicate with remote Oracle databases through Named Pipes (if the Oracle database is running on a host system that supports network communication using Named Pipes).

The Named Pipes is a high-level interface providing interprocess communications between clients and servers (distributed applications). One process (the server side of the application) creates the pipe, and the other process (the client side) opens it by name. What one side writes, the other can read, and vice versa. Named Pipes is specifically designed for PC LAN environments.  

server and client  

Custom  

• Logical Unit Type 6.2 (LU6.2)

The protocol is part of the IBM Advanced Program-to-Program Communication (APPC) architecture.

APPC is the IBM peer-to-peer (program-to-program) protocol for a System Network Architecture (SNA) network. SNA is an IBM reference model similar to the Open Systems Interconnect (OSI) model of the International Standards Organization (ISO).

APPC architecture lets the client and host communicate over an SNA network without forcing the client to emulate a terminal (as in terminal-to-host protocols). APPC architecture allows peer-to-peer communication; the client can initiate communication with the server.

An SNA network with the LU6.2 and Physical Unit Type 2.1 (PU2.1) protocols provides APPC. The LU6.2 protocol defines a session between two application programs; LU6.2 is a product-independent LU-type.

LU6.2 enables an Oracle application on a PC to communicate with an Oracle database. This communication occurs over an SNA network with the Oracle database on a host system that supports APPC.  

server and client  

Custom  

• Bequeath

Enables clients to retrieve information from the database without using the network listener. The Bequeath protocol internally spawns a server thread for each client application. In a sense, it does the same operation that a remote network listener does for your connection, yet locally.

Bequeath:

• Does not use a network listener (therefore, no network listener configuration is required)

• Is used for local connections where an Oracle client application (such as SQL*Plus) communicates with an Oracle server running on the same machine

• Only works in Dedicated Server mode. It cannot be used in a Multi-Threaded Server (MTS) mode.

• Is supported on Windows NT for 32-bit applications. It also works on Windows 95 for connections to a Personal Oracle8i database for 32-bit applications.

• Is installed by default with Net8 Client

server and client  

not applicable (installed with Net8 Client and Net8 Server)  

Net8 has a number of new features that simplify configuration and administration of the Oracle network:  

• Net8 Configuration Assistant

Net8 Configuration Assistant configures necessary client and server Net8 components after an install, as described in:

• "Net8 Server Installation"

• "Net8 Client Installation"

It may be also run in stand-alone mode to configure naming methods and the listener. To start the Net8 Configuration Assistant:

• On UNIX, run netca at $ORACLE_HOME/bin.

• On Windows NT, choose Start > Programs > Oracle - HOME_NAME > Network Administration > Net8 Configuration Assistant.

Additional Information: See:

• "Configuring the Network with the Local Naming Method"

• Chapter 7, "Enabling Optional Net8 Features"

server and client  

All  

• Net8 Easy Config

Net8 Easy Config enables you to set up net service names in the TNSNAMES.ORA file. The functionality of this product has been added to the Net8 Configuration Assistant. Oracle Corporation recommends using the Net8 Configuration Assistant.  

server and client  

not applicable (installed with the Oracle Net8 Assistant)  

• Net8 Assistant

The Net8 Assistant allows you to administer the following networking components:

• Profile -- Create or modify the client SQLNET.ORA configuration file on the local machine to control such client functions as authentication, domains, logging, tracing, and security.

• Net Service Names-- Create or modify net service names in the TNSNAMES.ORA local naming file.

• Listeners -- Create or modify the LISTENER.ORA file to control the listener.

• Oracle Names Servers -- Create or modify a centralized Oracle Names server to store networking objects, such as database addresses and net service names. An Oracle Names server may also be administered locally or remotely for such functions as starting and stopping with the Net8 Assistant.

To start the Net8 Assistant:

• On UNIX, run netasst at $ORACLE_HOME/bin.

• On Windows NT, choose Start > Programs > Oracle - HOME_NAME > Network Administration > Net8 Assistant.

Additional Information: See Chapter 6, "Configuring Naming Methods and the Listener" and Chapter 7, "Enabling Optional Net8 Features".  

server and client  

All  

Oracle Names is a distributed naming service developed for Oracle environments to help simplify the setup and administration of global, client/server computing networks. Oracle Names does this by establishing and maintaining an integrated system of Names servers. Oracle Names servers work like a directory service storing addresses for all the database services on a network and making them available to clients wishing to make a connection.

Additional Information: See "Configuring the Network with the Oracle Names Method".  

Oracle Names server machine  

Custom  

The Oracle Connection Manager provides three capabilities for Oracle8i:

• Connection Concentration -- Allows you to multiplex multiple logical client sessions through a single transport connection to an Oracle database destination.

  For more information, see "Enabling Connection Concentration".

• Net8 Access Control (also known as firewall support) -- Provides a proxy for denying or allowing access to a database server.

  For more information, see "Enabling Net8 Access Control".

• Multi-Protocol Support -- Allows client and database servers operating on different protocol stacks to communicate with each other.

  For more information, see "Enabling Multi-Protocol Support".

Oracle Connection Manager machine  

Custom  

Net8 offers the following external naming methods:  

• NetWare Directory Service (NDS) External Naming

NDS External Naming allows you to use external NDS naming conventions to connect to an Oracle database on a Novell NDS-enabled network.

Additional Information: See "Configuring the Network with the External Naming Method".  

server and client  

Custom  

• Network Information Service (NIS) External Naming

Organizations and corporations already using Network Information Service (NIS) as part of their systems infrastructure have the option to store Oracle service aliases and addresses in NIS, using NIS External Naming

Additional Information: See "Configuring the Network with the External Naming Method".  

server and client  

Custom  

Oracle Advanced Security consists of the following components:  

server and client  

Custom  

• Network Security

This Oracle network data encryption and checksumming service ensures secure transmission of data over networks. Network Security uses encryption and authentication engines from RSA Data Security, Incorporated.

The following algorithms are supported:

Encryption

• RC4_40 (US, Export & Upgrade)

• RC4_56 (US & Export)

• RC4_128 (US only)

• DES_56 (US & Upgrade)

• DES_40 (US, Export & Upgrade)

Checksumming

• MD5 (US, Export & Upgrade)

• Single Sign-On

Allows users to access multiple accounts and applications with a single password. This feature eliminates the need for multiple passwords for users and simplifies management of user accounts and passwords for system administrators.

Centralized, secure authentication services allow you to have high confidence in the identity of users, clients, and servers in distributed environments. Network authentication services can also provide the benefit of single sign-on for users.

The following authentication methods are supported:

• CyberSAFE

• Identix (Biometric)

• Kerberos

• RADIUS

• SecurID

• SSL

server and client  

Custom  

• DCE Integration

Distributed Computing Environment (DCE) Integration enables users to transparently use Oracle tools and applications to access Oracle8i databases in a DCE environment. The Oracle DCE Integration product consists of two major components:

• DCE Communications/Security method

• DCE CDS (Cell Directory Service) Naming method

server and client  

Custom