Skip to main content

CHECK ALL EXECUTION PLAN ID'S OF A SQLID IN ORACLE DATABASE


spool check_execution_plan_details.log

set linesize 600
select a.sql_id,a.snap_id,to_char(b.begin_interval_time,'mm/dd/yyyy hh24:mi') snap_tm,
a.INSTANCE_NUMBER,a.PLAN_HASH_VALUE,a.SORTS_DELTA,
a.EXECUTIONS_DELTA,a.disk_reads_delta,a.buffer_gets_delta,
a.rows_processed_delta,a.cpu_time_delta/1000000 cpu_time_delta,
a.elapsed_time_delta/1000000 iowait_delta,
a.clwait_delta/1000000 clwait_delta
from dba_hist_sqlstat a, dba_hist_snapshot b
where a.sql_id='&sql_id'
and a.SNAP_ID=b.snap_id
and a.instance_number=b.instance_number
and a.dbid=b.dbid
order by a.instance_number,a.snap_id desc,a.plan_hash_value;
spool off;

Comments

Post a Comment

Popular posts from this blog

ORA-28007: THE PASSWORD CANNOT NE REUSED

             - Here will see how to deal with  => ORA-28007: the password cannot be reused -  I got a request from client user, stating his account has been locked. When I check the status of the account I found the below. connect to SYS user & execute the below query of that database. SQL> select password,username,account_status,profile from dba_users where username='TEST'; PASSWORD               USERNAME   ACCOUNT_STATUS                 PROFILE ------------------             ----------------  -------------------------------           -------------------- AB2Aa8AC9971521e3     TEST       EXPIRED(GRACE)&LOCKED    NONAPP_USERS So, then I have unlocked the account and checked the same again & I found the below results. ...
Post a Comment
Read more

ORA-39014: One or more workers have prematurely exited.ORA-00018: maximum number of sessions exceeded

ERROR: I was Performing a full database import and during the import I faced the below error. ORA-39014: One or more workers have prematurely exited. ORA-39029: worker 6 with process name "DW07" prematurely terminated ORA-31672: Worker process DW07 died unexpectedly. Job "SYSTEM"."SYS_IMPORT_FULL_04" stopped due to fatal error at 00:59:40 ORA-39014: One or more workers have prematurely exited. SOLUTION:  Run the import with fewer parallel processes, like PARALLEL=2 instead of 8. I was able to run the import successfully. NOTE 1: This errors occurs when there are less session allocation in the database. check the session,process parameters and increase them accordingly. To avoid such errors again. NOTE 2 : Note: Increasing processes parameter increases the amount of shared memory that needs to be reserved & the OS must be configured to support the larger amount of shared memory. So here we first need to increase the Memory & SG...
Post a Comment
Read more