Re: FW: re: All RAC Nodes reboot without log-entry
Date: Wed, 23 Jan 2008 15:11:04 +0100
Message-ID: <47974AF8.4000004@gmx.de>
Hello,
The RAC is running since some days now without any reboot.
What we changed:
- the xntp deamon was not configured to slew the time but to step it
(thanks D'Hooge Freek). Although there was no step in time when the
reboots occured. Hm...
- the clusterinterconnect is running on a solaris IP multipathing
configuration: Everything was done like Metalink recommends. even so we
changed the second interface from "standby" to "active".
We are not sure which change did the trick, but it works now.
Regards, Björn
D'Hooge Freek schrieb:
> Björn
>
> I'm resending this email, because I noticed that I had only send it to the oracle-l list itself:
>
> Check if your ntp deamon is running and that is has been configured to not set the clock back in time, but instead slow the time by manipulating the "length" of a second.
> If the ntp deamon set the clock back in time, it can occur that the cluster layer notices that its current time is lower than the time of timestamps on disk (on the voting disks), and then thinks that is something wrong with the io paths. To safeguard your database against corruption it will then fail the node without trying to write any messages.
>
> I have seen this behaviour at a couple of client sites.
>
> Freek D'Hooge
> Uptime
> Oracle Database Administrator
> email: freek.dhooge_at_uptime.be
> tel +32(0)3 451 23 82
> http://www.uptime.be
> disclaimer
>
>
> ________________________________________
> From: D'Hooge Freek
> Sent: donderdag 17 januari 2008 22:22
> To: 'oracle-l'; oracle-l_at_freelists.org
> Subject: re: All RAC Nodes reboot without log-entry
>
> Check if your ntp deamon is running and that is has been configured to not set the clock back in time, but instead slow the time by manipulating the "length" of a second.
> If the ntp deamon set the clock back in time, it can occur that the cluster layer notices that its current time is lower than the time of timestamps on disk (on the voting disks), and then thinks that is something wrong with the io paths. To safeguard your database against corruption it will then fail the node without trying to write any messages.
>
> I have seen this behaviour at a couple of client sites.
>
>
> ------------------------------
>
> Date: Wed, 16 Jan 2008 17:01:53 +0100
> From: "bkaltofen_at_gmx.de" <bkaltofen_at_gmx.de>
> Subject: All RAC Nodes reboot without log-entry
>
> Hello,
>
> I'm facing the problem, that all my RAC nodes (2 Node Cluster 10.2.0.3
> on Solaris 10, Oracle CRS + ASM) reboot at the same time without any log
> entries in /var/etc/messages, /var/log/syslog and all log files under
> $ORACLE_CRS_HOME/log/...
>
> The cluster is a fresh installation. Any suggestions? Where can I look
> further?
>
> Kind regards,
> Björn
>
> ------------------------------
>
>
>
> Freek D'Hooge
> Uptime
> Oracle Database Administrator
> email: freek.dhooge_at_uptime.be
> tel +32(0)3 451 23 82
> http://www.uptime.be
> disclaimer
>
>
>
-- http://www.freelists.org/webpage/oracle-lReceived on Wed Jan 23 2008 - 08:11:04 CST