13.5 Configuring Static Service Registration

The listener uses the dynamic service information about the database and instance before using statically configured information in the listener.ora file.

Configuration of static service information is necessary in the following cases:

  • Use of external procedure calls

  • Use of Oracle Heterogeneous Services

  • Use of Oracle Data Guard

  • Remote database startup from a tool other than Oracle Enterprise Manager Cloud Control

  • Connections to Oracle databases earlier than Oracle8i release 2 (8.1)

13.5.1 Parameters for Static Service Registration

Understand the static service settings in the listener.ora file for static service registration.

Example listener.ora File

This example shows a listener.ora file configured for static service registration. The LISTENER entry defines the listening protocol address for a listener named Listener, and the SID_LIST_LISTENER entry provides information about the external services statically supported by the Listener listener.

LISTENER=
  (DESCRIPTION=
    (ADDRESS_LIST=
      (ADDRESS=(PROTOCOL=tcp)(HOST=sales-server)(PORT=1521))
      (ADDRESS=(PROTOCOL=ipc)(KEY=extproc) (queuesize=50))))
SID_LIST_listener=
  (SID_LIST=
    (SID_DESC=
      (SID_NAME=plsextproc)
      (ORACLE_HOME=/oracle8)
      (PROGRAM=extproc)))

The SID_LIST_listener_name parameter setting in the listener.ora file specifies information about the databases served by the listener. When services are configured statically, a listener starts a dedicated server process when it receives a client request. If the instance is not up, then the server returns an Oracle not available error message.

If a database cannot find the listener, then configure the listener.ora file with the GLOBAL_DBNAME parameter, as shown in the following example

SID_LIST_listener=
(SID_LIST=
 (SID_DESC=
  (GLOBAL_DBNAME=sales.example.com)
  (SID_NAME=sales)
  (ORACLE_HOME=/u01/app/oracle))

Note:

A statically-configured global database name disables TAF. To use TAF, do not set the GLOBAL_DBNAME parameter in the SID_LIST_listener_name section of the listener.ora file.

Static Service Settings in listener.ora

Oracle Net Manager Field listener.ora File Parameter Description

SID

SID_NAME

The Oracle system identifier (SID) of the instance. You can obtain the SID value from the INSTANCE_NAME parameter in the initialization parameter file.

Service Name

GLOBAL_DBNAME

The database service.

While processing a client connection request, the listener tries to match the value of this parameter with the value of the SERVICE_NAME parameter in the client connect descriptor. If the client connect descriptor uses the SID parameter, then the listener does not attempt to map the values. This parameter is primarily intended for configurations with Oracle8 databases (where dynamic service registration is not supported for dedicated servers). This parameter may also be required for use with Oracle8i and later database services by some configurations.

The value for this parameter is typically obtained from the combination of the DB_NAME and DB_DOMAIN parameters (DB_NAME.DB_DOMAIN) in the initialization parameter file, but the value can also contain any valid name used by clients to identify the service.

When using a connect descriptor with a SERVICE_NAME parameter, ensure that any SID_DESC entry does not have the value GLOBAL_DBNAME.

Oracle Home Directory

ORACLE_HOME

The Oracle home location of the instance. Without this setting, the listener assumes its Oracle home for the instance.

On Linux and UNIX, this setting is optional.

On Microsoft Windows, this setting is ignored. The Oracle home specified by the ORACLE_HOME parameter in HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOMEID of the Microsoft Windows registry is used.

Not applicable

SID_LIST_listener_name

The section of the listener.ora file that defines the database served by the listener.

13.5.2 Configuring Static Service Information for the Listener

Learn how to statically configure database service information for the listener using Oracle Enterprise Manager Cloud Control.

Note:

If you are using connect-time failover or TAF, such as in an Oracle Real Application Clusters environment, then do not set the GLOBAL_DBNAME parameter.

  1. Access the Net Services Administration page in Oracle Enterprise Manager Cloud Control.

  2. Select Listeners from the Administer list, and then select the Oracle home that contains the configuration files.

  3. Click Go. You may be prompted to log in to the database server.

    The Listeners page appears.

  4. Select a listener, and then click Edit.

    The Edit Listener page appears.

  5. Click the Static Database Registration tab, and then click Add.

    The Add Database Service page appears. Enter the required information in the fields.

  6. Click OK.

    Note:

    You can also configure static service information with Oracle Net Manager. See Statically Configure Database Service Information in the online help for additional information.