ORACLE NETWORK ; tnsnames.ora(local naming)

Local Naming에서 사용되는 Parameter들(tnsnames.ora)

1. Overview of Local Naming Parameters
tnsnames.ora파일안에는 net service name들이 명시되어있으며, 각 net service name들은
local naming에서 사용하는 connect descriptor(or listener protocol address)들과 매치됩니다.
 

각 net service name은 connect descriptor안에 명시되어있는 database network address를 가르킵니다.

또한, connect descriptor은 각 접속할 listener의 위치와, 데이터베이스의 service name의 내용을 포함합니다.

이러한 net service name을 이용하여 사용자의 application에서 server들과의 connection이 이루어지게 됩니다.

* local naming 방법으로 DB에 접속하는 방법(tnsnames.ora 파일사용)

sqlplus scott/tiger@net_service_name

   <==> 비교 : EZCONNECT : sqlplus scott/tiger@host_name:port/db_name  (EZCONNECT는 따로 설정이나 파일생성할 필요가 없음)

파일의 위치 :
기본적으로 $ORACLE_HOME/network/admin/tnsnames.ora,
만약에 TNS_ADMIN이 명시되면 TNS_ADMIN디렉토리 안에 생성해야 인식을 하게 됩니다.,  Solaris의 경우에는 /var/opt/oracle에 생성

2. tnsnames.ora 의 기본적인 파일내용

net_service_name= 

 (DESCRIPTION= 

   (ADDRESS=(protocol_address_information))

   (CONNECT_DATA= 

     (SERVICE_NAME=service_name)))

3. 여러개의 address_list 사용하기

예시

net_service_name= 

 (DESCRIPTION= 

  (ADDRESS_LIST= 

   (LOAD_BALANCE=on)

   (FAILOVER=off)

   (ADDRESS=(protocol_address_information))

   (ADDRESS=(protocol_address_information)))

  (ADDRESS_LIST= 

   (LOAD_BALANCE=off)

   (FAILOVER=on)

   (ADDRESS=(protocol_address_information))

   (ADDRESS=(protocol_address_information)))

  (CONNECT_DATA=

   (SERVICE_NAME=service_name)))

위와 같이 하나의 net_service_name안에 여러개의 ADDRESS_LIST를 사용할 수 있으며, 

첫번째 ADDRESS_LIST는 LOAD_BALANCE=on, FAILOVER=off 인 protocol address들 2개로 구성되어있으며, 

두번째 ADDRESS_LIST도 LOAD_BALANCE-off, FAILOVER=on 인 protocol address 2개로 구성되어있습니다.

해당 net_service_name을 이용해서 접속을 시도하게 되면, 

첫번째 ADDRESS_LIST안에 있는 protocol address들 중에서 무작위로 골라서 접속시도하게 되고

(첫번째나 두번째 protocol address),

그 이후에 두번째 ADDRESS_LIST안에 있는 procotol address들(세번째, 네번째)을 시도합니다.

Note:

Oracle Net Manager supports only the creation of one protocol address list for a connect descriptor.

4. Connect-Time Failover and Client Load Balancing with Oracle Connection Managers

When a connect descriptor in a tnsnames.ora file contains at least two protocol addresses for Oracle Connection Manager, parameters for connect-time failover and load balancing can be included in the file.

Example 6-4 illustrates failover of multiple Oracle Connection Manager protocol addresses.

Example 6-4 Multiple Oracle Connection Manager Addresses in tnsnames.ora

sample1=

 (DESCRIPTION= 

   (SOURCE_ROUTE=yes) 

   (ADDRESS=(PROTOCOL=tcp)(HOST=host1)(PORT=1630))    # hop 1 

   (ADDRESS_LIST=  

     (FAILOVER=on) 

     (LOAD_BALANCE=off)                                # hop 2 

     (ADDRESS=(PROTOCOL=tcp)(HOST=host2a)(PORT=1630)) 

     (ADDRESS=(PROTOCOL=tcp)(HOST=host2b)(PORT=1630)))

   (ADDRESS=(PROTOCOL=tcp)(HOST=host3)(PORT=1521))    # hop 3

   (CONNECT_DATA=(SERVICE_NAME=Sales.us.example.com)))

In Example 6-4:

The client is instructed to connect to an protocol address of the first Oracle Connection Manager, as indicated by:

(ADDRESS=(PROTOCOL=tcp)(HOST=host1)(PORT=1630))

The first Oracle Connection Manager is then instructed to connect to the first protocol address of another Oracle Connection Manager. If the first protocol address fails, then it tries the second protocol address. This sequence is specified with the following configuration:

(ADDRESS_LIST=  

  (FAILOVER=ON) 

  (LOAD_BALANCE=off)

  (ADDRESS=(PROTOCOL=tcp)(HOST=host2a)(PORT=1630)) 

  (ADDRESS=(PROTOCOL=tcp)(HOST=host2b)(PORT=1630)) 

The Oracle Connection Manager then connects to the database service using the following protocol address:

(ADDRESS=(PROTOCOL=tcp)(HOST=host3)(PORT=1521)) 

Example 6-5 illustrates client load balancing among two Oracle Connection Managers and two protocol addresses:

Example 6-5 Client Load Balancing in tnsnames.ora

sample2=

 (DESCRIPTION= 

   (LOAD_BALANCE=on) 

   (FAILOVER=on)

   (ADDRESS_LIST= 

     (SOURCE_ROUTE=yes) 

     (ADDRESS=(PROTOCOL=tcp)(HOST=host1)(PORT=1630)) 

     (ADDRESS=(PROTOCOL=tcp)(HOST=host2)(PORT=1521)))

  (ADDRESS_LIST= 

     (SOURCE_ROUTE=yes) 

     (ADDRESS=(PROTOCOL=tcp)(HOST=host3)(port=1630)) 

     (ADDRESS=(PROTOCOL=tcp)(HOST=host4)(port=1521)))

   (CONNECT_DATA=(SERVICE_NAME=sales.us.example.com)))

In Example 6-5:

The client is instructed to pick an ADDRESS_LIST at random and to failover to the other if the chosen ADDRESS_LIST fails. This is indicated by the LOAD_BALANCE and FAILOVER parameters being set to on.

When an ADDRESS_LIST is chosen, the client first connects to the Oracle Connection Manager, using the Oracle Connection Manager protocol address that uses port 1630 indicated for the ADDRESS_LIST.

The Oracle Connection Manager then connects to the database service, using the protocol address indicated for the ADDRESS_LIST.

5. Local Naming Parameters

This section lists and describes the tnsnames.ora file parameters that comprise connect descriptors. Configuration parameters fall into the following categories:

Connect Descriptor Descriptions

Protocol Address Section

Optional Parameters for Lists

Connect Data Section

Security Section
 

5.1. Connect Descriptor Descriptions

Each connect descriptor is contained within the DESCRIPTION parameter. Multiple connect descriptors are characterized by the DESCRIPTION_LIST parameter. These parameters are described in this section.

5.1.1 DESCRIPTION

Purpose

Use the DESCRIPTION parameter as a container for a connect descriptor.

Embed this parameter under the DESCRIPTION_LIST parameter.

Example

net_service_name=

(DESCRIPTION=

  (ADDRESS=...)

  (CONNECT_DATA=(SERVICE_NAME=sales.us.example.com)))
 

5.1.2 DESCRIPTION_LIST

Purpose

Use he DESCRIPTION_LIST parameter defines a list of connect descriptors for a particular net service name.

Example

net_service_name= 

(DESCRIPTION_LIST=

 (DESCRIPTION=

  (ADDRESS=...)

  (CONNECT_DATA=(SERVICE_NAME=sales.example.com)))

 (DESCRIPTION=

  (ADDRESS=...)

  (CONNECT_DATA=(SERVICE_NAME=sales2.us.example.com))))
 

5.2 Protocol Address Section

The protocol address section of the tnsnames.ora file specifies the protocol addresses of the listener.

This section lists and describes the following parameters:

ADDRESS

ADDRESS_LIST
 

5.2.1 ADDRESS

Purpose

Use the ADDRESS parameter to define a single listener protocol address.

Embed this parameter under either the ADDRESS_LIST parameter or the DESCRIPTION parameter.

See Also:

Chapter 4, "Protocol Address Configuration" for descriptions of the correct parameters to use for each protocol

Example

net_service_name=

(DESCRIPTION= 

 (ADDRESS=(PROTOCOL=tcp)(HOST=sales-svr)(PORT=1521))

 (CONNECT_DATA=(SERVICE_NAME=sales.us.example.com))
 

5.2.2 ADDRESS_LIST

Purpose

Use the ADDRESS_LIST parameter to define a list of protocol addresses. If there is only address list, ADDRESS_LIST is not necessary.

Embed this parameter under either the DESCRIPTION parameter or the DESCRIPTION_LIST parameter.

Example

net_service_name=

 (DESCRIPTION= 

  (ADDRESS_LIST=

   (ADDRESS=(PROTOCOL=tcp)(HOST=sales1-svr)(PORT=1521))

   (ADDRESS=(PROTOCOL=tcp)(HOST=sales2-svr)(PORT=1521)))

  (ADDRESS_LIST=

   (FAILOVER=on)

   (ADDRESS=(PROTOCOL=tcp)(HOST=sales1-svr)(PORT=1521))

   (ADDRESS=(PROTOCOL=tcp)(HOST=sales2-svr)(PORT=1521))

  (CONNECT_DATA=(SERVICE_NAME=sales.us.example.com)))

5.3 Optional Parameters for Lists

For multiple addresses, the following parameters are available for usage:

ENABLE

FAILOVER

LOAD_BALANCE

RECV_BUF_SIZE

SDU

SEND_BUF_SIZE

SOURCE_ROUTE

TYPE_OF_SERVICE

5.3.1 ENABLE

Purpose

The keepalive feature on the supported TCP transports can be enabled for a net service client by embedding (ENABLE=BROKEN) under the DESCRIPTION parameter in the connect string. Keepalive allows the caller to detect a dead remote server, although typically it will take 2 hours or more to notice. Operating system TCP configurables, which vary by platform, define the actual keepalive timing details.

Default

tcp_keepalive is off by default on the client side

Values

BROKEN

Example

net_service_name=

 (DESCRIPTION= 

  (enable=broken)

  (ADDRESS=(PROTOCOL=tcp)(HOST=sales1-svr)(PORT=1521))

  (ADDRESS=(PROTOCOL=tcp)(HOST=sales2-svr)(PORT=1521)))

  (CONNECT_DATA=(SERVICE_NAME=sales.us.example.com))

5.3.2 FAILOVER

Purpose

Use the parameter FAILOVER to enable or disable connect-time failover for multiple protocol addresses.

When you set the parameter to on, yes, or true, Oracle Net, at connect time, fails over to a different address if the first protocol address fails. When you set the parameter to off, no, or false, Oracle Net tries one protocol address.

Embed this parameter under either the DESCRIPTION_LIST parameter, the DESCRIPTION parameter, or the ADDRESS_LIST parameter.

Important:

Do not set the GLOBAL_DBNAME parameter in the SID_LIST_listener_name section of the listener.ora. A statically configured global database name disables connect-time failover.

Default

on for DESCRIPTION_LISTs, DESCRIPTIONs, and ADDRESS_LISTs

Values

on | off | yes | no | true | false

Example

net_service_name=

 (DESCRIPTION= 

  (FAILOVER=on)

  (ADDRESS=(PROTOCOL=tcp)(HOST=sales1-svr)(PORT=1521))

  (ADDRESS=(PROTOCOL=tcp)(HOST=sales2-svr)(PORT=1521)))

  (CONNECT_DATA=(SERVICE_NAME=sales.us.example.com)))

5.3.3 LOAD_BALANCE

Purpose

Use the LOAD_BALANCE parameter to enable or disable client load balancing for multiple protocol addresses.

When you set the parameter to on, yes, or true, Oracle Net progresses through the list of addresses in a random sequence, balancing the load on the various listener or Oracle Connection Manager protocol addresses. When you set the parameter to off, no, or false, Oracle Net tries the protocol addresses sequentially until one succeeds.

Embed this parameter under either the DESCRIPTION_LIST parameter, the DESCRIPTION parameter, or the ADDRESS_LIST parameter.

Default

on for DESCRIPTION_LISTs

Values

on | off | yes | no | true | false

Example

net_service_name=

 (DESCRIPTION= 

  (LOAD_BALANCE=on)

  (ADDRESS=(PROTOCOL=tcp)(HOST=sales1-svr)(PORT=1521))

  (ADDRESS=(PROTOCOL=tcp)(HOST=sales2-svr)(PORT=1521)))

  (CONNECT_DATA=(SERVICE_NAME=sales.us.example.com))
 

5.3.4 RECV_BUF_SIZE

Purpose

Use the RECV_BUF_SIZE parameter to specify, in bytes, the buffer space for receive operations of sessions. This parameter is supported by the TCP/IP, TCP/IP with SSL, and SDP protocols.

Note:

Additional protocols might support this parameter on certain operating systems. Refer to operating-system specific documentation for information about additional protocols that support this parameter.

Embed this parameter under the DESCRIPTION parameter or at the end of the protocol address.

Default

The default value for this parameter is operating-system specific. The default for the Solaris 2.6 Operating System is 32768 bytes.

Usage

Setting this parameter in the connect descriptor for a client overrides the RECV_BUF_SIZE parameter at the client-side sqlnet.ora file.

See Also:

Oracle Database Net Services Administrator's Guide for information about configuring this parameter

Example

net_service_name= 

 (DESCRIPTION= 

   (ADDRESS_LIST=

     (ADDRESS=(PROTOCOL=tcp)(HOST=sales1-server)(PORT=1521)

        (RECV_BUF_SIZE=11784))

     (ADDRESS=(PROTOCOL=tcp)(HOST=sales2-server)(PORT=1521)

        (RECV_BUF_SIZE=11784))

   (CONNECT_DATA=

     (SERVICE_NAME=sales.us.example.com)))

net_service_name= 

 (DESCRIPTION= 

   (RECV_BUF_SIZE=11784)

   (ADDRESS_LIST=

     (ADDRESS=(PROTOCOL=tcp)(HOST=hr1-server)(PORT=1521)

     (ADDRESS=(PROTOCOL=tcp)(HOST=hr2-server)(PORT=1521))

   (CONNECT_DATA=

     (SERVICE_NAME=hr.us.example.com)))
 

5.3.5 SDU

Purpose

Use the parameter SDU to instruct Oracle Net to optimize the transfer rate of data packets being sent across the network with the session data unit (SDU) size you specify.

Embed this parameter under the DESCRIPTION parameter.

Default

8192 bytes (8 KB)

Values

512 bytes to 32767

Usage

Setting this parameter in the connect descriptor for a client overrides the DEFAULT_SDU_SIZE parameter at client-side sqlnet.ora file.

See Also:

Oracle Database Net Services Administrator's Guide for complete SDU usage and configuration information

Example

net_service_name= 

 (DESCRIPTION=

  (SDU=8192)

   (ADDRESS_LIST=

     (ADDRESS=(PROTOCOL=tcp)(HOST=sales1-server)(PORT=1521))

     (ADDRESS=(PROTOCOL=tcp)(HOST=sales2-server)(PORT=1521)))

  (CONNECT_DATA=

    (SERVER_NAME=sales.us.example.com))
 

5.3.6 SEND_BUF_SIZE

Purpose

Use the parameter SEND_BUF_SIZE to specify, in bytes, the buffer space for send operations of sessions. This parameter is supported by the TCP/IP, TCP/IP with SSL, and SDP protocols.

Note:

Additional protocols might support this parameter on certain operating systems. Refer to operating-system specific documentation for information about additional protocols that support this parameter.

Embed this parameter under the DESCRIPTION parameter or at the end of the protocol address.

Default

The default value for this parameter is operating-system specific. The default for the Solaris 2.6 Operating System is 8192 bytes.

Usage

Setting this parameter in the connect descriptor for a client overrides the SEND_BUF_SIZE parameter at the client-side sqlnet.ora file.

See Also:

Oracle Database Net Services Administrator's Guide for information about configuring this parameter

Example

net_service_name= 

 (DESCRIPTION= 

   (ADDRESS_LIST=

     (ADDRESS=(PROTOCOL=tcp)(HOST=sales1-server)(PORT=1521)

        (SEND_BUF_SIZE=11784))

     (ADDRESS=(PROTOCOL=tcp)(HOST=sales2-server)(PORT=1521)

        (SEND_BUF_SIZE=11784))

   (CONNECT_DATA=

     (SERVICE_NAME=sales.us.example.com)))

net_service_name= 

 (DESCRIPTION= 

   (SEND_BUF_SIZE=11784)

   (ADDRESS_LIST=

     (ADDRESS=(PROTOCOL=tcp)(HOST=hr1-server)(PORT=1521)

     (ADDRESS=(PROTOCOL=tcp)(HOST=hr2-server)(PORT=1521))

   (CONNECT_DATA=

     (SERVICE_NAME=hr.us.example.com)))
 

5.3.7 SOURCE_ROUTE

Purpose

Use the parameter SOURCE_ROUTE to enable routing through multiple protocol addresses.

When you set to on or yes, Oracle Net uses each address in order until the destination is reached.

To use Oracle Connection Manager, an initial connection from the client to Oracle Connection Manager is required, and a second connection from Oracle Connection Manager to the listener is required.

Embed this parameter under either the DESCRIPTION_LIST parameter, the DESCRIPTION parameter, or the ADDRESS_LIST parameter.

See Also:

Oracle Database Net Services Administrator's Guide for complete configuration information

Default

off

Values

yes | no | on | off

Example

net_service_name=

 (DESCRIPTION= 

  (SOURCE_ROUTE=on)

  (ADDRESS=(PROTOCOL=tcp)(HOST=cman-pc)(PORT=1630))

  (ADDRESS=(PROTOCOL=tcp)(HOST=sales1-svr)(PORT=1521)))

  (CONNECT_DATA=(SERVICE_NAME=sales.us.example.com))
 

5.3.8 TYPE_OF_SERVICE

Purpose

Use the parameter TYPE_OF_SERVICE parameter to specify the type of service to use for an Oracle Rdb database. This parameter should only be used if the application supports both an Oracle Rdb and Oracle database service, and you want the application to load balance between the two.

Embed this parameter under the DESCRIPTION parameter.

Example

net_service_name=

 (DESCRIPTION_LIST=

  (DESCRIPTION=

   (ADDRESS=...)

   (CONNECT_DATA= 

    (SERVICE_NAME=generic)

    (RDB_DATABASE=[.mf]mf_personal.rdb)

    (GLOBAL_NAME=alpha5))

   (TYPE_OF_SERVICE=rdb_database))

  (DESCRIPTION=

   (ADDRESS=...)

   (CONNECT_DATA=

    (SERVICE_NAME=sales.us.example.com))

   (TYPE_OF_SERVICE=oracle9_database)))
 

5.4 Connect Data Section

The connection data section of the tnsnames.ora file specifies the name of the destination service.

5.4.1 CONNECT_DATA

Purpose

Use the CONNECT_DATA parameter to define the service to which to connect.

Embed this parameter under the DESCRIPTION parameter.

Usage Notes

CONNECT_DATA permits the following subparameters:

FAILOVER_MODE

GLOBAL_NAME

HS

INSTANCE_NAME

RDB_DATABASE

SERVER

SERVICE_NAME

SID

Example

net_service_name=

 (DESCRIPTION= 

  (ADDRESS=(PROTOCOL=tcp)(HOST=sales1-svr)(PORT=1521))

  (ADDRESS=(PROTOCOL=tcp)(HOST=sales2-svr)(PORT=1521))

  (CONNECT_DATA=

   (SERVICE_NAME=sales.us.example.com)))
 

5.4.2 FAILOVER_MODE

Purpose

Use the FAILOVER_MODE parameter to instruct Oracle Net to fail over to a different listener if the first listener fails during run-time. Depending upon the configuration, session or any SELECT statements which were in progress are automatically failed over.

This type of failover is called Transparent Application Failover (TAF) and should not be confused with the connect-time failover FAILOVER parameter.

Embed this parameter under the CONNECT_DATA parameter.

See Also:

Oracle Database Net Services Administrator's Guide for complete configuration information

Subparameters

FAILOVER_MODE supports the following subparameters:

BACKUP: Specify the failover node by its net service name. A separate net service name must be created for the failover node.

TYPE: Specify the type of failover. Three types of Oracle Net failover functionality are available by default to Oracle Call Interface (OCI) applications:

session: Fails over the session; that is, if a user's connection is lost, a new session is automatically created for the user on the backup. This type of failover does not attempt to recover selects.

select: Allows users with open cursors to continue fetching on them after failure. However, this mode involves overhead on the client side in normal select operations.

none: This is the default, in which no failover functionality is used. This can also be explicitly specified to prevent failover from happening.

METHOD: Specify how fast failover is to occur from the primary node to the backup node:

basic: Establishes connections at failover time. This option requires almost no work on the backup database server until failover time.

preconnect: Pre-establishes connections. This provides faster failover but requires that the backup instance be able to support all connections from every supported instance.

RETRIES: Specify the number of times to attempt to connect after a failover. If DELAY is specified, RETRIES defaults to five retry attempts.

DELAY: Specify the amount of time in seconds to wait between connect attempts. If RETRIES is specified, DELAY defaults to one second.

Note:

If a callback function is registered, then RETRIES and DELAY subparameters are ignored.

Example

See Also:

Oracle Database Net Services Administrator's Guide for implementation examples
 

5.4.3 GLOBAL_NAME

Purpose

Use the GLOBAL_NAME parameter to identify the Oracle Rdb database.

Embed this parameter under the CONNECT_DATA parameter.

Example

net_service_name= 

 (DESCRIPTION= 

   (ADDRESS=...)

   (ADDRESS=...)

   (CONNECT_DATA=

    (SERVICE_NAME=generic)

    (RDB_DATABASE=[.mf]mf_personal.rdb)

    (GLOBAL_NAME=alpha5)))
 

5.4.4 HS

Purpose

Use the HS parameter to instruct Oracle Net to connect to a non-Oracle system through Heterogeneous Services.

Embed this parameter under the CONNECT_DATA parameter.

See Also:

Oracle Database Net Services Administrator's Guide for complete configuration information

Default

None

Values

ok

Example

net_service_name= 

 (DESCRIPTION=

   (ADDRESS=...)

   (ADDRESS=...)

   (CONNECT_DATA=

    (SID=sales6)

    (HS=ok)))
 

5.4.5 INSTANCE_NAME

Purpose

Use the INSTANCE_NAME parameter to identify the database instance to access. Set the value to the value specified by the INSTANCE_NAME parameter in the initialization parameter file.

Embed this parameter under the CONNECT_DATA parameter.

See Also:

Oracle Database Net Services Administrator's Guide for information about the use of INSTANCE_NAME

Example

net_service_name= 

 (DESCRIPTION=

   (ADDRESS=...)

   (ADDRESS=...)

   (CONNECT_DATA=

    (SERVICE_NAME=sales.us.example.com)

    (INSTANCE_NAME=sales1)))
 

5.4.6 RDB_DATABASE

Purpose

Use the RDB_DATABASE parameter to specify the file name of an Oracle Rdb database.

Embed this parameter under the CONNECT_DATA parameter.

Example

net_service_name= 

 (DESCRIPTION= 

   (ADDRESS=...)

   (ADDRESS=...)

   (CONNECT_DATA=

    (SERVICE_NAME=sales.us.example.com)

    (RDB_DATABASE= [.mf]mf_personal.rdb)))
 

5.4.7 SERVER

Purpose

Use the SERVER parameter to instruct the listener to connect the client to a specific type of service handler.

Embed this parameter under the CONNECT_DATA parameter.

Values

dedicated to specify that client requests be served by dedicated server

shared to specify that client request be served by shared server

Notes:

Shared server must be configured in the database initialization file in order for the client to connect to the database with a shared server process. See the Oracle Database Net Services Administrator's Guide for configuration information.

The USE_DEDICATED_SERVER parameter in the sqlnet.ora file overrides this parameter.

pooled to get a connection from the connection pool if database resident connection pooling is enabled on the server

See Also:

Oracle Database Net Services Administrator's Guide for more information about database resident connection pooling

Oracle Call Interface Programmer's Guide and Oracle Database Administrator's Guide for more information about enabling and configuring database resident connection pooling

Example

net_service_name= 

 (DESCRIPTION=

   (ADDRESS=...)

   (ADDRESS=...)

   (CONNECT_DATA=

    (SERVER_NAME=sales.us.example.com)

    (SERVER=dedicated)))
 

5.4.8 SERVICE_NAME

Purpose

Use the SERVICE_NAME parameter to identify the Oracle9i or Oracle8 database service to access. Set the value to a value specified by the SERVICE_NAMES parameter in the initialization parameter file.

Embed this parameter under the CONNECT_DATA parameter.

See Also:

Oracle Database Net Services Administrator's Guide for information about the use of the SERVICE_NAME parameter

Example

net_service_name= 

 (DESCRIPTION=

   (ADDRESS=...)

   (ADDRESS=...)

   (CONNECT_DATA=

    (SERVICE_NAME=sales.us.example.com)))
 

5.4.9 SID

Purpose

Use the SID parameter to identify the Oracle8 database instance by its Oracle System Identifier (SID). If the database is Oracle9i or Oracle8, use the SERVICE_NAME parameter rather than the SID parameter.

See Also:

Oracle Database Net Services Administrator's Guide for information about the use of SID

Embed this parameter under the CONNECT_DATA parameter.

Example

net_service_name= 

 (DESCRIPTION=

   (ADDRESS=...)

   (ADDRESS=...)

   (CONNECT_DATA=

    (SID=sales)))
 

5.5 Security Section

The security section of the tnsnames.ora file specifies the following security-related parameters for use with Oracle Advanced Security features:

SECURITY

SSL_SERVER_CERT_DN
 

5.5.1 SECURITY

Purpose

Use the SECURITY parameter to enable secure connections.

Embed this parameter under the DESCRIPTION parameter.

Usage Notes

SECURITY permits the SSL_SERVER_CERT_DN subparameter.

Example

net_service_name=

 (DESCRIPTION= 

  (ADDRESS=(PROTOCOL=tcp)(HOST=sales1-svr)(PORT=1521))

  (ADDRESS=(PROTOCOL=tcp)(HOST=sales2-svr)(PORT=1521))

  (CONNECT_DATA=

   (SERVICE_NAME=sales.us.example.com))

   (SECURITY=

    (SSL_SERVER_CERT_DN="cn=sales,cn=OracleContext,dc=us,dc=example,dc=com")))
 

5.5.2 SSL_SERVER_CERT_DN

Purpose

Use the SSL_SERVER_CERT_DN parameter to specify the distinguished name (DN) of the database server. The client uses this information to obtain the list of DNs it expects for each of the servers, enforcing the database server DN to match its service name.

Usage Notes

Use this parameter in conjunction with the sqlnet.ora parameter SSL_SERVER_DN_MATCH to enable server DN matching.

See Also:

Oracle Database Advanced Security Administrator's Guide

Example

net_service_name= 

 (DESCRIPTION=

   (ADDRESS=...)USE_DEDICATED_SERVER

   (ADDRESS=...)

   (CONNECT_DATA=

    (SERVICE_NAME=finance.us.example.com))

   (SECURITY=

    (SSL_SERVER_CERT_DN="cn=finance,cn=OracleContext,dc=us,dc=example,dc=com")))