I would say simply convert over to Apache::DBI you would not have to change any of your code except
use DBI; to use Apache::DBI Will most likely solve any problems you are having cheers On Thu, Jan 27, 2011 at 4:26 PM, Bill Ward <b...@wards.net> wrote: > > > On Thu, Jan 27, 2011 at 4:04 AM, John Scoles <sco...@pythian.com> wrote: > >> On 26/01/2011 3:35 PM, Bill Ward wrote: >> >>> On Wed, Jan 26, 2011 at 12:27 PM, John Scoles<sco...@pythian.com> >>> wrote: >>> >>>> Or, is there some way to verify the OCI environment and reset it when >>>>> it is found to be unusable - in other words, trap the >>>>> "OCIHandleAlloc(OCI_HTYPE_ERROR)" error and reconnect? >>>>> >>>>> Well normally an environment will not die unless you loose >>>> connectivity. If >>>> you have lost connectivity then there would not be much point in trying >>>> to >>>> reconnect automatically your network or DB is Down?? >>>> >>> Databases go down sometimes. There could be a power failure or >>> hardware crash, or maybe the DB is just being bounced by the DBAs >>> after making a configuration change or upgrade. The problem is even >>> if the database comes back up, it still keeps generating the same >>> error. Why should I also have to manually restart the Apache server >>> just because the database has come back online? >>> >> That's odd, Are you using Apache::DBI ??? Which version of DBD::Oracle and >> OCI are you using? >> >> > Nope. These apps were written long before Apache::DBI was a twinkle in > Edmund's eye. > > We're using DBI 1.607, DBD::Oracle 1.22, and Apache 2.2.9 with mod_perl > 2.000004 > > I don't know about OCI in particular but we're using Oracle database > version 10.2.0.4.0. > > <#12dc95fa6bae3667_> > <#12dc95fa6bae3667_> <#12dc95fa6bae3667_> > <#12dc95fa6bae3667_> > -- The best compliment you could give Pythian for our service is a referral.
