Re: tracking down hidden SQL???
From: Adric Norris <landstander668_at_gmail.com>
Date: Mon, 21 Oct 2013 08:40:19 -0500
Message-ID: <CAJueESqX7R853aa_sZTDoRuzk=9dB4=xdWZP6+MFkG_RYLt58w_at_mail.gmail.com>
On Thu, Oct 17, 2013 at 9:48 AM, Chris Taylor < christopherdtaylor1994_at_gmail.com> wrote:
> Hey, the other thing you could do, if you know some identifying
> information for these sessions, like OSUSER, machine/terminal, client_info
> etc, you could setup a LOGIN TRIGGER that enables a 10046 trace and capture
> any/all SQL executed in the session.
>
> Some apps (like PeopleSoft) will populate client_info so it makes it
> easier to trace one session instead of all the connected sessions. Maybe
> you have something available to you that will enable you to create a
> limited trace on a few sessions.
>
Date: Mon, 21 Oct 2013 08:40:19 -0500
Message-ID: <CAJueESqX7R853aa_sZTDoRuzk=9dB4=xdWZP6+MFkG_RYLt58w_at_mail.gmail.com>
On Thu, Oct 17, 2013 at 9:48 AM, Chris Taylor < christopherdtaylor1994_at_gmail.com> wrote:
> Hey, the other thing you could do, if you know some identifying
> information for these sessions, like OSUSER, machine/terminal, client_info
> etc, you could setup a LOGIN TRIGGER that enables a 10046 trace and capture
> any/all SQL executed in the session.
>
> Some apps (like PeopleSoft) will populate client_info so it makes it
> easier to trace one session instead of all the connected sessions. Maybe
> you have something available to you that will enable you to create a
> limited trace on a few sessions.
>
So far there doesn't seem to be any distinguishing info for the sessions, which would make it easy to separate them from other app-related connections. If I'm able to come up with something, however, I'll certainly consider doing this.
Thanx!
-- http://www.freelists.org/webpage/oracle-lReceived on Mon Oct 21 2013 - 15:40:19 CEST