In One of our database environment we noticed that AWR report is not available for particular time interval.
In further investigating we found one MMON related error in the alert log.
Cause:
While MMON activity is important in maintaining information in the database, if the cpu utilization and database activities exceeds cpu or run time policies, then MMON activity can be temporarily suspended. This is done so that more important activity can continue. The "Suspending MMON ... for 82800 seconds" warning messages indicate that you should look at the overall performance of your system to check if there is anything that could be causing MMON activities to exceed their resource allocation such that they are suspended.
Solution: Increase the Server configuration add RAM and more CPUs.
In further investigating we found one MMON related error in the alert log.
Cause:
While MMON activity is important in maintaining information in the database, if the cpu utilization and database activities exceeds cpu or run time policies, then MMON activity can be temporarily suspended. This is done so that more important activity can continue. The "Suspending MMON ... for 82800 seconds" warning messages indicate that you should look at the overall performance of your system to check if there is anything that could be causing MMON activities to exceed their resource allocation such that they are suspended.
Solution: Increase the Server configuration add RAM and more CPUs.
