How to Control the Set of Top SQLs Captured During AWR Snapshot Generation
(Doc ID 554831.1)
Last updated on OCTOBER 23, 2019
Applies to:
Oracle Database - Enterprise Edition - Version 10.2.0.1 to 10.2.0.5 [Release 10.2]Oracle Database - Enterprise Edition - Version 11.2.0.4 to 11.2.0.4 [Release 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Information in this document applies to any platform.
Symptoms
- Table WRH$_ACTIVE_SESSION_HISTORY is growing to a large size.
- It is suspected that it may be an issue with purging (similar to the problem described in <Note 387914.1>).
But, it appears purging works correctly, and the output from the following query shows default values for snap_interval (1 hour) and retention period (7 days) which is correct:
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |