Re: Thick vs thin client - 11g R2
From: Yong Huang <yong321_at_yahoo.com>
Date: Fri, 24 Sep 2010 07:55:14 -0700 (PDT)
Message-ID: <573099.24491.qm_at_web80601.mail.mud.yahoo.com>
> As far as the non-printable characters, the developers tell me that
> what they are doing matches the database characterset. I have no way
> to verify
Date: Fri, 24 Sep 2010 07:55:14 -0700 (PDT)
Message-ID: <573099.24491.qm_at_web80601.mail.mud.yahoo.com>
> As far as the non-printable characters, the developers tell me that
> what they are doing matches the database characterset. I have no way
> to verify
In 11gR2, sometimes it's possible to see the character set in v$session_connection_info.client_charset:
SQL> select client_charset, count(*)
2 from v$session_connect_info
3 where sid in (select sid from v$session)
4 group by client_charset;
CLIENT_CHARSET COUNT(*)
-------------- ------------
UTF8 159 Unknown 24 AL32UTF8 4
I added the "where sid in" part because some sessions in v$session_connect_info are invisible (recursive etc).
Most garbage character problems can be easily diagnosed with SQL trace.
By the way, on our RAC, we always use Java OCI (thick) client because the thin client can't do server side failover or load balance controlled by services.
Yong Huang
-- http://www.freelists.org/webpage/oracle-lReceived on Fri Sep 24 2010 - 09:55:14 CDT