Last updated on FEBRUARY 10, 2017
Applies to:Oracle Database - Enterprise Edition - Version 10.1.0.2 and later
Information in this document applies to any platform.
When examining V$SQL during a given hour, a certain SQL statement is consuming a very high amount of resources, so much so that it has dominated the resources provided to the instance for the majority of the hour. Yet later on, when trying to examine the performance details for that particular hour within DBA_HIST_SQLSTAT, there is no record of it. You may even locate SQL_ID and SQL_PLAN_HASH_VALUE information in view DBA_HIST_ACTIVE_SESS_HISTORY but cannot join them to their relevant columns within DBA_HIST_SQLSTAT for that hour.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms