Yes, this is expected behavior. When the resource or its monitor is enabled, the rgm moves the RG into PENDING_ONLINE state. So it tries to start all enabled resources, not just the one that you enabled most recently. Any one of those resources might fail to start and produce the message.
On 02/ 8/10 01:54 PM, Corrado Romano wrote: > Hi, > > thx for the answer. > Actually all the info I had were not directly taken by me but from a third > person who can access the server. > From the information I had the error seemed to be related to a totally > different misconfigured resource which didn't start (failure of START > method). Once this other resource has been corrected the error has > disappeared and the cluster now works as expected. > > Thk u very much > Ciao > Corrado >
