My Oracle Support Banner

EM 13c: OMS Fails to Start and emctl.msg File Reports Critical error err=3 detected in module Notification Delivery (Doc ID 2415712.1)

Last updated on OCTOBER 03, 2018

Applies to:

Enterprise Manager Base Platform - Version 13.2.0.0.0 and later
Information in this document applies to any platform.

Symptoms

EM 13.2 OMS Fails to start

$OMS_HOME/bin/emctl start oms
Oracle Enterprise Manager Cloud Control 13c Release 2
Copyright (c) 1996, 2016 Oracle Corporation.  All rights reserved.
Starting Oracle Management Server...
WebTier Successfully Started
Oracle Management Server is Down
JVMD Engine is Down

During the startup time, emctl.msg ($../gc_inst/em/EMGC_OMS1/sysman/log/) gets updated stating that OMS is internally crashing with the following error during the startup itself.

Critical error err=3 detected in module Notification Delivery
OMS will be restarted. A full thread dump will be generated in the log file
/tools/oracle/product/cloudcontrol/13.2/gc_inst/user_projects/domains/GCDomain/servers/EMGC_OMS1/logs/EMGC_OMS1.out
to help Oracle Support analyse the problem.

HealthMonitor <timestamp> Notification Delivery error: External OS Command [OSCMD NAME] is hung, its execution exceeded 330 seconds time limit for queue=OSCMD1, device_id=15, ruleset_name=RuleSetName, rule_name=RuleName, rule_owner=SYSMAN. Restarting OMS ...

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
Cause
Solution
References


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