RE: Bind values missing from SQL trace

Looks to me like the application is just sending in an empty string for
the bind variable value.  Do you have some evidence to the contrary?

Do other bind variable values show up as expected in the trace files?

Just curious - why use grep to locate the longest-running query - why
not tkprof with sort=fchela?


-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Rich Jesse


Using grep, I quickly locate the longest-running statement, but when I
view the essential binds, I see this:


BINDS #18:
 bind 0:
   value=""

So where's the values for the two binds that I need? 

Privileged/Confidential Information may be contained in this message or 
attachments hereto. Please advise immediately if you or your employer do not 
consent to Internet email for messages of this kind. Opinions, conclusions and 
other information in this message that do not relate to the official business 
of this company shall be understood as neither given nor endorsed by it.

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


Other related posts: