Your database is open and the listener LISTENER is up. You issue the command:
LSNRCTL> RELOAD -
What is the effect of reload on sessions that were originally established by listener?
Your database is open and the listener LISTENER is up. You issue the command:
LSNRCTL> RELOAD -
What is the effect of reload on sessions that were originally established by listener?
Reloading the listener with the LSNRCTL RELOAD command refreshes the listener with the current information from the listener.ora file without stopping it. Existing connections are not affected by this operation and continue to function normally.
I hope this will help you study :) If the listener is running and modifications are made to the listener.ora file manually, with Oracle Net Manager or with Enterprise Manager, you must reload the listener to refresh the listener with the most current information. The reload command rereads the listener.ora file for the new definitions. As you can see, it is not necessary to stop and start the listener to reload it. Although stopping and restarting the listener can also accomplish a reload, using the reload command is better because the listener is not actually stopped, which makes this process more efficient. The following code shows an example of the reload command: LSNRCTL> reload listener1 Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=btlnx63)(PORT=1522))) The command completed successfully LSNRCTL>
c is correct