Re: Is there a way to know which driver (thick / thin jdbc, odbc, .net, oci, ...) was used to connect to the database
- From: "Jaromir D.B. Nemec" <jaromir@xxxxxxxxxxxx>
- To: <Freek.DHooge@xxxxxxxxx>, "Niall Litchfield" <niall.litchfield@xxxxxxxxx>, "oracle-l-freelists" <oracle-l@xxxxxxxxxxxxx>
- Date: Tue, 7 Jul 2009 01:12:55 +0200
Hi Freek,
my tests on 10.2.0.3 Linux show that at least the JDBC driver set the
program column in v$session
thin driver - connection string jdbc:oracle:thin:@... program = 'JDBC Thin
Client'
OCI (thick) - connection string jdbc:oracle:oci:@.. program = 'java.exe'
HTH
Jaromir
----- Original Message -----
From: "D'Hooge Freek" <Freek.DHooge@xxxxxxxxx>
To: "Niall Litchfield" <niall.litchfield@xxxxxxxxx>; "oracle-l-freelists"
<oracle-l@xxxxxxxxxxxxx>
Sent: Monday, July 06, 2009 5:02 PM
Subject: RE: Is there a way to know which driver (thick / thin jdbc, odbc,
.net, oci, ...) was used to connect to the database
Hi,
The program column does not seems to be automatically set.
For most sessions it is empty, for others it contains the real name of the
application (such as sqlplus).
Regards,
Freek D'Hooge
Uptime
Oracle Database Administrator
email: freek.dhooge@xxxxxxxxx
tel +32(0)3 451 23 82
http://www.uptime.be
disclaimer
-----Original Message-----
From: Niall Litchfield [mailto:niall.litchfield@xxxxxxxxx]
Sent: vrijdag 3 juli 2009 18:08
To: D'Hooge Freek; oracle-l-freelists
Subject: Re: Is there a way to know which driver (thick / thin jdbc, odbc,
.net, oci, ...) was used to connect to the database
My memory is that the thin driver populates the program column of
v$session with its name, the others may also do the same.
--
http://www.freelists.org/webpage/oracle-l
--
http://www.freelists.org/webpage/oracle-l
- References:
- Is there a way to know which driver (thick / thin jdbc, odbc, .net, oci, ...) was used to connect to the database
- Re: Is there a way to know which driver (thick / thin jdbc, odbc, .net, oci, ...) was used to connect to the database
- RE: Is there a way to know which driver (thick / thin jdbc, odbc, .net, oci, ...) was used to connect to the database
Other related posts:
- » Is there a way to know which driver (thick / thin jdbc, odbc, .net, oci, ...) was used to connect to the database - D'Hooge Freek
- » Re: Is there a way to know which driver (thick / thin jdbc, odbc, .net, oci, ...) was used to connect to the database - Niall Litchfield
- » RE: Is there a way to know which driver (thick / thin jdbc, odbc, .net, oci, ...) was used to connect to the database - D'Hooge Freek
- » Re: Is there a way to know which driver (thick / thin jdbc, odbc, .net, oci, ...) was used to connect to the database - Jaromir D.B. Nemec
- » Is there a way to know which driver (thick / thin jdbc, odbc, .net, oci, ...) was used to connect to the database - Reardon, Bruce (RTABBAY)
- » Re: Is there a way to know which driver (thick / thin jdbc, odbc, .net, oci, ...) was used to connect to the database - Niall Litchfield
- » RE: Is there a way to know which driver (thick / thin jdbc, odbc, .net, oci, ...) was used to connect to the database - D'Hooge Freek