Re: Session distribution on 9i RAC

Steffen Roegner wrote:

> Howard,
>
> We are talking about one node out of that I want to prevent from
> registering with remote listeners here.

I understand that. It's called a 'spare node configuration', and as I said, the only way to do it when instances are > 2 is to not set the remote_listener parameter for the spare node(s) (and also make sure no client tnsnames.ora files make reference to the spare node(s) directly, of course).

In other words, you can make a spare node either by feeding it useless and incorrect information about where, remotely, to register (which is what you did). Or you can not give it any information about remote locations at all (which is what I was trying to say was the better way of proceeding).

> I have LOCAL_LISTENER set to
> sth. like LISTENER_NODE4 as this is the regarding entry in the local
> tnsnames.ora.

Local_listener is irrelevant to the matter at hand. I only mentioned it last time because it gets policed: set it to some value XXX, and if the local tnsnames.ora cannot resolve XXX into a valid host and port, the instance cannot start.

Remote_listener, *at the moment*, does NOT work like that: you can (and have done, if I read your last post correctly) set remote_listener to complete nonsense. That has the same effect as not setting it at all (because the spare node doesn't now know how to find the other listeners to register with), but it is not strictly kosher.

> What would be an appropriate entry in REMOTE_LISTENER?

Null.

> I do not want the instance to remotely register and the value is
> supposed to be a 'network_name' so I think it has to remain empty right?

It's an optional parameter. It's therefore legitimate to leave it null. And that's the correct entry to make when registration with non-local listeners is to be stopped.

Regards
HJR Received on Sun Aug 22 2004 - 15:11:23 CDT