This content has been marked as final. Show 5 replies
The log and trace files end with notification that "The account is locked"
There is no indication which account is locked. I have unlocked the sysman, dbsnmp, and system accounts, in sqlplus, and verified that they were unlocked by connecting to them using "connect" in sqlplus, previous to trying to open the EM. So I have no idea which account is locked, unless the accounts are being locked by something else. (?)
Okay, I've done some more investigation.
I logged into sqlplus as SYS AS SYSDBA
Tried to connect to SYSMAN but the system responded with a message that the account is locked and then it disconnected my session.
Connected back to the database via the command: CONNECT SYS AS SYSDBA
Entered the password and connected successfully
Unlocked the SYSMAN account via the command: ALTER USER SYSMAN ACCOUNT UNLOCK;
Connected to the database successfully as SYSMAN
Tried to open OEM: Opened directly to the Status display with out opening the login page
Went back to sqlplus and tried connection as SYSMAN but the system said the account was locked
Trace file emoms.trc also says the account is locked.
So it does look like the attempt to open the OEM, or something else, is locking the sysman account
It could be that DB Control and/or some other application were repeatedly trying to connect to the repository as user sysman without success causing the account to be locked.
I suggest follow the steps in the following MOS note to change the sysman password for DB Control.
How To Change the Password of the Database User Sysman (DB Control Repository Schema) (Doc ID 259379.1)
This is exactly the information I needed. I notice two methods for changing the password one for DB version prior to 10.2 and one for 10.2 and later. I learned the procedures for those versions prior to 10.2 and was applying those to my 11.2 DB. The proper procedure worked exactly right and it is a much better process than the previous one.
Thank-you for the help.