Re: sql with SQL_OPCODE=0
- From: Yong Huang <yong321@xxxxxxxxx>
- To: oracle-l@xxxxxxxxxxxxx
- Date: Wed, 1 Dec 2010 09:47:38 -0800 (PST)
I spent some time trying to find more about these pseudo SQLs and even
opened a TAR, which was completely fruitless. At one point I thought I
found the connection between them and the real user SQLs based on
x$kgltr. But later I gave up, though I still keep the "forsaken"
write-up online:
http://yong321.freeshell.org/oranotes/PseudoSQLs_table_x_x_x_x_x_x.txt
Most of the time, there're 6 hex numbers after table_, but 4 number
forms also exist, as shown in Dennis Yurichev's Oracle function call
list:
$ grep table_% *
kks.txt:May call sscanf (?, "table_%x_%x_%x_%x", ...)
kks1.txt:May call sscanf (?, "table_%x_%x_%x_%x", ...)
kks1.txt:May call sscanf (?, "table_%x_%x_%x_%x_%x_%x", ...)
koka.txt:May call sprintf (?, "table_%x_%x_%x_%x_%x_%x", ...)
Yong Huang
-----Original message-----
You might want to look at this post I did a while back.
http://kerryosborne.oracle-guy.com/2009/04/hidden-sql-why-cant-i-find-my-sql-text/
Dion and I actually had a bit of discussion on that post. Also 27db bit of the
table name may be the hex representation of the object_id being accessed (also
discussed in that post). Dion, I'd be interested in any other things you've
learned on this subject recently as I haven't really thought about it since
that post.
--
//www.freelists.org/webpage/oracle-l
Other related posts:
