Home > Oracle > OracleDBControl

OracleDBControl

June 24th, 2009

If you have ever exported and imported complete databases and moved them around from one server to another, you have probably noticed the issues that might occur with the EM repository. During the last delivery project that I worked on I had to import two databases in two Oracle servers (10.2.0.4) installed on Microsoft Windows 2003 x64. Everything was going smooth with the DBCA during the creation of the new database. I have selected the database to be manager using Enterprise Manager so the EM repository was being installed. Unfortunately it errored out. The logs are stored in the following location:

D:\oracle\product\10.2.0\db_1\cfgtoollogs\emca\instance_name (ORACLE_HOME\cfgtoollogs\emca\instance_name)

I found out that everything with the creation of the EM repository has been successful except the actual start of the windows service. In the log files I found the following trace:

24.06.2009 10:11:50 oracle.sysman.emcp.EMReposConfig createRepository
INFO: Creating the EM repository (this may take a while) ...
24.06.2009 10:14:32 oracle.sysman.emcp.EMReposConfig invoke
INFO: Repository successfully created
24.06.2009 10:14:42 oracle.sysman.emcp.util.DBControlUtil secureDBConsole
INFO: Securing Database Control (this may take a while) ...
24.06.2009 10:15:08 oracle.sysman.emcp.util.DBControlUtil secureDBConsole
INFO: Database Control secured successfully.
24.06.2009 10:19:48 oracle.sysman.emcp.util.DBControlUtil startOMS
INFO: Starting Database Control (this may take a while) ...
24.06.2009 10:21:13 oracle.sysman.emcp.util.DBControlUtil startOMS
INFO: Starting Database Control (this may take a while) ...
24.06.2009 10:25:08 oracle.sysman.emcp.util.DBControlUtil startOMS
INFO: Starting Database Control (this may take a while) ...
24.06.2009 10:24:08 oracle.sysman.emcp.util.DBControlUtil startOMS
INFO: Starting Database Control (this may take a while) ...

When the timeout kicks the service fails to start.

The same thing happened on the two Windows servers and I was not sure what the possible reason could be.

Previously I have dealt with EMCA issues and the best article that I have found so far was one called “Problem Re-Creating the Sysman Account with EMCA results in Error ORA-20001” with Metalink Doc.ID 738671.1.

I usually perform the following to deconfigure a repository:

set ORACLE_HOME=
set ORACLE_SID=
cd ORACLE_HOME\BIN
emca -deconfig dbcontrol db -repos drop

This will completely remove the EM repository from the database server.
You might check that the following directories have been removed by the above command.
If not, remove them manually.

/
/oc4j/j2ee/OC4J_DBConsole__

To create a repository use the following:

set ORACLE_HOME=
set ORACLE_SID=
cd ORACLE_HOME\BIN
emca -config dbcontrol db -repos create

This will create the repository. Logs for the repository should be in the same location as previously mentioned.
ORACLE_HOME\cfgtoollogs\emca\instance_name

The problem with the windows servers was that the DBControl service would not start again with the identical problem in the logs.

24.06.2009 10:15:08 oracle.sysman.emcp.util.DBControlUtil startOMS….

At that point of time I was not sure what to do next since I had everything else working fine except the EM.
I noticed that the servers were part of domain and named using the following convention:
dbname_purpose_test

Then I decided to request the responsible IT department to rename the oracle servers following the convention:
dbname-purpose-test

I unregistered the EM again and tried to create it again after the servers were renamed and restarted.

The OracleDBControl services started just fine on both servers.

This Monday I was back in the office and had more time to search for relevant information in Metalink.
I found an article called “Quick Guide to Avoid Issues in Creating DB Control Using EMCA” with DocID 750768.1.

It says that Underscore ‘_’ is not allowed in hostname – “RFC 952 – DoD Internet host table specification” and much more useful information.

HTH,
St0ma

Categories: Oracle Tags:
  1. No comments yet.
Comments are closed.