Enabling and Reading event 10046 / SQL Trace

As I’m done with the book and back from a quick vacation (to Prague, which is an awesome place – well, at least during the summer) I promised (in Twitter) that now I’d start regularly writing blog articles again. In a separate tweet I asked what to write about. Among other requests (which I’ll write about later), one of the requests was to write something about enabling and reading SQL trace files… 

I am probably not going to write (much) about SQL trace for a single reason – Cary Millsap has already written a paper so good about this topic, that there’s no point for me to try to repeat it (and my paper wouldn’t probably be as clear as Cary’s).

So, if you want to get the most out of SQL Trace, read Cary’s Mastering Performance with Extended SQL Trace paper:


The above link directs you to Method-R’s article index, as there’s a lot of other useful stuff to read there.

Wow, now I’m done with my first request – to write something about SQL Trace :-)


This entry was posted in Oracle and tagged , , . Bookmark the permalink.

One Response to Enabling and Reading event 10046 / SQL Trace

  1. Pavol Babel says:

    I do not use Twitter, but can I have another request? :) Well, I have two :)

    1. We were discussing here http://blog.tanelpoder.com/2011/06/05/cache-buffers-chains-latch-contention-using-latchprofx-sql-example/ the reason why are processing blocking on CBC. You suggested it is because of pinning and you are right. I just asked you to describe pinning process a little bit (why does oracle has to write to buffer header when pinning? is it really writing to x$bh.us_nxt and x$bh.us_prev??? ). So maybe now there it is the right time to anwer :)
    I understand consistent get – examination. Oracle does not grab CBC latch two times (CBC grab, pin, CBC release, block read, CBC grab, unpin, CBC release), but only once (grab CBC in shared mode, read block very fast, release CBC),
    2. I have found quite big difference between free space in v$sgastat and x$ksmsp. Could you explain it, please?

Leave a Reply

Your email address will not be published. Required fields are marked *