Re: Can SQLNET client contain multiple IPs for a single SID??

I have several OPS clusters defined just like this, but I use the same SID on each node.

Another way to get around your problem is to have two listeners defined on each node such that only one is "active" under normal operating conditions. When you have an IP takeover event, the surviving node then starts its "other" listener, which would "listen" on the new IP address for that node  on a separate adapter ) and contain the proper SID_LIST for the listener.

This is the method I use.

-Kevin

--

remove the x for an email reply
Dicky wrote in message <01bdab54$29f53420$01011fb4_at_steve>...
>Hi everybody, who can tell me the way that a SQLNET client entry
>(tnsnames.ora) can contain more than one IP for a single SID for redundant.
> My OPS system is built on two machines which concurrently sharing files on
>a set of external harddisks. Each machine has its own SID, for instance,
>SID1 and SID2, respectively. And both of them have capable of taking over
>each other's IP when either of one go down. Based on the above design,
>end-users using SQLNET client are divided into two group -- Group A
>connects to the first machine (SID1) and Group B connects to the second
>machine (SID2). Everything goes fine except in the case of IP takeover
>between machines happens. If the first machine go down, the second machine
>takes over the first machine's IP, and then tries to provide same services
>as the first machine. Group A users even can "tnsping" their SQLNET alisa
>for the first machine, but can't connect to the database anyway because the
>SID in the tnsname file doesn't match the SID on the second machine. What
>can i do??
>
>Thanks in advance!
>
>Dicky
Received on Mon Feb 08 1999 - 12:20:10 CST