oracle listener error times out

[raunaz]

Hi All, 

We are experiencing VCS warning messages saying Oracle listener resource has mied out. It has happened for few times. 

But we found the system is working fine and no issue. And at the same time the CPU usage is quite high.

The question here is how we can confirm the high CPU that caused the time out issue. 

The VSC version is 4.o and here are the setting of the resource.

hatype -display Netlsnr

#Type        Attribute              Value

Netlsnr      ActionTimeout          40

Netlsnr      AgentClass             TS

Netlsnr      AgentFailedOn

Netlsnr      AgentPriority          0

Netlsnr      AgentReplyTimeout      130

Netlsnr      AgentStartTimeout      60

Netlsnr      ArgList                Owner Home TnsAdmin Listener EnvFile MonScript LsnrPwd AgentDebug Encoding

Netlsnr      AttrChangedTimeout     60

Netlsnr      CleanTimeout           60

Netlsnr      CloseTimeout           60

Netlsnr      ConfInterval           600

Netlsnr      FaultOnMonitorTimeouts 4

Netlsnr      FireDrill              0

Netlsnr      InfoInterval           0

Netlsnr      InfoTimeout            30

Netlsnr      LogDbg

Netlsnr      LogFileSize            33554432

Netlsnr      MonitorInterval        60

Netlsnr      MonitorStatsParam      Frequency 0 ExpectedValue 100 ValueThreshold 100 AvgThreshold 40

Netlsnr      MonitorTimeout         60

Netlsnr      NumThreads             1

Netlsnr      OfflineMonitorInterval 300

Netlsnr      OfflineTimeout         300

Netlsnr      OnlineRetryLimit       0

Netlsnr      OnlineTimeout          300

Netlsnr      OnlineWaitLimit        2

Netlsnr      OpenTimeout            60

Netlsnr      Operations             OnOff

Netlsnr      RestartLimit           0

Netlsnr      ScriptClass            TS

Netlsnr      ScriptPriority         0

Netlsnr      SourceFile             ./OracleTypes.cf

Netlsnr      SupportedActions       VRTS_GetInstanceName VRTS_GetRunningServices

Netlsnr      ToleranceLimit         0

[Elvis_L_]

Hi raunaz,

it appears you're having same problem as I am looking. I found this here, but I don't know how viable is the root cause and solution. please check this out.

http://www.rimserv.com/2010/07/vcs-netlsr-agent-unable-to-monitor.html

btw, is your engine_A.log reports anything on the Netlsnr timeout?

[Marianne · Accepted solution]

You can increase the MonitorTimeout (current value is 60 sec).

Before you do that, please see this recommendation in the VCS User Guide:

For best results, VERITAS recommends measuring the time it takes to bring a resource online, take it offline, and monitor before modifying the defaults. Issue an online or offline command to measure the time it takes for each action. To measure how long it takes to monitor a resource, fault the resource and issue a probe, or bring the resource online outside of VCS control and issue a probe.

You will need to do this during high CPU usage.