tag:blogger.com,1999:blog-27482298.post99395725636814460..comments2024-02-25T22:29:18.572+00:00Comments on Andrew's Oracle Blog: V$SQL_BIND_CAPTUREUnknownnoreply@blogger.comBlogger2125tag:blogger.com,1999:blog-27482298.post-79220926851721565642013-03-28T22:16:39.700+00:002013-03-28T22:16:39.700+00:00Dear Martin,
Thank you for taking the time to com...Dear Martin,<br /><br />Thank you for taking the time to comment on this post. I try to read Tanel Poder's posts too. Unfortunately most of them are way over my head! I'll try to take a look at your blog when I get a moment.<br /><br />Kind regards,<br /><br />AndrewAndrew Reidhttps://www.blogger.com/profile/10622696064206411002noreply@blogger.comtag:blogger.com,1999:blog-27482298.post-46547357596498197322013-03-28T14:37:46.159+00:002013-03-28T14:37:46.159+00:00Andrew,
v$sql_bind_capture is the first place whe...Andrew,<br /><br />v$sql_bind_capture is the first place where I look for bind variables but I take the results with a grain of salt since I saw Tanel Poder's article http://blog.tanelpoder.com/2010/10/18/read-currently-running-sql-statements-bind-variable-values/ and his comment: "V$SQL_BIND_CAPTURE is not a reliable way for identifying the current bind variable values in use. Oracle’s bind capture mechanism does not capture every single bind variable into SGA (it would slow down apps which run lots of short statements with bind variables). The bind capture only selectively samples bind values, during the first execution of a new cursor and then every 15 minutes from there (controlled by _cursor_bind_capture_interval parameter), assuming that new executions of that same cursor are still being started (the capture happens only when execution starts, not later during the execution)."<br /><br />MartinMartin Preisshttps://www.blogger.com/profile/06388592214305009761noreply@blogger.com