Nigel,
> Am 11.02.2020 um 17:47 schrieb Nigel Horne,, :
>
> I like that module and will be sad to see it go. If you want I'll happily
> take it over.
it doesn't work anymore. And there is a drop-in replacement.
I don't know what's the expectation. Can you explain that a bit?
DBD::AnyData is
I don't work with Oracle, but here's a guess. Maybe the database was
unresponsive before your script started running, not as a result of it. If
so, maybe your script tried to prepare the statement, failed, and retried
12000 times. Eventually the DBA noticed the problem and restarted the
database,
On 13/2/20 11:13 am, JohnD Blackburn wrote:
Is that a behavior of DBI or DBD::Oracle?
Maybe your script, if you are blindly looping when it gets an error? Overall, I don't think there is enough information to point directly at a
cause. Presumably the DBA meant that a SQL statement (of some
Is that a behavior of DBI or DBD::Oracle?
My script says prepare or die, so any retries would have had to come directly
from the DBD::Oracle module
Script basically says:
use DBD::Oracle;
my $dbh = DBI->connect("dbi:Oracle:$dbSID", $user, $passwd, {AutoCommit => 0 });
my $statement =
The DBA pulled info from some cache that showed the SQL statement from the
script was executed 12610 times.
So if I were to add an “or die $!” statement after the fetchrow_array(), that
might fix things? (or prevent it from trying to continue if there are errors?)
Or catch errors after the
