Net8 Getting Started 
Release 8.0.5 for Windows NT and Windows 95/98 
A64419-01
 
Library
 
Product
 
Contents
 
Index
 

Prev Next

6
Configuring the Network

This chapter describes how to configure your network.

Specific topics discussed are:

Configuration Overview

Before a database server can receive connections from clients, clients must be configured with service names (easy to remember aliases for database addresses) that match the address preconfigured in each server machine's LISTENER.ORA file. These addresses are used by the client to connect to the network listener during a connection. During a connection, a client passes the system ID (SID) of the server to which it wants to connect.

The LISTENER.ORA file identifies and controls the behavior of the network listeners that listen for the databases on the machine. This file includes network listener descriptors and addresses of all network listeners on a machine, the SIDs of the databases they listen for, and various control parameters.

Client configuration is accomplished by creating a list of the service names and addresses of network database destinations through a TNSNAMES.ORA client configuration file or an Oracle Names Server. A client (or a server that is part of a distributed database) needs this information to know where to make connections.

Configuration is based upon one of two models:

Network Configuration Model  Suitable When...  Naming Method  Configuration Tool 

Localized management 

Network addresses are mapped in a TNSNAMES.ORA file on each node (no Oracle Names Server). 

Host naming  

Local naming  

External naming 

Net8 Easy Configuration Tool 

Centralized management 

Networks where an Oracle Names Server performs network address resolution. An Oracle Names Server stores client configuration profiles in one location. 

Oracle Names 

Oracle Net8 Assistant 

 

Naming Methods

Service names can be created using the following configuration methods:

Naming Method  Description 

Host Naming 

Resolves service names through a TCP/IP network's Domain Name System (DNS) or in the /ETC/HOSTS file. This method is recommended for simple TCP/IP environments.  

See "Using the Host Naming Method" in this chapter. 

Local Naming (no Oracle Names Server) 

Resolves service names to network addresses by using information configured and stored on each individual client. Local Naming is most appropriate for simple distributed networks with a small number of services that change infrequently.  

See "Using the Local Naming Method" in this chapter. 

Oracle Names 

Stores names and addresses of all database services on a network on an Oracle Names Server. Connection requests are routed through an Oracle Names Server, which resolves the service name to a network address. The information is then returned to the client.  

See "Using the Oracle Names Method" in this chapter. 

External Naming 

External naming refers to service name resolution by using a supported third-party naming service.  

See "Using the External Naming Method" in Chapter 8, "Performing Advanced Configuration"

 

Configuration Files

Depending on the naming method you use, the following configuration files may be created or updated in ORACLE_HOME\NET80\ADMIN:

Configuration File  Description 

LISTENER.ORA 

Includes addresses of all network listeners on a server, the SIDs of the databases for which they listen, and various control parameters used by the network listener. This file resides on the server. 

TNSNAMES.ORA 

Includes a list of service names of databases. This file resides on clients. 

SQLNET.ORA 

Includes the names resolution method. This file resides on clients. 

SDNS.ORA 

Includes lists of Oracle Names Servers. This file resides on clients. 

 


Additional Information:  

See Appendix C, "Configuration Files" for more information about these files. 


 
 

Using the Host Naming Method

The host naming method is enabled by default during Typical installation for TCP/IP network environments only. The LISTENER.ORA has a line which specifies the TCP/IP host name of your server. Clients that use this host name in their connect string can connect.

Your client machine may connect to a database using the host name of the machine on which the database resides if:

Server Configuration

Ensure GLOBAL_DBNAME = HOSTNAME as specified in the ORACLE_HOME\NET80\ADMIN\LISTENER.ORA configuration file, where HOSTNAME is the TCP/IP host name or alias of the server system.

During the installation of Net8, the GLOBAL_DBNAME of the default database is set to the system name.

To verify GLOBAL_DBNAME is correctly specified, manually check the LISTENER.ORA file of use the Oracle Net8 Assistant:

Check the LISTENER.ORA file...  Use the Oracle Net8 Assistant... 

Ensure the line shown in bold exists: 

SID_LIST_LISTENER_NAME=
   (SID_LIST =
      (SID_DESC =
         (SID_NAME = SID)
         (GLOBAL_DBNAME = HOSTNAME)
      )
   )
 
  1. Choose Start > Programs > Oracle for Windows NT - HOME_NAME > Oracle Net8 Assistant. 
The Oracle Net8 Assistant starts. 
  1. Double-click the Listeners folder. 
  2. Select the appropriate network listener from the Listeners folder. 
The network listener details appear on the right side of the screen: 
  1. Select Database Services from the drop-down list. 
  2. Ensure the TCP/IP host name is correctly specified in the Global Database Field. 
  3. Choose Save Network Configuration from the File menu. 
  4. Choose Exit from the File menu to exit the Oracle Net8 Assistant application. 
 
 

Client Configuration

No client configuration is necessary for using the Host Naming Adapter. The connection is established by using the default TCP/IP port for the network listener.

Multiple Databases On a Server

If you have multiple databases on a server, you can set TCP/IP aliases for the server system, and assign a separate GLOBAL_DBNAME parameter for each different databases in the LISTENER.ORA file.

The client will then connect to the specific database based on the host name used for connection.

Using the Local Naming Method

With the local naming method, service names are added to the TNSNAMES.ORA files. Service names are mapped to database address. Clients use this service name in their connect string to connect.

Server Configuration

To configure using the local naming method:


Note:  

Net8 Easy Configuration Tool only supports configurations using TCP/IP, SPX, Named Pipes, and Bequeath Protocol Adapters. To configure a service name using the LU6.2 Protocol Adapter, you must manually edit the configuration files. 


 
 
  1. Choose Start > Programs > Oracle for Windows NT - HOME_NAME > Net8 Easy Configuration Tool.
  2. The Oracle Net8 Easy Config wizard starts:

  3. Enter a new service name (up to 64 characters) in the New Service Name field to create a new service name, and click Next. The service name can be any name you choose.
  4. The next page appears:

  5. Select the network protocol you want to use (this protocol adapter must also be installed on the clients), and click Next.
  6. The page appropriate for your protocol adapter appears; in the example here, TCP/IP is assumed:

  7. Enter the appropriate information for your chosen protocol in the fields, and click Next.
  8. The next page appears:

  9. Enter the name of the SID of the database to which you want to connect in the Database SID field, and click Next. The default SID is ORCL.
  10. The following page appears:

  11. Click Next (testing is performed later in this chapter).
  12. Click Finish to save your configuration and quit the Net8 Easy Configuration Tool.
  13. Oracle Net8 Easy Config adds the new service names to the TNSNAMES.ORA in ORACLE_HOME\NET80\ADMIN.

  14. If you have more than one supported Oracle Protocol Adapter in your ORACLE_HOME directory, use Net8 Easy Configuration Tool to configure other services following the same steps.

Client Configuration

After the server is configured, it is best to simply copy over the TNSNAMES.ORA configuration file located at ORACLE_HOME\NET80\ADMIN on the server to the same location on the clients. This will ensure the files are consistent. Otherwise, you must use the Oracle Net8 Easy Config tool on every client, introducing possible errors.

Using the Oracle Names Method

Oracle Names simplifies the setup and administration of global, client/server computing networks. Oracle Names makes network address and database link information available to all nodes throughout the network. Each database server's network address is identified with a simple service name. Client applications then can request a database connection with that name rather than a lengthy address.

Oracle Names is made up of Names Servers that store a service's name and network address. Services include databases, database link definitions, and object aliases. Client applications request a connection using a simple name, rather than the lengthy address, and the name is resolved to the address by a Names Server. Oracle Names shields users and applications from changes made to the network infrastructure. It provides for centralized administration of network service names.

The diagram below shows that:

Oracle Names Features

The automatic discovery feature of Oracle Names version 8 enables network connectivity with virtually no configuration files.

Oracle Names version 8 includes three features to improve network performance and ease of administration:

Differences Between Versions of Oracle Names

There are significant differences between this version of Oracle Names and earlier versions:

Setting Up and Oracle Names Server

The steps to set up an Oracle Names Server include:

Step 1: Install

Step 2: Configure the Server

Step 3: Define a Well-Known Oracle Names Server

Step 4: Create a Well-Known Oracle Names Server

Step 5: Configure Clients and Servers To Use Oracle Names Server

Step 1: Install

Ensure the following are installed:

Step 2: Configure the Server

On the server, the network listener must be configured to identify a database listener on that server for an Oracle Names Server.

To configure the network listener:

  1. From the Control Panel window, double-click Services.
  2. The Services window appears.

  3. Check the status of the network listener OracleHOME_NAMETNSListener. If the network listener is stopped (the status column is blank), go to the Step 3. If the status is Started, stop the network listener:
  4. To stop the network listener:

    1. From the Control Panel's Services window, select OracleHOME_NAMETNSListener80 (the service name if you are using the default network listener name LISTENER) or OracleHOME_NAMETNSListener80LSNR (where LSNR is the non-default network listener name), and click Stop.
    2. The Services confirmation dialog box appears, prompting you if it is OK to stop the service.

    3. Click Yes.
    4. The network listener is stopped. The status column is blank.

  5. Click Close to quit the Services window.
  6. Set the global database name and register services with the Oracle Names Server using the Oracle Net8 Assistant or editing the ORACLE_HOME\NET80\ADMIN\LISTENER.ORA file.
  7. The global database name specifies the name by which the network listener registers the database instance with an Oracle Names Server and the name by which the Oracle Names Server identifies a database. You can use any alias, but Oracle Corporation recommends setting the global database name to the value of the INITSID.ORA's DB_NAME and DB_DOMAIN parameters. The default global database name is ORACLE.WORLD.

    When clients request the connect information for a database from an Oracle Names Server, this is the alias they use. The domain must also be added to the end of this name.

    Registering services with the Oracle Names Server instructs the network listener to find and register with a well-known Oracle Names Server. When the network listener starts, it looks for hosts with the well-known host names, tries to gather connection information from the Oracle Names Server, and registers its SID(s) with it.

    Use the Net8 Assistant...  Modify the LISTENER.ORA file... 
    1. Choose Start > Programs > Oracle for Windows NT - HOME_NAME > Oracle Net8 Assistant. 
    The Oracle Net8 Assistant starts. 
    1. Double-click the Listeners folder. 
    2. Select the appropriate network listener from the Listeners folder. 
    The network listener details appear on the right side of the page: 
    1. Select Database Services from the drop-down list. 
    2. Modify the Global Database Field with the an alias. Preferably, use the values of DB_NAME and DB_DOMAIN from the INITSID.ORA as the alias. 
    3. Select General Parameters from the drop-down list. 
    4. Select Register Services with Oracle Names. 
    5. Choose Save Network Configuration from the File menu. 
    6. Choose Exit from the File menu to exit the Oracle Net8 Assistant. 
     

    Ensure GLOBAL_DBNAME is set to an alias. Preferably, use the values of DB_NAME and DB_DOMAIN from the INITSID.ORA as the alias. For example: 

    SID_LIST_LISTENER_NAME=
       (SID_LIST =
          (SID_DESC =
             (SID_NAME = SID)
             (GLOBAL_DBNAME = GLOBAL_DBNAME.DOMAIN)
          )
       )
    USE_PLUG_AND_PLAY_listener = ON
     
     
     

Step 3: Define a Well-Known Oracle Names Server

To define a well-known Oracle Names Server:

For all clients and servers, ensure your network administrator has named the Oracle Names Servers as a well-known names server, allowing clients to access the Oracle Names Servers using the well-known name.

Well-known names are dependent on the protocol adapter:

The well-known host names for TCP connections   The well-known computer Names for Named Pipes connections1  The well-known service name for an SPX connection 

oranamesrvr0 
oranamesrvr1 
oranamesrvr2 
oranamesrvr3 
oranamesrvr4 

ORANAMESRVR0 
ORANAMESRVR1 
ORANAMESRVR2 
ORANAMESRVR3 
ORANAMESRVR4 

oranamesrvr 

 
1 Well-known Names Server names for Names Pipes must be in all uppercase letters.

This implies you can have as few as one well-known Oracle Names Server (whose alias would be oranamesrvr0) and as many as five (with aliases oranamesrvr0 to oranamesrvr4).

The numbers 0 to 4 indicate the order in which the client tries to contact the Oracle Names Servers, if more than one exists in the network.

For example, for TCP/IP, Oracle Names Servers are made well-known by adding aliases oranamesrvr(0-4) to the Domain Name Service (DNS) or in the SYSTEMROOT\SYSTEM32\DRIVERS\ETC\HOSTS file.

The HOSTS file may include the following entries:

144.25.219.146 host0  oranamesrvr0
144.25.219.147 host1  oranamesrvr1
144.25.219.148 host1  oranamesrvr2

Step 4: Create a Well-Known Oracle Names Server

You may use the Oracle Names Control Utility (NAMESCTL80), or the Oracle Net8 Assistant to create a well-known Oracle Names Server on the machine where Oracle Names Server is installed.

Prior to creating a well-known Oracle Names Server, you must decide whether:

See Chapter 6, "Oracle Names," of the Oracle Net8 Administrator's Guide to help with these decisions.

Oracle Corporation recommends you create at two least Oracle Names Servers, one to act as the Oracle Names Server and one to act as a backup Oracle Names Server. Each of these should reside on its own machine.

To create a well-known Oracle Names Server, use the Oracle Net8 Assistant or the NAMESCTL control utility:

Use the Net8 Assistant...  Use the control utility NAMESCTL80... 
  1. If you want to create a region database, follow Steps 1-2 in Section 6.7, "Creating a Database to Store Names Server Information", of the Oracle Net8 Administrator's Guide
  2. On the machine where Oracle Names software resides, choose Start > Programs > Oracle for Windows NT - HOME_NAME > Oracle Net8 Assistant. 
The Oracle Net8 Assistant starts. 
  1. Select the Oracle Names Servers folder. 
  2. A message appears, saying the Oracle Net8 Assistant does know of any Oracle Names Servers in the network. 

  3. Click OK to acknowledge message. 
  4. Choose Create from the Edit menu, or click on the "+" button to create a new Names Server. 
The Names Wizard starts. 
  1. The wizard guides you through the creation and configuration process. 
  2. - a unique Oracle Name Server name 

    - an address for the Oracle Names Server 

    - a choice to store information in a database or replicate information among Oracle Names Server 

    If you choose to store information in a database, you are prompted for the listener address, and database SID, user name and password. 

    - to identify if this Oracle Names Server is in the root region 

  3. Choose Exit from the File menu to exit the Oracle Net8 Assistant application. 
  4. Repeat Steps 2-7 to create additional Oracle Names Servers on different machines within a region or another region. The Oracle Net8 Assistant does not support creation of multiple Oracle Names Servers on one machine. 
 
  1. If you want to create a region database, follow Steps 1-2 in Section 6,7, "Creating a Database to Store Names Server Information", of the Oracle Net8 Administrator's Guide
  2. Start the Oracle Names Server on each machine where Oracle Names software resides: 
From the MS-DOS command prompt, enter:C:\> NAMESCTL80NAMESCTL> STARTOr, from the Control Panel's Services window, select OracleHOME_NAMENamesService80, and click Start. 
  1. Create a SDNS.ORA file in ORACLE_HOME\NET80\NAMES. 
This file contains the names of the Oracle Names Server(s) in a particular region. The machine reads this file to find the addresses of other Oracle Names Servers.From the command line, enter:NAMESCTL> REORDER_NS  

 

 

Step 5: Configure Clients and Servers To Use Oracle Names Server

To configure the client and server machines to recognize Oracle Names Servers, use the Oracle Net8 Assistant or the NAMESCTL control utility:

Use the Net8 Assistant...  Use the control utility NAMESCTL80... 
  1. Choose Start > Programs > Oracle for Windows NT/Windows 95/98 - HOME_NAME > Oracle Net8 Assistant. 
The Oracle Net8 Assistant starts. 
  1. Select the Oracle Names Servers folder. 
  2. A message appears, saying the Oracle Net8 Assistant does know of any Oracle Names Servers in the network. 

  3. Choose Discover Oracle Names Servers from the Tools menu. 
This produces an SDNS.ORA file in ORACLE_HOME\NET80\NAMES. This file contains the names of the Oracle Names Server(s). This file is read to find the addresses of Oracle Names Servers.The following message appears:"Discovered Oracle Names Server in the region. Please exit the tool and start again." 
  1. Choose Exit from the File menu to exit the Oracle Net8 Assistant application. 
 

From the MS-DOS command prompt, enter:  

C:\> NAMESCTL80  

NAMESCTL> REORDER_NS  

This produces an SDNS.ORA file in ORACLE_HOME\NET80\NAMES. This file contains the names of the Oracle Names Server(s). This file is read to find the addresses of Oracle Names Servers. 

 

  • Ensure Oracle Names is the first method Net8 will use to reconcile service names by using the Oracle Net8 Assistant or editing the ORACLE_HOME\NET80\ADMIN\SQLNET.ORA file:

  • Use the Net8 Assistant...  Modify the SQLNET.ORA file... 
    1. Choose Start > Programs > Oracle for Windows NT/Windows 95/98 - HOME_NAME > Oracle Net8 Assistant. 
    The Oracle Net8 Assistant starts. 
    1. Click the Profiles icon. 
    The profile details appear on the right side of the page: 
    1. Select Naming from the drop-down list. 
    2. Click the Methods tab. 
    3. Choose ONAMES from the Available Methods list, and click <. 
    4. Select the ONAMES in the Selected Methods list, and click the Promote button to move the selection to the top of the list. 
    5. Choose Save Network Configuration from the File menu. 
    6. Choose Exit from the File menu to exit the Oracle Net8 Assistant application. 
    7. Oracle Names Server configuration is complete. 

     

    Add the NAMES.DIRECTORY_PATH parameter, so it includes ONAMES:NAMES.DIRECTORY_PATH = (ONAMES, TNSNAMES)  

    The order is important. Net8 tries to use the first method. If the first method fails to resolve the service name, Net8 tries to use the next method.  

    Oracle Names configuration is complete. 

     

    Configuring Oracle Connection Manager

    The Oracle Connection Manager provides three capabilities for Oracle8:

    The clients require a TNSNAMES.ORA file or Oracle Names Server, the Oracle Connection Manager requires a CMAN.ORA, and the server requires multiplexing parameters set in the INITSID.ORA.

    Conditions for Using Oracle Connection Manager

    Setting Up an Oracle Connection Manager

    The steps to set up an Oracle Connection Manager include:

    Step 1: Install

    Step 2: Configure Clients

    Step 3: Configure Oracle Connection Manager

    Step 4: Configure the Server

    Step 1: Install

    Ensure the following are installed:

    Step 2: Configure Clients

    To configure the client:

    Set the Oracle Connection Manager address through a TNSNAMES.ORA file or Oracle Names Server.

    If using Oracle Names Server, the Oracle Connection Manager automatically updates the addresses in the Names Server, inserting the address for the CMAN into the existing address.

    If you are using the local naming method, modify the ORACLE_HOME\NET80\ADMIN\TNSNAMES.ORA file located in ORACLE_HOME\NET80\ADMIN.

    To modify the TNSNAMES.ORA file:

    1. Choose Start > Programs > Oracle for Windows NT/Windows 95 - HOME_NAME > Oracle Net8 Assistant.
    2. The Oracle Net8 Assistant appears.

    3. Select the Service Names folder.
    4. The list of current service names appears:

    5. Select CMEXAMPLE.WORLD:
    6. Modify the Address 1 tab with the address information for the Oracle Connection Manager.
    7. Click Advanced.
    8. The Advanced Options dialog box appears:

    9. Ensure Source Route is checked, and click OK.
    10. This option creates a source route of addresses through all Oracle Connection Managers to the destination address.

    11. Select the Address 2 tab and modify it with the address information for the server. The second address is used by the Oracle Connection Manager to connect to the server.
    12. You can have multiple CMAN addresses in the ADDRESS_LIST if necessary. The Oracle Connection Managers basically act as routers, pointing the connection request to the next hop.
    13. Choose Save Network Configuration from the File menu.
    14. Choose Exit from the File menu to exit the Oracle Net8 Assistant.

    Below is a comparison of a regular TNSNAMES.ORA file and a TNSNAMES.ORA file with an entry to use the Oracle Connection Manager (Connection Manager entries are shown in boldface text):
    INVENTORYDB.WORLD= 
       (DESCRIPTION= 
            (ADDRESS= 
                  (PROTOCOL=TCP) 
                  (HOST=INVENTORY) 
                  (PORT=1521) 
            ) 
           (CONNECT_DATA= 
                  (SID=ORCL) 
           ) 
        )
    
     
    INVENTORYDB.WORLD= 
       (DESCRIPTION= 
           (ADDRESS_LIST= 
               (ADDRESS= <---CMAN address
                   (PROTOCOL=TCP) 
                   (HOST=CMAN) 
                   (PORT=1610) <---must match  port in CMAN.ORA file
               ) 
              (ADDRESS= 
                   (PROTOCOL=TCP) 
                   (HOST=INVENTORY) 
                   (PORT=1521) 
              ) 
            ) 
           (CONNECT_DATA= 
                  (SID=ORCL) 
           ) 
          (SOURCE_ROUTE=YES) 
        ) 
     
     

    Enabling Multi-Protocol Support

    Below is a TNSNAMES.ORA entry set up to use the Oracle Connection Manager with multiple protocols:

    INVENTORYDB.WORLD= 
       (DESCRIPTION= 
           (ADDRESS_LIST= 
               (ADDRESS= 
                   (PROTOCOL=SPX) 
                   (SERVICE=CMAN) 
              (ADDRESS= 
                   (PROTOCOL=TCP) 
                   (HOST=INVENTORY) 
                   (PORT=1521) 
              ) 
            ) 
           (CONNECT_DATA= 
                  (SID=ORCL) 
           ) 
          (SOURCE_ROUTE=YES) 
        )

    In this example, the client will use SPX to connect to the CMAN, then the CMAN will use TCP/IP to connect to the server. This is the same functionality that was provided with the Oracle Multi-Protocol Interchange (MPI) of Oracle7.

    Step 3: Configure Oracle Connection Manager

    Configuration of the Oracle Connection Manager may require the modification of the CMAN.ORA file located in ORACLE_HOME\NET80\ADMIN if you are using protocol adapters other than TCP/IP or require additional features.

    Non-TCP/IP Protocol Adapters

    If you used protocols other than TCP/IP between the client and 
    Oracle Connection Manager, you must modify the line beginning  CMAN = 
    (ADDRESS_LIST=

    to listen to the protocols adapter address the same way you would modify LISTENER.ORA file.

    Enabling Connection Concentration

    Section 7.3.2, "Enabling Connection Concentration Features," of the Oracle Net8 Administrator's Guide explains how to enable multiplexing.

    Enabling Specifying Network Access Control Rules

    Section 7.3.3, "Enabling Connection Concentration Features," of the Oracle Net8 Administrator's Guide explains how to enable network access rules.

    Enabling Optional Parameters

    If you require other optional parameters, you must remove the `#' preceding those parameters from the CMAN.ORA file.


    Additional Information:  

    See "Understanding the CMAN.ORA File" in Appendix C, "Configuration Files" for a complete description of the CMAN.ORA file and its parameters. 


     
     

    Step 4: Configure the Server

    To use the multiplexing, configure the server for Multi-Threaded Server (MTS) by setting MTS parameters in the ORACLE_HOME\DATABASE\INITSID.ORA for each instance. See Appendix B, "Initialization Parameter Files", in your Getting Started guide.

    Testing the Configuration on the Server

    Once you have configured the network, test the configuration by performing a loopback test on the server.

     A loopback test uses Net8 to go from the server back to itself, bypassing the Interprocess Communication (IPC). Performing a successful loopback verifies that Net8 is functioning on the server side.

    The steps to test the configuration are:

    Step 1: Start Oracle Names Server

    Step 2: Start the Network Listener

    Step 3: Start Oracle Connection Manager

    Step 4: Perform a Loopback Test

    Step 1: Start Oracle Names Server

    If you are using Oracle Names, start an Oracle Names Server on the machine where Oracle Names Server is installed and configured with the NAMESCTL80 control utility or the Control Panel:

    Use the control utility NAMESCTL80...  Use the Windows NT Control Panel... 
    1. From the command line, enter: 
    C:\> NAMESCTL80NAMESCTL> STATUSIf the STATUS command indicates the Oracle Names Server is running, go to Step 3. If the Oracle Names Server is not running, go to Step 2. 
    1. Start the Oracle Names Server. Enter: 
    NAMESCTL> START 
    1. Exit from the NAMESCTL utility. Enter: 
    NAMESCTL> EXIT 
    1. From the Control Panel window, double-click Services. 
    The Services window appears. Look for the OracleHOME_NAMENamesService80 service. A blank in the Status column indicates that the service is not running. If the service is already running, close the window and go to the section "Step 2: Start the Network Listener"
    1. Select the service, and click Start. 
    The service starts. 
    1. In the Services window, click Close. 
     
     

    Step 2: Start the Network Listener

    For Net8 to accept connections on the server, a network listener must be started. If you have started an Oracle Names Server, the network listener upon startup automatically registers the databases specified in the SID_LIST_LISTENER_NAME section of the ORACLE_HOME\NET80\ADMIN\LISTENER.ORA file with the well-know Oracle Names Servers.

    On the server, start the listener with the LSNRCTL80 control utility or the Control Panel:

    Use the control utility LSNRCTL80...  Use the Windows NT Control Panel... 
    1. From the command line enter: 
    C:\> LSNRCTL80LSNRCTL> STATUS LISTENER_NAME where LISTENER_NAME is the name of the network listener defined in the LISTENER.ORA file with the alias LISTENER. It is not necessary to identify the network listener if you are using the default network listener, named LISTENER.If the STATUS command indicates the network listener is running, go to Step 2. If the network listener is not running, go to Step 3. 
    1. Even if the network listener is running, Oracle Corporation advises you to stop the network listener, and start it again. To stop the network listener, enter: 
    LSNRCTL> SET PASSWORD PASSWORD
    LSNRCTL> START LISTENER_NAME 

    SET PASSWORD is only required if the password is set in the LISTENER.ORA file. The password defaults to ORACLE

    1. Start the network listener. Enter: 
    LSNRCTL> START LISTENER_NAMEOracleHOME_NAMETNSListener80LSNR is created if this command is run for the first time against a non-default network listener name. 
    1. Exit from the LSNRCTL80 utility. Enter: 
    LSNRCTL> EXIT 
    1. From the Control Panel window, double-click Services. 
    The Services window appears. Look for OracleHOME_NAMETNSListener80 (the service name if you are using the default network listener name LISTENER) or OracleHOME_NAMETNSListener80LSNR (where LSNR is the non-default network listener name). OracleHOME_NAMETNSListener80LSNR is only created if the following command has been run:LSNRCTL80 START LISTENER_NAMEA blank in the Status column indicates that the service is not running. If the service is already running, close the window and go to the section "Step 3: Start Oracle Connection Manager"
    1. Select the service, and click Start. 
    The service starts. 
    1. In the Services window, click Close. 
     
     

    Step 3: Start Oracle Connection Manager

    If you are using Oracle Connection Manager, start it on the machine where Oracle Connection Manager is installed and configured with the CMCTL80 control utility or the Control Panel:

    Use the control utility CMCTL80...  Use the Windows NT Control Panel... 
    1. From the command line, enter: 
    C:\> CMCTL80CMCTL> START CMAN 
    1. Exit from the CMCTL80 utility. Enter: 
    CMCTL> EXIT 
    1. From the Control Panel window, double-click Services. 
    The Services window appears. 
    1. If you are using Oracle Names, select the OracleHOME_NAMECMAdminService80 and click Start. If you are not using Oracle Names, do not start this service, and go to Step 3. 
    The service starts. 
    1. Select the OracleHOME_NAMECManService80, and click Start. A blank in the Status column indicates that the service is not running. 
    The service starts. 
    1. In the Services window, click Close. 
     
     

    Step 4: Perform a Loopback Test

    A loopback test is when the server makes a connection to a database on its own machine.


    Note:  

    The instructions below only apply if you have configured using the local naming method. If you have not configured with the local naming method, connect to the database using the instructions in "Step 5: Connect to the Database" of Chapter 7, "Connecting To a Database"


     
     

    To perform the loopback test:

    1. Choose Start > Programs > Oracle for Windows NT - HOME_NAME > Net8 Easy Configuration Tool.
    2. Oracle Net8 Easy Config starts.

    3. Click Test.
    4. Select a service name from the Existing Services list box you created in "Using the Local Naming Method" in this chapter.
    5. Click Next.
    6. The Connection Test page appears:

    7. Enter a valid user account user ID and password, such as SYSTEM and MANAGER, for the database you want to connect to, and click Test. The database administrator can provide this information.
    8. The status of the test appears in the field below the Test button. A successful test display the following message:

      The connection test was successful.
      
    9. Click Done when the test is complete.
    10. The final page appears.

    11. Click Finish to dismiss Net8 Easy Configuration Tool wizard.

    Testing the Configuration on the Client

    After performing a loopback test, use any of the mechanisms below to test client connections:

    Verify TCP/IP Network Connections

    If you are using TCP/IP, follow the instructions below to specify the destination address for TCP/IP and use PING to see if the server is running.

    Determine the Server's IP Address

    Use PING

    Most TCP/IP transports attempt to use the DNS. DNS is a mechanism used to translate the host name specified in the TNSNAMES.ORA file into the host internet address (IP). If a DNS is present on your network and the TCP/IP vendor supports DNS, the host name is successfully translated to the host address. The host IP address can be determined by using the Control Panel's Network utility to access DNS information.

    Depending on your vendor, workstation configuration, and network configuration, your TCP/IP software can also use a SYSTEMROOT\SYSTEM32\DRIVERS\ETC\HOSTS file to map host names to Internet addresses if DNS is not detected or supported.

    If DNS and the HOSTS file are unable to resolve the host name during a remote database connection, the following error message appears:

    ORA-12545: TNS: name lookup failure
    

    If your network administrator cannot resolve the problem, the solution to this error message is to go around DNS and the HOSTS file by modifying the (HOST = SERVER_NAME) section of the TNSNAMES.ORA, so SERVER_NAME is changed to the IP address of the server.

    The following sections explain how to determine the server's IP address and verify that DNS and the HOSTS file are working correctly.

    Determine the Server's IP Address

    If you are not using TCP/IP, go to "Verify Oracle Database Connections Using TNSPING" in this chapter.

    To determine the server's TCP/IP internet address:


    Note:  

    If you are not authorized for access on the server, ask your server administrator for assistance. 


     
     
    1. From the Control Panel window, double-click Network.
    2. The Network window appears.

    3. Choose the Protocols tab.
    4. The Protocols view appears:

    5. From the Protocol view, select the TCP/IP Protocol Adapter, and click Properties.
    6. The Microsoft TCP/IP Properties dialog box appears with the IP Address view:

    7. Obtain the IP address, and click Cancel to close the Microsoft TCP/IP Properties dialog box.
    8. Click Cancel to close the Network window.
    9. Continue to the next section, "Use PING".

    Use PING

    If you are using TCP/IP, PING allows you to determine if DNS or the HOSTS file are correctly set up and your network operating system is functioning correctly.

    To use PING:

    From the client, enter the following at the command prompt:

    C:\> PING SERVER_NAME
    

    where SERVER_NAME is the host name, alias, or Internet address of the server to which you are trying to connect.

    If your network is functioning correctly, the following message appears:

    Reply from SERVER_NAME: bytes=nn time=nnms

    If there is a problem, this message appears:

    Request timed out
    

    Or:

    Reply from SERVER_NAME: Destination host unreachable
    

    The following is a partial list of reasons why a host is inaccessible:

    If PING returns an error message, ask your network administrator to help you resolve the problem. If the problem is not resolved, and you attempt to make a Net8 connection, you may receive one of the following error messages:

    Verify Oracle Database Connections Using TNSPING

    Use the TNSPING80 utility to determine whether or not you can reach the network listener service. TNSPING80, however, never actually connects with the network listener. A socket is never created and opened. TNSPING80 only checks to ascertain that a network listener is present on the server side.

    When you connect to a network listener using TNSPING80, an estimate of the round trip time in milliseconds appears. If TNSPING80 fails, a network error message appears without the resource use of a database connection.

    To use TNSPING80:

    From the client, enter:

    TNSPING80 SERVICE_NAME COUNT 
    

    where SERVICE_NAME is the service name (defined in the TNSNAMES.ORA) you created in "Using the Local Naming Method" of this chapter and COUNT is the number of times the program attempts to reach the server. COUNT is optional.

    The output looks like:

    TNS Ping Utility for 32-bit Windows: Version 8.0.4.0.0 - Production on 27 OCT-97 
    20:20:33
    
    Copyright, 1997(c) Oracle Corporation 1997. All rights reserved.
    
    Attempting to contact (ADDRESS=(COMMUNITY=tcp.world)(PROTOCOL=TCP)(Host=host_
    name)(Port=1521))
    OK (60 msec)

    Verify Oracle Database Connection Using Oracle Net8 Easy Config


    Note:  

    The instructions below only apply if you have configured using the local naming method. If you have not configured with the local naming method, connect to the database using the instructions in "Step 5: Connect to the Database" of Chapter 7, "Connecting To a Database"


     
     

    Use the Oracle Net8 Easy Config application to determine whether or not you can reach the network listener service.

    To verify connectivity for a client machine:

    1. Choose Start > Programs > Oracle for Windows NT - HOME_NAME > Net8 Easy Configuration Tool.
    2. Oracle Net8 Easy Config starts.

    3. Click Test.
    4. Select a service name from the Existing Services list box you created in "Using the Local Naming Method" in this chapter.
    5. Click Next.
    6. The Connection Test page appears:

    7. Enter a valid Username and Password, such as SYSTEM and MANAGER, for the database you want to connect to, and click Test.
    8. The status of the test appears in the field below the Test button. A successful test displays the following message:

      The connection test was successful.
      
    9. Click Done when the test is complete.
    10. The final page appears.

    11. Click Finish to save your configuration and dismiss the Net8 Easy Configuration Tool.


     
    Prev
     
    Next
     
    Oracle 
    Copyright © 1998 Oracle Corporation. 
    All Rights Reserved. 
     
    Library
     
    Product
     
    Contents
     
    Index