Clusterware not starting a db resource after failing to stop the resource....
Hello all, first time posting here
I came across an issue recently where we had timeouts in the agent which checks the status of the ASM diskgroup resources e.g.
2013-12-28 23:31:38.844: [ AGFW][3967694592] {0:7:48} Received state change for ora.DATA.dg <hostname> 1 [old state = ONLINE, new state = UNKNOWN]
After this the cluster decided the take dependant dbs offline. There are 2 instances and it successfully stopped 1 but timed out (1 minute) stopping the other.
(I should probably increase this timeout). Anyway, after the stop failed, it did a resource clean (shutdown abort) successfully.
The issue is that the cluster didn't attempt to start the resource after doing a "clean" even though restart_attempts=1
I came across an issue recently where we had timeouts in the agent which checks the status of the ASM diskgroup resources e.g.
2013-12-28 23:31:38.844: [ AGFW][3967694592] {0:7:48} Received state change for ora.DATA.dg <hostname> 1 [old state = ONLINE, new state = UNKNOWN]
After this the cluster decided the take dependant dbs offline. There are 2 instances and it successfully stopped 1 but timed out (1 minute) stopping the other.
(I should probably increase this timeout). Anyway, after the stop failed, it did a resource clean (shutdown abort) successfully.
The issue is that the cluster didn't attempt to start the resource after doing a "clean" even though restart_attempts=1
0