RE: logs
- From: "Jim Silverman" <jsilverman@xxxxxxxxxxxxx>
- To: "Oracle-L@Freelists" <oracle-l@xxxxxxxxxxxxx>
- Date: Thu, 2 Mar 2006 08:07:44 -0500
I don't disagree that there is potentially useful information in the TNS
log. However, if you consider 470,000 connections per month to be a
surprisingly high number, in a previous life we had applications that
saw this many connections every couple of days. (I don't have any hard
numbers, but this is probably a good order of magnitude.) As a result,
trying to sift any useful information from this amount of noise was
virtually impossible.
That said, if there are particular events in which you are interested, I
agree that Perl would do a nice job of culling through the hundreds of
thousands of log entries to find them.
=====================================
Jim Silverman
Senior Systems Database Administrator
Solucient, LLC
Telephone: 734-669-7641
FAX: 734-930-7611
E-Mail: jsilverman@xxxxxxxxxxxxx
-----Original Message-----
From: Grant Allen [mailto:gxallen@xxxxxxxxx]
Sent: Wednesday, March 01, 2006 5:14 PM
To: Jim Silverman
Cc: Oracle-L@Freelists
Subject: Re: logs
On 3/2/06, Jim Silverman <jsilverman@xxxxxxxxxxxxx> wrote:
>
> You could examine the listener.log, located at
$ORACLE_HOME/network/log.
> I've never found anything terribly useful there, but it is something
you
> could check for network-type issues.
Believe me, it can be a very handy log file. I had a client in December
with Listener crash and hang issues, and this little log showed that
470000 (yes, four hundred and seventy thousand) connections that had
been made that month.
We shot the developer responsible :-)
I agree with Jared - automate monitoring of this. I hear perl is useful
for this, right Jared? :-P
Ciao
Fuzzy
:-)
This message is a private communication. It may contain information that is
confidential
and legally protected from disclosure. If you are not an intended recipient,
please do
not read, copy or use this message or any attachments, and do not disclose them
to others.
Please notify the sender of the delivery error by replying to this message, and
then
delete it and any attachments from your system.
Thank you,
Solucient LLC
(eXclaimer 4x)
Other related posts:
