Scribd
Upload
10 views1 page

Optimizer Information

The document provides information on sources for SQL execution plans and AWR data, specifically mentioning v$sql, v$sql_text, v$sql_plan, dba_hist_sqltext, and dba_hist_sql_plan. It also describes the use of the dbms_stats.diff_table_stats_in_history function to compare table statistics between analysis runs. An example SQL query is provided to illustrate how to use this function.

Uploaded by

PGTEST
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
10 views1 page

Optimizer Information

The document provides information on sources for SQL execution plans and AWR data, specifically mentioning v$sql, v$sql_text, v$sql_plan, dba_hist_sqltext, and dba_hist_sql_plan. It also describes the use of the dbms_stats.diff_table_stats_in_history function to compare table statistics between analysis runs. An example SQL query is provided to illustrate how to use this function.

Uploaded by

PGTEST
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 1

 Explain Plan

The source for DISPLAY_CURSOR is v$sql / v$sql_text / v$sql_plan


The source for DISPLAY_AWR is dba_hist_sqltext & dba_hist_sql_plan.

 The dbms_stats.diff_table_stats_in_history function should give you the number of rows


differs between each table analyse run.

select * from table(dbms_stats.diff_table_stats_in_history(


ownname => user,
tabname => upper('&tabname'),
time1 => systimestamp,
time2 => to_timestamp('&time2','yyyy-mm-dd:hh24:mi:ss'),
pctthreshold => 0));

You might also like