On Thu, 2 Jan 2003, Paul Simon wrote:

> Hi all
> 
> I have a feeling this may be [OT], "take it to the DBI
> list..." But I'm hoping to eliminate as much as
> possible any suspicion that Apache::DBI/mod_perl is
> causing my headache. I'm trying to push this platform
> at work ;) If anyone can shed some light on this then
> I'd be very appreciative, of course. 
> 
> I have what's becoming a reoccuring problem with an
> app running under:
> 
> Apache/2.0.42 (Win32) mod_perl/1.99_08-dev Perl/v5.8.0
> 
> 
> I'm using Apache::compat and Apache::DBI for
> persistent database connections. 
[ ... ]
> 
> For completeness sake, here's the connection string:
> my $DBH  = DBI->connect("DBI:ODBC:$db", $user, $pass,
> { RaiseError => 1, PrintError => 1, AutoCommit => 1 })
> or print( "Unable to connect to Database:
> $DBI::errstr\n" ) ;
> 
> Finally, the error message I'm getting is:
> 
> DBI->connect(pdb9) failed:
> [Oracle][ODBC][Ora]ORA-12535: TNS:operation timed out
> (SQL-S1000)(DBD: db_login/SQLConnect err=-1) at
> /Apache2/lib/perl/Apache/Standard3.pm line 29 
> 
> This problem goes away if the ORacle server(on it's
> own hardware running windows 2000 pro) is restarted.
> The last time this happened the box Oracle resides on
> needed a cold reboot! So far, I haven't had to restart
> apache.
> 
> Could Apache::DBI or mod_perl2 cause this behavior?

When you say the problem goes away, does this mean that
things work fine after the restart of the Oracle server?
Or do you periodically have to do this restart?

Are you using the latest versions of DBI and DBD::ODBC?
If not, does an upgrade help?

-- 
best regards,
randy kobes

Reply via email to