Oracle listener startup or stop failed.
[Case 1]
Oracle listener startup or stop fails when the PRIMECLUSTER RMS resource settings are invalid.
Check the following resource setup information by executing "clorainfo -c" command. Refer to "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. Refer to "Chapter 2 Environment Setup".
[Case 2]
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 manually. Refer to "3.2.4.1 Oracle must be stopped".
