I can't start my dbconsole (Oracle 11g) anymore, executing "emctl start dbconsole" gives me the error "A service specific error occurred: 2.". I already tried the suggested solutions in this forum (copying directories, etc.) but nothing worked.
When I look in my emagent.log i see the error:
"2011-11-29 08:00:54,864 Thread-8352 <Hochfahren von Agent> : Fehler bei Hochfahren von HTTP LISTENER
(00716) 2011-11-29 08:36:37,659 Thread-9236 Agent 10.2.0.4.2 wird aus N:\app\product\11.2.0\dbhome_1
gestartet (00701) 2011-11-29 08:36:37,737 Thread-9236 <Hochfahren von Agent> : Fehler bei Hochfahren von HTTP LISTENER (00716)"
--> startup HTTP LISTENER failure
I have to say that I have 5 different DB instances with 5 DBConsole-Services running on that machine, 3 of them are running, the other 2 have the same problem with the HTTP LISTENER. I was thinking about some port problem, but I am not sure where to start looking at.
Thanks in advance
Any clues in emdb.nohup? This file is often more informative than the other log-/trace-files.
And you are sure your machine can handle 5 database instances + 5 dbconsoles?
I saw timeout problems, when dbconsole could not start quick enough because of lack of resources (especially RAM).
i have enough RAM for the DB instances, there are also some GBs free, but i don't know how much the dbconsoles needs, at least i don't see any timeouts or performance issues
anyway, thanks for the emdb.nohub hint, i think there are some interesting lines:
-- Tue Nov 29 08:36:41 2011::Pid 7024 not found. reaped=7024, processStatus=14080 --
-- Tue Nov 29 08:36:42 2011::Checking status of EMAgent : 7024 --
-- Tue Nov 29 08:36:42 2011::EMAgent exited at Tue Nov 29 08:36:42 2011 with return value 55. --
-- Tue Nov 29 08:36:42 2011::EMAgent has exited due to initialization failure. --
-- Tue Nov 29 08:36:42 2011::Stopping other components. --
-- Tue Nov 29 08:36:42 2011::EMWD Stopping DBConsole. --
11/11/29 08:36:43 Fehler beim Starten von ORMI-Server VWAGWOSEVF03 Port 5.523: Unrecognized Windows Sockets error: 0: JVM_Bind
11/11/29 08:36:43 Shutting down OC4J...
-- DBConsole internal stop. No OC4J admin passwd hence hard stop. --
-- Tue Nov 29 08:36:47 2011::Commiting Process death. --
-- Tue Nov 29 08:36:47 2011::Exiting watchdog loop
any ideas what the problem could be with the PID 7024 and the windows socket?
Edited by: 890408 on Nov 29, 2011 4:06 AM
Unfortunately I never saw this error message before in the context of dbconsole. As suggested you should move to the Grid Control forum (also applicable for standalone dbconsole).
May be you see a message in the Windows event log, when you try to start dbconsole as a service in the control panel.