Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Oracle Data Guard Question
- Thread starter olemma
- Start date
- Thread starter
- #2
Anyone???? I add more info:
In case of switchover or failover, we definitely want it to be as transperent as possible to the apps. Most of our apps are using jdbc connections, a few the OCI api. I guess the best solution will be the the first: connect time failover in the tnsnames.ora, correct?
Possible solutions:
were you going to use connect time failover in the tnsnames.ora? - possibly
or update a LDAP repository? - no
or use a "big ip" type of front end load balancer? - not likely
or take over the failed machines IP address on the new machine? - this will involve manual changes
Will this sample tnsnames.ora solve my issue? Will have to make sure to copy a similar string to all client tnsnames.
sales.us.acme.com=
(DESCRIPTION=
(ADDRESS_LIST=
(LOAD_BALANCE=off)
(FAILOVER=ON)
(ADDRESS=(PROTOCOL=tcp)(HOST=sales1-server)(PORT=1521))
(ADDRESS=(PROTOCOL=tcp)(HOST=sales2-server)(PORT=1521)))
(CONNECT_DATA=(SERVICE_NAME=sales.us.acme.com)))
I have a question about this tnsnames.ora entry. Let say a failover occured, and all new and existing connections are routed to sales2-server will sales1-server is being fixed and brought back up. After sales1-server is brought back up and sync'ed...it will become the stand-by instance. New connections and even exising connections will still have to connect to sales2-server, the new primary. Is this possbile with the above connect string? or should there be a swithover right after sales1-server is sync'ed?
In case of switchover or failover, we definitely want it to be as transperent as possible to the apps. Most of our apps are using jdbc connections, a few the OCI api. I guess the best solution will be the the first: connect time failover in the tnsnames.ora, correct?
Possible solutions:
were you going to use connect time failover in the tnsnames.ora? - possibly
or update a LDAP repository? - no
or use a "big ip" type of front end load balancer? - not likely
or take over the failed machines IP address on the new machine? - this will involve manual changes
Will this sample tnsnames.ora solve my issue? Will have to make sure to copy a similar string to all client tnsnames.
sales.us.acme.com=
(DESCRIPTION=
(ADDRESS_LIST=
(LOAD_BALANCE=off)
(FAILOVER=ON)
(ADDRESS=(PROTOCOL=tcp)(HOST=sales1-server)(PORT=1521))
(ADDRESS=(PROTOCOL=tcp)(HOST=sales2-server)(PORT=1521)))
(CONNECT_DATA=(SERVICE_NAME=sales.us.acme.com)))
I have a question about this tnsnames.ora entry. Let say a failover occured, and all new and existing connections are routed to sales2-server will sales1-server is being fixed and brought back up. After sales1-server is brought back up and sync'ed...it will become the stand-by instance. New connections and even exising connections will still have to connect to sales2-server, the new primary. Is this possbile with the above connect string? or should there be a swithover right after sales1-server is sync'ed?
- Status
Similar threads
- Question
