Dynamic Registration of Oracle Listener

Static registration is used before Dynamic Registration of Oracle Listener. The so-called static registration refers to reading listener when an Oracle instance is started. the configuration in ora is then registered to Listener. It has two main disadvantages:

1. Listener does not know the real-time status of the Oracle instance

2. The configuration in listener. ora is troublesome and needs to be modified manually.

Dynamic Registration

Dynamic Registration means that after an Oracle instance is started, the instance status and parameters (instance_name, service_name) are synchronized to the Listener in real time through the pmon process. If the instance_name parameter is null, the default value is SID. If service_name is null, the default value is db_name.db_domain.

With dynamic registration, we do not even need listener. ora. At this time, the command lsnrctl start will start the default Listener (TCP protocol, port 1521, Service and Instance are from service_name and instance_name respectively.

Here is a small tip: pmon does not actually synchronize the Oracle instance to the Listener in real time, but every several dozen seconds, but you can use the alter system register command to manually synchronize.

Here is an example:

In this example, listener. ora is not configured and the status after listener. ora is started is as follows:

STATUS of the LISTENER
------------------------
Alias LISTENER
Version TNSLSNR for Linux: Version 11.2.0.1.0-Production
Start Date 18-SEP-2013 16:58:01
Uptime 0 days 0 hr. 12 min. 54 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Log File/opt/oracle/diag/tnslsnr/data/listener/alert/log. xml
Listening Endpoints Summary...
(DESCRIPTION = (ADDRESS = (PROTOCOL = tcp) (HOST = 192.168.1.15) (PORT = 1521 )))
Services Summary...
Service "orcl. localdomain" has 1 instance (s ).
Instance "orcl", status READY, has 1 handler (s) for this service...
The command completed successfully

The instance_name and service_names parameters are configured as follows:

SQL> show parameter instance_name

NAME TYPE VALUE
-----------------------------------------------------------------------------
Instance_name string orcl
SQL> show parameter service_name

NAME TYPE VALUE
-----------------------------------------------------------------------------
Service_names string orcl. localdomain

From the above, we can find that the Service and Instance in Listener correspond to the instance_name and service_names parameters. Specifically, the service_names parameter can specify multiple service_names separated by commas.

In client tnsnames. ora, we can set SID to instance_name:

Test =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP) (HOST = 192.168.1.15) (PORT = 1521 ))
)
(CONNECT_DATA =
(Sid = orcl)
)
)

You can also set service_name to be equal to any of services_names:

Test =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP) (HOST = 192.168.1.15) (PORT = 1521 ))
)
(CONNECT_DATA =
(Service_name = orcl. localdomain)
)
)

Dynamic Registration and static registration of Oracle listeners

Static registration and Dynamic Registration of Oracle DBA listeners

Dynamic Registration and static registration of Oracle Listener

Linux/Unix shell monitoring Oracle Listener (monitor Listener)

One Oracle instance is configured with multiple Listener or multiple ports

1 2 Next Page