RE: 10046 trace.. bind question

Ric,

The reason I mentioned the implicit conversion thing was not related the original query, but because I once had a case where the developers used a nvarchar2 datatype in their code instead of a varchar2, resulting in full table scans instead of index access. Took a while before we found out what happened.  

Freek D'Hooge
Uptime
Oracle Database Administrator
email: freek.dhooge_at_uptime.be
tel +32(0)3 451 23 82
http://www.uptime.be
disclaimer

-----Original Message-----
From: Ric Van Dyke [mailto:ric.van.dyke_at_hotsos.com] Sent: zondag 24 augustus 2008 17:23
To: D'Hooge Freek; contactarul_at_gmail.com; oracle-l_at_freelists.org Subject: RE: 10046 trace.. bind question

Roger that on the nvarchr2 or varchar2, like you I have seen the "n" data types don't get a value printed in the trace so I figured that the data is being interpreted as a varchar2 not an nvarchar2.

It would be interesting to see the SQL, the explain plan and the stat lines of the SQL being run, it may well be that a data type conversion is taking place, although it seems odd since Oracle by default always converts the SRTING type (varchar2 in this case) to a NUMBER and not a NUMBER to a STRING. So I don't think this is an implicit conversion. But with out the code we are guessing.

• Ric

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