Sunday, December 5, 2010

Incompatible state when starting up a WebLogic managed server

Problem:

After starting up the Oracle WebLogic 11g AdminServer server, you may get the following error when trying to start up any of your managed servers:


For server soa_server1, the Node Manager associated with machine LocalMachine is not reachable.
All of the servers selected are currently in a state which is incompatible with this operation or are not associated with a running Node Manager or you are not authorized to perform the action requested. No action will be performed.
Solution:

This is simply due to the Node Manager not running.

1. Start up the Node Manager as follows:
export MW_HOME=/u01/app/oracle/middlware
cd $MW_HOME/wlserver_10.3/server/bin
nohup $MW_HOME/wlserver_10.3/server/bin/startNodeManager.sh &
Applicable Versions:
  • Oracle WebLogic 11g (11.1.1.x)

4 comments:

Anonymous said...

Sorry, This is not true.

Ahmed Aboulnaga said...

Care to elaborate?

Sharat Kuncha said...

Thank you so much for the info. It helped me save lot of time.

Ahmed Aboulnaga said...

In response to Anonymous (on my old blog) who is still having this issue:

(1) How do you know that NodeManager is running?

Can you "ps -ef | grep NodeManager" and confirm that NodeManager is running? Can you "telnet localhost 5556" to confirm that the port is being listened on by NodeManager?

(2) What do you see in the $WL_HOME/common/nodemanager/nodemanager.log log file?

If you're sure that NodeManager is running, then your next step is to look at the log above.