Have you checked *reverse* dns on the ip - 60 of the 61 seconds sound like dns timeout.
> On 4 Apr 2025, at 20:56, Johnson, Bruce E - (bjohnson) <bjohn...@arizona.edu> > wrote: > > > >> On Mar 31, 2025, at 4:20 PM, Johnson, Bruce E - (bjohnson) >> <bjohn...@arizona.edu> wrote: >> >> Sadly no. It’s still instantaneous on-prem but takes 61 seconds to get the >> database handle with the ip address. (and DNS resolves just fine ) >> >>> On Mar 31, 2025, at 1:32 AM, Mark Lawrence via dbi-users >>> <dbi-users@perl.org> wrote: >>> >>> External Email >>> >>>> The DB tools I use (Oracle SQL Developer and DBVisualizer) are working as >>>> expected with the instances I have, but trying to run my Perl code using >>>> DBI/DBD::Oracle/Oracle Instant Client is giving me extreme delays >>>> creating the DB handle; running a simple test program to time the process >>>> shows the program taking a minute or longer to create the database handle. >>> >>> My thoughts in such a scenario usually move towards DNS. I don't know if >>> DBI, or DBD::Oracle, or some Oracle library is doing name to address >>> translation, but perhaps IPv6 Happy Eyeballs is in play with a 60 second >>> timeout? >>> >>>> my $dbnamel="host=xxxxxxx.pharmacy.arizona.edu;sid=xxxxxxx"; >>>> my $dbnamec="host=xxxxxxxx.us-west-2.rds.amazonaws.com;sid=xxxxxxx"; >>> >>> Maybe try with IP addresses? > > Turned out to be None of the above. > > Weirdly the delay was from using > "$dbnamec="host=xxxxxxxx.us-west-2.rds.amazonaws.com;sid=xxxxxxx”;" in the > connection statement > > When I switched to using the tnsnames.ora configuration name for the > connection > > $dbnamec=“CLOUDTEST”; > > It worked like a charm. > > -- > Bruce Johnson > University of Arizona > College of Pharmacy > Information Technology Group > > Institutions do not have opinions, merely customs > >
