Why listener goes down

This should show the current status of the listener. If the listener is up and running, the problem may lie with the listener not having been associated with the correct instance or protocol.

To make sure all instances are correct, you can obtain basic information about the listener and the configuration settings by simple commands, such as the STATUS command. The status command will give basic information about the listener as well as the configured protocol addresses, summary of the services registered, and the service handlers allocated to each service. Below are descriptions of each status signals. If you are still unable to get the listener up and running, you may want to delete the listener and create a new one in the network configuration assistant.

The last possible cause may be a network problem. Check to see that there is a proper network connection if you find that the listener has been configured and is running correctly. Find centralized, trusted content and collaborate around the technologies you use most.

Connect and share knowledge within a single location that is structured and easy to search. I was creating a new database, while configuring the network configuration. Its showing the status of existing listener as down. Even though I ran the command lsnrctl start I am still getting the status as down.

How do I resolve this? Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? When the listener fails to establish connections, you can always find evidence of the problem in the listener log file. You can see the location of the listener log file by issuing the lsnrctl command from the UNIX prompt:.

Copyright c Oracle Corporation All rights reserved. ARRDVARK has 1 service handler s ecc1 has 1 service handler s sddp has 1 service handler s mwwa has 1 service handler s weer has 1 service handler s. The command completed successfully. To see if this log file contains errors, we can execute the following UNIX command:.

This command searches the listener log file for any entry with the string "ORA-". The "cat command says to print the file. With a password, privileged operations, such as saving configuration changes or stopping the listener, used from the Listener Control utility will require a password.

If the unencrypted password is not removed, you will be unable to successfully set an encrypted password. For Oracle9 i databases, the listener uses the dynamic service information about the database and instance it has received through service registration before using statically configured information in the listener. Dynamic service registration is configured in the database initialization file.

It does not require any configuration in the listener. However, listener configuration must be synchronized with the information in the database initialization file. To ensure service registration works properly, the initialization parameter file should contain the following parameters:. As long as the listener configuration is synchronized with the database configuration, PMON can register service information with a nondefault local listener or a remote listener on another node.

Synchronization is simply a matter of specifying the protocol address of the listener in the listener. Registration to remote listeners, such as in the case of Oracle Real Application Clusters, can be configured for shared server or dedicated server environments.

If you set the parameter to null with the statement that follows, then PMON de-registers information with the remote listener with which it had previously registered information. Configure the listener. Once the listener is configured, the listener can be administered with the Listener Control utility or Oracle Enterprise Manager.

This section describes some of the common administrative tasks for the listener, including the following topics:. In addition to starting the listener, the Listener Control utility verifies connectivity to the listener. Depending upon the current status of the selected listener, the operation will be either Stop or Start. Click OK to perform the operation. The status output provides basic status information about a listener, including a summary of listener configuration settings, the listening protocol addresses, and a summary of services registered with the listener.

The STATUS command provides basic status information about a listener, including a summary of listener configuration settings, the listening protocol addresses, and a summary of services registered with the listener. Displays a summary of the services registered with the listener and the service handlers allocated to each service.

Specifies the name of the instance associated with the service along with its status and number of service handlers associated with the service. Therefore, the status is non known. The SERVICES command of the Listener Control utility provides detailed information about the services and instances registered with a listener and the service handlers allocated to each instance.

The listener blocks all connections to this instance. Identifies the name of the service handler. Dispatchers are named D through D Following this, additional information about the service handler displays, such as whether the service handler is a dispatcher, a local dedicated server, or a remote dedicated server on another node. This output shows that two database services, sales. Client connection requests to sales. All handlers have a status of ready , indicating that they are ready to receive connections.