SEVERE: EM is not configured for this database

To contact us Click HERE
Hi Friends,

I was doing this Oracle 10gR1 database upgrade to Oracle 10gR2 using DBUA (Database Upgrade Assistant) when my upgrade failed due to this error:


[Thread-54] [10:25:54:325] [BasicStep.configureSettings:304]  messageHandler being set=oracle.sysman.assistants.util.UIMessageHandler@6014f7
[Thread-54] [10:25:54:325] [SummarizableStep.setUpgradeStatus:620]  **++Set Upgrade status to:=1
oracle.sysman.assistants.util.step.StepExecutionException: Enterprise manager configuration failed due to the following error -
EM is not configured for this database. No EM-specific actions can be performed.
Refer to the log file at C:\OracleHomes\db10gr2\cfgtoollogs\dbua\emrep\upgrade1\emConfig.log for more details.
You can retry configuring this database with Enterprise Manager later by manually running C:\OracleHomes\db10gr2\bin\emca script.
    at oracle.sysman.assistants.util.em.EMConfigStep.executeImpl(EMConfigStep.java:141)
    at oracle.sysman.assistants.util.step.BasicStep.execute(BasicStep.java:210)
    at oracle.sysman.assistants.util.step.BasicStep.callStep(BasicStep.java:251)
    at oracle.sysman.assistants.dbma.backend.EMConfigStep.executeStepImpl(EMConfigStep.java:101)
    at oracle.sysman.assistants.dbma.backend.SummarizableStep.executeImpl(SummarizableStep.java:174)
    at oracle.sysman.assistants.util.step.BasicStep.execute(BasicStep.java:210)
    at oracle.sysman.assistants.util.step.Step.execute(Step.java:140)
    at oracle.sysman.assistants.util.step.StepContext$ModeRunner.run(StepContext.java:2468)
    at java.lang.Thread.run(Thread.java:534)
[Thread-54] [1:7:4:273] [EMConfigStep.handleNonIgnorableError:197]  EMConfig Error:=Error ignored: Could not complete the Enterprise Manager configuration.
Enterprise manager configuration failed due to the following error -
EM is not configured for this database. No EM-specific actions can be performed.
Refer to the log file at C:\OracleHomes\db10gr2\cfgtoollogs\dbua\emrep\upgrade1\emConfig.log for more details.
You can retry configuring this database with Enterprise Manager later by manually running C:\OracleHomes\db10gr2\bin\emca script.

[Thread-54] [1:7:4:273] [EMConfigStep.executeStepImpl:161]  EM Configuration Step Complete..
[Thread-54] [1:7:4:273] [SummarizableStep.executeImpl:175]  execute impl:Enterprise Manager Configuration = DONE Sucessfully
[Thread-54] [1:7:4:273] [BasicStep.configureSettings:304]  messageHandler being set=oracle.sysman.assistants.util.UIMessageHandler@6014f7

At first, i thought its over! My database is gone...but a few research down the line gave me a breather :)
I was upgrading my Oracle Enterprise Manager (OEM) Grid Control Database from 10.1.2.0 to 10.2.1.0. A Grid Control Database installation does not have a separate DBConsole installed as the Database is also managed by the OEM itself.

So in my particular case, i could simply press OK & then move ahead. The upgrade was almost complete & nothing else was required.

I just reconfigured the LSNRCTL & NET SERVICE NAME using Net Configuration Tool & rebooted my server & my new database was up & running.

However, if you are not upgrading a GC Repository Database, but an actual standalone database, this error should not be ignored as your DB Console would not be upgraded due to it.
You must followup with Oracle & find out why the upgrade for DBConsole failed.

Hope this info helps!

Keywords:
Oracle Database, Oracle 10GR1, Oracle 10GR2, Oracle Enterprise Manager, OEM, Grid Control, GC Repository Upgrade, Database Upgrade, DB Console, LISTENER.ORA, TNSNAMES.ORA, SQLNET.ORA, Listener Control, TNS Listener, DBUA, EMCA etcRelated Posts : OEM