Edit the listener.ora file to remove the lines added above and restart the listener as follows: That's it!, you should always protect your listener with a password.
With a listener password, nothing can be done to any of your listeners except by someone who knows your password. To set a listener password, use the change_password command in listener control: $ lsnrctl. The fist time you do this, no password is set, so just press return when you are asked for the existing password. Once that has been done, you have to specify the password before attempting most listener operations. Without a listener password set, any ‘oracle’ account on any machine (even a client) can stop and change listeners on any other machine on your network, including production servers. So, running a command like this from a dev box as the oracle userid: $ lsnrctl stop liveserver. Use the Listener Control utility's CHANGE_PASSWORD command or Oracle Net Manager to set or modify an encrypted password in the PASSWORDS_ listener_name parameter in the listener.ora file. [ listener_name ]: Specify the listener name, if the default name of LISTENER is not used. Usage Notes. When SET CURRENT_LISTENER is set, the Listener Control utility commands act on the listener you set. You do not have to specify the name of How to set the Oracle database listener password. Setting an Oracle listener password in clear text. The listener password can be set in clear text as follows: (It should be noted that it is possible to set more than one listener password in this way.). Open the $ORACLE_HOME/network/admin/listener.ora file and locate the name of your listener. For instance my listener has the default name LISTENER. Should you want to remove the listener password do the following: Edit the listener.ora file to remove the lines added above and restart the listener as follows: That's it!, you should always protect your listener with a password. By default the listener comes with no password, and anyone can change listener settings through the lsnrctl tool. In Oracle 9i, any computer on your network can stop your listener in the blink of an eye if you do not password protect it. First, a point on passwords. If you have done all of this correctly, you will see the following: Just as a note, if the listener you are protecting does not have the default name of LISTENER, you must do before issuing the change_password command. At this point, save the configuration of the listener to the file system. If you are on 10g, it will save with no problems: And you have a password protected listener. However, this does not happen on 9i. If you perform a save_config, you will see the following: Oops! The reason is this: in Oracle 10g, operating system authentication for the listener has been implemented. If you have done all of this correctly, you will see the following: Just as a note, if the listener you are protecting does not have the default name of LISTENER, you must do before issuing the change_password command. At this point, save the configuration of the listener to the file system. Hence, using command sc command we can delete listener service from windows service controller and registry. It is also safer way to delete listener service using command line sc program. It is very usefull command option when we are not using GUI tools or absent of Oracle software. Problem: How to delete listener on Windows Manually: Sometimes we are not using GUI tools in remote Oracle dba support due to bandwidth problem or security related risks. Managing listener utilities in unix environment is easy to use command line. Just as a note, if the listener you are protecting does not have the default name of LISTENER, you must do before issuing the change_password command. At this point, save the configuration of the listener to the file system. If you are on 10g, it will save with no problems: And you have a password protected listener. By default the listener comes with no password, and anyone can change listener settings through the lsnrctl tool. In Oracle 9i, any computer on your network can stop your listener in the blink of an eye if you do not password protect it. Listener security. The first thing to do is to put a password on your listener. By default the listener comes with no password, and anyone can change listener settings through the lsnrctl tool. In Oracle 9i, any computer on your network can stop your listener in the blink of an eye if you do not password protect it. To password protect your listener, perform the following as your Oracle user: If you have done all of this correctly, you will see the following: Just as a note, if the listener you are protecting does not have the default name of LISTENER, you must do before issuing the change_password command. At this point, save the configuration of the listener to the file system.
http://andrewfraserdba.com/2007/05/24/listener-passwords-always-for-9i-never-for-10g/ http://docs.oracle.com/cd/B19306_01/network.102/b14213/lsnrctl.htm http://www.petefinnigan.com/ramblings/set_listener_password.htm http://www.dba-oracle.com/t_listener_password_security_lsnrctl.htm http://www.dba-oracle.com/t_listener_password_security_lsnrctl.htm https://www.dbametrix.com/delete-listener-windows.html http://www.orafaq.com/node/567 http://www.orafaq.com/node/567 http://www.dba-oracle.com/t_listener_password_security_lsnrctl.htm
how to remove oracle listener password