Oracle Database - Connect Descriptor (TNS Connect String)


The Connect Descriptor (known also as TNS Connect String) is a type of connect identifier. It defines the parameters that need the Oracle Net Service to connect to a database service :

  • the protocol
  • the host
  • the port
  • the SID
  • the database connection type

You can gives a connect descriptor:

  • manually <note warning>The Connect descriptor must be given in 1 line or you have to use single quote. See here for more information on the syntax: connect identifier syntax. </note>
  • or through different mechanisms named naming method.


A connect descriptor is comprised of one or more protocol addresses of the listener and the connect information for the destination service.



  • the ADDRESS section contains the following:
    • PROTOCOL parameter, which identifies the listener protocol address. The protocol is tcp for TCP/IP.
    • HOST parameter, which identifies the host name. The host is sales-server.
    • PORT parameter, which identifies the port. The port is 1521, the default port number.
  • The CONNECT_DATA section contains the following:
    • SID parameter, which identifies the SID of the Oracle database. The SID is sales.
    • SERVICE_NAME parameter, which identifies the service. The destination service name is a database service named
    • INSTANCE_NAME parameter, which identifies the database instance. The instance name is optional.
    • SERVER parameter which identifies the service handler type where the parameter value can be

Database connection type

If shared server is configured in the initialization parameter file, you can select Dedicated Server to force the listener to spawn a dedicated server, bypassing shared server configuration. If shared server is configured in the initialization parameter file and you want to guarantee the connection always uses shared server, select Shared Server.

Enhancing Service Accessibility using Multiple Listeners

For some configurations, such as Oracle Real Application Clusters, multiple listeners on multiple nodes can be configured to handle client connection requests for the same database service. In the following example, can connect using listeners on either sales1-server or sales2-server.


A multiple-listener configuration also enables you to leverage the failover and load balancing features, either individually or in combination with each other. The following topics describe the features:

  • Connect-time Failover
  • Transparent Application Failover
  • Client Load Balancing
  • Connection Load Balancing

More … Enhancing Service Accessibility using Multiple Listeners

How to get the TNS connect string ?

You can get the connect string by performing a tnsping on the tnsname.

C:\Documents and Settings\Nicolas>tnsping orcl

TNS Ping Utility for 32-bit Windows: Version - Production on 10-JUN-2009 11:09:18

Copyright (c) 1997,  2007, Oracle.  All rights reserved.

Used parameter files:

Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = ngerard)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED
) (SID = orcl)))
OK (80 msec)

C:\Documents and Settings\Nicolas>tnsping qsdb > c:\tns.txt

You can then retrieve the TNS Connect Descriptor from the file tns.txt of from the screen. The TNS Connect string is :


Powered by ComboStrap