Hello experts,

We have setup SuSE Hawk Cluster between 2 LINUX server nodes, and we have a problem in one of the node. Oracle 12c Database is protected by the cluster. The issue is exactly after 30 days node A moves the Database to node B at 3AM CET, when we check the logs it looks like the Oracle Listener is stopped by oracle user and the same user is trying to start back the listener but it fails to do so and hence the cluster does a failover of the application to Node B and reboots Node A. When we check the Oracle logs we are not able to find any clue on why the listener was shutdown. If anyone has seen this kind of behavior please help us with some details.

Details:
Operating System : SLES 11 SP4 with latest patch level
Cluster software : SLES High Availability Extension
Cluster Type : Active - Passive
Resource Policies : Failover to next priority node and no fail back to home node.
Oracle 12c Release 1.

Thanks.

Regards,
Yoganand.V

Have never seen this, but this is what I'd do:

Check crontabs for root and oracle user
Check system cron jobs /etc/cron.*/*
Check logrotate jobs /etc/logrotate.d/*
Check the system access log /var/log/secure

Output of "crm status" and "crm configure show" will help to understand your current status and cluster configuration.