MMON Process Causing Blocking And Contention - enq: WF - contention waits
(Doc ID 2649588.1)
Last updated on APRIL 17, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 12.2.0.1 and laterInformation in this document applies to any platform.
Symptoms
MMON Process Causing High WF - contention waits.
WF - contention waits are seen when MMON (Manageability Monitor) is attempting the auto-flush function. That means that the
database is trying to flush the ASH (Active Session History) data into the AWR (Active Workload Repository) for the historical repository.
database is trying to flush the ASH (Active Session History) data into the AWR (Active Workload Repository) for the historical repository.
Changes
Expired and old AWR related data not being cleared causing Auto-Flush Action to run long.
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 |
Changes |
Cause |
Solution |
References |