OEM Startup Fails due SYSMAN122140_OPSS account is EXPIRED

By /

Problem

I was trying to start my OEM local environment and I got a error related to some user that has been expired:

[oracle@emcc ~]$ emctl status oms
Oracle Enterprise Manager Cloud Control 13c Release 5  
Copyright (c) 1996, 2021 Oracle Corporation.  All rights reserved.
WebTier is Up
Oracle Management Server is Down
JVMD Engine is Down
[oracle@emcc ~]$ emctl start oms
Oracle Enterprise Manager Cloud Control 13c Release 5  
Copyright (c) 1996, 2021 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/oem13c/gc_inst/user_projects/domains/GCDomain/servers/EMGC_OMS1/logs/EMGC_OMS1.out
AdminServer Could Not Be Started
Check Admin Server log file for details: /u01/app/oracle/oem13c/gc_inst/user_projects/domains/GCDomain/servers/EMGC_ADMINSERVER/logs/EMGC_ADMINSERVER.out
Oracle Management Server is Down
JVMD Engine is Down

Then I checked the first log reported above and I found something like this:

Oct 21, 2026 12:30:17 PM oracle.security.jps.internal.policystore.util.JpsDataManagerUtil getDBConnection
WARNING: Can not connect DB with URL jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=emrepo.dibiei.com)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=oempdb)))
java.sql.SQLException: ORA-28001: the password has expired

Solution

What I did to fix this was connect in the repository database, search for any EXPIRED/LOCKED account and unlock the account using the password hash values.

Example:

[oracle@emcc ~]$ sqlplus / as sysdba
SQL*Plus: Release 19.0.0.0.0 - Production on Wed Oct 21 15:10:06 2026
Version 19.30.0.0.0
Copyright (c) 1982, 2025, Oracle.  All rights reserved.
Connected to:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.30.0.0.0
SQL> 
SQL> show pdbs
    CON_ID CON_NAME                       OPEN MODE  RESTRICTED
---------- ------------------------------ ---------- ----------
         2 PDB$SEED                       READ ONLY  NO
         3 RMAN_CATALOG                   READ WRITE NO
         4 OEMPDB                         READ WRITE NO
SQL> 
SQL> alter session set container = oempdb;
Session altered.

Querying users EXPIRED:

SQL> set lines 400
set pages 50
col username format a30
col created format a20
col account_status format a30
col last_login format a40
select username, created, account_status, last_login
from dba_users
where account_status LIKE 'EXPIRED%'
order by 1;SQL> SQL> SQL> SQL> SQL> SQL>   2    3    4  
USERNAME                       CREATED              ACCOUNT_STATUS                 LAST_LOGIN
------------------------------ -------------------- ------------------------------ ----------------------------------------
ANONYMOUS                      17-APR-19            EXPIRED & LOCKED
CLOUD_ENGINE_USER              25-JUN-24            EXPIRED & LOCKED
CLOUD_SWLIB_USER               25-JUN-24            EXPIRED & LOCKED
CTXSYS                         17-APR-19            EXPIRED & LOCKED
EUS_ENGINE_USER                25-JUN-24            EXPIRED & LOCKED
SYSMAN122140_OPSS              25-JUN-24            EXPIRED                        07-AUG-26 11.38.19.000000000 AM -03:00
XS$NULL                        17-APR-19            EXPIRED & LOCKED
7 rows selected.

I found this SYSMAN122140_OPSS user. I don’t know what is the current password for that user, and if I reset it with a new password, I would need to update the OMS config.

So I just grabbed the spare4: 

SQL> SELECT spare4 FROM sys.user$ WHERE name = 'SYSMAN122140_OPSS';
SPARE4
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
S:3B7CE963C4F3CD42A8DBB3822C1DFAA81AE030BAEF121052B2AF0F64AFB6;T:53B3D79632920EFF339E580AF826653FAD52506EBA4E6F9B099F6DAD447DF73CB2D072DAF661AF190E4A66BFF1814AA2B885E64337B1BAEF37A72DDCC4CC5507FB8AC5A20FF6B774CF1EAE31F6714C2D

And reseted the password with VALUES option:

SQL> ALTER USER SYSMAN122140_OPSS IDENTIFIED BY VALUES 'S:3B7CE963C4F3CD42A8DBB3822C1DFAA81AE030BAEF121052B2AF0F64AFB6;T:53B3D79632920EFF339E580AF826653FAD52506EBA4E6F9B099F6DAD447DF73CB2D072DAF661AF190E4A66BFF1814AA2B885E64337B1BAEF37A72DDCC4CC5507FB8AC5A20FF6B774CF1EAE31F6714C2D' ACCOUNT UNLOCK;
User altered.

Now the OEM could be started normally:

[oracle@emcc ~]$ 
[oracle@emcc ~]$ emctl start oms
Oracle Enterprise Manager Cloud Control 13c Release 5  
Copyright (c) 1996, 2021 Oracle Corporation.  All rights reserved.
Starting Oracle Management Server...
WebTier Successfully Started
Oracle Management Server Successfully Started
Oracle Management Server is Up
JVMD Engine is Up
[oracle@emcc ~]$

Leave a Comment

Scroll to Top

Discover more from Blog do Dibiei

Subscribe now to keep reading and get access to the full archive.

Continue reading