OracleDBConsole<Instance> don't start after install a second database [message #628646] |
Wed, 26 November 2014 13:46 ![Go to next message Go to next message](/forum/theme/orafaq/images/down.png) |
![](//www.gravatar.com/avatar/790a12b2d2820900e1a418c5aa94d255?s=64&d=mm&r=g) |
chillkroetle
Messages: 21 Registered: October 2014 Location: germany
|
Junior Member |
|
|
Hi everybody,
i hope somebody can help me. I've installed Oracle on Windows 2008R2 within a VMware. My first instance is started successfull without any problems. Next i installed a second database with the database configuration assistent. My first database is called Instance1, the second database is called Instance2.
After the installation all services are started successfully and i can connect to both instances over the enterprise manager.
But when i restart the VMware Windows one of the OracleDBConsole<Instance> service don't start. It stays a long time on "is starting". In this time i cannot open the windows network environment, etc. After a Windows restart it could be that it is the service OracleDBConsoleInstance1 and on the next reboot OracleDBConsoleInstance2.
After the service "is starting" mode is over i can't start the service manually. What is the problem here?
|
|
|
|
|
|
|
|
|
Re: OracleDBConsole<Instance> don't start after install a second database [message #628896 is a reply to message #628893] |
Sun, 30 November 2014 07:12 ![Go to previous message Go to previous message](/forum/theme/orafaq/images/up.png) ![Go to next message Go to next message](/forum/theme/orafaq/images/down.png) |
John Watson
Messages: 8964 Registered: January 2010 Location: Global Village
|
Senior Member |
|
|
Are you assigning an IP address to your VM with DHCP? Because OEM really doesn't like that. Look for any directories in your %ORACLE_HOME% with names that have an ip address embedded within them. On my 11.2.0.3 Windows install, I have these
c:\app\oracle\product\11.2.0\db112\192.168.1.65_orcla
c:\app\oracle\product\11.2.0\db112\oc4j\j2eeOC4J_DBConsole_192.168.1.65_orcla
If you have any names like that, you may need to bind the hostname to a static address (I always use 127.0.0.1) and then drop and recreate Database Control.
|
|
|
Re: OracleDBConsole<Instance> don't start after install a second database [message #628903 is a reply to message #628896] |
Sun, 30 November 2014 11:59 ![Go to previous message Go to previous message](/forum/theme/orafaq/images/up.png) ![Go to next message Go to next message](/forum/theme/orafaq/images/down.png) |
![](//www.gravatar.com/avatar/d29f577f753cb4b873212fd5ed0da4cd?s=64&d=mm&r=g) |
EdStevens
Messages: 1376 Registered: September 2013
|
Senior Member |
|
|
John Watson wrote on Sun, 30 November 2014 07:12you may need to bind the hostname to a static address (I always use 127.0.0.1) and then drop and recreate Database Control.
While I agree with the rest that you said (not quoted here) I'd like to offer a counter argument to the suggestion to specifically use ip address 127.0.0.1 (or its alias, 'localhost').
As you know, if the only fixed IP address the server has is 127.0.0.1, the listener will never get a connection from any other system -- like the host system.
When I set up virtual machines on my desktop, I want to be able to treat them exactly like I do any server in my data center. That means a couple of things right up front.
First, the vm console is effectively the same as the physical console of a physical machine. I don't get up and go to the data center to interact with those systems, so neither do I use the vm console for my vm's. Second, because of the previous, I access my vms (and their databases) using exactly the same desktop tools as used for my live servers and databases. Putty, sqlplus, SQL Developer, WinSCP, UltraEdit, SQL Navigator, etc, etc, etc. And all of that means that my vm's have to have a fixed address that is routable -- not 127.0.0.1. My preference and practice is to configure the vm's as 'hostonly'. That way they can have a fixed, routable IP address, can be connected to from my desktop system exactly the same as any server in the data center, and are completely hidden from the corporate network, so I can do whatever I like with them and not worry about any impact outside of my own desktop.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Re: OracleDBConsole<Instance> don't start after install a second database [message #629320 is a reply to message #629150] |
Sun, 07 December 2014 07:06 ![Go to previous message Go to previous message](/forum/theme/orafaq/images/up.png) |
![](//www.gravatar.com/avatar/790a12b2d2820900e1a418c5aa94d255?s=64&d=mm&r=g) |
chillkroetle
Messages: 21 Registered: October 2014 Location: germany
|
Junior Member |
|
|
Hi EdStevens,
when i set the dbconsole service which do not start automatically to manual start type and reboot the VM i can start manual the problem dbconsole service without any problems after the reboot of the VM. So it seems that it only have a problem when i set the service to the automatic start type.
In the OracleDBConsoleELO2srvc it logs:
istatus
12/07/14 14:00:46 Received exitCode 1 from emctl istatus
12/07/14 14:00:51 Timedout while tracking process to start. Terminating..
|
|
|