Skip Headers

Oracle9i Net Services Administrator's Guide
Release 2 (9.2)

Part Number A96580-02
Go to Documentation Home
Go to Book List
Book List
Go to Table of Contents
Go to Index
Go to Master Index
Master Index
Go to Feedback page

Go to previous page Go to next page
View PDF

Quick Start to Oracle Net Connections

This chapter is designed to help novice users set up and test a simple but common configuration--one between a client application and a database over a TCP/IP network.

This chapter contains these topics:

Prerequisites to Establishing Connectivity

The tasks in this quick start show a TCP/IP connection between a client computer and a database server. The following about the database server and client computers is assumed:

Task 1: Confirm Network Availability

Before using Oracle Net to connect a client computer to a database server, confirm that the client computer can successfully communicate with the database server computer. Evaluating network connectivity can eliminate network-based errors.

To confirm network connectivity:

  1. Confirm that the database server computer can communicate with itself with a loopback test.

    A loopback test is a connection from the database server back to itself. Many network protocols provide a means of testing network connections. The utility PING can be used for TCP/IP network.

    In a TCP/IP network, each computer has a unique IP address. A name resolution service, such as Domain Name System (DNS), can be used to map the IP address of a computer with its host name. If a name resolution service is not used, then the mapping is typically stored in a centrally maintained file called hosts. This file is located in the /etc directory on UNIX and the \winnt directory on Windows NT. For example, an entry for a database server computer named sales-server may look like the following:

    #IP address of server     host name       alias            sales-server

    To use PING, enter the following at the command line:

    ping database_server_host

    The database_server_host is the host name of the database server computer. For example:

    ping sales-server

    If the loopback was unsuccessful, try using the IP address of the database server. For example:

  2. Verify the client computer can successfully communicate with the database server computer.

    This varies according to the network protocol. For TCP/IP, you can use PING, FTP or TELNET utilities. If the client computer cannot reach the server, verify that the network cabling and network interface cards are correctly connected. Contact your network administrator to correct these problems.

Task 2: Start the Listener and the Database Server

The listener and database server must be running in order for the database server to receive connections.

  1. Start the listener with the Listener Control utility. From the command line, enter:
    LSNRCTL> START [listener_name]

    where listener_name is the name of the listener defined in the listener.ora file. It is not necessary to identify the listener if you are using the default listener, named LISTENER.

    A status message indicating that the listener has started successfully displays.

  2. Start the database:
    1. Start SQL*Plus without connecting to the database:
      sqlplus /nolog
    2. Connect to the database as SYSDBA:
      SQL> CONNECT username/password as sysdba

      For example, SYSTEM/MANAGER is a SYSDBA user.

    3. Enter the STARTUP command, specifying the database name and full path of the parameter file:
      SQL> STARTUP database_name pfile=file

      If you do not specify the PFILE option, the Oracle database uses the standard initialization parameter file located in the $ORACLE_BASE/admin/db_name/pfile/sid directory on UNIX platforms, and ORACLE_BASE\admin\db_name\pfile\sid directory on Windows NT. If you do not specify a database name, then the database uses the value of the DB_NAME parameter specified in the initialization parameter file.

      See Also:

      Oracle9i Database Administrator's Guide for further information about starting the database

  3. Confirm that database service registration with the listener has completed. From the Listener Control utility, enter:
    LSNRCTL> SERVICES [listener_name]

The SERVICES command lists the services supported by the database, along with at lease one available service handler.

See Also:

"SERVICES Command"

Task 3: Configure the Client to Use a Net Service Name

Once network connectivity has been verified, you can use Oracle Net Configuration Assistant to create a net service name, a simple name for the database service. The net service name resolves to the connect descriptor, that is, the network address of the database and the name of the database service. The client will use the net service name to connect to the database.

The following example shows the net service name sales mapped to a connect descriptor for a database called A client can use sales mapped to connect to


To configure a client with a net service name:

  1. Start Oracle Net Configuration Assistant.

    See Also:

    "Oracle Net Configuration Assistant"

    The Welcome page appears.

  2. Select Local Net Service Name Configuration.
  3. Click Next.

    The Net Service Name Configuration page appears.

  4. Click Add, and then click Next.

    The Net Service Name Configuration, Database Version page appears:

  5. If the destination service is an Oracle9i or Oracle8i database, then select Oracle8i or later database or service. If destination service is an Oracle8 release 8.0 database, then select Oracle8 release 8.0 database or service.
  6. Click Next.

    The Net Service Name Configuration, Service Name appears.

  7. Enter the name that identifies the database.

    The service name is defined during database creation. If you are unsure what the service name is, ask the Database Administrator who created the database.

  8. Click Next.

    The Net Service Name Configuration, Select Protocols page appears.

  9. Select the protocol on which the listener is configured to listen. Note that this protocol must also be installed on the client. The listener is configured to listen on TCP/IP by default.
  10. Click Next.

    The page appropriate for the selected protocol appears.

  11. Enter the appropriate protocol parameters for the selected protocol in the fields provided, and then click Next.

    The Net Service Name Configuration, Test page appears.

  12. Click Yes perform a test.

    During a test, Oracle Net Configuration Assistant contacts the remote database service, establishes a connection, and ends contact.

    A successful test results in the following message:

    Connecting...Test successful.

    If the test fails, it can be because the:

    • Default username (scott) and password (tiger) are not valid
    • Protocol address information does not match the listener information
    • Listener is not running
    • Destination database service is down

    Depending on your diagnosis of the problem, perform one of the following tasks:

  13. Click Next.

    The Net Service Name Configuration, Net Service Name page appears.

  14. Accept the default net service name or enter another net service name in the Net Service Name field. The name you enter should be unique to the client.
  15. Click Next.

    The Net Service Name Configuration, Another Net Service Name page appears.

  16. Click No, and then click Next.

    The Net Service Name Configuration, Configuration Done page appears.

  17. Click Next, and then click Finish.

Task 4: Connect to the Database

From the client computer, connect to the database server as follows.

  1. Start SQL*Plus:
  2. Connect to the database as follows:
    CONNECT username/password@net_service_name

    where username and password are the database user and password, and net_service_name is the net service name that you created in "Task 3: Configure the Client to Use a Net Service Name".