Re: Windows NT cluster fail over

I am assuming your need for clustering is resilience rather than performance ( by the fact that you refer to FailSafe and don't mention OPS).

If this is the case and you only need one or other side of the cluster to be active at any one time, then why not start/stop the listener as part of your failover process (presumably you are starting the database on Node B when it fails on Node A - why not include the listener at the same time?) If the clash is on IP/Port between the two listeners then this should resolve the problem.

Brian
<mikestreeton_at_my-deja.com> wrote in message news:7p8sjj$tlf$1_at_nnrp1.deja.com...
> I am running two NT servers running oracle 8.1.5. The servers form a
> cluster using microsoft clustering. We are not using Oracle failsafe
> and simply require a manual process for failing over the database
> application. The problem I have is with the Listener configuration on
> both machines I have set up the listener to listen for the cluster
> address, but this causes a clash and the current standby system cannot
> start the listener the active server is okay. I have thought about
> setting up each side to listen to different port address e.g. 1521 and
> 1526 and then map these in the client tnsnames.ora file. Will this work
> or are there better ways of getting the config set up?
>
> Many Thanks
>
> Mike
>
>
> Sent via Deja.com http://www.deja.com/
> Share what you know. Learn what you don't.
Received on Mon Aug 16 1999 - 09:39:29 CDT