Re: Monitoring SQL Developer Usage
From: Niall Litchfield <niall.litchfield_at_gmail.com>
Date: Fri, 5 Apr 2013 20:12:25 +0100
Message-ID: <CABe10saqs9s+dyt9R=U8ayn=-NO+h5fR-WT_P=QhSzEaZPKt=g_at_mail.gmail.com>
I'm not a consultant currently but the consulting mantra 'never trust the client; they lie' applies.
On Apr 5, 2013 8:06 PM, "Jeff Smith" <jeff.d.smith_at_oracle.com> wrote:
> The system is easily gamed, this is true - that is, looking at a
> reported module or application name being reported in v$session.
> Another reason why I asked about why you wanted to track this
> information - there might be a better solution for you based on those reqs.
>
> On 4/5/2013 2:58 PM, Niall Litchfield wrote:
> > There's no way to do this. You*can* of course monitor which db someone
> > logs into with a client claiming to be SQL*Developer from a workstation
> > claiming to be X in ways already described.
>
>
>
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>
Date: Fri, 5 Apr 2013 20:12:25 +0100
Message-ID: <CABe10saqs9s+dyt9R=U8ayn=-NO+h5fR-WT_P=QhSzEaZPKt=g_at_mail.gmail.com>
I'm not a consultant currently but the consulting mantra 'never trust the client; they lie' applies.
On Apr 5, 2013 8:06 PM, "Jeff Smith" <jeff.d.smith_at_oracle.com> wrote:
> The system is easily gamed, this is true - that is, looking at a
> reported module or application name being reported in v$session.
> Another reason why I asked about why you wanted to track this
> information - there might be a better solution for you based on those reqs.
>
> On 4/5/2013 2:58 PM, Niall Litchfield wrote:
> > There's no way to do this. You*can* of course monitor which db someone
> > logs into with a client claiming to be SQL*Developer from a workstation
> > claiming to be X in ways already described.
>
>
>
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>
-- http://www.freelists.org/webpage/oracle-lReceived on Fri Apr 05 2013 - 21:12:25 CEST