Configuration issue in node manager ( Oracle Weblogics 11g )

Hello Everyone,
We have developed an Admin server and a Managed server. Both are working fine. When we tried to implement node manager concept in it, we were partially unsuccessful to make this task completed.
Under Environment -> Machines -> machine_name -> Under Monitoring tab
     We could see status as inactive.
Sequence of Steps we followed:-
     - Create new Machine ( Environment -> machine )
     - added Managed Server to the Machine
     - In Managed Server, Environment variable is set. Invoked WLST. Enrolled domain_home to wls_home/common/nodemanager

This is the scenario which i followed, kindly read it . . you will get clear idea. .
Machine 1 - Admin Server
Machine 2 - Managed Server
In Admin server, Environments -> server -> Machine 2 has been added. I am able to start and stop managed services.
Node Manager:-
In Machine 1 ( Admin server ) - Environments -> machine -> create -> In listener address ( gave ip address of machine 2 ) -> in listerner port -> 5556.
- Environments -> machine -> select - created machine ->configuration -> servers -> add maanged server - machine 2.
In Machine 2 ( Managed Server ) - In WLS_HOME/server/bin -> ./setENV**.sh -> Invoke wlst -> Used connect cmd to get connect admin url in WLST -> executed enroll cmd
- Then executed ./startnodemanager.sh script
We assume that now under Environment -> Machine -> Machine_Name -> monitoring -> status should be reachable but for me its inactive. I found this message - weblogic.nodemanager.NMConnectException.
=================================================================================================================
Now below you will find node manager logs and properties file
Log viewed when ./startnodemanager.sh is executed
+ CLASSPATH=/home/oracle/oracle11g/Middleware/patch_wls1036/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/oracle/oracle11g/Middleware/patch_oepe180/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/oracle/oracle11g/Middleware/patch_ocp371/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/oracle/oracle11g/Middleware/patch_adfr1111/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/oracle/oracle11g/Middleware/jdk160_29/lib/tools.jar:/home/oracle/oracle11g/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/home/oracle/oracle11g/Middleware/wlserver_10.3/server/lib/weblogic.jar:/home/oracle/oracle11g/Middleware/modules/features/weblogic.server.modules_10.3.6.0.jar:/home/oracle/oracle11g/Middleware/wlserver_10.3/server/lib/webservices.jar:/home/oracle/oracle11g/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/home/oracle/oracle11g/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar:/home/oracle/oracle11g/Middleware/patch_wls1036/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/oracle/oracle11g/Middleware/patch_oepe180/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/oracle/oracle11g/Middleware/patch_ocp371/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/oracle/oracle11g/Middleware/patch_adfr1111/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/oracle/oracle11g/Middleware/jdk160_29/lib/tools.jar:/home/oracle/oracle11g/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/home/oracle/oracle11g/Middleware/wlserver_10.3/server/lib/weblogic.jar:/home/oracle/oracle11g/Middleware/modules/features/weblogic.server.modules_10.3.6.0.jar:/home/oracle/oracle11g/Middleware/wlserver_10.3/server/lib/webservices.jar:/home/oracle/oracle11g/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/home/oracle/oracle11g/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar::/home/oracle/oracle11g/Middleware
+ '[' '!' -z '' ']'
+ '[' '!' -z '' ']'
+ export CLASSPATH
+ export PATH
+ cd /home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager
+ set -x
+ '[' '' '!=' '' ']'
+ '[' '' '!=' '' ']'
+ /home/oracle/oracle11g/Middleware/jdk160_29/bin/java -client -Xms32m -Xmx200m -XX:MaxPermSize=128m -Dcoherence.home=/home/oracle/oracle11g/Middleware/coherence_3.7 -Dbea.home=/home/oracle/oracle11g/Middleware -Xverify:none -Xverify:none -Djava.security.policy=/home/oracle/oracle11g/Middleware/wlserver_10.3/server/lib/weblogic.policy -Dweblogic.nodemanager.javaHome=/home/oracle/oracle11g/Middleware/jdk160_29 weblogic.NodeManager -v
<Oct 12, 2012 4:01:52 PM> <INFO> <Loading domains file: /home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager/nodemanager.domains>
Oct 12, 2012 4:01:52 PM weblogic.nodemanager.server.NMServerConfig initDomainsMap
INFO: Loading domains file: /home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager/nodemanager.domains
<Oct 12, 2012 4:01:52 PM> <INFO> <Loaded node manager configuration properties from '/home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager/nodemanager.properties'>
Oct 12, 2012 4:01:52 PM weblogic.nodemanager.server.NMServer <init>
INFO: Loaded node manager configuration properties from '/home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager/nodemanager.properties'
Node manager v10.3
Configuration settings:
NodeManagerHome=/home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager
ListenAddress=
ListenPort=5556
ListenBacklog=50
SecureListener=false
AuthenticationEnabled=true
NativeVersionEnabled=true
CrashRecoveryEnabled=false
JavaHome=/home/oracle/oracle11g/Middleware/jdk160_29/jre
StartScriptEnabled=false
StopScriptEnabled=false
StartScriptName=startWebLogic.sh
StopScriptName=
LogFile=/home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager/nodemanager.log
LogLevel=INFO
LogLimit=0
LogCount=1
LogAppend=true
LogToStderr=true
LogFormatter=weblogic.nodemanager.server.LogFormatter
DomainsFile=/home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager/nodemanager.domains
DomainsFileEnabled=true
StateCheckInterval=500
UseMACBroadcast=false
DomainRegistrationEnabled=false
DomainsDirRemoteSharingEnabled=false
Domain name mappings:
TestDomain -> /home/oracle/oracle11g/Middleware/user_projects/domains/TestDomain
<Oct 12, 2012 4:01:54 PM> <INFO> <Plain socket listener started on port 5556>
Oct 12, 2012 4:01:54 PM weblogic.nodemanager.server.Listener run
INFO: Plain socket listener started on port 5556
nodemanager.log
<Oct 12, 2012 4:01:52 PM> <INFO> <Loading domains file: /home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager/nodemanager.domains>
<Oct 12, 2012 4:01:52 PM> <INFO> <Loaded node manager configuration properties from '/home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager/nodemanager.prop
erties'>
<Oct 12, 2012 4:01:54 PM> <INFO> <Plain socket listener started on port 5556>
more nodemanager.properties
#Sun Oct 07 06:39:50 BST 2012
DomainsFile=/home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager/nodemanager.domains
LogLimit=0
PropertiesVersion=10.3
DomainsDirRemoteSharingEnabled=false
javaHome=/home/oracle/oracle11g/Middleware/jdk160_29
AuthenticationEnabled=true
NodeManagerHome=/home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager
JavaHome=/home/oracle/oracle11g/Middleware/jdk160_29/jre
LogLevel=INFO
DomainsFileEnabled=true
StartScriptName=startWebLogic.sh
ListenAddress=
NativeVersionEnabled=true
ListenPort=5556
LogToStderr=true
SecureListener=false
LogCount=1
DomainRegistrationEnabled=false
StopScriptEnabled=false
QuitEnabled=false
LogAppend=true
StateCheckInterval=500
CrashRecoveryEnabled=false
StartScriptEnabled=false
LogFile=/home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager/nodemanager.log
LogFormatter=weblogic.nodemanager.server.LogFormatter
ListenBacklog=50
-bash-3.2$
more nodemanager.domains#
#Fri Oct 12 16:00:36 BST 2012
TestDomain=/home/oracle/oracle11g/Middleware/user_projects/domains/TestDomain
-bash-3.2$
All these were found in Admin Server. . . Kindly provide ur suggestions . .

Similar Messages

Unable to initialize Node Manager on Weblogic 11g (10.3.5) Linux env..

Hello,
I worked earlier on Weblogic 8.1 and after a long gap I am coming back to Weblogic Server.
And I tried to install & setup Weblogic Server 11g R1 (10.3.5). I successfully installed WL 11g on a Linux machine, configured the domain, and admin server without any problem. I created a managed server on the Console and tried to initialize the node manager to be able to start the managed server. I am getting the following error message repeatedly. And I did not select SSL connection, while setting up the environment.
Can someone help me resolve this issue?
<Sep 13, 2011 12:19:31 PM> <WARNING> <Uncaught exception in server handlerjavax.net.ssl.SSLHandshakeException: [Security:090476]Invalid/unknown SSL header was received from peer inb01.n2nservices.com - 192.168.112.46 during SSL handshake.>
javax.net.ssl.SSLHandshakeException: [Security:090476]Invalid/unknown SSL header was received from peer inb01.n2nservices.com - 192.168.112.46 during SSL handshake.
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireException(Unknown Source)
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireAlertSent(Unknown Source)
at com.certicom.tls.record.ReadHandler.fireAlert(Unknown Source)
at com.certicom.tls.record.ReadHandler.getProtocolVersion(Unknown Source)
at com.certicom.tls.record.ReadHandler.checkVersion(Unknown Source)
at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Source)
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown Source)
at com.certicom.tls.record.ReadHandler.read(Unknown Source)
at com.certicom.io.InputSSLIOStreamWrapper.read(Unknown Source)
at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264)
at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306)
at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158)
at java.io.InputStreamReader.read(InputStreamReader.java:167)
at java.io.BufferedReader.fill(BufferedReader.java:136)
at java.io.BufferedReader.readLine(BufferedReader.java:299)
at java.io.BufferedReader.readLine(BufferedReader.java:362)
at weblogic.nodemanager.server.Handler.run(Handler.java:71)
at java.lang.Thread.run(Thread.java:662)
Sep 13, 2011 12:19:31 PM weblogic.nodemanager.server.Handler run

Can you see what listen address you have given to Node Manager in console or in config.xml?
<machine xsi:type="unix-machineType">
<name>Servername</name>
<node-manager>
<name>Servername</name>
<listen-address>localhost</listen-address>
</node-manager>
</machine>
Another way to start Managed server is to use startManaged.sh script.

Timezone issue with Node manager

Hi
We have a strange problem in our Weblogic manager server as below.
We started the manage server & Node manager in Jan 2011, when the daylight saving was on., then when time zone changed to winter time to summer time, node manager was unable to pick the time zone change.
It was still printing log files with wintertime in April 2011.
But after we restart the node manager & manage server, we found that then it has pick the summer time.
So want to know how to avoid such problems, that node manager & manage server should pick the current timezone (even when it change to summer to winter or vice versa) without restarting the servers.
Please can anyone guide me on this such strange problem & solution of it.
regards,
jay

Hi
My OS is Linux box and is able to pick the time correctly, but nodemanager & manage server which are started before time zone change is not able to pick the timezone change and continue running with timezone where it has started and the same time OS (date command) shows that it is changed to summer time.
Do i need to specify any configuration for nodemanger & manage server for picking the time when time zone is changed.
regards,
Jay
Edited by: user13160729 on May 23, 2011 11:07 PM

Can Enterprise Manager Grid Control 10g R4 manages Oracle DB 11g?

Are there some articles or documents for that?

I assume you are asking whether it is possible to run Enterprise Manager Grid Control without using the embedded database. The answer is yes. There is a step in the install wizard that ask you whether you want to create an embedded database, or use an existing database environment. Just follow the instructions on the wizard to point your EM server to the database of your choice. You can even run EM on RAC provided that you already have the license for it.

OBIEE 11g (11.1.1.5.0) - Issue with starting Node Manager

Hi,
Have anyone faced an issue with starting Node Manager in OBIEE 11g (11.1.1.5.0)? OS is 64 bit Linux, WebLogic is 10.3.5. I used the software-install method and followed by running config.sh. Everything completed successfully. I updated the catalog and rpd location in the FMW control screen.
To get it activated I bounced services and when I try to start Node Manager it gives below error --
<Aug 30, 2011 2:02:42 PM CDT> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
<Aug 30, 2011 2:02:42 PM> <SEVERE> <Fatal error in node manager server>
java.io.IOException: Unsupported cypher suite: TLS_RSA_EXPORT_WITH_RC4_40_MD5
at weblogic.nodemanager.server.SSLListener.init(SSLListener.java:82)
at weblogic.nodemanager.server.NMServer.start(NMServer.java:206)
at weblogic.nodemanager.server.NMServer.main(NMServer.java:377)
at weblogic.NodeManager.main(NodeManager.java:31)
Aug 30, 2011 2:02:42 PM weblogic.nodemanager.server.NMServer main
SEVERE: Fatal error in node manager server
java.io.IOException: Unsupported cypher suite: TLS_RSA_EXPORT_WITH_RC4_40_MD5
at weblogic.nodemanager.server.SSLListener.init(SSLListener.java:82)
at weblogic.nodemanager.server.NMServer.start(NMServer.java:206)
at weblogic.nodemanager.server.NMServer.main(NMServer.java:377)
at weblogic.NodeManager.main(NodeManager.java:31)
+ set +x
I see the same issue reported in ML OBIEE 11g - Node manager fails to start upon upgrade [ID 1329442.1] and WebLogic Server: Node Manager Startup is Failing with java.io.IOException: Unsupported cypher suite [ID 1329260.1] I tried to modify commEnv.sh. But it didnt help me.
Please let me know if anyone have faced similar issue and what exactly did you do to resolve it.
Cherrish Vaidiyan
Edited by: Cherrish on Aug 30, 2011 3:14 PM

Hi,
There are Two types of Cipher suites --- Certicom Cipher Suite and SunJSSE Equivalent Cipher Suite. And with Weblogic 10.3.5, you are using Sun JSSE Cipher Suite, and by default Node Manager uses the Certicom Cipher Suite.
In the nodemanager.properties, Add CipherSuite=SSL_RSA_EXPORT_WITH_RC4_40_MD5, save and restart Node Manager.
Reference Metalink Note: WebLogic Server 10.3.x: Getting "Unsupported Cipher" Exceptions When Starting Node Manager [ID 1307325.1]
Cherrish Vaidiyan

Configuring DB Console (grid manager) on the Databse 11G RAC template

Hi,
I thought the dbconsole was installed in the RAC template. I actualy have a two node setup on OVM 3.0.3 and I can't start/cofigure/deconfigure the db console !
runing a "emct start dbconsole" give a message as :
OC4J Configuration issue. /u01/app/oracle/product/11.2.0/dbhome_1/oc4j/j2ee/OC4J_DBConsole_racnode01_ORCL not found.
Indeed, I have nothing named like this in this directory, whichever node I try.
I made some reserches, and none of the emca -confir or emca -deconfig work...
So, is the dbConsole automaticaly configured ? What am I missing ?
Thanks.

Hi,
I thought the dbconsole was installed in the RAC template. I actualy have a two node setup on OVM 3.0.3 and I can't start/cofigure/deconfigure the db console !
runing a "emct start dbconsole" give a message as :
OC4J Configuration issue. /u01/app/oracle/product/11.2.0/dbhome_1/oc4j/j2ee/OC4J_DBConsole_racnode01_ORCL not found.
Indeed, I have nothing named like this in this directory, whichever node I try.
I made some reserches, and none of the emca -confir or emca -deconfig work...
So, is the dbConsole automaticaly configured ? What am I missing ?
Thanks.

11g node manager reachable but server does not start from admin console

I have a issue with node manager is reachable from admin console and from command prompt it is not connected and could not able to start the managed server.
If i change /config/nodemanager/nm_password.properties plain text and restart it is not reachable in admin console abut can connect from command prompt. I could not able to start the even with this scenario.
i see below error when try to check machine monitor tab.
<Error> <NodeManager> <BEA-300033> <Could not execute command "getVersion" on the node manager. Reason: "Access to domain 'dom_11gint' for user 'Ckr10ycOJN' denied".>
Ckr10ycOJN username in config.xml
node manager and managed servers are not root user process.
Please help me if have any suggestions.

Pls. make sure the following points in your environment.
1) Check '*nodemanager.domains*' file in <<WL_HOME>>\commo\nodemanager directory
     a) This file should have the entry for your domain 'dom_11gint'.
     b) Ensure the path referred in the nodemanager.domains file is correct one.
2) Ensure the following remote server startup parameters are passed properly.
     a) In the Admin Console, Navigate Servers --> <<SERVER_NAME>> -->Configuration --> Server Start
     b) Pass the required Class Path, Arguments, User Name, Password(User name and Password to boot the managed servers)

Steps to setup and configure Node Manager on local and remote machine

Hello,
I am using WLS 10.3 on Windows.
I have two machines, One cluster and two managed servers (one on each machine) created under a domain. I have used configuration wizard to create the domain.
I have gone through documents on Node Manager and found what to configure. But I have not found when to configure. In other words I want to know what is the sequence of steps if I have to set Node Manager on my local machine (in which domain exists) and on remote machine.
Please let me know the sequence of steps I need to follow to set and configure the Node Manager on local and remote machine. I want to use Java Node Manager (not the Script node manager).
Thanks,
Sanjay

Hello,
Ok, let me tell you what I have done till now.
1) Installed WebLogic 10.3 on machine A (local machine, on which I have created domain and my Admin Server is running. Also Managed Server 1 is created on this machine).
2) Installed WebLogic 10.3 on machine B (remote machine, on which Managed Server 2 will be created).
3) On machine A I used the configuration wizard and create a domain. While creating the domain I did the following:
i) Created two managed servers.
ii) Created a cluster
iii) Assigned Servers to cluster.
iv) Created two machines.
v) Assigned servers to machines (Admin Server and MS_1 to machine A and MS_2 to machine B).
4) Sarted Admin Server.
5) On the Admin Console I made some configurations for the Node Manager on Machines -> Machine A -> Node Manager. Assigned the values:
i) Type (SSL)
ii) Listen Address (IP_Address of machine A)
iii) Listen Port (5556)
6) Similarly did for Machine B.
So till now phsically the managed server (MS_2) directory and configuration is not there on Machine B (its only configured on machine A because I created the domain on Machine A).
Now I want install/configure/setup NM on both the machines. Start my both the managed servers using Admin Console (which will use the node managers).
What are the sequence of steps I need to follow my task?
Any help and suggestions are welcome with warm regards.
Thanks,
Sanjay

Can i use single node manager with two weblogic domain?

I am very new to weblogic and node manager.
i had created two domains in weblogic. (single node manger).
Can i connect both domains with same nodemanger?
How to do this?

The node manager uses a nodemanager.domains file to determine which domains it manages, for example,
domain_name=/path_to_domain/domain_name
other_domain_name=/path_to_other_domain/other_domain_name
This file can be found in the NODEMANAGER_HOME, that you specified when starting the node manager (startNodeManager - NODEMGR_HOME="${WL_HOME}/../oracle_common/common/nodemanager")
When you are running the domain on multiple machines you have to enroll the node manager into the domain (http://docs.oracle.com/cd/E23943_01/web.1111/e13813/reference.htm#i1065827)
A scripted example can be found here: Middleware Snippets: Automate WebLogic Installation and Configuration. The Node Manager administration guide can be found here: Oracle&reg; Fusion Middleware Node Manager Administrator's Guide for Oracle WebLogic Server 11g Release 1 (10.3.6) -….

OC4J Configuration issue. when trying to enable OEM on 10g

Good Morning to all ;
Just now i posted question related to OEM (when getting error).
I can't connect my OEM with any user
Here i created DB using DBCA with OEM but i couldn't login via BROWSER ...
Please ignore this question here .. ( Not a Duplicate Question)
This question is different , but related to OEM ( Ok . I am explaining my issues here. I created Database using DBCA without enabling OEM.
then i set ORACLE_SID and tried to execute OEM but getting error.
$ emctl start dbconsole
TZ set to Asia/Calcutta
OC4J Configuration issue. /u01/app/oracle/product/10.2.0/db_1/oc4j/j2ee/OC4J_DBConsole_linuxserver_orcltest not found.
NOTE : I want to know answer for 2nd question. what is OC4J Configuration issue. - How can i resolve that ? or
Thanks in advance ..

Hello Sb
I perfectly upgraded my DB with OEM to 10.2.0.4.0 on OEL4. i'm going to do on rhel-5
*$ export ORACLE_SID=orcl*
[oracle@oel ~]$ sqlplus /nolog
SQLPlus: Release 10.2.0.4.0 - Production on Sun Apr 21 00:59:53 2013*
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
SQL> conn /as sysdba
Connected.
SQL> startup
ORA-01081: cannot start already-running ORACLE - shut it down first
SQL> cl scr
SQL> select comp_name , version , status from dba_registry;
COMP_NAME
VERSION STATUS
Oracle Database Catalog Views
10.2.0.4.0 VALID
Oracle Database Packages and Types
10.2.0.4.0 VALID
Oracle Workspace Manager
10.2.0.4.3 VALID
COMP_NAME
VERSION STATUS
JServer JAVA Virtual Machine
10.2.0.4.0 VALID
Oracle XDK
10.2.0.4.0 VALID
Oracle Database Java Packages
10.2.0.4.0 VALID
COMP_NAME
VERSION STATUS
Oracle Expression Filter
10.2.0.4.0 VALID
Oracle Data Mining
10.2.0.4.0 VALID
Oracle Text
10.2.0.4.0 VALID
COMP_NAME
VERSION STATUS
Oracle XML Database
10.2.0.4.0 VALID
Oracle Rule Manager
10.2.0.4.0 VALID
Oracle interMedia
10.2.0.4.0 VALID
COMP_NAME
VERSION STATUS
OLAP Analytic Workspace
10.2.0.4.0 VALID
Oracle OLAP API
10.2.0.4.0 VALID
OLAP Catalog
10.2.0.4.0 VALID
COMP_NAME
VERSION STATUS
Spatial
10.2.0.4.0 VALID
Oracle Enterprise Manager
10.2.0.4.0 VALID
17 rows selected.
Thanks ..

EM Configuration issue. /u01/.../node01_node01 not found

Hi,
am new to troubleshooting enterprise manager. twas working perfectly before. http://192.168.50.161:1158/em.
now it is not working and when I checked via the console: $ emctl --help it returns:
EM Configuration issue. /u01/app/oracle/product/11.1.0/db_1/node01_node01 not found.
any tips on how to fix this problem?
please help.
thanks.

I resolved the issue by creating soft links to the directory...
Let's say your original hostname was as01.corp.purisma.com, and your new hostname is as01. My SID is as01 in this example.
So, you need to change it in two places:
If your ORACLE_HOME is /d0/oracle/product/10.2.0/db_1, then:
Under: /d0/oracle/product/10.2.0/db_1
ln -s as01.corp.purisma.com_as01 as01_as01
Under: /d0/oracle/product/10.2.0/db_1/oc4j/j2ee
ln -s OC4J_DBConsole_as01.corp.purisma.com_as01 OC4J_DBConsole_as01_as01
I was then able to start the enterprise manager by issuing the standard 'emctl start dbconsole' command.

Multiple Node Manager Instances and servers sharing the same domain home.

Hi,
We have a 8 man server weblogic cluster spread over 4 machines. Each machine runs 2 man servers each.
Each of the machine is configured to run node manager.
We use shared storage accessible to all 8 servers and all 8 man servers have the same domain_home.
Lets call it W:/domain
Now the problem we are facing is that node manager running on 1 machine is trying to access/control a managed server on a different machine after a machine restart.
eg.
ManServer1 Home : W:/domain/servers/server1 ====> runs on Machine 1
ManServer2Home : W:/domain/servers/server2 ====> runs on Machine 2
Problem is node manager on machine 1 is trying to restart man server 2. The path W:/domain/servers/server2 is accessible to Machine 1.
After a restart, what I assume is happening is that the nodemanager is checking all servers folder under Domain_Home/Servers and trying to restart servers instead of restarting only those which it should start. The config file has the server and machine assignment done correctly. Is there a way to make this configuration towork. Or do we need to create different domain_home's for different man servers like
Domain_Home for MS1: W:/domain/MS1 ( Server Home would be : W:/domain/MS1/servers/MS1)
Domain_Home for MS2: W:/domain/MS2 ( Server Home would be : W:/domain/MS2/servers/MS2)
Regards,
Atheek
Edited by: atheek1 on 03-May-2010 00:27

Thanks - We have tried putting 2 dad entries in file, but not sure how you connect. You only specify a port number, so how does it connect that to a db???

EM Configuration issue.

I have installed grid agent on different server. When i ran emctl status agent i am getting below error.
EM Configuration issue. /u01/app/oracle/product/10g/hostname.com_ORCL.
OS is AIX
Thanks in advance...

I am in AGENT_HOME.You are under Agent installation that's one thing. You also need to make sure your environment variable ORACLE_HOME point to AGENT_HOME not the database installation.

Passing memory settings from the Node Manager to the Managed Server

All,
I am trying to start a Managed server from the Node Manager. The configuration is as follows:
I have a domain with two managed servers(M1, M2). I could start both of them using the shell scripts without any problems. Both of the servers has custom memory settings -Xms3072m -Xmx3072m -XX:PermSize=256m
to facilitate deployment and effective operation of managed servers (the applications being deployed are kind of large).
Now, I am trying to start the same two servers using Admin Console:
In the admin console: I created a Unix Machine(U1) assigned the managed servers (M1, M2) to U1. I started the Node Manager on U1.
When I try to start a Managed Server from console, the server is starting but the memory settings (-Xms3072m -Xmx3072m -XX:PermSize=256m ) are not passed to the managed server startup, so the application deployment is failing with out of Memory errors. I tried to assign same memory settings to Node manager assuming it will pass on that configuration to the node manager without any luck.
Any help is appreciated.
Thanks
Raj

Starting Managed Server from Node Manager

Oracle 11G Configuration Issue

Hi All,
I am in the process of installing Oracle Forms and Reports 11g[11.1.2].
I have installed Oracle 11g, getting a issue while configuring it.
INST – 07249 :An Unexpected error occurred during the validation of Middleware home location
INST-07286: Specified Oracle Middleware home locationdoes not have version 10.3.5 of weblogic server.If the version is incorrect then configuring with the weblogic server will fail
WLS 10.3.5 have been installed, and I can access the Admin console.
I did checked for the WLS version in its registry file created on WLS installation to confirm its version number.
I have used the same middle ware home location which I used to install the WLS.
Please can you get me some information to overcome this issue?

This is well explained from user's guide:
Stopping Node Manager Before Installing Oracle Forms and Reports (Windows Only)
If you are installing Oracle Forms and Reports on a Microsoft Windows operating system, you must make sure that the Node Manager utility that was installed with Oracle WebLogic Server is stopped before you begin the installation:
1.     Verify the Oracle WebLogic Server Node Manager utility is stopped. If it is running, kill the process.
2.     Determine if the nodemanager.properties file is present in the WebLogic_Home\common\nodemanager directory.
*1.     If the nodemanager.properties file is not present, continue installing Oracle Forms and Reports.*
*2.     If the nodemanager.properties file does exist, open it and verify that the ListenPort parameter is included and that it is set. If the ListenPort parameter is not included or set, edit the nodemanager.properties file so that it is similar to the*
following, where NODE_MANAGER_LISTEN_PORT represents the port the Node Manager listens on, such as 5556:
*3.     ListenPort=NODE_MANAGER_LISTEN_PORT*

Configuration issue in node manager ( Oracle Weblogics 11g )

Similar Messages

Maybe you are looking for