Frank,
Get in a huddle with your DBA over this. My understanding is that when database 1 fails, database 2 becomes the primary and stays the primary until some event happens to reset the system back to your original configuration. However, there are a number of configurations you and your DBA can cook up together, considering that you have 3 databases, so that you are always covered. ________________________________ From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Frank Caruso Sent: Thursday, January 08, 2009 11:02 AM To: [email protected] Subject: Sybase Database Connections ** We are going to run 3 Sybase databases in our new ARS environment. There are two ARS hosts running 7.1p3 on Solaris 9. I am trying to figure out how ARS handles database connections from the point of a failover situation. Our Sybase interface file has all three database hosts defined, wth the first one listed as the primary. When ARS starts it grabs the the database Server-Name from the conf file and makes connections to that database. It will continue to create connections as needed up to the max amounts defined. If the current database crashes (goes off line, whatever) and ARS cannot connect will it try to use the next database listed in the Sybase interface file? I understand that users will probably get connection errors but what I was hoping was that ARS would play nice with the Sybase openclient and just try to use the next database listed. My other concern is that if ARS does try to use the other database, and makes connections, and then the primary database comes back online that we could get connections to 2 different databases. Any thoughts are appreciated. Thank you Frank __Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are" html___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are"
