This morning I opened Enterprise Manager and instead of the regular “login”-screen, I found following screen:
Everything is up and running but Enterprise Manager is not able to connect to the database instance. Sounds like a connection problem, not?
These are the steps I followed to solve this issue and to reset the “sysman”-account:
STEP1: Check EM log file:
[oracle@myserver log]$ pwd
/opt/oracle/product/11.1.0/db/myserver.mydomain_DWHD
/sysman/log
[oracle@ myserver log]$ tail -50 emoms.log
…
2008-02-11 23:12:04,968 [ApplicationServerThread-11]
ERROR app.SessionObjectManager sessionDestroyed.128 -
java.sql.SQLException: ORA-28000: the account is locked
java.sql.SQLException: ORA-28000: the account is locked
…
STEP 2: Check database users:
SYSTEM> select username, account_status from dba_users;
USERNAME ACCOUNT_STATUS
------------------------------ -------------
MGMT_VIEW OPEN
SYS OPEN
SYSTEM OPEN
DBSNMP OPEN
SYSMAN LOCKED(TIMED)
STEP 3: Stop the Database Console
[oracle@myserver dbascripts]$ emctl stop dbconsole
Oracle Enterprise Manager 11g Database Control Release 11.1.0.6.0
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
https://myserver.mydomain:1158/em/console/aboutApplication
Stopping Oracle Enterprise Manager 11g Database Control ...
... Stopped.
[oracle@myserver dbascripts]$
STEP 4: Reset the SYSMAN-account
[oracle@myserver log]$ sqlplus "/ as sysdba"
SQL*Plus: Release 11.1.0.6.0 - Production on Tue Feb 12 09:51:59 2008
Copyright (c) 1982, 2007, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SYS> alter user sysman identified by <new_password> account unlock;
User altered.
STEP 5: Reset the SYSMAN-account in the “targets.xml”-file ($ORACLE_HOME/myserver.mydomain _mySID/sysman/emd) and modify the “Username”-Property and the “Password”-property as follows:
[oracle@myserver emd]$ pwd
/opt/oracle/product/11.1.0/db/myserver.mydomain_DWHD/sysman/emd
[oracle@myserver emd]$ cp targets.xml targets.xml.ori
[oracle@myserver emd]$ vi targets.xml
…
<Property NAME="UserName" VALUE="SYSMAN" ENCRYPTED="FALSE"/>
<Property NAME="password" VALUE="<new_password>" ENCRYPTED="FALSE"/>
…
STEP 6: Reset the SYSMAN-account in the “emoms.properties”-file ($ORACLE_HOME/myserver.my_domain_mySID/sysman.config) and modify the “oracle.sysman.eml.mntr.emdRepPwd”-parameter and the “oracle.sysman.eml.mntr.emdRepPwdEncrypted” in the following way:
[oracle@myserver config]$ pwd
/opt/oracle/product/11.1.0/db/myserver.mydomain_DWHD/sysman/config
[oracle@myserver config]$ cp emoms.properties emoms.properties.ori
[oracle@myserver config]$ vi emoms.properties
…
oracle.sysman.eml.mntr.emdRepPwd=<new_password>
…
oracle.sysman.eml.mntr.emdRepPwdEncrypted=FALSE
…
STEP 7: Start the Database Console
[oracle@myserver dbascripts]$ emctl start dbconsole
Oracle Enterprise Manager 11g Database Control Release 11.1.0.6.0
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
https://myserver.mydomain:1158/em/console/aboutApplication
Starting Oracle Enterprise Manager 11g Database Control ...... started.
------------------------------------------------------------------
Logs are generated in directory
/opt/oracle/product/11.1.0/db/myserver.mydomain_DWHD/sysman/log
STEP 8: Test
Superb!! Worked like a charm! Thank you ever so much.
WONDERFUL!!!!!! Thank You!
Worked perfect the first time! Thanks
Thank u so much dear !! 🙂
Good one !!! Thanks…
muchas gracias, no sabes todas las formas con las que trate de desbloquear al usuario sysman..=)Claudio.
Thank you, for giving is the different possibilities to unlock the sysman account.
Great man!
One of the most helpful post out there. Thanks a lot
Hi…It was absolutely superb. Thanks a lot. Keep the good work.
Saved my life! Every and only the steps needed!Wagner Madeira
after one day and half of unuseful work, i’ve finally found this post, and you’ve solved my trouble on my oracle installation windows. I had already tryed to unlock the sysman account before, but i didn’t know about those files… Thanks a lot.
Brilliant thanks for that. Keep up the good work.
Thanks a lot! I finally can continue with my real work…
And one more very grateful reader. Thanks for a great article
Thank you very much
Thank You verymuch….it worked very well….i have a questionafter i did this ,i started dbconsole….there in the browser it saysClusterDatabase:xyzThe database status is currently unavailable.It is possible that the database is in mount or nomount state.Click startup or perform recovery to do furthur operation.I dont know my database is up n running and i can do everything through sqlplus and my dbconsole is started status….can u help me what to do next..Thanks in advance.sam
Excellent, thank you!*getting hartbeat under control*
Excellent work. Thank you
AWESOME!!! this was f***** great!!!
Really I hadn’t known about those two files (emoms.properties, targets.xml), yet.
Of all those other troubleshoot, this the only one works for my environment.
Thanks a lot.
Nice explanation.It worked for me. ALthough for a different error i.e. paaswrod not correct. It appears this neds to be implemented whenever the sysman password neeeds to be changed.
In my installation, location of targets.xml and emoms.properties is a bit different, but after executing all the steps the EM 11g was up and running again. So thank you very much. Job very well done.
What happend when the password is encrypted, and “oracle.sysman.eml.mntr.emdRepPwd” doesn’t exist in targets.xml file?
Thanks,
Eran
THANK YOU. None of the other “fixes” I found mentioned targets.xml. Editing this file got it working for me.
I did exactly as you explained but now i’m facing a problem…. my oem services are not starting up. after i do emctl start dbconsole when i go to web browser type url of enterprise manager the following message come up..
can you help me regarding this. I’m using Oracle 11gr2 64bit on windows server 2008.
503 Service Unavailable
Servlet error: An exception occurred. The current application deployment descriptors do not allow for including it in this response. Please consult the application log for details.
excellent, I could finally solve the problem. each time it happened I had to recreate everything again, thank you.