Oracle listener startup or stop failed.
[Case 1] (Standby Operation, Scalable Operation with Oracle RAC, Single-Node Cluster Operation)
Oracle listener startup or stop fails when the PRIMECLUSTER RMS resource settings are invalid.
Check the following resource setup information by executing the “clorainfo -c” command. See “4.6 clorainfo - Display Resource Configuration and Monitoring Status”.
Oracle user name
Listener name
TNSName (net service name)
Scripts (e.g. PreOnlineScript)
A correct path must be set.
The script must have execution permission.
The script must behave correctly.
If your setup information is incorrect, set proper values again. See “Chapter 2 Environment setup”.
[Case 2] (Standby Operation, Single-Node Cluster Operation)
Oracle listener startup or stop fails when the listener settings such as IP address and port number are incorrect.
Check listener logs, so you might be able to detect the cause of the failure.
Check if the settings of listener.ora are correct.
Also, check if the listener can be started or stopped properly. If you discontinue Oracle instance resource monitoring, you can operate Oracle database manually. See “3.2.4.1 Oracle database must be stopped”.
[Case 3] (Scalable Operation with Oracle RAC)
When starting userApplication with listener resource in the state where Oracle Clusterware is not running, the resource state enters Warning until exceeds the time set as ScriptTimeout (refer to step 16 of “2.3.5 userApplication with Oracle RAC Instances and Listeners”). If it exceeds the time set as ScriptTimeout with the resource state maintain Wait, the resource state will enter Faulted.
Execute the following methods according to each pattern.
In the case of configuration that the Oracle Clusterware and Oracle RAC instance are registered in different userApplication. (It matches “Configuration A” in “2.3.3 userApplication and Resource Configuration”.)
At first, check whether Oracle Clusterware is running.
The following command execution, you can check whether Oracle Clusterware is running.
# su - <Grid user> $ crsctl status resource
When the following message is outputted, Oracle Clusterware may be not running.
CRS-0184: Cannot communicate with the CRS daemon.
When Oracle Clusterware is not running, there is a possibility that the setting that Oracle Clusterware starts earlier than Oracle RAC Instance is incorrect.
Check whether the script which starts Oracle Clusterware resource is set as the PreOnlineScript of Oracle RAC Instance (refer to “note” of step 10 of “2.3.5 userApplication with Oracle RAC Instances and Listeners”).
In the case of configuration that the Oracle Clusterware and Oracle RAC instance are registered in the same userApplication. (It matches “Configuration B” in “2.3.3 userApplication and Resource Configuration”.)
There is a possibility that starting of listener resource is failed.
Check whether you have no mistakes in setting of listener resource (“2.3.5 userApplication with Oracle RAC Instances and Listeners”).
In addition, check whether you have no mistakes in setting of listener (refer to “Case 2”).
In the case of configuration that the Oracle Clusterware is not registered. (It matches “Configuration C” in “2.3.3 userApplication and Resource Configuration”.)
Check whether Oracle Clusterware is running.
The following command execution, you can check whether Oracle Clusterware is running.
# su - <Grid user> $ crsctl status resource
When the following messages are outputted, Oracle Clusterware may be not running.
CRS-0184: Cannot communicate with the CRS daemon.
Clear Faulted state of the resource, after that, execute the following commands and start Oracle Clusterware.
# <Grid user's $ORACLE_HOME>/crsctl start crs
After that, start userApplication.
