Re: Monitoring SQL Developer Usage
From: Jeff Smith <jeff.d.smith_at_oracle.com>
Date: Fri, 05 Apr 2013 15:04:46 -0400
Message-ID: <515F204E.9070808_at_oracle.com>
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.
Date: Fri, 05 Apr 2013 15:04:46 -0400
Message-ID: <515F204E.9070808_at_oracle.com>
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-lReceived on Fri Apr 05 2013 - 21:04:46 CEST