On Monday, October 14, 2002, at 01:10 PM, Michael Peppler wrote:
> On Fri, 2002-10-11 at 14:27, Henri Asseily wrote: >> >> Regarding what I've dubbed DBIx::HA, here's the idea: >> >> There hasn't been up to now (or at least I haven't found any) a widely >> available Perl/DBI-based system for system architects who handle >> high-availability groups of servers, either in read-only load-balanced >> mode or read-write hot-backup mode. >> Oracle, Sybase and others do offer high-availability options, but they >> cost upward of $30,000 for a single implementation. In addition, I >> tested Sybase's OpenSwitch which does not cooperate properly with DBI, >> but that's a story for another day. > > That's almost certainly an issue with DBD::Sybase. It's probably not > handling (or passing) the proper connection attributes (at the C / > Sybase API level). > I agree. The behavior we saw was that DBD would talk to openswitch and get a properly working database handle, but when/if the db server died and/or openswitch would change the active server to another one, the dbh would be in a bad state, be dead and still point to the unavailable server. Somehow when openswitch does the handshake, DBD::Sybase takes it and goes straight to the db server that is pointed at. The only way right now to fix it is to ping the connect, and if unavailable, disconnect and reconnect. Henri.
