Having some similar select statements only the first is shown because the execution plan won’t be recalculated.

All of this SQL dumping on Oracle is awful, somw ways are only possible with tools available only from metalink…. no GUI…. MS provides everything for free, has a GUI for trace files and so on. Nevertheless Oracle is a constant source for income, because noone does really KNOW more than some small pieces of knowledge and everything is scattered around.

You can also capture a workload on a 9.2.0.8.0 database, but since we capture at a pretty low level I don’t think you can extract the SQL out of it directly. You can of course capture the SQL while replaying.
-Harald

]]>By: Wouter Wethmarhttps://prutser.wordpress.com/2009/01/11/capturing-sql-statements/#comment-69
Fri, 13 Feb 2009 07:55:00 +0000http://prutser.wordpress.com/?p=154#comment-69Why didn’t I found this blog before . . . . . . .
I missed it, I like it and I hope there wil de more . . . . .

Question :
Starting with Oracle version 10.2.0.4 you can record database input to replay it again…. I quess that is also on a sql level . . . . . Is there a way to use the replay ‘output’ to capture aql statements ?

]]>By: Log Buffer #131: a Carnival of the Vanities for DBAshttps://prutser.wordpress.com/2009/01/11/capturing-sql-statements/#comment-25
Fri, 16 Jan 2009 17:20:53 +0000http://prutser.wordpress.com/?p=154#comment-25[…] asked question by students while I am teaching DBA classes at Oracle University is: “How can I capture the SQL statements issued on my database,” and his answer lists five […]
]]>By: Sandeephttps://prutser.wordpress.com/2009/01/11/capturing-sql-statements/#comment-24
Fri, 16 Jan 2009 01:58:10 +0000http://prutser.wordpress.com/?p=154#comment-24Excellent post!. In fact yesterday I was trying a a similar stuff at customer site and 10132 would have been to good to experience something new!. It is good to have you on the blogging world sharing practical tips for other DBAs.

]]>By: Bjørn Engsighttps://prutser.wordpress.com/2009/01/11/capturing-sql-statements/#comment-11
Tue, 13 Jan 2009 11:11:09 +0000http://prutser.wordpress.com/?p=154#comment-11Event 10132 does actually not cause lines to be printed in the trace file when you do a hard parse. In stead, it causes the optimizer to dump the execution plan when it is generated. These two things often appear right after each other, but this is not necessarily true. You can parse a statement without generating an execution plan, e.g. using the DBMS_SQL package; and an execution plan can be generated even when you don’t do hard parses, e.g. if a bind value changes sufficiently in Oracle11.
]]>By: Rick van Ekhttps://prutser.wordpress.com/2009/01/11/capturing-sql-statements/#comment-10
Tue, 13 Jan 2009 10:56:53 +0000http://prutser.wordpress.com/?p=154#comment-10Hello Harold, I enjoyed reading your blog. No GUI stuff but just the power of a plain command line. Showing where it is about, simple and straight forward. To my opinion the best way to show how it works.
]]>