Issue - EM is not able to connect to the db instance even if the db instance is up and running. (In this picture the listener is down just because I didn't started. It is not our concern here)
Impact - we can't manage the database and its instance using Enterprise Manager.
Resolutions - We need to check on SYSMAN account.
(1) SYSMAN: this accounts should be open, and the password is not expired.
> sysman : Used to perform Oracle Enterprise Manager admin tasks.
The EM super admin account with mgmt_user, resource &
select_catalog_role roles granted. When we log in the OEM using SYS or
SYSTEM, we are logging in as this super user.
** DBSNP : If we see this account locked and expired. We need to alter this account as
well because this account is used to monitor and manage the database.
==> SQL> alter user sysman account unlock identified by newpassword ;
(2) Having SYSMAN and DBSNP accounts available seems to be good enough. However, I would also just check on two more things.
> remote_login_passwordfile
I would make sure that this parameter is set to "exclusive"
==> SQL> show parameter password
SQL> alter system set remote_login_passwordfile=exclusive scope=spfile;
Then, restart the database instance.
> password file exist?
I would also make sure that a password file exist or just recreate it.
==> $> orapwd file=file_name password=new_password entries=max_num_of_users
i.e) orapwd file=$ORACLE_HOME/dbs/orapworcl password=oracle entries=10
Lastly, I have found that we need to be really really PATIENT until the EM starts working correctly. We would expect to see the problem corrected right away after resetting the accounts. But nope!!! It seems that it takes quite long time for the EM to recognize the reconfiguration. It would be a great idea to restart the EM control.
No comments:
Post a Comment