Q: I was not able to start the Oracle 11g Enterprise Manager service.
This happened after renaming my computer and although I reconfigured Oracle and my network settings (eg hosts file) for the new computer name it was not enough to get it working.
Basically, the Oracle Enterprise Manager service could not be started on the Windows Services management console. Alternatively, running ‘emctl start dbconsole’ on a command prompt did not do it either.
Checked for solutions on the Internet and found that several others had faced the same problem too.
A: Checking the log file OracleDBConsoleORCLsvc.log (in the oracle_home\computername\sysman\log directory) I found that Oracle had exited with a certain numeric exit code. The log further referred to the log file OracleDBConsoleorcl.nohup which contains a lot more detail on what happened.
In my case, the log file told me that the Java runtime could not find a particular directory (applib) and bombed the startup process. Finding a similar directory elsewhere (which actually contained another log file), I copied it over to where Oracle was looking for it, and this got the EM working again.
Lesson learnt: The OracleDBConsoleorcl.nohup log file contains a wealth of details about the Oracle Enterprise Manager service. It’s helpful to refer to it in solving problems of not being able to start the Oracle Enterprise Manager.