RE: 10046 trace and null bind variables

You can get a positive confirmation on that by noting the "avl=00" part. That means the value has a zero-byte storage representation.  

Which leads me to the place where I'm reminded that NULL and the empty string are identical in Oracle SQL, which always makes me throw up in my mouth a little bit.    

Cary Millsap

Hotsos Enterprises, Ltd.

http://www.hotsos.com

Nullius in verba  

Hotsos Symposium 2007 / March 4-8 / Dallas

Visit www.hotsos.com for curriculum and schedule details...

From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Ric Van Dyke
Sent: Tuesday, February 20, 2007 2:21 PM To: kennaim_at_gmail.com; oracle-l_at_freelists.org Subject: RE: 10046 trace and null bind variables  

Correct.  

Ric Van Dyke

Hotsos Enterprises

Hotsos Symposium March 4-8, 2007. Be there.

From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Ken Naim
Sent: Tuesday, February 20, 2007 2:58 PM To: oracle-l_at_freelists.org
Subject: 10046 trace and null bind variables  

When a 10046 trace does not have a value clause for a given bind variable, I am assuming it is null. Am I correct?

Thanks,

Ken  

  bind 11: dty=2 mxl=22(21) mal=00 scl=00 pre=00 oacflg=03 oacfl2=206001 size=0 offset=296

    bfp=11063d280 bln=22 avl=00 flg=01

 EXEC
#50:c=0,e=489,p=0,cr=0,cu=0,mis=0,r=0,dep=1,og=4,tim=23888497307655

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