My Oracle Support Banner

OMS Stop/Start not working due to ORA-28000 error with SYSMAN account locked status (Doc ID 2587425.1)

Last updated on JANUARY 02, 2020

Applies to:

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

Symptoms

OMS stop is not working and processes are in pending state, unable to stop the OMS completely.

cd <middleware-home>/bin/
 ./emctl stop oms -all -force
Oracle Enterprise Manager Cloud Control 13c Release 3
Copyright (c) 1996, 2018 Oracle Corporation. All rights reserved.
Stopping Oracle Management Server...
WebTier Successfully Stopped
Oracle Management Server Already Stopped
Oracle Management Server is Down
JVMD Engine is Down
Stopping BI Publisher Server...

 

+ <EM_INSTANCE_HOME>/user_projects/domains/GCDomain/servers/EMGC_ADMINSERVER/logs/EMGC_ADMINSERVER.out

 

<Warning> <oracle.mds> <BEA-000000> <Failed to get schema version from registry for repository "mds-owsm" because of exception: weblogic.jdbc.extensions.ConnectionDeadSQLException: weblogic.common.resourcepool.ResourceDeadException: 0:weblogic.common.ResourceException: Could not create pool connection for datasource 'mds-owsm'. The DBMS driver exception was: ORA-28000: the account is locked>

<Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "mds-sysman_mds": ORA-28000: the account is locke>

 

+ <EM_INSTANCE_HOME>/em/EMGC_OMS<n>/sysman/log/emoms.trc

 

[#EM_SYSTEM_POOL#:BadSQLEvaluation] ERROR dbjava.sqleval doWork.148 - Exception from BadSQLEvaluation: java.sql.SQLException: ORA-28000: the account is locked

[<oms-host>:<oms http port>_Management_Service:MDA_SCHEDULER] WARN  engine.MdaScheduler logp.251 - Error in isMDAGloballyDisabled
oracle.sysman.emInternalSDK.sdkas.mda.MdaException: Exception while looking up JVMD DataSource : weblogic.common.resourcepool.ResourceDeadException: 0:weblogic.common.ResourceException: Could not create pool connection for datasource 'jvmd-ds'. The DBMS driver exception was: ORA-28000: the account is locked

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!


In this Document
Symptoms
Changes
Cause
Solution
 Changing the SYSMAN and MGMT_VIEW Passwords


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