Oracle Enterprise Manager Grid Control Installation 11g Failed with SEVERE: Exception: java.net.BindException: Address already in use: JVM_Bind

February 14th, 2011 | Posted in 11G, Blog, enterprise manager, grid control | 4 Comments

I have seen few posts in the OTN forum asking about how to fix the Exception: java.net.BindException: Address already in use: JVM_Bind during the installation of Oracle Enterprise Manager Grid Control Installation 11g (11.1.0.1.0).
You can find exactly the 2 posts here:
Thread 1
Thread 2
The complete error is:

SEVERE: Exception: java.net.BindException: Address already in use: JVM_Bind
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:365)
at java.net.ServerSocket.bind(ServerSocket.java:319)
at java.net.ServerSocket.<init>(ServerSocket.java:185)
at oracle.sysman.omsca.util.CoreOMSConfigAssistantUtil.checkPort(CoreOMSConfigAssistantUtil.java:2251)
at oracle.sysman.omsca.adapter.wls.OMSWLSAdapterUtil.checkNodeMgrPort(OMSWLSAdapterUtil.java:656)
at oracle.sysman.omsca.adapter.wls.OMSWLSAdapter.adapterPreReq(OMSWLSAdapter.java:1185)
at oracle.sysman.omsca.framework.OMSGenericAdapter.doPreRequisiteChecks(OMSGenericAdapter.java:264)
at oracle.sysman.omsca.framework.OMSCAFreshInstall.execute(OMSCAFreshInstall.java:90)
at oracle.sysman.omsca.framework.OMSConfigAssistantDriver.main(OMSConfigAssistantDriver.java:210)
11 févr. 2011 15:38:59 oracle.sysman.omsca.adapter.wls.OMSWLSAdapter adapterPreReq
FIN: OMSWLSAdapter::Failed to validate node manager port
11 févr. 2011 15:38:59 oracle.sysman.omsca.framework.OMSCAFreshInstall execute
SEVERE: ERROR: Pre req checks of EM failed.
11 févr. 2011 15:38:59 oracle.sysman.omsca.framework.OMSConfigAssistantDriver main
FIN: Got resultfalse

It seems that nobody have posted in these two threads the procedure solution.
The error is raised during the OMS configuration.From the error it seems this is just a port issue which has been used by other process.

The quick procedure to fix the problem is to check the port 7401. This port number is required by the node manager during the installation process.

References:
Oracle Enterprise Manager Grid Control Advanced Installation and Configuration Guide 11g Release 1 (11.1.0.1.0)
2.3 : Understanding Installation Basics
Section : What Ports Are Used for Installation?

http://download.oracle.com/docs/cd/E11857_01/install.111/e16847/preparing_for_install.htm#BACEEJEH

The following are the default ports used for installation:
Node Manager
The default HTTPS port for Node Manager is 7401. If 7401 is not available, then the first available free port from the range 7401 to 7500 is selected.

The steps I will use below are for the installation of Oracle Enterprise Manager Grid Control 11g Release 1 (11.1.0.1.0) under windows xp.
But, you can use the same for other environments, only the commands will change.

1- Find the process ID (PID), which process is using the port 7401.
netstat -nao | findstr 7401
TCP   169.254.230.7:7401    0.0.0.0:0    LISTENING  2544
2- Note the PID (process id) for that port.
3- Next you will find out that PID with windows task manager program.
Note: By default with task manager it will not show the PID of the processes. You have to enable it from the options menu.
4- Kill the process from the task manager program
5- Try again the installation
Scridb filter


4 Comments to “Oracle Enterprise Manager Grid Control Installation 11g Failed with SEVERE: Exception: java.net.BindException: Address already in use: JVM_Bind”

  1. edsion_pong says:

    nice!thanks

  2. Fred says:

    Thanks, this exactly solved my problem !!

    I don’t understand why this whole installation procedure is so f*** complicated at all….

  3. Chinh Tran says:

    Can you help me solve this proplem in linux?Thanks!


Leave a Comment





Subscribe


Polls

which oracle topic interests you most?

View Results

Loading ... Loading ...


Oracle Class Tweets


Recent Posts


Recent Comments

  • Jaspreet: Brilliant explanation.
  • Yousuf: Very Nice… Just wanted to check you have done all patching at Node 1 only.. is there any thing need to...
  • Yousuf: Very Nice.. Thanks for sharing.. Once question.. You have executed all commands on Node 1 only.. Is there any...
  • Emir: Thanks… Great article
  • borse firmate: Thank you for another informative blog. The place else may just I am getting that kind of information...
  • leandro: why this parameter is systemwide? could you read from a asm instance from one failure group and from the...
  • Mohammad: paul, we create pfile from target database to source database and later we change database name, and...
  • Muhammad Ikram: Thanks Brother for sharing pearls of knowledge. May ALLAH reward you for this both here and...
  • rgrover: Thanks for the POST. I recently encounter similar issue. Your POST helped.
  • gopalredy: really its very use full to dbas
  • Vivian: This is awesome! Thank you so much!
  • henry zhong: CDB=DB, and PDB=SCHEMA but in a sub dictionary?
  • Dehbashee: Salam Brother, Thanx for sharing, however, i would be interested in chaging the password for the grid user...
  • wissem: No we don’t need that :) Just the scripts I posted above
  • Md. Tanweer: Thanks for posting the material. I really appreciate if you can send me, if you have tutorial for 11g...
  • christiaan: Thanks!! This has been bugging the hell out of me for so long.
  • Rajasekhar: Thank you
  • Samarjit Panigrahy: Very Nice and Simple Demo… Cool :)
  • cq: Any reason not to use auto patch for both CRS and RAC homes with one command? Or use opatch auto for RAC home as...
  • Hitesh: Hi, Can we use this RACcheck tool on oracle SE version ? Thanks