I would wrap all DB calls in a eval, and implement exception handling. If an error occurs try to close the handle (in a eval), clear it, and then the next time around, reopen it.
-----Original Message----- From: Jesse, Rich [mailto:[EMAIL PROTECTED] Sent: Monday, October 18, 2004 5:06 PM To: Paul Appleby; BAXTER, LINCOLN A Cc: [EMAIL PROTECTED] Subject: RE: Slow connection to Oracle 9i Hmmmm...one thing I thought of is to check the validity of the handle, in case the Oracle instance bounces (i.e. The Oracle instance is available, but the persistent connection no longer exists). Does that automagically happen in the connect or should there be code to check for a specific error either on the connect or maybe the statement handle? Rich Rich Jesse System/Database Administrator [EMAIL PROTECTED] QuadTech, Sussex, WI USA -----Original Message----- From: Jesse, Rich [mailto:[EMAIL PROTECTED] Sent: Monday, October 18, 2004 3:51 PM To: Paul Appleby; BAXTER, LINCOLN A Cc: [EMAIL PROTECTED] Subject: RE: Slow connection to Oracle 9i Perhaps this'll help: http://perl.apache.org/docs/1.0/guide/performance.html#Persistent_DB_Connect ions There's a link on that site to "Tim Bunce's Advanced DBI talk", but it returns a 500. Tim??? Rich Rich Jesse System/Database Administrator [EMAIL PROTECTED] QuadTech, Sussex, WI USA -----Original Message----- From: Paul Appleby [mailto:[EMAIL PROTECTED] Sent: Monday, October 18, 2004 3:39 PM To: BAXTER, LINCOLN A Cc: [EMAIL PROTECTED] Subject: RE: Slow connection to Oracle 9i My CGI application will be called by different users at different times. Are you saying the first user's connection can be left open for all the other users? How? Paul
