OEM intelligent agent

I'm running 8.0.5 on Red Hat 6.0. The system has been running happily for two months, but I'm now starting to play with the management tools and having a problem.
When I start the OEM intelligent agent via
"lsnctrl dbsnmp_start"
I get the following error message in DBSNMPW.log:
NMS-00315: Message 315 not found; No message file for product=network, facility=
NMS
From OEM Doc I found the following:
NMS-00315: Failed to create tcl package index.
Cause: The tcl package index could not be created.
Action: Make sure all the shared libraries in the $ORACLE_HOME/network/agent/library directory are correct.
I checked the $ORACLE_HOME/network/agent/library and found it was empty.
I then started orainst and checked to see that OEM intelligent agent was installed, it shows as being installed
Has anyone run into this problem? Does anyone have a solution?
Thanks

hello,
I have a problem with the installation of a agent in OEM on linux (Fedora).
this error has occur :
Oracle9i Enterprise Edition Release 9.0.1.5.0 - Production
With the Partitioning option
JServer Release 9.0.1.4.0 - Production
SQL> SQL> SQL> WEBSITE Creation FAILED = EM Website ERR:Host not found
CREATE DEFAULT WEBSITE FAILED : ORA-20998: Host not found
BEGIN
ERROR at line 1:
ORA-20999: CREATE DEFAULT WEBSITE FAILED : ORA-20998: Host not found
ORA-06512: at line 234
Disconnected from Oracle9i Enterprise Edition Release 9.0.1.5.0 - Production
With the Partitioning option
JServer Release 9.0.1.4.0 - ProductionWebsite target creation script failed.
Apr 19, 2004 11:26:04 AM oracle.agent.ConfigureAgent startAgentService
INFO: Starting the agent...
Starting the agent...TZ set to Europe/ParisOracle Enterprise Manager 10g Release 10.1.0.2.0.
Copyright (c) 1996, 2004 Oracle Corporation. All rights reserved.Starting agent .................... failed.
Apr 19, 2004 11:26:38 AM oracle.agent.ConfigureAgent startAgentService
INFO: Started agent Successfully
Started agent Successfully
The Management Agent Configuration Assistant has failed. The following failures were recorded:
Enterprise Manager Website target configuration failed.
Agent Service Failed to start.
Exit status: 1
Configuration assistant "Agent Configuration Assistant" failed
Can you help me please to resolve this problem.
ps:
OEM is succesfully installed in my computer.

Similar Messages

  • Oracle Support: SNMP, OEM Console & Intelligent Agent

    I have the Intelligent Agent running fine (thanks to the "Does
    anyone at Oracle Support read these messages" thread). I can
    tnsping the agent and listener from the Win98 OEM Console
    machine, I can access the listener when manually discovered.
    When I try to submit a job, there is nothing in the Destinations
    window. I have SNMP enabled on the 8.0.5.1 server.
    Simple question, will it work or not, I really have got better
    things to do with my time.
    Sick of wasting time.
    Paul Smyth
    null

    Yes it will work. You'de better sign a Technical Support Contract
    with Oracle (if you havent) and call them.
    They surely can help.
    Regards,
    Michael
    Paul Smyth (guest) wrote:
    : I have the Intelligent Agent running fine (thanks to the "Does
    : anyone at Oracle Support read these messages" thread). I can
    : tnsping the agent and listener from the Win98 OEM Console
    : machine, I can access the listener when manually discovered.
    : When I try to submit a job, there is nothing in the
    Destinations
    : window. I have SNMP enabled on the 8.0.5.1 server.
    : Simple question, will it work or not, I really have got better
    : things to do with my time.
    : Sick of wasting time.
    : Paul Smyth
    null

  • How to config or start Intelligent Agents for OEM

    I have install the ORACLE 8.1.7 on redhat 7 successfully. Then I start the "o8ibegin" database instance, start the Oracle Management Server successfully. But, when I start the OEM by using "oemapp console", I could not discover the nodes, it tells me that I maybe do not have Oracle Intelligent Agents. I have chosen to install Oracle Intelligent Agents on install phase, and I have checked that Oracle Intelligent Agents have installed on my system.
    I want to know how to start the Oracle Intelligent Agents service. I remember Oracle Intelligent Agents is a service on Windows NT/2000 version. I alos met such problem on Windows NT/2000, and when I start the Oracle Intelligent Agents service throught service applet on control panel, I resolve the problem.

    try 'lsnrctl dbsnmp_start' to start
    and 'lsnrctl dbsnmp_status' to verify

  • OEM Repository and Intelligent Agent

    How many OEM repository and Intelligent Agent do I need to have to schedule a unique job on three of the 4 databases I have?
    Thanks,
    Mirabelle

    If databases are not discovered, you could have a problem with any of the following files.
    listener.ora
    oratab ( UNIX/Linux)
    Microsoft Registry (Windows)
    1. Check the $ORACLE_HOME\network\agent\log\nmiconf.log for warnings or errors.
    2. Verify the database sid exists in the listener.ora file. When the Agent parses the listener.ora, it looks for the "sid_list=...." section. If this section is missing, the Agent will not discover the database.
    3. Verify the database sid exists in the oratab or Microsoft Registry. (In some cases, the sid is case sensitive.)
    4. Stop and Restart the Agent. NOTE: This step is necessary because the Agent will only parse the files during startup.
    5. Check the services.ora file and verify the Database services now exists in the file.
    6. Refresh the Node through the EM Console.

  • OEM 9i Supporting 10g Intelligent Agents

    Hello.
    We currently use OEM 9.2.0.1 for monitoring and tracking of our 9i database instances. I want to add in our application server when we go live with iAS 9.0.4.1. We're currently running 1.0.2.2, which of course is well behind the times. Will the 10g iAS Intelligent Agent communicate with a 9i EM? If so, are there any limitations, or special considerations I need to take into account? Thanks.

    Nope. Totally different architectures.

  • Linux Intelligent Agent - OEM cannot discover node

    Hi,
    I have a Linux AS 2.1 Server with a Oracle 9.2.0.1 Database running. I have 2 Oracle Management Servers ... one is running on this running on the Linux AS 2.1 Server and another on Solaris 9i.
    When start the OEM on the Linux Server and try to discover the Databases on the Linux Server themselves then everything goes fine. When I am trying to discover the databases on the Linux Server from the OEM running in Solaris it does not work.
    The Solaris box has connection to the Linux Server and the repository for the Solaris OEM runs on the Linux Machine.
    When I go back to the OEM on the Linux Machine then I can discover the Solaris box.
    To come to a boddom line here: Whatever I do I am not able to discover the databases on the Linux AS Server besides from the OEM directly running on this box.
    Is that a bug in the Linux Intelligent Agent ? If yes is there a Patch to fix that ? Or is there a work around.
    Please let me know if you have any idea.
    Thanks Marcus

    Ok I figured it out .... the problem is/was the entry of the Loopback Interface entry in the etc hosts:
    127.0.0.1 dbserver localhost.localdomain localhost
    The Intelligent Agent listens to the Loopback Interface now. All incoming requests from and OMS will of course get a timeout because the IP address of the server is 10.1.0.10 .
    You have 2 options now:
    1. Change the entry in the /etc/hosts below to localhost and add an entry to the /etc/hosts file:
    127.0.0.1 localhost localhost.localdomain localhost
    10.10.0.1     dbserver
    Restart the Intelligent Agent and any OMS in your network should be able to discover the note.
    2. In the snmp_rw.ora file you can bind the Intelligent Agent with the following entries to an specific hostname and/or port:
    DBSNMP.HOSTNAME = <hostname or ip address>
    DBSNMP.CS_BASE_PORT = <port number>
    If you start up Agent now you will see in the nmiconf.log file error messages like that:
    Warning: No Listener found for SID db01. db01 will be skipped     
    Warning : No Listener found for SID db02. db02 will be skipped
    Warning : No Listener found for SID db03. db03 will be skipped
    Warning : No Listener found for SID omsrep. omsrep will be skipped
    This is because the Agent looks up in the tnsnames.ora file or whatever you name resolution is and finds the connect descriptors still withe the old name. So all entries in the tnsnames.ora file have to be changed.

  • Intelligent Agents -- OEM

    How can I check that Intelligent agent is running on my Oracle machine (For Sun Solaris Intel)
    Regds

    Nope. Totally different architectures.

  • Ora8, Intelligent Agent, RH6 & OEM on NT

    I've spent most of today trawling through these messages looking
    for information on getting the Intelligent Agent up and running
    on Linux, RedHat 6.0.
    I am running 8.0.5 EE with the glibcpatch installed (hopefully
    correctly, as I cannot get the README file of the FTP site).
    Everything works, the Agent even starts (2 * dbsnmp processes)
    but I cannot discover the services on my box from an NT machine
    running the Oracle Enterprise Manager.
    By putting tracing on the Agent (level 16) I find that the log
    file ends with the following (continually being added to the
    file).
    nttcnr: exit
    nttcon: exit
    nsopen: unable to open transport
    nsmfr: 1596 bytes at 0x844f2a8
    nsmfr: 416 bytes at 0x844f100
    nsmal: 416 bytes at 0x844f060
    nsmal: 1596 bytes at 0x844f208
    nsopen: opening transport...
    nttcon: entry
    nttcon: toc = 3
    nttcnp: entry
    ntvlin: entry
    ntvlin: exit
    nttcnp: Validnode Table IN use; err 0x0
    nttcnp: getting sockname
    nttcnp: exit
    nttcnr: entry
    nttcnr: waiting to accept a connection.
    ntt2err: entry
    ntt2err: exit
    nttcnr: exit
    nttcon: exit
    Any ideas? Any help greatly appreciated. I really don't want to
    go back to 5.2 or 5.1 if I can help it.
    ps. Can you put the glibcpatch README on the HTTP site and not
    the FTP site? I'd love to know what's in it!
    Angus
    null

    Angus (guest) wrote:
    : I've spent most of today trawling through these messages
    looking
    : for information on getting the Intelligent Agent up and
    running
    : on Linux, RedHat 6.0.
    : I am running 8.0.5 EE with the glibcpatch installed (hopefully
    : correctly, as I cannot get the README file of the FTP site).
    : Everything works, the Agent even starts (2 * dbsnmp processes)
    : but I cannot discover the services on my box from an NT
    machine
    blah-blah
    I've reverted to RedHat5.2 and RedHat 5.1's version of TCL.
    Everything now runs as expected.
    Angus.
    null

  • Has Anyone gotten the Intelligent Agent to work???

    I have Oracle installed and all is well except for a few minor
    problems that I think the Intelligent Agent will solve. Has
    anyone gotten this to work on RedHat 6.0 with Oracle
    Enterprise Edition 8.0.5.1??? I was able to get it to work
    under Oracle8 SE, but I need EE for the ConText Cartridge.
    I have gotten to the point where I can get the dbsnmp process
    running, but OEM cannot talk to it.
    Please help
    --Bryan
    null

    I'm having the same problem. Does anyone out there have a
    solution?
    I am running RedHat Linux 6.0 straight out of the box. The only
    change I made was to set the kernel parameters according to the
    release notes and recompile the kernel.
    P.S. Oracle deserves our thanks for providing free developer
    licenses to so many of its products, but this is the buggiest
    install I've ever seen in my 12 years of working with their
    products. Didn't anyone from Oracle test the install? This
    problem and the zero length libnjni8.so file are the real
    doozies.
    I've followed the release notes and installation guide to the
    letter and have found several documentation / distribution bugs
    that should have leapt out at the first person who tried it.
    Thorsten Khnemann (guest) wrote:
    : Bryan Batchelder (guest) wrote:
    : : anyone else who could not get it to compile with TCL 7.5 to
    : : please at least let me know other people are having the same
    : : problem.
    : Same problem here, the
    : "gmake -f ins_oemagent.mk agent" gives the message
    : "gcc: unrecognized option
    : `-R/home/oracle/run/product/8.1.5/lib/'" and hundreds
    : of unresolved references.
    : Tested on RedHat 6.0, egcs 1.1.2
    null

  • 8.1.7 Intelligent Agent on Redhat Linux 6.2

    Hello,
    Can anyone help?
    My OEM fails to discover a Redhat Linux node but I can manually configure it (so the node address must be OK). When I check that the agent is running (lsnrctl dbsnmp_agent) it says that the db subagent is already running. If there is something obvious, I've probably missed it because I'm relatively new to both Oracle and Linux/Unix. Any clues, please?

    I found this reply on Oracle Metalink and it worked for me (looks like agent on Linux for some reason does not use default ports:
    On IA nodes, edit the snmp_rw.ora file and add the following lines :
    DBSNMP.ADDRESS = (ADDRESS=(PROTOCOL=tcp)(HOST=<ip-address>)(PORT=1748))
    DBSNMP.SPAWNADDRESS = (ADDRESS=(PROTOCOL=tcp)(HOST=<ip-address>)(PORT=
    1754))
    where <ip-address> is the IP-Address of the node to be discovered.
    Note: ports 1748/1754 must be open for the OMS to communicate with the Agent.
    The OMS starts communication on ports 1748 and 1754 to get the discovery
    information from the Intelligent Agent.
    The ports 1748 and 1754 are dedicated for the Intelligent Agent, and should
    not be used by any other program.
    Ports used by the Intelligent Agent:
    ++++++++++++++++++++++++++
    During the discovery phase, the Communication Daemon OMS
    will contact the Intelligent Agent via the ports 1748 and 1754 and retrieve
    the discovery information.
    Port 1748 is used for the basic communication, while the port 1754 is
    used for file transfer. The communication is always initiated from the
    Communication Daemon or OMS towards the Intelligent Agent.
    The ports are hardcoded in the Intelligent Agent and should not be altered
    in any way. The ports are referenced in the snmp_rw.ora file as:
    dbsnmp.address=(address=(protocol=tcp)(host=somehostname)(port=1748))
    dbsnmp.spawnaddress=(address=(protocol=tcp)(host=somehostname)(port=1754))
    The meaning of the dbsnmp.address and dbsnmp.spawnaddress are solely to
    determine the resolution path for the Enterprise Manager framework to get
    in touch with the Intelligent Agent, and should not be used to specify
    other ports.

  • Intelligent Agent doesn't work

    Hi dear colleagues,
    I got a problem with the Intelligent Agent.
    I installed Oracle 8i EE 8.1.5 and OEM 2.1 on Windows 2000 server. When I
    try to discover the databases with OEM, OEM could only find the node, it could
    not find any database. So I thought maybe the Agent got some problem. I
    opened the log file nmiconf.log, the following is the message in it:
    DBSNMP for 32-bit Windows: release 8.1.5 - Production on 13-MAY-02 20:04:18
    Warning : Listener LISTENER defined in H:\Oracle\Ora81\network\admin\listener.ora will be skipped because, it does not have a corresponding NT service entry
    Warning : Skipping OracleOraHome81TNSListener : Couldnot find corresponding listener definition in {H:\Oracle\Ora81\network\admin\listener.ora}
    Warning : No Listener found for SID SIDDB1. SIDDB1 will be skipped
    Warning : No Listener found for SID SIDDB3. SIDDB3 will be skipped
    But I don't know where and how to create a NT service entry corresponding to
    the listener LISTENER. Please help me!
    Thanks!
    Wendell

    I think there is no problem with the intelligent agent. It seems to be a problem with your net8 configuration. I think the problem could be caused by several reasons:
    1. Your listener is not configured properly: the listener.ora file should contain a valid service entry for the database (you can do this with the net8 assistant provided by oracle. Normally it should be installed by default)
    2. The agent looks in the wrong listener.ora file for a service entry. So do you have more then one ORACLE_HOME and more the one listener.ora file on the node?
    3. Do you have more then one network interface and are you working with more then one hostname alias? That could also cause a problem. It could be a solution to replace the hostname in the host=name part of the listener.ora file with the right!! IP adress. May be you have to test all the IP adresses of your node.

  • Oracle intelligent agent failure

    Hi,
    I am on windows 2000 server running Oracle 9i database and I cannot start the intelligent agent for database 9i it keeps giving the ,message that it is idle therefore was stopped. When I start it in dos it dumps the message belog in its log. I would like to use the OEM to manage my database but can't because the OMS cannot detect my nodes cos the agent is not running. Please assist.
    The message
    Service name is Oracleoracle9_HomeAgent
    Failed while initializing Collection Service
    Error initializing subsystems
    Agent exited on with return value 55
    Could not start agent. Initialization failure
    Agent startup failed. Check F:\ora9i\network\log\Oracleoracle9_HomeAgent.nohup for details

    Hi,
    check for the time zone.
    In my case it was solved when I was creating a system environment variable named TZ and choosed a valid content, see metalink for timezone problems:
    nsupportedtzs.lst
    supportedtzs.lst
    in the sysman\admin should have a common denominator.
    Regards
    Matthias

  • Oracle Intelligent Agent cannot be started

    I have installed Oracle 9i into RedHat Linux 9. When I start the Oracle Intelligent Agent, I get nothing response, and find the agent cannot be started.
    I find the error message in dbsnmp.nohup which is showed below:
    /opt/ora9/product/9.2/bin/dbsnmp: error while loading shared libraries: libvppdc.so: cannot open shared object file: No such file or directory
    Agent exited at Thu Nov 13 23:20:31 HKT 2003 with return value 127
    Agent thrashing. Exiting dbsnmpwd at Thu Nov 13 23:20:31 HKT 2003
    I found the library object is existed.
    [oracle@localhost lib]$ ll libvpp*
    -rw-r--r-- 1 oracle oinstall 552036 Apr 26 2002 libvppdc.so
    Can anyone help me to solve the problem?
    Thank you.
    Regards,
    Franklin

    Problem of method 1 (for re-install the oem agent / dbsnmp)
    When I follow the "work Around Procedure" from
    http://www.puschitz.com/InstallingOracle9i.shtml#OracleInstallationErrors
    and download the RPMs (glibc-2.3.2-5.i686.rpm glibc-common-2.3.2-5.i386.rpm glibc-devel-2.3.2-5.i386.rpm) for the procedures.
    When I run the command (#rpm -Uvh --oldpackage glibc-2.3.2-5.i686.rpm glibc-common-2.3.2-5.i386.rpm glibc-devel-2.3.2-5.i386.rpm),I found the error shown below:
    error:glibc-2.3.2-5.i686.rpm:V3 DSA Signature:BAD, key ID db42a60e
    error:glibc-2.3.2-5.i686.rpm cannot be installed
    Problem of method 2
    When I try to unpack glibc-2.3.2-5.i686.rpm and replace libc-2.3.2.so and libc.so.6 by using the following steps
    # mkdir /root/tmp
    # mv glibc-2.3.2-5.i686.rpm /root/tmp
    # cd /root/tmp
    # rpm2cpio glibc-2.3.2-5.i686.rpm | cpio -idmv
    # cp /lib/libc-2.3.2.so /lib/libc-2.3.2.so.ORIG
    # cp lib/libc-2.3.2.so /lib/.
    # rm -f /lib/libc.so.6
    # ln -s /lib/libc-2.3.2.so /lib/libc.so.6
    I find the system is halted, when I run (# cp lib/libc-2.3.2.so /lib/.) When I reboot the system, I find error
    init:error while loading shared libraries:libc.so.6:cannot open shared object file:No such file or directory
    Kernel panic: Attempted to kill init.
    Please help me to fix the problem. Many thanks.
    Regards,
    Franklin.

  • INTELLIGENT AGENT PROBLEM RECOVERY ON NT

    제품 : ORACLE SERVER
    작성날짜 : 1997-12-16
    The Oracle Intelligent Agent 7.3.3 on NT is self-configuring and
    requires TCP/IP fully configured on the NT system.
    The Agent's startup algorithm:
    When the agent is started, the startup process reads the LISTENER.ORA,
    TNSNAMES.ORA and NT REGISTRY. It compares the values stored in each location.
    If any discrepencies exist, the agent service will either not start
    or service discovery will not occur.
    Starting the Intelligent Agent:
    1. Verify the Sqlnet configuration files are correct:
    - All sid entries in the LISTENER.ORA must have valid TCP/IP service
    descriptors defined in the TNSNAMES.ORA file.
    - The TNSNAMES.ORA should not contain service descriptors for local
    sides not defined in the LISTENER.ORA file.
    - TCP/IP must be fully configured on the system.
    2. NT 4.0: Click on START->SETTINGS->CONTROL PANEL->SERVICES.
    Highlight the service ORACLEAGENT. Click on the START button.
    NT 3.51: Find the MAIN program group.
    Click on CONTROL PANEL->SERVICES.
    Highlight the service ORACLEAGENT. Click on the START button.
    ***NOTE: If the 7.3.3 agent will not start, verify the OEM version
    is not 1.4.
    If the version is 1.4, install the 8.0.3 Intelligent Agent.
    Agent troubleshooting tips:
    1. Verify TCP/IP is configured correctly.
    - At a dos prompt, type HOSTNAME.
    This is the actual configured TCP/IP HOSTNAME of the system.
    - Verify the hostname resolved by the agent. The DBSNMP.ADDRESS
    parameter in the ORANT/network/snmp_rw.ora contains this
    information.
    If the file does not contain the actual hostname, TCP/IP is not
    properly configured on the system or the network.
    2. Correcting TCP/IP configuration problems:
    - Edit the WINNT\system32\drivers\etc\hosts and lmhosts files.
    (*NOTE: If these files have never been used, only sample files will
    exist in the directory. Either rename or copy the .sam files
    to just the file name with no extention.)
    - Follow the example below (replace the information in brackets
    with the actual host information for that system.):
    HOSTS file:
    <122.111.111.111> <hostname>
    LMHOSTS file:
    <122.111.111.111. <netbios name or hostname> #PRE
    - Delete the ORANT\network\agent\*.q and SERVICES.ORA files.
    (*NOTE: The *.q files hold information about jobs and events.
    Do not delete these files without first removing all jobs
    and events registered against this agent.)
    - Delete the $ORACLE_HOME\network\admin\SNMP_RO.ORA and      
    SNMP_RW.ORA files.
    - Restart the agent at a DOS prompt:
    NET START ORACLEAGENT
    3. Check the NT EVENT VIEWER->APPLICATIONS->LOG for any errors
    starting the DBSNMP process.
    4. Check the ORANT/NETWORK/LOG/NMICONF.LOG file for other possible
    errors.
    5. If using NTFS, check permissions to the \orant\network directory
    structure.

    Angus (guest) wrote:
    : I've spent most of today trawling through these messages
    looking
    : for information on getting the Intelligent Agent up and
    running
    : on Linux, RedHat 6.0.
    : I am running 8.0.5 EE with the glibcpatch installed (hopefully
    : correctly, as I cannot get the README file of the FTP site).
    : Everything works, the Agent even starts (2 * dbsnmp processes)
    : but I cannot discover the services on my box from an NT
    machine
    blah-blah
    I've reverted to RedHat5.2 and RedHat 5.1's version of TCL.
    Everything now runs as expected.
    Angus.
    null

  • Oracle Intelligent Agent Exe encountered a problem and needed to close

    Whenever the server is rebooted I get the error "Oracle Intelligent Agent Executable encountered a problem and needed to close". The agent won't start, and I found a work around that included deleting files from the network/agent and admin folders, then restarting the agent. This works, however the next time the server reboots I have to go through all of this again. Any ideas why this keeps occurring?
    Also, what does this agent do? I've read through some documentation and can't quite tell if I actually need it started. Do you use this agent to only remotely monitor/administer through OEM? I'm really confused and could use some insight. All my process appear to be working fine.

    Because of the error message I guess you are on Windows and database version is lower than 10g (by the way it's always a good idea to tell the environment, because Oracle runs on different platforms in different versions).
    ... 'encountered a problem and needed to close' is generic Windows error message with millions of possible reasons. So it's not possible to find remotely a solution. You are right, Intelligent Agent is a counterpart of OEM, but outside production environments rarely needed. I recommend you change the service properties from 'automatic' to 'manual' in control panel. So it does not start at reboot time.
    Werner

Maybe you are looking for