on 8/26/03 3:24 PM, Mladen Gogala at [EMAIL PROTECTED] wrote:
Well, that is because of your understanding of the word "failover". Don't be confused, there are other words
in desperate need of redefinition, too. One of them is "unbreakable".
To make the long story short, "FAILOVER=ON" makes possible for Oracle*Net to skip the non-functioning
TNS descriptor, not that the application should simply fail over and continue from another node. The application
will simply fail, without the desired "over", unless it's written using OCI, which is the only means for an
application to resume on one of the surviving nodes. In other words, it is the TNS descriptor that "fails over",
not your application. I hope that things are clearer now.
--
Mladen Gogala
Oracle DBA
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of laura pena
Sent: Tuesday, August 26, 2003 5:49 PM
To: Multiple recipients of list ORACLE-L
Subject: RAC - setting up failover and load_balance
So I have RAC setup ( Solaris 2.8 , Veritas DBE/AC 3.5 MP1 and HDS disks if you are interested) and I am attempting to setup my failover and loadbalancing from a client.
I brought down VLDBN1
and Thought I should fail over to VLDB2 ... but I did not.
Here is what I have in my tnsnames.ora:
VLDB =
(DESCRIPTION =
(FAILOVER=ON)
(LOAD_BALANCE = yes)
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 10.10.250.25)(PORT = 1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = 10.10.250.26)(PORT = 1521))
)
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = VLDBN2)
(FAILOVER_MODE=
(BACKUP=SECONDAY)
(TYPE=select)
(METHOD=basic)
(RETRIES=5)
(DELAY=5)
)
)
)
SECONDARY =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 10.10.250.26)(PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = VLDBN2)
)
)
Any ideas?
