Database installs with Enterprise Manager configuration warning
Last Updated September 12, 2009
The following warning window pops up at the end of the Database Creatation Assistant (DBCA) run:
Enterprise manager configuration failed due to the following error - Error instantiating EM configuration files Refer to the log file at c:\oracle\product\10.2.0\db_1\cfgtoollogs\dbca\protect\emConfig.log for more details. You can retry configuring the database with Enterprise Manager later by manually running C:\oracle\product\10.2.0\db_1\bin\emca script.
Refering to the emConfig.log, you find something like the following:
Destination (shared install) : C:\oracle\product\10.2.0\db_1\totallydismal_protect DeployMode : dbconsole Creating directories... Setting console properties ... Setting log and trace files locations for Console ... Setting log and trace files locations for Agent ... Sep 1, 2009 2:35:39 PM oracle.sysman.emcp.util.PlatformInterface executeCommand CONFIG: CreateService FAILED: The specified service already exists. Service creation failed. Aborting... Sep 1, 2009 2:35:39 PM oracle.sysman.emcp.util.PlatformInterface executeCommand WARNING: Error executing CMD /C C:\oracle\product\10.2.0\db_1\bin\emctl.bat deploy dbconsole C:\oracle\product\10.2.0\db_1\totallydismal_protect totallydismal:3938 totallydismal protect Sep 1, 2009 2:35:39 PM oracle.sysman.emcp.EMAgentConfig instantiateEMConfigFiles CONFIG: Failed to deploy state dirs Sep 1, 2009 2:35:39 PM oracle.sysman.emcp.EMConfig perform SEVERE: Error instantiating EM configuration files Refer to the log file at C:\oracle\product\10.2.0\db_1\cfgtoollogs\dbca\protect\emConfig.log for more details. Sep 1, 2009 2:35:39 PM oracle.sysman.emcp.EMConfig perform CONFIG: Stack Trace: oracle.sysman.emcp.exception.EMConfigException: Error instantiating EM configuration files at oracle.sysman.emcp.EMAgentConfig.updateAgentConfigFiles(EMAgentConfig.java:2689) at oracle.sysman.emcp.EMAgentConfig.performConfiguration(EMAgentConfig.java:1206) at oracle.sysman.emcp.EMAgentConfig.invoke(EMAgentConfig.java:230) at oracle.sysman.emcp.EMAgentConfig.invoke(EMAgentConfig.java:208) at oracle.sysman.emcp.EMConfig.perform(EMConfig.java:175) at oracle.sysman.assistants.util.em.EMConfiguration.run(EMConfiguration.java:436) at java.lang.Thread.run(Thread.java:534)
The database has been created and should be fine.
The error comes up on windows servers that have previously had the Oracle agent installed on it, where the agent was NOT properly stopped and deleted prior to reinstallation. The agent works independently from the database and provides information to Oracle's Enterprise Manager. The Oracle database will not be impacted directly by its presence or absence. Click OK to move past the warning and you will see that the database is alive and well.
The Oracle agent can be reinstalled at a later time, if desired.
Imported Document ID: TECH221425
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe