Re: rac cluster crashes

  • From: Mark Strickland <strickland.mark@xxxxxxxxx>
  • To: adar666@xxxxxxxxxxxx
  • Date: Tue, 21 Apr 2009 11:45:11 -0700

To enable VIP tracing, add the following in $CRS_HOME/bin/racgvip:

_USR_ORA_DEBUG=1
export _USR_ORA_DEBUG

I *believe *you'll find the resulting trace in

$CRS_HOME/racg/dump/ora.*nodename*.vip.trc

The output is cryptic, of course, but if the VIP is timing out, you'll see
it.

-Mark


On Tue, Apr 21, 2009 at 12:53 AM, Yechiel Adar <adar666@xxxxxxxxxxxx> wrote:

>  Where can I find the VIP trace file.
> My co-worker did an upgrade last night, on windows 64 bit from oracle
> 10.2.0.3. to 10.2.0.4 + the last CPU.
> I got called at midnight because the VIP did not work after the upgrade.
>
> When he went to bed, they changed the tnsnames to use physical address
> instead of vip and that is the way it is working now.
>
> Adar Yechiel
> Rechovot, Israel
>
>
>
> Mark Strickland wrote:
>
> This sounds kinda similar to what happened to us after upgrading from
> 10.1.0.3 to 10.1.0.5.  From my posting in 2006 about our Upgrade-from-Hell "
> //www.freelists.org/post/oracle-l/Upgrade-from-92-to-102-NONRac-Basic-Steps,2
> ":
>
> *[Oracle Support] was able to identify the cause of the problem in the VIP 
> trace file.  It was occasionally timing out while checking the
>
> default gateway.  The timeout threshold was 2 seconds and the engineer had us 
> change that to 10. *
>
>
> Perhaps this will help.
>
> -Mark
>
>

Other related posts: