Agent is unreachable

Hi!
I'm using EM12cR2 on Solaris SPARC. EM agent 12.1.0.2.0 became to crash after 2 days network subnet was changed.
How occurs the problem:
1. I started agent
2. After few hours i got a notification
Message=Agent is Unreachable (REASON = unable to connect to http server at https://DSSINVDB01:3872/emd/main/. [peer not authenticated]). Host is unreachable (REASON = Unknown Error pinging the host of URL https://DSSINVDB01:3872/emd/main/.1).
3. After 10..30 mins i got notification that agent became up again.
4. steps 2-3 occured few times per day.
5. After few hours or days agent became unreachable for keeps and didn't restart
./emctl status agent gets the following:
Status agent Failure:unable to connect to http server at https://dssinvdb01:3872/emd/lifecycle/main/. [peer not authenticated]
Agent is Not Running
$ps -ef | grep agent
oracle 21236 1 0 окт. 25 ? 0:53 /u01/app/oracle/agent12c/core/12.1.0.2.0/perl/bin/perl /u01/app/oracle/agent12c
oracle 24472 21236 0 окт. 28 ? 11:34 /u01/app/oracle/agent12c/core/12.1.0.2.0/jdk/bin/sparcv9/java -Xmx128M -XX:MaxP
Others agents on other hosts don't have such issue.
I checked logs of EM agent and didn't found any essential errors.
I totally cleared (deinstalled & removed all files) and installed fresh agent binaries on that host. But it also didn't help.
Ntp clients configured...

On the one server with patch cluster + 10_Recomended problem was solved, but on another one - still exists.
I've got notifications
Agent is Unreachable (REASON = unable to connect to http server at https://dssinvdb01:3872/emd/main/. [peer not authenticated]). Host is unreachable (REASON = Unknown Error pinging the host of URL https://dssinvdb01:3872/emd/main/.1).
3 times per day. Agent is restarted ( emctl status agent > Started at is refreshed regulary )
This server has also Solaris 10 update 10 installed but i'm not sure that latest 10_recommended was aplied as on the first host.

Similar Messages

  • Agent is unreachable but the host is reachable

    Hi all,
    I am getting alerts
    Message=Agent is Unreachable (REASON = unable to connect to the agent at https://xxxxx.xxx.xxxx.xxxx.xx.xx:xxxx/xxx/main/ [Connection refused: connect]) but the host is reachable.  Our database instance are two nodes rac  in windows platform. I checked listeners and services and all are ok. However when i ran emctl status agent comand then i am getting following message.
    C:\Users\xxxx>emctl status agent
    Environment variable ORACLE_UNQNAME not defined. Please set ORACLE_UNQNAME to da
    tabase unique name.

    Ensure the ORACLE_HOME is properly set to the Agent home on the target server
    Set the ORACLE_UNQNAME to your unique db name
    stop and start the agent

  • Agent becoming unreachable frequently

    Hi,
    Have noticed that one particular OEM agent becomes unreachable , and the agent status shows that the agent is up and running .
    But the data collection status shows that DISABLED BY UPLOAD MANAGER.
    From front end it shows that the agent is unreachable and agent is blocked.
    Impact on service: status changes to status pending .
    Regards
    Kishan M G
    Edited by: KISHAN M G on Mar 13, 2013 11:30 AM

    Did you check the emoms.log on the OMS host to see why the agent is blocked. try unblocking the agent and also resecure the same.

  • Agent is Unreachable (REASON = Connection refused) but the host is UP

    Folks,
    Can I pick your brains, I keep recieving the smtp alert from Grid control which says;
    Agent is Unreachable (REASON = Connection refused) but the host is UP
    upto 5 minutes later the smtp mail is received
    Agent is Unreachable clear : <SERVER> - Agent Unreachable is cleared
    I have tried the usual
    $> cd $ORACLE_HOME/bin
    $> emctl start agent
    $> emctl status agent
    $> emctl upload agent
    This is successful however shortly the messages re-appear. This is on a pre-production grid control which manages 35+ databases on 25+ Hosts and the smtp errors are filling the mailbox with these messages. FYI - The Hosts causing my headache are from a 2 node RAC hosting several instances including ASM running agent version 10.2.0.4.0
    The network team says they are not seeing any connection drops in their logs.
    Any assistance would be appreciated

    Thanks DBA05 for pointing me to look at the trc and nohup files in there I found a number of errors which I could enter into metalink and subsequently identified the Patch 7031906 which seems to have fix a number of the issues and errors identified.
    Primarily
    Using a 10.2.0.4 Grid Agent to monitor a 10.2.0.4 Database.
    The 10.2.0.4 Agent version is certified to monitor a 10.2.0.4 Database.
    The <AGENT_HOME>/sysman/log/emagent.trc shows that the health_check metric is repeatedly failing for this database :
    2008-06-09 15:21:11,173 Thread-3658 ERROR fetchlets.healthCheck: GIM-00105: file not found
    2008-06-09 15:21:11,174 Thread-3658 ERROR engine: [oracle_database,dbname,health_check] : nmeegd_GetMetricData failed : Instance Health Check initialization failed due to one of the following causes: the owner of the EM agent process is not same as the owner of the Oracle instance processes; the owner of the EM agent process is not part of the dba group; or the database version is not 10g (10.1.0.2) and above.
    Repeated failure while executing this metric can cause the Agent to re-start, as it runs out of file handlers at the OS level.
    - The database is a 64 bit installation but emagent executable is of 32 bit installation though the
    64 bit agent software is installed.
    I also found these worth a check
    - Re-starting the database to create this hc_<SID>.dat file does not help in resolving the Healthcheck Metrics error.
    - The <DATABASE_OH>/dbs/hc_<SID>.dat file has sufficient permissions to be read by the agent
    Mark

  • Agent is unreachable when Power On VM

    Hi,
    When I try to start a VM I always have the error : Agent is unreachable!
    On my VM server:
    service ovs-agent status
    ok! process OVSPolicyServer exists.
    ok! process OVSLogServer exists.
    ok! process OVSMonitorServer exists.
    ok! process OVSAgentServer exists.
    ok! process OVSRemasterServer exists.
    ok! OVSAgentServer is alive.
    What is the problem?
    Thanks

    I have look in th OVS_QUERY.LOG and have this error right after a press the Power On button:
    StackTrace:
    File "/opt/ovs-agent-2.3/OVSXSysInfo.py", line 65, in get_rpm_version
    vr = timeout_command(cmd)
    File "/opt/ovs-agent-2.3/OVSCommons.py", line 71, in timeout_command
    raise Exception('timeout_command() timed out!')
    "2010-02-19 07:33:25" ERROR=> get_agent_version: failed:<Exception: timeout_command() timed out!>
    StackTrace:
    File "/opt/ovs-agent-2.3/OVSXSysInfo.py", line 65, in get_rpm_version
    vr = timeout_command(cmd)
    File "/opt/ovs-agent-2.3/OVSCommons.py", line 71, in timeout_command
    raise Exception('timeout_command() timed out!')

  • Getting agent is unreachable

    Team,
    We are getting the error message often Agent is unreachable in OEM12C. I don't find any clue in the log files.
    Could you please guide me how to handle this issue?
    Thanks,
    Robin

    Hi Robin,
    Can you please give us more details :-
    a) Version of Enterprise Manager you are using.
    b) When do you see agent getting into unreachable state ? Is this after some specific activity ?
    c) Is it possible for you to give us more details one one such agent ? If yes, we can send you the scripts to collect the data.
    Regards
    Rahul

  • Rman jobs "Suspended on Agent Unreachable" through EM

    Hi, all:
    when I schedule an RMAN backup in OEM, It has a
    suspended on agent unreachable status immediately. Deleting the job and creating a new one, and the new job became suspended even before it's first scheduled job
    I can manually backup through rman prompt, no problem.
    The database is RAC 10.2.0.3 on linux*86.
    I checked web found lots of friends had the same problem without solutions, is there anyone has experience to fix it?
    Thanks a lot

    Have you done anything to determine why the agent is unreachable such as checking its status with emctl or reading a log file?

  • Corrective Action on Agent Unreachable?

    Let me first explain exactly what I am looking to do. My current setup is a repeating job that recreates connections (tunnels) to the agent boxes every 15 minutes to ensure that connections stay up. This can get hung up and drag the network down. Ideally, I would like to setup an automated system to correct the issues. If an Agent becomes unreachable, I want to initiate a corrective action that will try to recreate the connection. I was told that the corrective action would be run ON THE AGENT, which would inevitably fail if there was no connection. So a 2nd task would be added to the corrective action in response to the first failed task, that would run the connection scripts on the OEM box and re-establish connection. If that fails as well, then I would like a notification to be sent out (incident rules typically).
    That is my ideal set up. Here are the issues I am running into. The first is that the Agent Unreachable does not seem to be an editable metric. It is listed as a metric called Response > Status, under All Metrics. However, under Metric settings, it can not be edited, and thus, I do not see a way to tie a corrective action to this metric. Once I do tie the corrective action to this metric, do I need to set up a job to run in the corrective action or is the corrective action basically a job that runs in response to an event? That is how I understood it...just looking for verification. It would be greatly appreciated if I could be pointed in the correct direction.

    I'm not sure you can do this through a metric alert corrective action, but it sounds like a great enhancement request. You didn't mention the EM version that you're using, but if you're on EM12c you can implement something like this through an advanced notification method. There's more than one way to do it but here's what I just tested and confirmed will work:
    1) Generate an ssh key for the oracle user running the OMS, and save the key with no password
    2) Copy the generated public key to $HOME/.ssh/authorized_keys for the user running the agent on the host where you would like to restart the agent
    3) Create a shell script owned by the OMS oracle user that contains the line "ssh [email protected] /pathtoagent/bin/emctl start agent"
    4) Log in to EM12c as user SYSMAN and create an advanced notification method that calls the shell script created in step 3
    5) Create an incident ruleset applying to the agent target
    6) Create an rule in the ruleset that applies to incoming incidents where Category = Availability and Severity = Critical
    7) Create an action for that rule that calls the advanced notification method from step 4
    Then stop the agent to test it. Once the incident is generated, the notification method will run, ssh from the OMS host to the agent host, and start up the agent again.
    It doesn't look like you can pass parameters to the notification methods, so you may need to create a separate notification method and separate shell script for every agent you monitor.
    You could probably also do this through an SNMP trap advanced notification if you have other management software on your network that could catch the trap and respond to it appropriately.
    But for me the real question would be: why are your agents going unreachable so often that you need to bother with this?

  • How do I delete a sync agent?

    I am trying to clean up my Azure environment. I have a bunch of Sync Agents that are no longer being utilized, but each time I select one to attempt to delete, I get an error that states "The Sync Agent was not deleted",
    without giving me any specifics.
    Does anyone know how I can go about deleting Sync Agents that are no longer in use?
    Thanks

    Hi,
    1. Local Agent cannot be deleted if its associated on-Premise database is unreachable
    Description/Symptoms : If a local end point (database) that is registered with a local SQL Azure Data Sync
    agent becomes unreachable, the local agent cannot be deleted.
    Cause : The local agent cannot be deleted because the unreachable database is still
    registered with the agent and when you try to delete the agent, the deletion
    process tries to reach the database, which fails. This database cannot be
    unregistered too, because during unregistration process, local agent tries to
    connect to database which cannot be reachable.
    Resolution/Workaround : Create a local database with the same name as the one that cannot be reached,
    unregister this database from local agent, and then proceed to delete the agent.
    2.  Sync Group cannot be deleted within 3 minutes of uninstalling/stopping the agent Description/Symptoms
    You are not able to delete a sync group with in 3 minutes of uninstalling/stopping the associated local SQL Azure Data Sync agent.
    Resolution/Workaround : Remove a sync group with associated sync agents online (strongly recommended).
    If agent is offline but installed, bring it online on the on-premise computer, wait for the status of the agent as online in Azure portal, and then remove the sync group.
    If agent is offline because it was uninstalled, perform the following steps and try deleting the sync group.
    -Remove agent XML file from the SQL Azure Data Sync installation folder if the file exists
    -Install the agent on same/another on-premise machine, submit agent key from portal generated for the agent that’s showing offline
    3. cannot delete my sync group
    Description/Symptoms : You fail in your attempt to delete a sync group.
    Cause/Fix : Any of the following can result in a failure to delete a sync group.
    The agent is offline  : Be sure that the agent is online then try again.
    The Data Sync service is stopped :
    * In the Start menu search on Services
    * Click Services in the Programs section of the search results.
    * Find the SQL Azure Data Sync Preview service.
    * If the service status is Stopped right-click the service name and select Start from the dropdown menu.
    A database is offline : Check your SQL Azure and SQL Server databases to be sure they are all online.
    The sync group is provisioning or synchronizing : Wait until the provisioning or synchronizing process finishes then retry deleting the sync group.
    Hope this helps.
    Regards,
    Shirisha Paderu

  • How to tell EM Repo that an Oracle Agent VM is gone (perm)

    Hi all,
    We have an Oracle Managed Agent on a VM in our plug-in development environment, and that VM is gone (and not coming back up). The OEM Repo now thinks there are still targets deployed.
    I need to undeploy those plug-ins, but can't because the repo says the agent is unreachable.
    Is there a way to 'tell' the EM Repo that the agent is gone, so we can clean up and the repo no longer thinks there is an agent with plug-ins/targets deployed?
    Thanks for any feedback,
    Ed

    Thanks for the responses all!
    By deleting the targets one by one (I used CLI), the "emcli delete_target" command reported it was deleted successfully. However, looking in the EM UI, it was still 'undeploying' from the agent. So it wasn't marked as 'done' in the repo.
    By using the emcli delete_target command with the -delete_monitored_targets option, it removed it without problem.
    Thanks again.
    Ed

  • Agent is unable to communicate withOMS (AgenttoOMS Communication is broken)

    All,
    Last Week , we faced a problem with agent communication with OMS , we couldnt trace out what & why it has happened
    Do we have any Trace logs Either in OS(network) level/ OMS / Agent Level to trace what went wrong & where ?
    Your valuable inputs will be higly appreciated
    - Error Msg : from OMS :
    ~Agent is unable to communicate with the OMS. (REASON = Agent is Unreachable (REASON : Agent to OMS Communication is broken)
    P.S
    At this time Neither OMS nor Agent went Down !
    Thanks
    Edited by: user10407423 on Nov 6, 2008 1:41 AM

    Yes logs are available both at agent and oms.
    For agent, go to <agent_home>/sysman/log
    For OMS, go to OMS_HOME/sysman/log and opmn/logs
    HTH

  • VM Agent cannot be contacted after VM Template Powered on.

    Hi,
    Installed Oracle VM 2.2.
    I have setup Server Pool, registered Oracle EL 5 template and created a virtual machine on the VM Server.
    This all seem to work fine.
    Problem occurs when I start the virtual machine. The Agent cannot be contacted anymore:
         Get Status from Agent Exception:oracle.ovs.biz.controller.exception.UnreachableException: Agent is unreachable!
    Doing a test on agent connection:
    /opt/ovs-agent-2.3/utils/do_rpc.py https://oracle:<passwd>@rrws00102:8899 echo hello
    echo ['hello'] =>
    success:echo=hello
    I can connect to the new virtual machine console and complete the installation.
    I can connect from the virtual machine and the VM Server to other hosts so network config
    seems to be intact.
    I've searched the forum but was unable to find a solution.
    Oracle Support tech notes also did not provide a solution.
    Any idea what is going wrong?
    Thanks
    Roelie Viviers
    Edited by: Roelie Viviers on Mar 30, 2010 2:36 PM
    Edited by: Roelie Viviers on Mar 30, 2010 2:37 PM

    Did you have a look at the file in /var/log/ovs/ or is it /var/log/ovs-agent/ directory ? Any thing strange in there ?

  • Oracle 10g GetMetricData Division by Zero Error

    Windows Server 2000 (SP4)
    Oracle 10gR1 (10.1.0.2.0)
    ASM enabled
    Using advice found:
    http://www.dbazine.com/blogs/blog-cf/chrisfoot/blogentry.2005-09-17.7657940139
    http://www.dbazine.com/blogs/blog-cf/chrisfoot/10goemlessons
    on this forum and other places, I have more or less restored functionality to my 10g EM console. The upload process appears to be working normally and the web interface works for just about everything except the "Home" tab. I also cannot reach the ASM page to perform ASM functions.
    Here are the most recent entries from the emagent.trc file.
    2006-03-22 08:25:54 Thread-3020 WARN upload: FxferSend: received http error in header from repository: http://MYSERVER.MYDOMAIN.lcl:5500/em/upload/
         ERROR-400|ORA-20206: Target does not exist: Agent does not exist for http://MYSERVER.MYDOMAIN.LCL:1830/emd/main
         ORA-06512: at "SYSMAN.EMD_LOADER", line 1662
    ORA-06512: at line 1
    2006-03-22 08:25:54 Thread-3020 ERROR upload: Failed to upload file A0000001.xml, ret = -2
    2006-03-22 08:25:54 Thread-3020 ERROR upload: 3 Failures in a row for A0000001.xml, we give up
    2006-03-22 08:25:54 Thread-3020 ERROR upload: Error in uploadXMLFiles. Trying again in 300.00 seconds.
    2006-03-22 08:26:13 Thread-3528 WARN http: 392,-1: nmehl_httpListener: signaled to exit from emctl
    == Restarted ===
    2006-03-22 08:30:17 Thread-3376 WARN command: Job Subsystem Timeout set at 600 seconds
    2006-03-22 08:30:17 Thread-3376 WARN upload: Upload manager has no Failure script: disabled
    2006-03-22 08:30:17 Thread-3376 WARN upload: Recovering left over xml files in upload directory
    2006-03-22 08:30:17 Thread-3376 WARN upload: Recovered 0 left over xml files in upload directory
    2006-03-22 08:30:17 Thread-3376 WARN metadata: Metric collectSnapshot does not have any data columns
    2006-03-22 08:30:23 Thread-3376 WARN TargetManager: Regenerating all Metadata
    2006-03-22 08:30:24 Thread-3376 ERROR util.files: ERROR: nmeufis_new: failed in lfiopn on file: E:\oracle\product\10.1.0\db_1\MYSERVER.MYDOMAIN.lcl_SID\sysman\emd\agntstmp.txt. error = 2 (No such file or directory)
    2006-03-22 08:30:24 Thread-3376 WARN collector: the column name tabscanall_ps in this condition does not exist
    2006-03-22 08:30:24 Thread-3376 WARN collector: the column name tabscanall_pt in this condition does not exist
    2006-03-22 08:30:24 Thread-3376 ERROR recvlets: Inserted target oracle_database SID.pcs.url.com into hash table
    2006-03-22 08:30:56 Thread-3816 ERROR util.files: nmeufile_getLength: Error in lfilen. Error = 2 (No such file or directory)
    2006-03-22 08:32:20 Thread-3416 ERROR fetchlets.oslinetok: Process stderr = Illegal division by zero at E:\oracle\product\10.1.0\db_1\sysman\admin\scripts/semd_common.pl line 144.
    2006-03-22 08:32:20 Thread-3416 ERROR engine: [oracle_database,SID.pcs.url.com,dumpFull] : nmeegd_GetMetricData failed : Illegal division by zero at E:\oracle\product\10.1.0\db_1\sysman\admin\scripts/semd_common.pl line 144.
    2006-03-22 08:32:24 Thread-3416 ERROR fetchlets.oslinetok: Process stderr = Illegal division by zero at E:\oracle\product\10.1.0\db_1\sysman\admin\scripts/semd_common.pl line 144, <STDIN> line 2.
    2006-03-22 08:32:24 Thread-3416 ERROR engine: [oracle_database,SID.pcs.url.com,archFull] : nmeegd_GetMetricData failed : Illegal division by zero at E:\oracle\product\10.1.0\db_1\sysman\admin\scripts/semd_common.pl line 144, <STDIN> line 2.
    2006-03-22 08:47:20 Thread-3476 ERROR fetchlets.oslinetok: Process stderr = Illegal division by zero at E:\oracle\product\10.1.0\db_1\sysman\admin\scripts/semd_common.pl line 144.
    2006-03-22 08:47:20 Thread-3476 ERROR engine: [oracle_database,SID.pcs.url.com,dumpFull] : nmeegd_GetMetricData failed : Illegal division by zero at E:\oracle\product\10.1.0\db_1\sysman\admin\scripts/semd_common.pl line 144.
    2006-03-22 08:47:23 Thread-3476 ERROR fetchlets.oslinetok: Process stderr = Illegal division by zero at E:\oracle\product\10.1.0\db_1\sysman\admin\scripts/semd_common.pl line 144, <STDIN> line 2.
    2006-03-22 08:47:23 Thread-3476 ERROR engine: [oracle_database,SID.pcs.url.com,archFull] : nmeegd_GetMetricData failed : Illegal division by zero at E:\oracle\product\10.1.0\db_1\sysman\admin\scripts/semd_common.pl line 144, <STDIN> line 2.
    And here are the entries from the emoms.log file.
    2006-03-22 08:28:55,562 [Orion Launcher] ERROR app.ContextInitializer contextInitialized.256 - Integration Class not found: oracle.sysman.ias.ias.IASIntegration
    2006-03-22 08:28:56,000 [Orion Launcher] ERROR app.ContextInitializer contextInitialized.256 - Integration Class not found: oracle.sysman.eml.target.slb.common.SLBIntegration
    2006-03-22 08:28:56,187 [Orion Launcher] ERROR app.ContextInitializer contextInitialized.256 - Integration Class not found: oracle.sysman.eml.ssl.intg.SSLIntegration
    2006-03-22 08:28:56,343 [Orion Launcher] ERROR app.ContextInitializer contextInitialized.256 - Integration Class not found: oracle.tip.oem.central.domain.ProcessConnectDomainIntg
    2006-03-22 08:28:56,343 [Orion Launcher] ERROR app.ContextInitializer contextInitialized.256 - Integration Class not found: oracle.tip.oem.central.instance.ProcessConnectInstanceIntg
    2006-03-22 08:28:56,359 [Orion Launcher] ERROR app.ContextInitializer contextInitialized.256 - Integration Class not found: oracle.webdb.admin.em.PortalIntegration
    2006-03-22 08:28:56,359 [Orion Launcher] ERROR app.ContextInitializer contextInitialized.256 - Integration Class not found: oracle.webdb.admin.em.SSOIntegration
    2006-03-22 08:28:56,375 [Orion Launcher] ERROR app.ContextInitializer contextInitialized.256 - Integration Class not found: oracle.reports.em.RepIntg
    2006-03-22 08:28:56,375 [Orion Launcher] ERROR app.ContextInitializer contextInitialized.256 - Integration Class not found: oracle.sysman.ocs.mntr.target.OcsEmailIntegration
    2006-03-22 08:28:56,375 [Orion Launcher] ERROR app.ContextInitializer contextInitialized.256 - Integration Class not found: oracle.sysman.ocs.mntr.target.OcsOidIntegration
    2006-03-22 08:28:56,390 [Orion Launcher] ERROR app.ContextInitializer contextInitialized.256 - Integration Class not found: oracle.sysman.ocs.mntr.target.OcsOvfIntegration
    2006-03-22 08:28:56,390 [Orion Launcher] ERROR app.ContextInitializer contextInitialized.256 - Integration Class not found: oracle.sysman.ocs.mntr.target.OcsWebconfIntegration
    2006-03-22 08:28:56,406 [Orion Launcher] ERROR app.ContextInitializer contextInitialized.256 - Integration Class not found: oracle.sysman.ocs.mntr.target.OcsWirelessIntg
    2006-03-22 08:28:56,406 [Orion Launcher] ERROR app.ContextInitializer contextInitialized.256 - Integration Class not found: oracle.sysman.ocs.mntr.target.OcsCalGrpIntegration
    2006-03-22 08:31:28,171 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.476 - Number of HB error responses received = 1
    2006-03-22 08:31:28,218 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.485 - ERROR 0 EMD_URL = http://MYSERVER.MYDOMAIN.lcl:1830/emd/main CODE = 0 MSG = ORA-01403: no data found
    2006-03-22 08:32:28,218 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.476 - Number of HB error responses received = 1
    2006-03-22 08:32:28,218 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.485 - ERROR 0 EMD_URL = http://MYSERVER.MYDOMAIN.lcl:1830/emd/main CODE = 0 MSG = ORA-01403: no data found
    2006-03-22 08:33:28,218 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.476 - Number of HB error responses received = 1
    2006-03-22 08:33:28,218 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.485 - ERROR 0 EMD_URL = http://MYSERVER.MYDOMAIN.lcl:1830/emd/main CODE = 0 MSG = ORA-01403: no data found
    2006-03-22 08:34:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.476 - Number of HB error responses received = 1
    2006-03-22 08:34:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.485 - ERROR 0 EMD_URL = http://MYSERVER.MYDOMAIN.lcl:1830/emd/main CODE = 0 MSG = ORA-01403: no data found
    2006-03-22 08:35:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.476 - Number of HB error responses received = 1
    2006-03-22 08:35:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.485 - ERROR 0 EMD_URL = http://MYSERVER.MYDOMAIN.lcl:1830/emd/main CODE = 0 MSG = ORA-01403: no data found
    2006-03-22 08:36:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.476 - Number of HB error responses received = 1
    2006-03-22 08:36:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.485 - ERROR 0 EMD_URL = http://MYSERVER.MYDOMAIN.lcl:1830/emd/main CODE = 0 MSG = ORA-01403: no data found
    2006-03-22 08:37:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.476 - Number of HB error responses received = 1
    2006-03-22 08:37:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.485 - ERROR 0 EMD_URL = http://MYSERVER.MYDOMAIN.lcl:1830/emd/main CODE = 0 MSG = ORA-01403: no data found
    2006-03-22 08:38:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.476 - Number of HB error responses received = 1
    2006-03-22 08:38:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.485 - ERROR 0 EMD_URL = http://MYSERVER.MYDOMAIN.lcl:1830/emd/main CODE = 0 MSG = ORA-01403: no data found
    2006-03-22 08:39:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.476 - Number of HB error responses received = 1
    2006-03-22 08:39:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.485 - ERROR 0 EMD_URL = http://MYSERVER.MYDOMAIN.lcl:1830/emd/main CODE = 0 MSG = ORA-01403: no data found
    2006-03-22 08:40:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.476 - Number of HB error responses received = 1
    2006-03-22 08:40:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.485 - ERROR 0 EMD_URL = http://MYSERVER.MYDOMAIN.lcl:1830/emd/main CODE = 0 MSG = ORA-01403: no data found
    2006-03-22 08:41:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.476 - Number of HB error responses received = 1
    2006-03-22 08:41:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.485 - ERROR 0 EMD_URL = http://MYSERVER.MYDOMAIN.lcl:1830/emd/main CODE = 0 MSG = ORA-01403: no data found
    2006-03-22 08:42:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.476 - Number of HB error responses received = 1
    2006-03-22 08:42:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.485 - ERROR 0 EMD_URL = http://MYSERVER.MYDOMAIN.lcl:1830/emd/main CODE = 0 MSG = ORA-01403: no data found
    2006-03-22 08:43:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.476 - Number of HB error responses received = 1
    2006-03-22 08:43:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.485 - ERROR 0 EMD_URL = http://MYSERVER.MYDOMAIN.lcl:1830/emd/main CODE = 0 MSG = ORA-01403: no data found
    2006-03-22 08:44:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.476 - Number of HB error responses received = 1
    2006-03-22 08:44:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.485 - ERROR 0 EMD_URL = http://MYSERVER.MYDOMAIN.lcl:1830/emd/main CODE = 0 MSG = ORA-01403: no data found
    2006-03-22 08:45:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.476 - Number of HB error responses received = 1
    2006-03-22 08:45:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.485 - ERROR 0 EMD_URL = http://MYSERVER.MYDOMAIN.lcl:1830/emd/main CODE = 0 MSG = ORA-01403: no data found
    2006-03-22 08:46:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.476 - Number of HB error responses received = 1
    2006-03-22 08:46:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.485 - ERROR 0 EMD_URL = http://MYSERVER.MYDOMAIN.lcl:1830/emd/main CODE = 0 MSG = ORA-01403: no data found
    2006-03-22 08:47:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.476 - Number of HB error responses received = 1
    2006-03-22 08:47:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.485 - ERROR 0 EMD_URL = http://MYSERVER.MYDOMAIN.lcl:1830/emd/main CODE = 0 MSG = ORA-01403: no data found
    2006-03-22 08:48:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.476 - Number of HB error responses received = 1
    2006-03-22 08:48:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.485 - ERROR 0 EMD_URL = http://MYSERVER.MYDOMAIN.lcl:1830/emd/main CODE = 0 MSG = ORA-01403: no data found
    2006-03-22 08:49:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.476 - Number of HB error responses received = 1
    2006-03-22 08:49:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.485 - ERROR 0 EMD_URL = http://MYSERVER.MYDOMAIN.lcl:1830/emd/main CODE = 0 MSG = ORA-01403: no data found
    2006-03-22 08:50:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.476 - Number of HB error responses received = 1
    2006-03-22 08:50:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.485 - ERROR 0 EMD_URL = http://MYSERVER.MYDOMAIN.lcl:1830/emd/main CODE = 0 MSG = ORA-01403: no data found
    2006-03-22 08:51:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.476 - Number of HB error responses received = 1
    2006-03-22 08:51:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.485 - ERROR 0 EMD_URL = http://MYSERVER.MYDOMAIN.lcl:1830/emd/main CODE = 0 MSG = ORA-01403: no data found
    2006-03-22 08:52:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.476 - Number of HB error responses received = 1
    2006-03-22 08:52:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.485 - ERROR 0 EMD_URL = http://MYSERVER.MYDOMAIN.lcl:1830/emd/main CODE = 0 MSG = ORA-01403: no data found
    2006-03-22 08:53:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.476 - Number of HB error responses received = 1
    2006-03-22 08:53:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.485 - ERROR 0 EMD_URL = http://MYSERVER.MYDOMAIN.lcl:1830/emd/main CODE = 0 MSG = ORA-01403: no data found
    2006-03-22 08:54:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.476 - Number of HB error responses received = 1
    2006-03-22 08:54:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.485 - ERROR 0 EMD_URL = http://MYSERVER.MYDOMAIN.lcl:1830/emd/main CODE = 0 MSG = ORA-01403: no data found
    2006-03-22 08:55:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.476 - Number of HB error responses received = 1
    2006-03-22 08:55:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.485 - ERROR 0 EMD_URL = http://MYSERVER.MYDOMAIN.lcl:1830/emd/main CODE = 0 MSG = ORA-01403: no data found
    2006-03-22 08:56:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.476 - Number of HB error responses received = 1
    2006-03-22 08:56:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.485 - ERROR 0 EMD_URL = http://MYSERVER.MYDOMAIN.lcl:1830/emd/main CODE = 0 MSG = ORA-01403: no data found
    2006-03-22 08:57:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.476 - Number of HB error responses received = 1
    2006-03-22 08:57:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.485 - ERROR 0 EMD_URL = http://MYSERVER.MYDOMAIN.lcl:1830/emd/main CODE = 0 MSG = ORA-01403: no data found
    2006-03-22 08:58:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.476 - Number of HB error responses received = 1
    2006-03-22 08:58:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.485 - ERROR 0 EMD_URL = http://MYSERVER.MYDOMAIN.lcl:1830/emd/main CODE = 0 MSG = ORA-01403: no data found
    2006-03-22 08:59:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.476 - Number of HB error responses received = 1
    2006-03-22 08:59:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.485 - ERROR 0 EMD_URL = http://MYSERVER.MYDOMAIN.lcl:1830/emd/main CODE = 0 MSG = ORA-01403: no data found
    2006-03-22 09:00:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.476 - Number of HB error responses received = 1
    2006-03-22 09:00:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.485 - ERROR 0 EMD_URL = http://MYSERVER.MYDOMAIN.lcl:1830/emd/main CODE = 0 MSG = ORA-01403: no data found
    2006-03-22 09:01:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.476 - Number of HB error responses received = 1
    2006-03-22 09:01:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.485 - ERROR 0 EMD_URL = http://MYSERVER.MYDOMAIN.lcl:1830/emd/main CODE = 0 MSG = ORA-01403: no data found
    2006-03-22 09:02:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.476 - Number of HB error responses received = 1
    2006-03-22 09:02:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.485 - ERROR 0 EMD_URL = http://MYSERVER.MYDOMAIN.lcl:1830/emd/main CODE = 0 MSG = ORA-01403: no data found
    2006-03-22 09:03:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.476 - Number of HB error responses received = 1
    2006-03-22 09:03:28,281 [PingHeartBeatRecorder] ERROR emdrep.pingHBRecorder updateEMDListHeartBeat.485 - ERROR 0 EMD_URL = http://MYSERVER.MYDOMAIN.lcl:1830/emd/main CODE = 0 MSG = ORA-01403: no data found
    Here is the status from the sysman.emd_ping table:
    Agent is Unreachable (REASON = Connection refused: connect). Host is unreachable (REASON = Internal Error pinging the host for EMD_URL http://MYSERVER.MYDOMAIN.lcl:1830/emd/main.CreateProcess: /usr/sbin/ping MYSERVER.MYDOMAIN.lcl error=3)
    Finally, from the SYSMAN.MGMT_TARGETS table, I see the following statuses for the various target types
    Target_type; Last_load_time
    oracle_emrep; 22-MAR-06
    oracle_emd; 22-MAR-06
    host; 13-OCT-04
    oracle_database; 13-OCT-04
    oracle_listener; 13-OCT-04
    osm_instance; 13-OCT-04
    Any thoughts or additional suggestions?? I have been working on getting the EM console back up and fully functional for several days. I am more of a 9i type, not 10g.
    Yes, it's been 18 months since this last worked; what can I say? I inherited this server from a vendor.
    Regards,
    hmscott
    Does anyone have

    A couple of updates:
    1. I found a perl script file in the sysman\admin\scripts folder called semd_common.pl. I found the line number referenced in the log file. Apparently, the $total variable (representing disk space, I think) is not set properly. When I hard coded it to a fixed value and restarted the dbConsole, I stopped getting the division by zero error.
    Not a good solution, but maybe a step sideways. I'd like to remove my edit, but one thing at a time.
    2. I found another error message in the OracleDBConsoleSIDwebsrvc.log file:
    03/22/06 14:44:23 Received exitCode 1 from emctl istatus
    Googling this particular message did not reveal a whole lot to me.
    Any more ideas? Anyone?
    Regards,
    hmscott

  • Certified Targets for OEM 10.2 releases

    I have few questions on the certified targets for OEM 10.2.0.4
    What versions of Oracle Databases can be monitored using the EM 10.2.0.4?
    Also are there any drawbacks in monitoring the older versions of oracle viz 9.2 or 9i rel 1 version databases ?
    Can we monitor 11g databases with the 10.2.0.4 EM environment?
    Also, We have been getting Alerts from the Grid Setup when we have the Agent 10.2* running to monitor 9.2* release database
    Message=Agent is Unreachable (REASON = Connection refused). Host is unreachable (REASON = Timed out pinging the host for EMD
    Do you know what could be the reason for this Alert when i see everything is up and running..
    Let me know if you'l had similar problems/Bugs or fixes applied to remediate this problem
    Thanks

    1. For certification See Note 412431.1 Oracle Enterprise Manager 10g Grid Control Checker.
    2. For the alerts it seems that sometimes OMS unable to ping the agent box to get the availability of the Agent/host,
    OMS monitors by verifying agent over HTTP and host over ICMP.
    BR,
    MettoMorphism

  • Unable to create Server Pool

    Hi,
    I am new to setting up Oracle Virtualisation and am still trying to grasp some concepts so please bear with me. While trying to set up the Oracle VM Server as well as the Oracle VM Manager for virtualization (through the use of pre-built Oracle E-Business templates), we encountered issues with the network (which has since been resolved) and primarily with setting up the server pool to an Active status.
    The Virtual machine status displays an error when the VM is powered on. Looking at the Virtual Machine log in VM Manager, the error 'Agent is unreachable' is displayed.
    Furthermore, when trying to create the server pool (or even test the connection), the error, 'please check the IP and Oracle VM agent password' is displayed. The command services ovs-agent configure and service ovs-agent restart was used to change the password but the error still persists.
    Find in the below additional details relating to our network and server configuration:
    OVM Host (physical server containing OVM Server)
    IP Address: 10.204.97.132 (static)
    Subnet Host: 255.255.255.128
    Gateway: 10.204.97.129
    OVM Server
    IP Address: 10.204.97.131 (static)
    Subnet Host: 255.255.255.128
    Gateway: 10.204.97.129
    Client (local machine)
    IP Address: 10.204.97.134 (static)
    Subnet Host: 255.255.255.128
    Gateway: 10.204.97.129
    Access to OVM Manager: https://10.204.97.131:4443/OVS
    Access through VNCViewer: 10.204.97.132
    Any suggestions will be much appreciated. Let us know if you need further information.
    Thanks.
    Martin

    user7644580 wrote:
    Furthermore, when trying to create the server pool (or even test the connection), the error, 'please check the IP and Oracle VM agent password' is displayed. The command services ovs-agent configure and service ovs-agent restart was used to change the password but the error still persists.Interestingly, you managed to create the Server Pool originally, which means that it could at least reach the ovs-agent correctly for that purpose. I'd firstly recommend looking at /etc/hosts for all your machines to ensure that the hostname is mapped to the real IP address (and not 127.0.0.1) and that name resolution across all the machines is working correctly. Also, make sure you can telnet to port 8899 on the Oracle VM Server from your Oracle VM Manager both by IP address and hostname.

Maybe you are looking for