I've been tasked with making our Oracle db (used primarily as a DB back end for web applications) function within a disaster recovery plan now that we actually have hardware at a second site to do disaster recovery (other than 'Go buy a new server and restore it from backup' :-)
I'm planning to use Oracle's Data Guard to manage the db backend, which seems quite straightforward, but my question is about managing failover (what Oracle calls TAF) >From what I'm reading ><http://search.cpan.org/~pythian/DBD-Oracle-1.74/lib/DBD/Oracle.pm#TAF_(Transparent_Application_Failover)> DBD::Oracle uses the tns entry for TAF: eg: (FAILOVER_MODE= (TYPE=select) (METHOD=basic) (RETRIES=10) (DELAY=10)) Am I right in thinking that since each time a script is called it creates a handle, does its thing, then ends, in the event of a failure, the, each call of the script will take over 100 seconds to fail over, given the above settings? Therefore, to take advantage of TAF I'd have to utilize persistent DBI handles (using, for example, Apache::DBI <http://perl.apache.org/docs/1.0/guide/databases.html>) and once the first call to a failed instance takes 100 seconds to fail over, the $dbh will then talk to the backup server thereafter? -- Bruce Johnson University of Arizona College of Pharmacy Information Technology Group Institutions do not have opinions, merely customs
