Very interesting. I wonder what it’s used for and why it was exposed to v$ views. I’ve troubleshot lots of problems involving spinning processes, unexpected loops, bad sql plans, etc. In those scenarios, usually more than one statement is involved. If I understand correctly, I would think that counter would turnover constantly. I’m curious and puzzled by it. Clearly, there is/was a reason for it’s creation.
—
I’m behind on my reading. I hope I’m not past the relevance date :)
↧
Comment on What the heck is the SQL Execution ID – SQL_EXEC_ID? by Paul Janda
↧