Alert Log File Message "ERROR: Emon failed to start." And "wait for EMON to spawn"
(Doc ID 1361166.1)
Last updated on SEPTEMBER 04, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 11.1.0.7 to 11.2.0.2 [Release 11.1 to 11.2]Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Cloud Schema Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
EMON process fails during database start-up. When reviewing alert log file, the following error is seen:
Wed Jul 08 12:53:34 2009
ERROR: Emon failed to start.
Wed Jul 08 12:55:34 2009
ERROR: Emon failed to start.
Wed Jul 08 12:57:34 2009
ERROR: Emon failed to start.
Wed Jul 08 12:59:34 2009
ERROR: Emon failed to start.
Wed Jul 08 13:01:34 2009
ERROR: Emon failed to start.
Wed Jul 08 13:03:34 2009
ERROR: Emon failed to start.
There may be sessions waiting on "wait for EMON to spawn" as well, you can use below query to double check.
select sid, serial#, event from gv$session where upper(event) like upper('%wait for EMON to spawn%');
Changes
Enabled Advanced Queueing Notification System or if already in use, increased the client registered volume.
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 |