SQLT XTRACT Report – Sample
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.
Carlos Sierra's Tools and Tips
Tools and Tips for Oracle Performance and SQL Tuning
Join 3,750 other subscribers
Carlos Sierra
Working at the Oracle Cloud Infrastructure OCI. Living in Seattle, WA.
Disclaimer
Free Downloads
Pages
Slides
- Adapting and Adopting SQL Plan Management
- Online Index Rebuild Auromation
- SQL Tuning 101
- Understanding SQL Trace, TKPROF and Execution Plan for beginners
- Understanding my database through SQL*Plus using the free tool eDB360
- Survey of some free Tools
Carlos Sierra's Tools and Tips 
Hi Carlos,
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?
Thanks
Raj
anthonydba
May 3, 2013 at 10:40 am
Ray,
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
Carlos Sierra
May 4, 2013 at 4:15 am