emctl start oms Failed with 'Oracle Management Server Could Not Be Started' emctl.msg file reports OMS Heartbeat Recorder Error (12.1.0.2 as Repository Database) (Doc ID 2020043.1)

Last updated on JUNE 18, 2015

Applies to:

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

Symptoms

OMS fails to start with the following error:

$<OMS_HOME>/bin>./emctl start oms

Starting Oracle Management Server...
Starting WebTier...
WebTier Successfully Started
Oracle Management Server Could Not Be Started
Check EM Server log file for details: ../gc_inst/user_projects/domains/GCDomain/servers/EMGC_OMS1/logs/EMGC_OMS1.out
Oracle Management Server is Down

For every restart attempt, $EM_INSTANCE_BASE/gc_inst/em/EMGC_OMS1/sysman/log/emctl.msg file reports following errors:

OMS Heartbeat Recorder: error: Zero rows updated for this oms during heartbeat
Critical error err=3 detected in module OMS Heartbeat Recorder:
OMS will be restarted. A full thread dump will be generated in the log file
/u02/app/oraoms/products/12c/gc_inst/user_projects/domains/GCDomain/servers/EMGC_OMS1/logs/EMGC_OMS1.out
to help Oracle Support analyse the problem.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms