A listener resource has entered Warning.
[Case 1] (Standby Operation, Scalable Operation with Oracle RAC)
A listener resource enters Warning when listener monitoring is discontinued.
Check the monitoring status by executing the “clorainfo -m” command. Refer to “4.6 clorainfo - Display Resource Configuration and Monitoring Status”.
If listener monitoring has been discontinued, check if the listener has been activated then restart monitoring. Refer to “4.2 hvoraenable - Restart Monitoring Resources”.
[Case 2] (Standby Operation)
In listener monitoring using the tnsping command of the Oracle, when constant time did not have the reply of the tnsping command, the resource enters Warning (WatchTimeout).
If the following error message is output to syslog, you can confirm the cause of this problem: “ERROR: 0226: Watch Timeout occurred”
Check the listener log, and investigate and handle it.
In listener monitoring of PRIMECLUSTER Wizard for Oracle, if there is no reply from tnsping within a specified time, monitoring timeout will be considered. At the first monitoring timeout, the resource will only enter Warning, however, if it occurs twice in a row, a resource failure will be determined.
[Case 3] (Scalable Operation with Oracle RAC)
The monitoring of listener resource becomes failure when setting of WFTime is the followings, the resource state enter Warning until it is recovered by Oracle Clusterware.
[PersistentWarning]
[<second>]
It is possible to check setting of WFTime by the “clorainfo -c” command. (For detail of “WFTime”, refer to step 16 of “2.3.5 userApplication with Oracle RAC Instances and Listeners”).
Check whether the cause of resource failure is reported referring to the listener log or log files.
