Configure OEM 10g Database Control after Clone

After cloning an EBS environment I had tried to start the OEM 10g Database Control (DBConsole) and I got this message:
[oratest@testsrv1 ~]$ emctl start dbconsole
 OC4J Configuration issue.
 /oracle/test/db/testdb/10.2/ oc4j/j2ee/OC4J_DBConsole_testsrv1.domain_TEST not found.
[oratest@testsrv1 ~]$ emca -config dbcontrol db
 INFO: Database Control started successfully
 INFO: >>>>>>>>>>> The Database Control URL is http://testsrv1.domain:5500/em <<<<<<<<<<<
 Enterprise Manager configuration completed successfully
Well, I thought it looks fine, but when I opened the DB Console I saw this message at the top of the page:
 java.lang.Exception: Exception in sending Request :: null
After some research, logs digging and Metalink searches, I found that the Agent component should be relinked manually.
 But before there are two issues in file that should be fixed before executing the relink command.
I will show my actions step by step:
  1. Stop DB Console:
     emctl stop dbconsole
  2. cd $ORACLE_HOME/sysman/lib
  3. Edit and look for "JRE_LIB_DIR"
     In my instance JRE_LIB_DIR was populated with the old environment name..
     I changed it from:
  4. One more issue for, look for "$(LIBNMEM)  $(LIBNMER)"
     And change from:
     $(LIBNMEM)  $(LIBNMER) \
  5. Now relink the Agent component by issuing this command:
     make -f agent
  6. Recreate the DB Control configuration files (Again, even if you did it before)
     emca -config dbcontrol db
Following this procedure will make the DBConsole configured and work for the new cloned instance.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: