Thank You agent.kgb,
very interesting post, I checked the link which you have posted
Quote:
if you set the clock backwards while clusterware is running, the monitoring processes of clusterware processes fail, since they "think" they detected a scheduling problem of the root processes.
This will lead to a node reboot.
Hence stop clusterware before changing the clock.
It appears, in my case, that someone played with the time, intentionally, otherwise how would this happen? RAC has been running for 3 years and it never happened, suddenly it happens and that too, 2 hours difference.
Now, I will have to find out if time was changed on the AIX by user.