dbms_session.set_context from JDBC fails mysteriously, how can I trap it ?
From: Krist <krislioe_at_gmail.com>
Date: Wed, 10 Feb 2010 03:54:09 -0800 (PST)
Message-ID: <b9154067-cd8a-4566-b9be-46b88e3c6a2f_at_k2g2000pro.googlegroups.com>
Hi gurus,
-> and it Seems to use the last value set, i.e : '030'
Other loc_code also works perfectly.
Date: Wed, 10 Feb 2010 03:54:09 -0800 (PST)
Message-ID: <b9154067-cd8a-4566-b9be-46b88e3c6a2f_at_k2g2000pro.googlegroups.com>
Hi gurus,
Our ADF application connect via JDBC to Oracle DB and using VPD .
This is done by executing
dbms_session.set_context('vpd_new','loc_code', pLocCode) at the
beginning of the session.
Mysteriously, all loc_code succeed to be set resulting in the VPD is correctly working, EXCEPT for one loc_code, it doesn't work.
dbms_session.set_context('vpd_new','loc_code', '010') -> works
dbms_session.set_context('vpd_new','loc_code', '020') -> works
dbms_session.set_context('vpd_new','loc_code', '030') -> works
dbms_session.set_context('vpd_new','loc_code', '061') -> DOES NOT
work.
-> and it Seems to use the last value set, i.e : '030'
Other loc_code also works perfectly.
how can I know what happen when the application execute : dbms_session.set_context('vpd_new','loc_code', '061') Why does it fail ?
Can I know what command is really sent to the Database ?
or can it be other reason ?
Thank you for your help,
xtanto
Received on Wed Feb 10 2010 - 05:54:09 CST