RE: ASM in a Veritas Cluster Software environment

From: Matthew Zito <mzito_at_gridapp.com>
Date: Fri, 15 May 2009 14:50:04 -0400
Message-ID: <C0A5E31718FC064A91E9FD7BE2F081B1020BFD36_at_exchange.gridapp.com>



It'll work fine, just make sure the ASM instance is configured in the resource group as well, and add it as a dependent resource for the Oracle instance. Your failover time will be increased, obviously, as you will have to wait for ASM instance to start before VCS can start up the database.

There doesn't seem to be a huge advantage to using ASM in this config, though, since you could easily put the data on a cooked filesystem on top of an LVM, which would give you the disk concatenation.

Thanks,
Matt

-----Original Message-----

From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Lou Avrami Sent: Friday, May 15, 2009 2:43 PM
To: oracle-l_at_freelists.org
Subject: ASM in a Veritas Cluster Software environment

Hello all,

I've been assigned to build a data warehouse-type database on an Itanium server running HPUX 11.23. This server is currently the passive side of a Veritas Cluster active-passive configuration. RDBMS version 11.1.0.7 will be used. RAC will not be used. The idea is that if one of the servers goes down, the database will be migrated to the active server and started up by the cluster.

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?

Can anyone tell me if this will work or not? If so, any links to documentation would be greatly appreciated.

Thanks,
Lou Avrami

--

http://www.freelists.org/webpage/oracle-l

--

http://www.freelists.org/webpage/oracle-l Received on Fri May 15 2009 - 13:50:04 CDT

Original text of this message