RE: ASM in a Veritas Cluster Software environment
Date: Fri, 15 May 2009 17:57:30 -0400
You don't want to do any of that. Just configure the ASM instance to be shut down as part of the failover. That will clean everything up. Then it will be started up on the destination node, and the diskgroups mounted automatically.
-- Matthew Zito Chief Scientist GridApp Systems P: 646-452-4090 mzito_at_gridapp.com http://www.gridapp.com -----Original Message----- From: oracle-l-bounce_at_freelists.org on behalf of Rajeev Prabhakar Sent: Fri 5/15/2009 5:53 PM To: avramil_at_concentric.net Cc: oracle-l_at_freelists.org Subject: Re: ASM in a Veritas Cluster Software environment Hello Lou, Please ensure that the resource switchover/failover procedures take care of the dismounting and mounting of appropriate diskgroups on the relevant environments (going-to-be-passive and going-to-be-active node). So, no dangling file descriptors (howsoever remote a possibility ) or anything that prevents exclusive access to those disk groups on the surviving node). -Rajeev On Fri, May 15, 2009 at 2:42 PM, Lou Avrami <avramil_at_concentric.net> wrote:Received on Fri May 15 2009 - 16:57:30 CDT
> Hello all,
> I suggested that we use Automatic Storage Management, but the UNIX/storage admins seem to feel that this is not compatible with VCS. Personally I would think that it shouldn't really matter whether the database is using ASM or not. If VCS can move the diskgroups from one server to another, then it be fine. Perhaps assuming that ASM diskgroups can be included in a VCS failover configuration is presumptuous?
-- http://www.freelists.org/webpage/oracle-l -- http://www.freelists.org/webpage/oracle-l