Starting the node agent

Hi,
Have background in java but have been away from it for a while so getting reacquainted with it. I just downloaded the SDK and now I am following the instructions after downloading and using the Admin Consol. I am at the step where I have to start the node agent in the asadmin window and it fails. When I listed the node agent I realized that there was none. So I think I have to create a node agent before I can start it but I cannot do that until I create a node agent placeholder. When I use the command to do this it tells me that I need an operand. What is the exact command with operand that I have to place in the asadmin window to successfully create the placeholder for the node agent.

javaException wrote:
Actually he is talking about the the Sun Java System Application Server, certainly not IBM.Well that terminology is the same used in the IBM server space. And it might have helped if OP had mentioned the type of server in the first place.

Similar Messages

Start the node manager and rerun the command

Seeing the following in weblogic server log. When will I get this error? And how to retun node manager ?
The node manager at host ....and port 5555 seems to be down. Start the node manager and rerun the command.

You will get this message when the machine's NodeManager was not started.
Take a look at the following links to see how to install and start the Node Manager:
http://e-docs.bea.com/wls/docs81/adminguide/nodemgr.html#1150128
http://e-docs.bea.com/wls/docs81/adminguide/confignodemgr.html#1142955

Java Exception when attempt to start the SNMP agent

Hi,
I require to start the SNMP agent in Solaris 2.6 running Web Logic 5.1. Upon entering
the command :
$ java weblogic.SNMPAgent, it is asking me for the password , and I gave the same.
The system is
generating a Java Exception given below:
Exception in thread "main" com.adventnet.snmp.snmp2.agent.AgentRuntimeException:
Failure in opening SnmpSession, errstat: 0, errvalue: 0
at java.lang.Throwable.fillInStackTrace(Native Method)
at java.lang.Throwable.fillInStackTrace(Compiled Code)
at java.lang.Throwable.<init>(Compiled Code)
at java.lang.Exception.<init>(Compiled Code)
at java.lang.RuntimeException.<init>(RuntimeException.java:47)
at com.adventnet.snmp.snmp2.agent.AgentRuntimeException.<init>(AgentRuntimeException.java:63)
at com.adventnet.snmp.snmp2.agent.SnmpAgent.addClientAndOpenSession(SnmpAgent.java:801)
at com.adventnet.snmp.snmp2.agent.SnmpAgent.restartSnmpAgent(SnmpAgent.java:939)
at com.adventnet.snmp.snmp2.agent.SnmpAgent.restartSnmpAgent(CompiledCode)
at com.adventnet.snmp.snmp2.agent.SnmpAgent.setPort(Compiled Code)
at weblogic.management.snmp.agent.WebLogicAgent.init(Compiled Code)
at weblogic.management.snmp.agent.WebLogicAgent.startup(WebLogicAgent.java:377)
at weblogic.SNMPAgent.main(SNMPAgent.java:25)
Given below is the file <startSNMPAgent.sh> and it's central contents:
$JAVA weblogic.SNMPAgent -password pbgst -serverURLs t3://localhost:7001 -trap
Destinations localhost:162
The classpath settings are correct and as per documentation.
There are SNMP agents also running in the machine which have been started by default
by Solaris,
doing a ps -ef | grep snmp shows:
root 556 1 0 Jun 23 ? 0:00 /usr/lib/dmi/snmpXdmid -s sunhyd01
root 516 1 0 Jun 23 ? 0:00 /usr/lib/snmp/snmpdx -y -c /etc/snmp/conf
pbgst 28090 25879 0 17:01:37 pts/32 0:00 grep snmp
I tried to start the SNMP agent on a diff. port and specified the same in the
.sh file and also changed the
trap Destinations port ---- it still generates the same exception.
Please do try to resolve this problem for me, as the project is in production
phase.
Thanks for all help beforehand.
Baivab
P.S. How can I obtain the id for WebSupport center, as we have using WL licensed
product
recently purchased in 3 nos.

Hello,
way back we had the same problem and the reason was, that the path
names with the server instances were to long
(/opt/wlsroot/wlsInstances/axsExpert.SwissAir/S_243_7001 ->
/opt/wlsroot/wlsInstances/axsExpert.SAir/S_243_7001). But this was
with WLS 5.1 SP8.
Regards
Wolfgang Becker
Atraxis
On 9 Jul 2001 23:02:29 -0800, "Baivab Mitra"
<[email protected]> wrote:
>
Hello Michel,
Thanks for the reply. As you may have noticed, that the SNMP agents which are
already running, the owner is <root>. These services are required and I do not
have or I can not obtain the password to start/stop the same. As such, the only
option which I have is to start the weblogic-specific SNMP service in a different
port. Question: In the parameters, I specified : <snmpPort 1600 trace Destinations
1601> I am still getting the same error. What else is required and/or how do I
proceed to start the same service?
Thanks for your help beforehand,
Baivab
"Michael Girdley" <----> wrote:
It looks like another SNMP agent has already bound to the port.
Michael Girdley
BEA Systems
Learning WebLogic? http://learnweblogic.com
"Baivab Mitra" <[email protected]> wrote in message
news:[email protected]...
Hi,
I require to start the SNMP agent in Solaris 2.6 running Web Logic5.1.
Upon entering
the command :
$ java weblogic.SNMPAgent, it is asking me for the password , and Igave
the same.
The system is
generating a Java Exception given below:
Exception in thread "main"com.adventnet.snmp.snmp2.agent.AgentRuntimeException:
Failure in opening SnmpSession, errstat: 0, errvalue: 0
at java.lang.Throwable.fillInStackTrace(Native Method)
at java.lang.Throwable.fillInStackTrace(Compiled Code)
at java.lang.Throwable.<init>(Compiled Code)
at java.lang.Exception.<init>(Compiled Code)
at java.lang.RuntimeException.<init>(RuntimeException.java:47)
atcom.adventnet.snmp.snmp2.agent.AgentRuntimeException.<init>(AgentRuntimeExce
ption.java:63)
atcom.adventnet.snmp.snmp2.agent.SnmpAgent.addClientAndOpenSession(SnmpAgent.j
ava:801)
atcom.adventnet.snmp.snmp2.agent.SnmpAgent.restartSnmpAgent(SnmpAgent.java:939
atcom.adventnet.snmp.snmp2.agent.SnmpAgent.restartSnmpAgent(CompiledCode)
at com.adventnet.snmp.snmp2.agent.SnmpAgent.setPort(CompiledCode)
at weblogic.management.snmp.agent.WebLogicAgent.init(CompiledCode)
atweblogic.management.snmp.agent.WebLogicAgent.startup(WebLogicAgent.java:377)
at weblogic.SNMPAgent.main(SNMPAgent.java:25)
Given below is the file <startSNMPAgent.sh> and it's central contents:
$JAVA weblogic.SNMPAgent -password pbgst -serverURLst3://localhost:7001 -trap
Destinations localhost:162
The classpath settings are correct and as per documentation.
There are SNMP agents also running in the machine which have been startedby default
by Solaris,
doing a ps -ef | grep snmp shows:
root 556 1 0 Jun 23 ? 0:00 /usr/lib/dmi/snmpXdmid-s
sunhyd01
root 516 1 0 Jun 23 ? 0:00 /usr/lib/snmp/snmpdx -y-c
/etc/snmp/conf
pbgst 28090 25879 0 17:01:37 pts/32 0:00 grep snmp
I tried to start the SNMP agent on a diff. port and specified the samein
the
sh file and also changed the
trap Destinations port ---- it still generates the same exception.
Please do try to resolve this problem for me, as the project is inproduction
phase.
Thanks for all help beforehand.
Baivab
P.S. How can I obtain the id for WebSupport center, as we have usingWL
licensed
product
recently purchased in 3 nos.

How to start the ODI agent ?

Hi..
I just installed the Oracle Data Integrator to my computer. But, how could i start the ODI agent ?..
Could somebody guide me ?
Thank you,
Baharin

Have you read the user documentation > http://www.oracle.com/technology/products/oracle-data-integrator/10.1.3/htdocs/documentation/oracledi_users.pdf
sections
Managing Agents....................................................................................................................... 136
Launching a Listener Agent ................................................................................................... 136
Launching a Scheduler Agent................................................................................................ 138
Or you could try :- Step to setup windows agent
Ok? Not that you ever mark your posts (Total Questions: 42 (42 unresolved))
Cheers
John
http://john-goodwin.blogspot.com/

Error starting the Inetlligent Agent?????

i am facing issues starting inetlligent agent on linux AS 3
agentctl start
DBSNMP for Linux: Version 9.2.0.4.0 - Production on 30-NOV-2005 15:11:20
Copyright (c) 2003 Oracle Corporation. All rights reserved.
Starting Oracle Intelligent Agent...\nAgent startup failed. Check /Oracle/Ora9i/network/log/dbsnmp.nohup for det
ails
and when i check the file see the following........
------------------------ Wed Nov 30 15:07:20 IST 2005 ------------------------
Certain conflicts were resolved during discovery
Please consult /Oracle/Ora9i/network/log/nmiconf.log for details
Failed while initializing SNMP
Error initializing subsystems
Agent exited at Wed Nov 30 15:07:20 IST 2005 with return value 55
Could not start agent. Initialization failure
Plz help
Gagan

Hello,
I am a beginner in ORACLE DBA. I wanted to ask, is there any other method other than installing the intelligent agent to backup a database when it is missing on the first installation?
Thanks for any help
B. Erbil KONUK

Could not start the Oracle Agent service on local computer

I have Oracle Enterprise 9.2.0.1 on Windows 2000 server,
When I'm starting the Agent service I get this message:
"Could not start the OracleOra9201Agent service on local computer.
The service didn't return an error.This could be an internal Windows error or an internal service error. If the problem persists, contact your system administrator."
Could you please help me to fix this problem? What I should do??

Are you using DHCP or using static IP address?
Also search forum , you ight get lots of thread addressing same issue.

TimeZone issues when starting the OEM Agent since summertime switch Germany

Hello gurus,
since yesterday when the system time has swithched to summer time in Germany I have below errors when starting the agents on our systems:
****@*****: /oracle > su - ora*** -c /oracle/product/agent10g/bin/emctl start agent
Oracle Enterprise Manager 10g Release 3 Grid Control 10.2.0.3.0.
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
Starting agent ....... failed.
The agentTZRegion value in /oracle/product/agent10g/sysman/config/emd.properties is not in agreement with what agent thinks it should be.Please verify your environment to make sure that TZ setting has not changed since the last start of the agent.
If you modified the timezone setting in the environment, please stop the agent and exectute 'emctl resetTZ agent' and also execute the script mgmt_target.set_agent_tzrgn(<agent_name>, <new_tz_rgn>) to get the value propagated to repository.
Consult the log files in: /oracle/product/agent10g/sysman/log
So I tryed the suggested resetTZ, but get below errors:
root@******: /oracle/product/agent10g/sysman/log > su - oradeu -c /oracle/product/agent10g/bin/emctl resetTZ agent
Oracle Enterprise Manager 10g Release 3 Grid Control 10.2.0.3.0.
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
Updating /oracle/product/agent10g/sysman/config/emd.properties...
----- Mon Mar 31 10:18:48 2008::tzOffset for +01:00 is 60(min), but agent is runnning with tzOffset 120(min)
----- Mon Mar 31 10:18:48 2008::trying again after waiting for 1 sec to account for daylight transition
----- Mon Mar 31 10:18:48 2008::tzOffset for +01:00 is 60(min), but agent is runnning with tzOffset 120(min)
resetTZ failed.
The agentTZRegion in:
/oracle/product/agent10g/sysman/config/emd.properties
is not in agreement with what the agent thinks it should be.
Fix your environment.
Pick a TZ value that corresponds to time zone settings listed in:
/oracle/product/agent10g/sysman/admin/supportedtzs.lst
I checked the TZ settings:
*****> echo $TZ
MEZ-1MSZ,M3.5.0/02:00:00,M10.5.0/03:00:00
*****: /oracle/product/agent10g/sysman/config > more emd.properties|grep agentTZ
agentTZRegion=+01:00
which is the reason for the difference of 120min as shown by the resetTZ I assume because AIX system time says MEZ -1 and emd.properties finds GMT+1 which gives a difference of 120min.
I already applied the patch 5632264 to the agent, but the issue still exists.
When I manipulate the envirement TZ to GMT+01:00 the agent starts again, but this is no solution. Also patching the TZ of UNIX/AIX is no solution because this will cause other issues.
Any ideas how I can get the agent working again?
ps. I already tried a reinstallation of the Agent, but the issue still exists.
Thank you
F.Wittmann

Hello,
I already installed the DST patch v4. see my first post.
Below I attached the logs from starting the agenent since crash:
emctl.log (since start until crash)=
1310886 :: Thu Apr 3 10:29:31 2008::AgentLifeCycle.pm: Processing status agent
1310886 :: Thu Apr 3 10:29:31 2008::AgentStatus.pm:Processing status agent
1310886 :: Thu Apr 3 10:29:31 2008::AgentStatus.pm:emdctl status returned 1
1462412 :: Thu Apr 3 10:29:41 2008::AgentLifeCycle.pm: Processing start agent
1462412 :: Thu Apr 3 10:29:41 2008::AgentLifeCycle.pm: EMHOME is /oracle/product/agent10g
1462412 :: Thu Apr 3 10:29:41 2008::AgentLifeCycle.pm:status agent returned with retCode=1
1462412 :: Thu Apr 3 10:30:37 2008::AgentLifeCycle.pm: Exited loop with retCode=4
1003654 :: Thu Apr 3 10:35:00 2008::AgentLifeCycle.pm: Processing status agent
1003654 :: Thu Apr 3 10:35:00 2008::AgentStatus.pm:Processing status agent
1003654 :: Thu Apr 3 10:35:02 2008::AgentStatus.pm:emdctl status returned 3
1536132 :: Thu Apr 3 10:38:26 2008::AgentLifeCycle.pm: Processing status agent
1536132 :: Thu Apr 3 10:38:26 2008::AgentStatus.pm:Processing status agent
1536132 :: Thu Apr 3 10:38:26 2008::AgentStatus.pm:emdctl status returned 1
emdctl.trc (since start until crash)=
2008-04-03 10:29:41 Thread-1 WARN http: snmehl_connect: connect failed to (sat141:3872): A remote host refused an attempted connect operation. (error = 79)
2008-04-03 10:29:41 Thread-1 ERROR main: nmectla_agentctl: Error connecting to https://*****:3872/emd/main/. Returning status code 1
2008-04-03 10:37:05 Thread-1 WARN http: snmehl_connect: connect failed to (sat141:3872): A remote host refused an attempted connect operation. (error = 79)
2008-04-03 10:37:05 Thread-1 ERROR main: nmectla_agentctl: Error connecting to https://*****:3872/emd/main/. Returning status code 1
2008-04-03 10:38:26 Thread-1 WARN http: snmehl_connect: connect failed to (sat141:3872): A remote host refused an attempted connect operation. (error = 79)
2008-04-03 10:38:26 Thread-1 ERROR main: nmectla_agentctl: Error connecting to https://*****:3872/emd/main/. Returning status code 1
emagent.log (since start until crash)=
2008-04-03 10:31:13 Thread-1 EMAgent started successfully (00702)
2008-04-03 10:37:04 Thread-1670 <Upload Manager> Unsuccessful Upload attempts for XML file exceeds specified limit=3, Agent will shutdown (00851)
2008-04-03 10:37:04 Thread-1 EMAgent abnormal terminating (00704)
emagent.trc (since start until crash)=
2008-04-03 10:35:16 Thread-1076 WARN TargetManager: Regenerating all Metadata
2008-04-03 10:36:48 Thread-1076 DEBUG TargetManager: In getTypeAndNameForHostTarget
2008-04-03 10:36:48 Thread-1076 DEBUG TargetManager: getTypeAndNameForHostTarget found host, sat141
2008-04-03 10:36:48 Thread-1076 DEBUG TargetManager: In getTypeAndNameForHostTarget
2008-04-03 10:36:48 Thread-1076 DEBUG TargetManager: getTypeAndNameForHostTarget found host, sat141
2008-04-03 10:36:48 Thread-1076 DEBUG TargetManager: In getTypeAndNameForHostTarget
2008-04-03 10:36:48 Thread-1076 DEBUG TargetManager: getTypeAndNameForHostTarget found host, sat141
2008-04-03 10:36:48 Thread-1076 DEBUG TargetManager: In getTypeAndNameForHostTarget
2008-04-03 10:36:48 Thread-1076 DEBUG TargetManager: getTypeAndNameForHostTarget found host, sat141
2008-04-03 10:36:48 Thread-1076 WARN collector: Regenerating all DefaultColls
2008-04-03 10:36:58 Thread-1076 ERROR upload: Failed to upload file A0000003.xml, ret = -6
2008-04-03 10:36:58 Thread-1076 ERROR upload: 3 Failures in a row for A0000003.xml, we give up
2008-04-03 10:36:58 Thread-1076 ERROR upload: Error in uploadXMLFiles. Trying again in 72.00 seconds or earlier.
2008-04-03 10:37:04 Thread-1670 WARN upload: FxferSend: received fatal error in header from repository: https://stloem2:1159/em/upload
FATAL_ERROR::500|ORA-20603: Updating timezone region of a target is not supported. Use mgmt_target.set_agent_tzrgn() API to modify the timezone region.(target name = sat141:3872)(target type = oracle_emd)(new tzrgn = MET)(old tzrgn = +01:00)
ORA-06512: at "SYSMAN.CHECK_DUPLICATE_TARGETS", line 92
ORA-04088: error during execution of trigger 'SYSMAN.CHECK_DUPLICATE_TARGETS'
2008-04-03 10:37:04 Thread-1670 ERROR upload: number of fatal error exceeds the limit 3
2008-04-03 10:37:04 Thread-1670 ERROR upload: agent will shutdown now
2008-04-03 10:37:04 Thread-1670 ERROR : Signalled to Exit with status 55
2008-04-03 10:37:04 Thread-1 ERROR main: EMAgent abnormal terminating
=======================================================
when I run emctl config agent getTZ it returns me GMT+01:00,
but with this value the agent does not start, oly with MEZ....
root@******: /oracle/product/agent10g/oracore/zoneinfo > su - oradeu -c /oracle/product/agent10g/bin/emctl config agent getTZ
Oracle Enterprise Manager 10g Release 3 Grid Control 10.2.0.3.0.
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
GMT+01:00
Kind regards
F.Wittmann

Problem starting the oem agent

the agent ran when i configured it with the installation gui. now i need to restart itmanually. This is not on the grid control server.
databasE: 10.1.0.3
oem: 10.2.0.5
solaris
I am in my $AGENT_HOME/bin
oracle(eradev) 24> emctl start agent
EM Configuration issue. /opt/oracle/product/10.1.0.3/myserver.com_mydev not found.
The directory show is the oracle home of the database that is currently set to the ORACLE_SID.
I tried using the emca, but that seems to configure for stand alone OEM. I need to start an agent to communicate with my Grid Control OMS.
Edited by: Guess2 on Sep 10, 2009 7:26 AM

Try this:
$ cd $AGENT_HOME/bin
$ ./emctl start agent:p

Problems starting node agent

I am trying to create a cluster of 2 Windows 2003 servers using enterprise edition 8.1 2005Q2 installations. I installed on one server and setup a domain and node agent, created a cluster and deployed my application. I tried to install a node agent only version on the other server, but it doesn't seem to exist, so I installed with domain administration server also. I deleted the node agent and recreated it pointing to the DAS on the other server. I got it to create, but I cannot start it. I get the message Password entered is invalid, even though I am entering the same password used to create it and the same password used as the master password. I've tried deleting and recreating the node agent and then I get the error failed to start and the log contains the error below. After that first time, I continue to get the password invalid message
[#|2006-11-29T16:34:06.281-0500|SEVERE|sun-appserver-ee8.1|javax.ee.enterprise.system.nodeagent|_ThreadID=10;|NAGT0014:Unexpected Node Agent exception.
java.lang.ExceptionInInitializerError
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java:164)
     at com.sun.enterprise.pluggable.PluggableFeatureFactoryBaseImpl.invoke(PluggableFeatureFactoryBaseImpl.java:53)
     at $Proxy1.getSecuritySupport(Unknown Source)
     at com.sun.enterprise.security.SecurityUtil.getSecuritySupport(SecurityUtil.java:338)
     at com.sun.enterprise.ee.nodeagent.NodeAgent.initializeSecurity(NodeAgent.java:1125)
     at com.sun.enterprise.ee.nodeagent.NodeAgent.configureAgent(NodeAgent.java:1231)
     at com.sun.enterprise.ee.nodeagent.BaseNodeAgent.init(BaseNodeAgent.java:137)
     at com.sun.enterprise.ee.nodeagent.NodeAgent.synchronizeWithDASInternal(NodeAgent.java:545)
     at com.sun.enterprise.ee.nodeagent.NodeAgent.synchronizeWithDASInternal(NodeAgent.java:462)
     at com.sun.enterprise.ee.nodeagent.BaseNodeAgent.run(BaseNodeAgent.java:110)
     at com.sun.enterprise.ee.nodeagent.NodeAgentMain.startup(NodeAgentMain.java:149)
     at com.sun.enterprise.ee.nodeagent.NodeAgentMain.main(NodeAgentMain.java:190)
Caused by: java.lang.IllegalStateException: NSS password is invalid. Failed to authenticate to PKCS11 slot: internal
     at com.sun.enterprise.ee.security.EESecuritySupportImpl.<clinit>(EESecuritySupportImpl.java:148)
     ... 13 more
Message was edited by:
Envision
It turns out that the problem was related to the master password after all. Apparently the Windows Install doesn't set it, so it is left as adminadmin. Even after changing the master password, the node agent could not connect, because it needed the original password to connect first. If I changed the master password and re-created the node agent it works.

I am trying to create a cluster of 2 Windows 2003 servers using enterprise edition 8.1 2005Q2 installations. I installed on one server and setup a domain and node agent, created a cluster and deployed my application. I tried to install a node agent only version on the other server, but it doesn't seem to exist, so I installed with domain administration server also. I deleted the node agent and recreated it pointing to the DAS on the other server. I got it to create, but I cannot start it. I get the message Password entered is invalid, even though I am entering the same password used to create it and the same password used as the master password. I've tried deleting and recreating the node agent and then I get the error failed to start and the log contains the error below. After that first time, I continue to get the password invalid message
[#|2006-11-29T16:34:06.281-0500|SEVERE|sun-appserver-ee8.1|javax.ee.enterprise.system.nodeagent|_ThreadID=10;|NAGT0014:Unexpected Node Agent exception.
java.lang.ExceptionInInitializerError
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java:164)
     at com.sun.enterprise.pluggable.PluggableFeatureFactoryBaseImpl.invoke(PluggableFeatureFactoryBaseImpl.java:53)
     at $Proxy1.getSecuritySupport(Unknown Source)
     at com.sun.enterprise.security.SecurityUtil.getSecuritySupport(SecurityUtil.java:338)
     at com.sun.enterprise.ee.nodeagent.NodeAgent.initializeSecurity(NodeAgent.java:1125)
     at com.sun.enterprise.ee.nodeagent.NodeAgent.configureAgent(NodeAgent.java:1231)
     at com.sun.enterprise.ee.nodeagent.BaseNodeAgent.init(BaseNodeAgent.java:137)
     at com.sun.enterprise.ee.nodeagent.NodeAgent.synchronizeWithDASInternal(NodeAgent.java:545)
     at com.sun.enterprise.ee.nodeagent.NodeAgent.synchronizeWithDASInternal(NodeAgent.java:462)
     at com.sun.enterprise.ee.nodeagent.BaseNodeAgent.run(BaseNodeAgent.java:110)
     at com.sun.enterprise.ee.nodeagent.NodeAgentMain.startup(NodeAgentMain.java:149)
     at com.sun.enterprise.ee.nodeagent.NodeAgentMain.main(NodeAgentMain.java:190)
Caused by: java.lang.IllegalStateException: NSS password is invalid. Failed to authenticate to PKCS11 slot: internal
     at com.sun.enterprise.ee.security.EESecuritySupportImpl.<clinit>(EESecuritySupportImpl.java:148)
     ... 13 more
Message was edited by:
Envision
It turns out that the problem was related to the master password after all. Apparently the Windows Install doesn't set it, so it is left as adminadmin. Even after changing the master password, the node agent could not connect, because it needed the original password to connect first. If I changed the master password and re-created the node agent it works.

Starting the Oracle Intelligent Agent on Linux/390

I have recently installed Oracle Developer's Edition on SuSE Linux/390. When I try to start the Intelligent Agent, I get the following error.
------------------------ Mon Jun 3 11:59:43 EDT 2002 ------------------------
Certain conflicts were resolved during discovery
Please consult /oracle/product/9.0.1/network/log/nmiconf.log for details
Error: Failed to get directory/file info from environment
Failed while initializing Collection Service
Error initializing subsystems
Agent exited at Mon Jun 3 11:59:45 EDT 2002 with return value 55
Could not start agent. Initialization failure
Contents if nmiconf.log:
DBSNMP for Linux 2.4.7-SuSE-SMP: release 9.0.1 - Developer's Release on 03-JUN-02 11:59:43
Discovering services on linux1 configured on host addresses {linux1.dowjones.com 172.26.151.11}
Using oratab file /var/opt/oracle/oratab
Warning : problem getting ops version for /oracle/product/9.0.1 : CIDW
Any assistance would be greatly appreciated.

I don't think the Intelligent Agent is included with the developers release -
check the directory where it's supposed to be, I think you'll find it's not there.
You only need IA to start/stop the database from oem and schedule jobs.
I use OEM to control my instance and run performance packs etc, IA isn't needed for this.

Error while starting the app server instance

Hi,
When I am starting the stand-alone instance on app sever, i am getting the following error:
An error has occurred.
Operation 'start' failed in 'server' Config Mbean. Target exception message: The node agent could not start instance imgr. It is starting and must be stopped.
Could you please tell what might be wrong.
Regards.

I got this same error and it turned out to be because one of the developers had changed the line AS_JAVA="/usr/jdk/entsys-j2se" in /opt/sun/appserver/config/asenv.conf
to point to a 1.4.2_10 jre. (/usr/jdk/entsys-j2se was a symlink to /usr/java/jdk1.5.0_04/)
I changed it to an installation of 1.4.2_09 sdk that we had previously installed on their and everything worked fine.
I don't know whether it was because it pointed to a jre as opposed to an sdk or whether the jre was incorrectly installed. (it's a much around box, so everyone's allowed to do pretty much whatever they want to it)
Hope this helps,
Adam

Where do I find the "Node Manager" service?

Can anyone tell me where to find the "Node Manager Service" In Call Manager 5.1.2 or IPCC 4.5?
My db_CRA database in IPCC is not updating the real time ICD statistics table and Bug CSCsc09160 seems to indicate that stopping and starting the "Node Managers" may fix the issue.
From the bug report:
Symptom:
Under the db_cra two tables (RtCSQsSummary and RtICDStatistics) are not updating. They stop updating concurrently with engine failovers and reboots. Only a hard reboot or a
service failover brings them back into an active state.
When the RtCSQsSummary and RtICDStatistics tables do update on the
primary DB they do not update on the secondary DB and the data on them
doesnt get refreshed.
Conditions:
stopping Node manager on node 1, data fails to be written to node 2. Then when we start NM back up on node 1 data is still not written to either data store
Workaround:
Not much as a workaround, because the solution requirs stop on both Node
Managers and bring up node 1 first and the data starts writing to DB
again.
Thanks,
Brian

Post Author: jsanzone
CA Forum: Authentication
Sven,
The reference to Session Manager is more of a concept of operations versus an entity. The portion of code that you copied and pasted in your post is actually part of the verbiage used in an ASP script that BusinessObjects expects you to create in order for you to obtain your objective. You can use this coding to create your own customized script or you might be able to search around on the web for a more complete solution.

How to change the management agent to use new management service ?

RDBMS Version:: 10.2.0.3
Operating System and Version:: AIX 5L
OEM Console Operating System and Version:: AIX 5L
Configuring the Management Agent to Use a New Management Service
Hi,
I am trying to change the management agent to use new management service using following process.
1. Stop management agent.
2. Change in file Agent_home/sysman/config/emd.properties
For values REPOSITORY_URL and emdWalletSrcUrl and emdWalletDest
3. Delete all the files in the following directories:
AGENT_HOME/sysman/emd/upload/
AGENT_HOME/sysman/emd/state/
4. Start the management agent.
./emctl status agent is showing the new URL for management server (OMS).
But I am not able to locate the new host on the Web console at the OEM console where it is changed to.
Can you suggest me workaround for the same?
Thanks
Dilipkumar Patel

Hi,
I am getting following error when trying to upload.
tb152 /appl/oracle/oem/10.2.0/bin> ./emctl upload agent
Oracle Enterprise Manager 10g Release 10.2.0.1.0.
Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.
EMD upload error: uploadXMLFiles skipped :: OMS version not checked yet..
tb152 /appl/oracle/oem/10.2.0/bin>
Regards
Dilipkumar Patel.

Problem starting Oracle Intelligent Agent

Hi,
I have an Oracle Database 8i installed on Windows 2000 Server.
When I change my computer name, the Oracle Intelligent Agent could not be started.
What should I do to start the Oracle Intelligent Agent, if I want to use new computer name for my computer ?
Thanks in advanced.
Regards,
Eddy

Nick Yelevich (guest) wrote:
: Hkon W0ien (guest) wrote:
: : When starting oracle intelligent agent with the lsnrctl
: : dbsnmp_start command everything seems to be OK, but the
agent
: : dies immediately. The listener and everything else is
working
: : OK. The files snmp_ro.ora and snmp_rw.ora are created and as
: : fare as I know with the correct contents. I have turned on
: trace
: : and the last lines in the trace file dbsnmpw.trc shows the
: : following.
: : snmidlpi_PkgIndex: creating package index
: : -<ERROR>- snmidlpi_PkgIndex: failed to initialize init.tcl,
: : error 1
: : -<ERROR>- snmidlpi_PkgIndex: Tcl result:
: : I'm running RedHat 5.2 and Oracle v.8.0.5 production. All
files
: : in TNS_ADMIN are created using Oracle Net8 Assistant.
: : Any idea ?
: My situation is almost the same, but in my case snmp* files
had
: not been created. I have RedHat 5.2 and preproduction version
: Oracle 8.0.5.
I too can not start the intelligent agent. I am on Redhat 5.2
with the (I think production ) version of 8.0.5. Mine seems to
start up but the lsnrctl dbsnmp_status says that it is not
running. the dbsnmp_start seems to work but gives no feedback.
I get the error NMS-00315 in on of my log files. Any one have
any idea? I tried reinstalling the agent and infact the entire
oracle 8 server and got the same thing. thanks in advance.
Keir
null

How to start / stop nodes without domain-controller / automatically on Win?

Hi,
we have a distributed installation of CMSDK 9.0.4.
We have installed a 9.2.0.4 Database on Solaris and we are using the 10g(9.0.4) Infrastructure on Solaris with it.
The first installation of CMSDK uses a J2EE-MidTier installation on the Solaris server and contains the CMSDK domain controller and a normal node with nfs protocol server running.
The other installations are done on Win2003 Blades. Currently we are using two Blades. On each there is a J2EE-MidTier installation and within these we have installed CMSDK with HTTP-Node and normal node. We are using NTFS-Server within the normal nodes.
The Blades are within one Domain and we have NLB-Cluster activated for both.
The whole thing sounds complex, but it works fine. We only have some trouble regarding start/stop of the nodes:
1. If the solaris backend fails, our cluster-configuration tries to stop and start cmsdk. While stopping cmsdk, all nodes - even those on the Win-Servers - are stopped. But starting does not bring em up again automatically.
2. If a Windows Server is booted, the normal node does not start automatically.
3. If one Windows Server is not available, the ifsctl check takes a very long time because it's trying to get information from the missing one.
Is there a way to restart the domain controller and node on solaris without stopping the nodes on Windows?
How can we start the windows nodes automatically after reboot?
Is there a way to probably start the nodes without being managed / guarded by the domain controller?
Thanks for help,
Alex

Try adding this script to your /etc/init.d directory:
#!/bin/sh
ifsctl start << EOF
<ifsctl password>
EOF
Replace <ifsctl password> with the password that you would give at the prompt.
It will complain about Inappropriate ioctl for device, but it works.

Starting the node agent

Similar Messages

Maybe you are looking for