Hi again, I have a prod and a dev resource group as suggested below. The version I have uses the RGOffload resource type.
What I would like to do, however, is just shutdown the resources on the second node rather then try and move them off. The RGOffload will not offload if it fails so although the function is what I'm looking for, I want it to leave offline if it can't relocate. The scenario is if prod hardware failed, it can come up on the dev hardware and if dev is running, offline it so the resources are available to prod. Right now, if it cannot move dev, it fails the whole thing. This causes a deadlock and production down scenario - as it just happened this morning - go figure. Norm Dressler On Fri, 2007-14-12 at 14:46 +0100, Thorsten Frueauf wrote: > Hi Norm, > > I am assuming that you have at least two resource groups configured - > one for the production resources, and one (or even two) for your test > and development resources. > > If so, then you can use the strong negative affinity in order to offload > the test/dev resource group, before it is getting started on the > secondary node. > > The RG_affinities property for resource groups got introduced with SC > 3.1 U3. > > If you are running an earlier update of SC 3.1 you may use the RGOffload > resource type (obsolted by affinities). > > See > http://docs.sun.com/app/docs/doc/819-2974/ch14_resources_admin-42?a=view > for more details on affinities. > > See > http://docs.sun.com/app/docs/doc/819-0582/6n30g7ilc?l=en&a=view&q=RGOffload > to see the manpage for SUNW.RGOffload. > > Greets > Thorsten > > Norm Dressler wrote: > > I have a 2 node cluster running various Oracle schemas. > > > > With a recent upgrade, we have determined we can no longer run three of our > > environments on the backup server. > > > > Example, primary server runs production, secondary runs test and dev. > > > > In a failover situation, production should failover to the secondary. > > However, the secondary does not have sufficient resources to allow it to > > start. > > > > The solution is to shut down test prior to failing over. This must happen > > before Oracle tries to start on the secondary server. The scripts used to > > start Oracle are the same across the environments and the only difference > > is the SID. > > > > We also use data storage resources and it has the the ability to set the > > RunBeforeStartMethod parameter and since it is one of the first items to > > fail over, I thought I found my solution but unfortunately it did not run > > the script I wrote to shutdown test - the script consisted of scswitch > > commands. > > > > Does anyone know of a way to stop a resource on the secondary server prior > > to a resource failing over to it? > > > > Thanks for any assistance. > > > > Norm >
