Re: Failover for Network disconnect.

I'm guessing you already did this, but the client machine needs to have a modified tnsnames.ora which recognizes the primary and secondary instances. This has to specify a failover strategy.

Also, we found in using jdbc connections, that the client will need to be modified. We tested this with sqlplus on the client side. After returning an error, we then had to automatically retry the connection, which then went to the secondary instance.

You may find it easier to just turn off the network connection with "ifconfig" if the machine is remote, than by removing the network cable. Of course, you'll need a "tip" connection to the machine to reenable it for the next test.

Check http://technet.oracle.com and go to the documentation section. There are good examples on TAF in the 8i OPS, Network and Oracle Addendum sections. The OPS book in particular has a primary and secondary tnsnames.ora.

-Dirk

Sam He wrote:
>
> Hi, all
>
> I'm using oracle OCI to access database. The database connection can be
> transfered to backup database from primary database when primary database
> shutdown gracefully. The primary and backup database are just seperate
> database, not parallel servers. The problem is when I tried to get the same
> result when the network cable of the primary database machine was
> disconnected, it seems that the OCI statement was stuck there. I even
> couldn't get the OCI error. I also tested the socket communication by
> running two simple code on two Unix machines. When one of machines' cable
> is pull out, the socket will report error after 9 minutes. Maybe this is why
> OCI couldn't give us error response when cable disconnect. I guess OCI
> should have seeeion timeout, but I didn't find how to configure.
> If you guys give me some idea, thank you in advance.
>
> Sam He
Received on Tue Mar 20 2001 - 14:44:43 CST