SQL Tuning, eAdam, eDB360, SQLT, SQLHC
with 2 comments
In case you have never seen one, you can browse this SQLT XTRACT Report. This sample is a PDF file. The actual report is generated as HTML, which eases the navigation on it.
Written by Carlos Sierra
April 24, 2013 at 3:55 pm
Posted in SQLTXPLAIN (SQLT)
Tagged with SQLTXTRACT, XTRACT
Subscribe to comments with RSS.
I have been using your great SQLT tool for years now and it makes my job much easier and more productive.I am very keen to understand the logic behind using sqlt$ tables/views instead of using dynamic performance views directly.The active session history & AWR Active session history under “SQL Execution” heading provides me a clear view on where most of the wait was spent.I would like to have a SQL which queries v$active_session_history & v$sql_plan and dba_hist_active_sess_history and dba_hist_sql_plan as it mush quicker to get the same information w/o running SQLTXTRACT.
How do you associate the statement_id with the last execution of the SQL as there is no such a column in the ASH and AWR tables?
May 3, 2013 at 10:40 am
statement_id is a column that contains a number generated by SQLT. Each execution of SQLT uses a new number. SALT selects from the DBA and GV$ views mostly by SQL_ID, so what you see with regard to ASH data is simply a SELECT on SQL_ID.
Cheers — Carlos
May 4, 2013 at 4:15 am
Fill in your details below or click an icon to log in:
You are commenting using your WordPress.com account. ( Log Out / Change )
You are commenting using your Twitter account. ( Log Out / Change )
You are commenting using your Facebook account. ( Log Out / Change )
You are commenting using your Google+ account. ( Log Out / Change )
Connecting to %s
Notify me of follow-up comments via email.
Enter your email to receive notifications of new posts.
Join 1,426 other followers
Welcome. This blog is about SQL Tuning, Oracle Performance and Tools for both.
Blog at WordPress.com. The Journalist v1.9 Theme.
Get every new post delivered to your Inbox.