'Unable to Schedule a MMON Secondary' Message in Trace File After Enable/Disable Restricted Session (Doc ID 458981.1)

Last updated on APRIL 06, 2022

Applies to:

Oracle Database - Enterprise Edition - Version 10.1.0.4 and later
Information in this document applies to any platform.

Symptoms

-- 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.

Changes

After enable/disable restricted session.

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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.

'Unable to Schedule a MMON Secondary' Message in Trace File After Enable/Disable Restricted Session (Doc ID 458981.1)

Applies to:

Symptoms

Changes

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!