Monthly Archives: July 2012

Database Control Gives Error Message: “Enterprise Manager Is Not Able To Connect to the Database instance”

In the Database Control Console, the home page shows the following error:
Enterprise Manager is not able to connect to the database instance. The state of the components are listed below.
Instance Status:Open
Listener Status: Up
Agent Status: Succeeded

Please ensure that DBSNMP, SYSMAN, and SYS accounts are not locked nor password is expired for these accounts. If the accounts are locked or expired, please unlock or change the password accordingly.

If this doesn’t fix the issue, you need to try additional steps are required in order to make Oracle Enterprise Manager connect. Please ensure that ORACLE_HOME, ORACLE_SID environment variables are set correctly and then follow the below steps:

1) Stop the dbconsole by running the below command:
$emctl stop dbconsole

2) Connect to the DB as a user with DBA privileges using SQL*Plus and run the following command:
alter user sysman identified by <new password>

3) Next verify if the new password works
SQL> connect sysman/<new password>

4) Navigate to $ORACLE_HOME/<HostName_SID>/sysman/config and make 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

Login in again to verify if the issue is fixed.

Note:
If you reopen  ”emoms.properties” file, ”oracle.sysman.eml.mntr.emdRepPwd” is encrypted and the value ”oracle.sysman.eml.mntr.emdRepPwdEncrypted” is TRUE

Advertisements

3 Comments

Filed under Oracle

how to verify if your Database is running archive log/ no archive log mode in Oracle

Login as sys user and run the below command to verify if database log mode is in archive mode or no archive mode.

SQL>archive log list;

Database log mode              No Archive Mode
Automatic archival             Disabled
Archive destination            USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence     19
Current log sequence           21

You might get the value as shown above and if you notice the “Database log mode” is in “No Archive Mode”, then you need to enable  it by running the below commands:

SQL>shutdown immediate;

SQL>startup mount;

SQL>alter database archivelog;

SQL> alter database open;

To issue the SQL command to put the database in ARCHIVELOG mode, the database must be in MOUNTmode. If the database is currently open, you must shut it down cleanly (not abort), and then mount it.

With the database in NOARCHIVELOG mode (the default), recovery is possible only until the time of the last backup. All transactions made after that backup are lost.
In ARCHIVELOG mode, recovery is possible until the time of the last commit. Most production databases are operated in ARCHIVELOG mode.

To see the current archiving mode, query the V$DATABASE view:

SQL> select log_mode from sys.v$database;

LOG_MODE
————
ARCHIVELOG

Leave a comment

Filed under Oracle