RE: SQLPlus version tracking

From: Powell, Mark <mark.powell2_at_hp.com>
Date: Fri, 12 Oct 2012 17:43:43 +0000
Message-ID: <1E24812FBE5611419EFAFC488D7CCDD112155B2E_at_G5W2734.americas.hpqcorp.net>

However, I believe there is a bug such that the client version displayed is the client version of the querying user rather than that of the session client that should be displayed. You might want to connect using two different client versions then query for those two SID's and see what you get.

-----Original Message-----
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Yong Huang Sent: Friday, January 20, 2012 5:57 PM
To: oracle-l_at_freelists.org
Subject: Re: SQLPlus version tracking

> With some experiment, I think the widths of the numbers are 2, 1, 2,
> 1, 2 bytes, respectively. So we can use the following SQL to check the
> client version (run as sys):
> ...

A better SQL for an 11g database to check its client version:

with x as (select distinct to_char(ksuseclvsn,'xxxxxxx') v from x$ksusecon where ksusenum = &sid) select decode(v, ' 0', '10g or lower',

 to_number(substr(v,1,2),'xx') || '.' || --maj_rel
 to_number(substr(v,3,1),'x') || '.' || --mnt_rel
 to_number(substr(v,4,2),'xx') || '.' || --ias_rel
 to_number(substr(v,6,1),'x') || '.' || --ptc_set
 to_number(substr(v,7,2),'xx')) client_version -- port_mnt from x;

Have a good weekend!

Yong Huang

--
http://www.freelists.org/webpage/oracle-l


--
http://www.freelists.org/webpage/oracle-l

Received on Fri Oct 12 2012 - 19:43:43 CEST