'Unable to Schedule a MMON Secondary' Message in Trace File After Enable/Disable Restricted Session
(Doc ID 458981.1)
Last updated on JULY 08, 2021
Applies to:Oracle Database - Enterprise Edition - Version 10.1.0.4 and later
Information in this document applies to any platform.
***Checked for relevance on 04-Feb-2016***
-- Problem Statement:
A trace file is generated with errors such as:
Unable to schedule a MMON secondary at: Auto Flush Main 1
Attempt to create secondary process failed.
Can happen for several reasons:
- No process state objects
- Reached OS set limits
- A shutdown was going on
Check alert log for more details.
After enable/disable restricted session.
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