DB Tricks -->

DataBase Tips and Tricks

Main menu:


Did I save you some time? Buy me a coffee

Site search

September 2010
M T W T F S S
« Jun    
 12345
6789101112
13141516171819
20212223242526
27282930  

Categories

Tags

Blogroll

What to do when Enterprise Manager is not able to connect to the database instance (ORA-28001)

If you are trying to connect to the Oracle enterprise Manger and you get the following errors:

Enterprise Manager is not able to connect to the database instance.

And in the “Agent connection to instance” section:

Status: Failed
Details: ORA-28001: the password has expired (DBD ERROR: OCISessionBegin)

One of the reasons could be that the password for the SYSMAN user is expired. However, changing the password alone will not solve this issue. Several additional steps are required in order to make Oracle Enterprise Manager connect:

Before you start: Verify that ORACLE_HOME, ORACLE_SID environment variables are set. – If not, set them using as  environment variables or open a command line and type SET ORACLE_SID=<The database SID>

1. Stop the dbconsole: emctl stop dbconsole (dos and Unix) or  using the windows services stop the OrcleDBConsole<The database SID>.

2. Connect to the database as a user with DBA privilege with SQL*Plus
and run the following command:

alter user sysman identified by <the new password> ;

3. Verify that the new password works
SQL> connect sysman/<the new password>

4. Go to ORACLE_HOME/<HostName_SID>/sysman/config and save a backup of the emoms.properties file.

a) Open the file emoms.properties and search for:
oracle.sysman.eml.mntr.emdRepPwd=<some encrypted value>

Replace the encrypted value with the new password value

b) Search for oracle.sysman.eml.mntr.emdRepPwdEncrypted=TRUE
and change TRUE to FALSE

c) Save and close emoms.properties

5. Restart the dbconsole:

emctl start dbconsole (dos and Unix) or  using the windows services start the OrcleDBConsole<The database SID>.

6. Open  emoms.properties again and Search for:
a)oracle.sysman.eml.mntr.emdRepPwd=
verify  that the password is encrypted

b) oracle.sysman.eml.mntr.emdRepPwdEncrypted=
verify  that the value is set to  TRUE

7. Refresh Oracle Enterprise Manager

Comments

Comment from theophilos
Time September 11, 2009 at 6:10 am

you are damn good !!!

I am wondering how much experience a person must have to solve such problems!!!

Comment from admin
Time September 11, 2009 at 7:19 am

Thank you,
I have about 10 years of experience but every oracle error is different. I believe that once you know the concepts, with a lot of patience, you can solve stuff like this.
Thanks.

Comment from bvamos
Time January 26, 2010 at 3:37 am

Usually you should do the following:
alter user sysman account unlock;

Pingback from DB Tricks » “A service specific error occurred: 2″ when trying to start dbconsole
Time February 23, 2010 at 4:46 pm

[...] What to do when Enterprise Manager is not able to connect to the database instance. [...]

Comment from randa
Time August 8, 2010 at 6:04 am

thank you, very much for your help

Comment from admin
Time August 8, 2010 at 8:09 am

Glad to help

Write a comment





s