Message from discussion 11g Listener Logs
Received: by 10.68.227.230 with SMTP id sd6mr14324361pbc.8.1335198435241;
Mon, 23 Apr 2012 09:27:15 -0700 (PDT)
From: ExecMan <artme...@yahoo.com>
Subject: Re: 11g Listener Logs
Date: Mon, 23 Apr 2012 09:25:36 -0700 (PDT)
References: <firstname.lastname@example.org> <email@example.com>
X-Trace: posting.google.com 1335198435 14921 127.0.0.1 (23 Apr 2012 16:27:15 GMT)
NNTP-Posting-Date: Mon, 23 Apr 2012 16:27:15 +0000 (UTC)
Injection-Info: h20g2000yqd.googlegroups.com; posting-host=126.96.36.199; posting-account=Te8R5QoAAAD0OcZ51Bsj60HqyktlOVZb
X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:188.8.131.52)
Content-Type: text/plain; charset=ISO-8859-1
On Apr 23, 10:26=A0am, ddf <orat...@msn.com> wrote:
> On Apr 23, 7:17=A0am, ExecMan <artme...@yahoo.com> wrote:
> > Hi,
> > I'm trying to find a good way to parse / audit the 11g listener logs.
> > In our 10g databases this was pretty simple. =A0A couple of procedures
> > and an external table pointing to the log and I can run queries and
> > gather stats by the hour, connect counts from different hosts, etc.
> > But, for 11g with the log being in XML and could be a number of logs,
> > I'm not quite sure how to get this accomplished. =A0I've been searching
> > around and trying to brainstorm and was looking to see what anyone
> > else has done. =A0I'm sure I'm not the first who wants to parse the
> > listener log and get stats / counts.
> > Thanks!
> I'm running 184.108.40.206 and I find a text copy of the listener log in C:
> \oradb\diag\tnslsnr\<host>\listener\trace where c:\oradb is my
> diagnostic_dest. =A0I also find this text log under Linux on 220.127.116.11,
> again starting at <diagnostic_dest> and going to diag/tnslsnr/<host>/
> listener/trace. =A0I would expect that you can point this 10g script to
> the 11g location and continue to use it as you have always done.
> David Fitzjarrell
Hmm...I guess I could do that. I was hoping to use the newer
features, since eventually the old stuff will be scratched. Maybe
loading it and some type of XML query would work against it?