Sometimes it just happens when you want some functionality built into Oracle database. I think I’ll put on the blog my “wish list” items to not forget about them. Today’s one: I want to have an option to reduce bind variables dumping in the SQL trace based on SQL depth level. For instance, to dump only those variables which were used in top level calls only. It could be useful in case of queries with PL/SQL function calls with SQL in it, producing enormous amount of info in the trace file which you probably don’t want to see because you are interested in the “driving” bind variables only. Or in case of globally enabled tracing – again it’s possible that you probably don’t need bind variables from all executed statements and/or want to reduce generated trace files total size.
-
Categories
-
Tags
10.2.0.3 10.2.0.4 10.2.0.5 10g 10gR2 11.2.0.2 11.2.0.3 11g 11gR2 ANSI SQL ASH AWR benchmark bug bug-or-feature CBQT coalesce subquery connect by dynamic views Exadata FBI indexes join elimination memory MOS nested loops ORA-04031 Oracle JVM PDML poll presentations PX scripts shared cursors SPECjAppServer2004 sql_trace statistics Statspack subqueries subquery factoring subquery unnesting Tom Kyte tpt wait events wish list -
Top Posts
-
Blogroll
One Comment
may be set different level is good idea.
eg: record bind variables for recursive calls
record bind variables for non-recursive calss
One Trackback
[...] been too long from a previous wish for Oracle. While reading a MOS updated articles (in a new HTML interface which looks nice, much [...]