Make sure there's not a timeout issue or a connection limit on the db server
itself. One important test to run is finding out if disabling "Maintain
database connections" to Oracle resolved the problem. This will tell you
that the problem isn't connectivity to the db, but the time the connections
themselves are remaining alive.
HTH,
JC
_____
From: Earl, George [mailto:[EMAIL PROTECTED]
Sent: Friday, February 13, 2004 10:04 AM
To: CF-Talk
Subject: RE: Can't maintain Oracle connectivity - CF 5.0
George said:
> > All of a sudden we cannot maintain our Oracle connectivity using the
> > native drivers . . .
> > All data sources using these drivers are failing, even ones that we
> > have not used when the failures occur. If we restart the ColdFusion
> > Application service we get back our connectivity for just a few
> > minutes before all the Oracle data sources go down again . . .
> >
Dave Watts said:
> This doesn't sound like a CF problem at all - maybe it's a
> problem with the underlying network? You might try installing
> a newer version of the Oracle client, which is used by CF's
> native drivers.
Our Oracle client is up-to-date for the version of the database that we are
using, and we hope to do network tracing later this morning to see what is
happening between our web server and our database server.
Meanwhile we discovered that the ODBC drivers supplied with CF 5.0 work just
fine even though the native drivers break so we have switched over our
applications to the ODBC data sources while we troubleshoot the native ones.
I expect to be asked at some point why we are using resources to try to fix
the native drivers problem when the ODBC drivers are working 'just fine'. I
know the standard answers (performance, speed, robustness, scalability,
ability to use native database functions, etc.), but does everyone think
these are valid and worth pursuing?
We have also renamed the old native data sources that we created using the
old database server and created new ones using the new database server -
didn't resolve the problem.
With the native data sources through CF broken we were able to establish a
successful connection to the database using SQL Plus (but then we realized
we probably should have had the SQL Plus connection established before the
native data sources broke so we could see if the SQL Plus connection broke
as well, so we'll try that too.
Thanks!
George
[EMAIL PROTECTED]
_____
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
