, is to have debugging code in the script and hope
I have enough there so that if the incident does happen again, I have enough
info to understand what was happening at that time.
-Original Message-
From: Fennell, Brian
Sent: Wednesday, 19 February 2020 2:45 AM
To: JohnD Blackburn
err_total;
return wantarray
? ($tuple_count, defined $row_count ? $row_count : undef)
: $tuple_count;
}
Is that "while(1)" loop a potential contender for causing this?
-----Original Message-
From: JohnD Blackburn
Sent: Tuesday, 18 February 2020 8:51 AM
To: St
originated from outside of the organization. Do not click
links or open attachments unless you recognize the sender and know the content
is safe.
On Thu, 13 Feb 2020 06:58:37 +
JohnD Blackburn wrote:
> The DBA pulled info from some cache that showed the SQL statement from
> the
,
John
-Original Message-
From: Fennell, Brian
Sent: Saturday, 15 February 2020 5:47 AM
To: JohnD Blackburn ; dbi-users@perl.org
Subject: RE: Perl script excessively executing statement
CAUTION: This email originated from outside of the organization. Do not click
links
the execute statement?
From: Christopher Jones
Sent: Thursday, 13 February 2020 12:56 PM
To: dbi-users@perl.org; JohnD Blackburn
Subject: Re: Perl script excessively executing statement
CAUTION: This email originated from outside of the organization. Do not click
links or open attachments unless
, I don’t know how to reproduce it to test
if any mitigations are sufficient.
Cheers,
John
From: Geoffrey Rommel
Sent: Thursday, 13 February 2020 2:56 AM
To: JohnD Blackburn
Cc: dbi-users@perl.org
Subject: Re: Perl script excessively executing statement
CAUTION: This email originated from
Hi all,
I have a perl script in my monitoring system that has been working for months
without an issue.
Basically, it connects to an Oracle 12c database, prepares a statement, then it
executes the statement, then it has a while loop to process the returned rows.
So under normal conditions the
