Which command of Listener control utility (LSNRCTL) would you use to enable L1 process to start listening for the connections…?

You have a listener process, L1, currently listening for the connections to the PROD and ADMIN
databases. You create a new database, PAY, using CREATE DATABASE .. command. You have not
enabled dynamic instance registration. You modified the LISTENER.ORA file manually to include PAY
database for L1 listener process. Which command of Listener control utility (LSNRCTL) would you use
to enable L1 process to start listening for the connections to the PAY database without disrupting
any existing database communications?

You have a listener process, L1, currently listening for the connections to the PROD and ADMIN
databases. You create a new database, PAY, using CREATE DATABASE .. command. You have not
enabled dynamic instance registration. You modified the LISTENER.ORA file manually to include PAY
database for L1 listener process. Which command of Listener control utility (LSNRCTL) would you use
to enable L1 process to start listening for the connections to the PAY database without disrupting
any existing database communications?

A.
START

B.
RELOAD

C.
RESTART

D.
REFRESH

E.
START L1

F.
RELOAD L1

G.
RESTART L1

H.
REFRESH L1



Leave a Reply 1

Your email address will not be published. Required fields are marked *


jean

jean

RELOAD L1 – Reload the listener, to re-read the listener.ora file, but does not close the listener (without disrupting any existing database communications) . If the file has changed, it will refresh the listener.

You can view and change parameter settings. The basic syntax of Listener Control utility commands is as follows: lsnrctl command

Dynamically register – no need to modify listener.ora.
DB Instance will automatically notify the listener.

If you configure sid_llist in listerer.ora in that static registered.

Because the static registration parameters is manually add static, regardless of the database. The database can not confirm whether the listener is configured correctly.
Therefore, lsnrctl status display in the status unknown.

That does not guarantee connectivity database. Note: static registration monitoring, global database name in the configuration tnsnames.ora client service naming, “(Oracle 8i or later) Service Name” in completing the static content to be registered with the server listener when consensus.

Otherwise, it can not be connected —

RELOAD L1 – Reload the listener, to re-read the listener.ora file, but does not close the listener (without disrupting any existing database communications) . If the file has changed, it will refresh the listener.