My Oracle Support Banner

EM 13c: OMS Fails to Start. emctl.msg File Reports "java.sql.SQLException: ORA-44203: timeout waiting for lock on cursor" (Doc ID 2658394.1)

Last updated on APRIL 13, 2020

Applies to:

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

Symptoms

EM 13c OMS Fails to start with the following errors:

$ ./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 Could Not Be Started
Check EM Server log file for details: /u01/app/oracle/gc_inst/user_projects/domains/GCDomain/servers/EMGC_OMS1/logs/EMGC_OMS1.out
Oracle Management Server is Down
JVMD Engine is Down
Starting BI Publisher Server ...
BI Publisher Server Already Started
BI Publisher Server is Up

OMS is crashing internally at the time of startup.

$../gc_inst/em/EMGC_OMS1/sysman/log/emctl.msg file reports the following errors every time the OMS Start command is executed.

OMS Heartbeat Recorder: error: Could not get id: java.sql.SQLException: ORA-44203: timeout waiting for lock on cursor

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
/u01/app/oracle/gc_inst/user_projects/domains/GCDomain/servers/EMGC_OMS1/logs/EMGC_OMS1.out
to help Oracle Support analyse the problem.

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.