Rman jobs "Suspended on Agent Unreachable"

I don't know if this problem is coming from rman, EM, or jobs. The only time it occurs is when I create an "Oracle Recommended" backup job thorugh EM.
The job status is immediately suspended with the message "agent unreachable."
Other RMAN functions that run in jobs scheduled through EM work fine (crosscheck for example). It only happens with I schedule backups through the Oracle Recommended link in EM.
In the meantime, I'm running backups manually at the RMAN prompt.
There's hardly any literature on Metalink or on the forums about this. Can anyone shed some light?

I just ran across this thread when I was looking for a solution for the same issue ("Suspended on Agent Unreachable") hat had just happened to me. In my case, it was on RAC. I got that error when I created custom job and submitted it against cluster. The backup went OK, however, when I picked up one node, and submitted the same custom backup job from the specific node.

Similar Messages

  • 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?

  • Rman backup job Suspended on Agent Unreachable

    Hi,
    I have Oracle 10.2.0 installed on windows 2003 server. i configure oracle suggested rman backup which works fine till now. but now it shows
    Suspended on Agent Unreachable message and backup doesn't happen.
    if check like
    C:\Documents and Settings\Administrator>emctl status agen
    Oracle Enterprise Manager 10g Database Control Release 10
    Copyright (c) 1996, 2005 Oracle Corporation.  All rights
    Agent is Not Running
    C:\Documents and Settings\Administrator>emctl start agent
    Oracle Enterprise Manager 10g Database Control Release 10
    Copyright (c) 1996, 2005 Oracle Corporation.  All rights
    These Windows services are started:
       Application Experience Lookup Service
       Application Management
       Automatic Updates
       COM+ Event System
       COM+ System Application
       Computer Browser
       Cryptographic Services
       DCOM Server Process Launcher
       DefWatch
       Distributed File System
       Distributed Transaction Coordinator
       DNS Client
       DNS Server
       Error Reporting Service
       Event Log
       File Replication Service
       FTP Publishing Service
       HTTP SSL
       IIS Admin Service
       Indexing Service
       Intel PDS
       Intersite Messaging
       IPSEC Services
       Kerberos Key Distribution Center
       Logical Disk Manager
       LogMeIn
       LogMeIn Maintenance Service
       Net Logon
       Network Connections
       Network Location Awareness (NLA)
       NT LM Security Support Provider
       OracleDBConsoleneo
       OracleOraDb10g_home1iSQL*Plus
       OracleOraDb10g_home1TNSListener
       OracleServiceNEO
       Plug and Play
       Print Spooler
       Protected Storage
       Remote Access Connection Manager
       Remote Procedure Call (RPC)
       Remote Registry
       Secondary Logon
       Security Accounts Manager
       Server
       Shell Hardware Detection
       SQL Server (MSSQLSERVER)
       SQL Server Agent (MSSQLSERVER)
       SQL Server Analysis Services (MSSQLSERVER)
       SQL Server FullText Search (MSSQLSERVER)
       SQL Server Integration Services
       SQL Server Reporting Services (MSSQLSERVER)
       Symantec AntiVirus Server
       System Event Notification
       Task Scheduler
       TCP/IP NetBIOS Helper
       Telephony
       Terminal Services
       Windows Management Instrumentation
       Windows Search
       Windows Time
       Workstation
       World Wide Web Publishing Service
    The command completed successfully.means my agent was stop but now i start it.
    i find on Google that this type of error happen when you change in database like ip address, sid etc but i haven't do any change.
    i am facing same problem so many times.
    Now how to reschedule the existing backup job so that it starts work again.
    thanks
    umesh

    thanks for reply
    i do it.
    C:\Documents and Settings\Administrator>emctl status dbconsole
    Oracle Enterprise Manager 10g Database Control Release 10.2.0.1.0
    Copyright (c) 1996, 2005 Oracle Corporation.  All rights reserved.
    http://Techwave:5500/em/console/aboutApplication
    EM Daemon is not running.
    Logs are generated in directory C:\oracle\product\10.2.0\db_1/Techwave_neo/sysman/log
    C:\Documents and Settings\Administrator>emctl stop dbconsole
    Oracle Enterprise Manager 10g Database Control Release 10.2.0.1.0
    Copyright (c) 1996, 2005 Oracle Corporation.  All rights reserved.
    http://Techwave:5500/em/console/aboutApplication
    The OracleDBConsoleneo service is stopping.....
    The OracleDBConsoleneo service was stopped successfully.
    C:\Documents and Settings\Administrator>emctl start dbconsole
    Oracle Enterprise Manager 10g Database Control Release 10.2.0.1.0
    Copyright (c) 1996, 2005 Oracle Corporation.  All rights reserved.
    http://Techwave:5500/em/console/aboutApplication
    Starting Oracle Enterprise Manager 10g Database Control ...The OracleDBConsoleneo service is starting................
    The OracleDBConsoleneo service was started successfully.now it is working fine.
    now issue is how i reschedule my suspended job.
    i got this error.
    Edit is not supported for this job type, only general information about the job can be updated No scheduled executions - this job can not be modified.

  • Oracle Management Console 10g - Job Status - Suspended on Agent Unreachable

    Recently we updated our RDMS from 10.2.0.1 to 10.2.0.4.0 PATCH 25.
    Ever since we upgraded, we have had trouble with our RMAN backups. Now when a scheduled backup begins it never ends. Now whenever we schedule a job, from a backup to any simple system command, the status immediately returns "Suspended on Agent Unreachable".
    We can start and stop the dbconsole successfully, and I can use the OEM to monitor the database, and make changes to that. However, I cannot run any scheduled database jobs through the OEM. However, I can run the rman jobs via the command line.
    The database server, and the OEM console is on the save server. I am not running RAC. Everything database related is on this one server.
    Here are the results for emctl status agent:
    E:\oracle\product\10.2.0\db_1\BIN>emctl status agent
    Oracle Enterprise Manager 10g Database Control Release 10.2.0.4.0
    Copyright (c) 1996, 2007 Oracle Corporation.  All rights reserved.
    Agent Version     : 10.1.0.6.0
    OMS Version       : 10.1.0.6.0
    Protocol Version  : 10.1.0.2.0
    Agent Home        : E:\oracle\product\10.2.0\db_1\content.mydomain.com_ORCL
    Agent binaries    : E:\oracle\product\10.2.0\db_1
    Agent Process ID  : 34372
    Agent URL         : http://content.mydomain.com:3938/emd/main
    Started at        : 2010-01-11 14:58:24
    Started by user   : SYSTEM
    Last Reload       : 2010-01-11 14:58:24
    Last successful upload                       : (none)
    Last attempted upload                        : (none)
    Total Megabytes of XML files uploaded so far :     0.00
    Number of XML files pending upload           :     5016
    Size of XML files pending upload(MB)         :    42.77
    Available disk space on upload filesystem    :    37.94%
    Agent is Running and ReadyHere are the results for emctl status agent:
    E:\oracle\product\10.2.0\db_1\BIN>emctl upload
    Oracle Enterprise Manager 10g Database Control Release 10.2.0.4.0
    Copyright (c) 1996, 2007 Oracle Corporation.  All rights reserved.
    EMD upload error: uploadXMLFiles skipped :: OMS version not checked yet..I think the EMD upload error may be the problem, but I'm unsure how to resolve this.
    What do I need to do in order to resolve this issue?
    If any more info would be useful, please let me know and I will post it immediately.
    thanks.

    Rondeyli,
    Thanks, that was it. I followed your instructions, and was able to get the system to work. I had to alter the commands a bit to get them to work on my system, so here is what I did.
    I performed the following steps:
    1. Ran the following command:
            emctl stop dbconsole
    2. deleted all files in $AGENT_HOME/sysman/emd/upload and $AGENT_HOME/sysman/emd/state
    3. Ran the following command:
           emctl clearstate dbconsole
    4. Ran the following command:
           emctl secure dbconsole
    5. Ran the following command:
           emctl start dbconsoleThis got everything running for me.
    thanks.

  • OEM 10g - Job Status - Suspended on Agent Unreachable

    Hi,
    I have checked out a few post on this forum which is similar to my problem.
    But could not get the exact workaround.
    The scheduled backup is not getting failed / successful since 29th January 2010.
    We have not made any changes on the database level. But there was a patching activity at application level.
    and as soon as I try to schedule a backup it shows the same status "suspended on agent unreachable"
    I have checked the emctl status and dbconsole status.
    E:\oracle\product\10.2.0\db_1\BIN>emctl status agent
    Oracle Enterprise Manager 10g Database Control Release 10.2.0.4.0
    Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
    Agent Version : 10.1.0.6.0
    OMS Version : 10.1.0.6.0
    Protocol Version : 10.1.0.2.0
    Agent Home : e:\oracle\product\10.2.0\db_1\content.mydomain.de_aeb
    Agent binaries : e:\oracle\product\10.2.0\db_1
    Agent Process ID : 6104
    Agent URL : http://content.mydomain.de:3938/emd/main
    Started at : 2010-02-01 21:55:19
    Started by user : SYSTEM
    Last Reload : 2010-02-01 21:55:19
    Last successful upload : 2010-02-17 06:12:10
    Last attempted upload : 2010-02-17 06:12:25
    Total Megabytes of XML files uploaded so far : 323.40
    Number of XML files pending upload : 1
    Size of XML files pending upload(MB) : 0.01
    Available disk space on upload filesystem : 9.36%
    Agent is Running and Ready
    E:\oracle\product\10.2.0\db_1\BIN>emctl status dbconsole
    Oracle Enterprise Manager 10g Database Control Release 10.2.0.4.0
    Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
    http://content.mydomain.de:1158/em/console/aboutApplication
    Oracle Enterprise Manager 10g is running.
    Logs are generated in directory e:\oracle\product\10.2.0\db_1/scontent.mydomain.de_AEB/sysman/log
    Upload also seems to be working fine.
    E:\oracle\product\10.2.0\db_1\BIN>emctl upload
    Oracle Enterprise Manager 10g Database Control Release 10.2.0.4.0
    Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
    EMD upload completed successfully
    What should I do ? Will restarting the agent help ? Will restarting the agent have any adverse effect on DB ?
    Any help would be a great help.
    Rushabh

    Hi,
    This is urgent.. Please help..
    I am not able to start the emctl...
    Below is the error that I am getting..
    E:\oracle\product\10.2.0\db_1\BIN>emctl stop agent
    Oracle Enterprise Manager 10g Database Control Release 10.2.0.4.0
    Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
    This will stop the Oracle Enterprise Manager 10g Database Control process. Conti
    nue [y/n] :y
    The OracleDBConsoleaeb service is stopping..........
    The OracleDBConsoleaeb service was stopped successfully.
    E:\oracle\product\10.2.0\db_1\BIN>emctl clearstate agent
    Oracle Enterprise Manager 10g Database Control Release 10.2.0.4.0
    Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
    EMD clearstate completed successfully
    E:\oracle\product\10.2.0\db_1\BIN>emctl secure agent
    Oracle Enterprise Manager 10g Database Control Release 10.2.0.4.0
    Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
    Enter Agent Registration password :
    Agent is already stopped... Done.
    Securing agent... Started.
    Requesting an HTTPS Upload URL from the OMS... Failed.
    The OMS is not set up for Enterprise Manager Security.
    E:\oracle\product\10.2.0\db_1\BIN>emctl start agent
    Oracle Enterprise Manager 10g Database Control Release 10.2.0.4.0
    Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
    The service name is invalid.
    More help is available by typing NET HELPMSG 2185.
    When I try to secure agent it is asking for a password, but it is already saved I think..
    When I press enter it is showing the above error.
    What should I do now ?
    Regards,
    Rushabh
    Edited by: user650383 on Feb 16, 2010 10:44 PM

  • Backup Suspended on Agent Unreachable - 11GR2 Windows

    Hi as the title suggests an RMAN backup has gone into a state of Suspended on Agent Unreachable.
    I have a 2 node RAC and have run emctl status dbconsole on each node. On node 1 I get a message: EM Daemon is running. On node 2 I get a message: Oracle enterprise Manager 11g is running.
    Why are these messages different? and could this be the reason why the job has gone into the state it has?
    Thanks in advance

    I strongly suggest to not using RMAN via OEM, but with the good old command line.
    The messages are different because on one node there is the real web app (oc4j...) while on the other one there is only the agent running so it is expected.
    Alessio

  • Suspended on agent unreachable

    Oracle 10.2.0.3.0
    From Enterprise Manager, I am attempting to Create Backup. After I create the job, I receive "Suspended on agent unreachable".
    When I run emctl status agent, it says, "Agent is running and ready."
    Short of deleting the agent and reinstalling it, is there anything else I can do to fix the problem?
    If I need to reinstall the agent, is there a location other than Metalink that I can download the software? My service identifier has expired and I'm not sure when I'll be able to get a new one.
    Thank You.

    have you tried the following:
    1. Stop the agent
    emctl stop agent
    2.remove some files on emd
    cd $ORACLE_HOME/sysman/emd
    rm agntstmp.txt
    rm lastupld.txt
    rm blackouts.xml
    rm -r upload/*
    rm -r state/*
    rm -r collection/*
    3. clear the agent and start it again.
    emctl clearstate agent (this should delete all state files but sometimes it is not enough, but I experienced that it is better to use this command after deletion of the files)
    emctl secure agent (optional depends if you using secure agent or not)
    emctl start agent
    Edited by: user480489 on Jan 5, 2011 3:32 PM

  • Suspended on agent

    Hello
    I have got rac system and when i try to schedule a backup at enterprise manager ,status of backup job change to "Suspended on Agent Unreachable".
    I check agent and dbconsole on both system it is working. And also agent page at enterprise manager it seems okey too.What can i do to fix this problem?

    [oracle@name ~]$ emctl status agent
    Oracle Enterprise Manager 11g Database Control Release 11.1.0.7.0
    Copyright (c) 1996, 2008 Oracle Corporation. All rights reserved.
    Agent Version : 10.2.0.4.0
    OMS Version : 10.2.0.4.0
    Protocol Version : 10.2.0.4.0
    Agent Home : /u01/app/oracle/product/11.2.0/db/name1
    Agent binaries : /u01/app/oracle/product/11.2.0/db
    Agent Process ID : 30000
    Parent Process ID : 29934
    Agent URL : https://name1:3938/emd/main
    Repository URL : https://name1:1158/em/upload/
    Started at : 2010-07-12 12:57:53
    Started by user : oracle
    Last Reload : 2010-07-12 12:57:53
    Last successful upload : (none)
    Last attempted upload : (none)
    Total Megabytes of XML files uploaded so far : 0.00
    Number of XML files pending upload : 0
    Size of XML files pending upload(MB) : 0.00
    Available disk space on upload filesystem : Unknown
    Data channel upload directory : /u01/app/oracle/product/11.2.0/db/name1/sysman/recv
    Last successful heartbeat to OMS : 2010-07-12 15:02:37
    Agent is Running and Ready
    Edited by: user12879921 on 12.Tem.2010 05:02
    Edited by: user12879921 on 12.Tem.2010 05:13

  • CloudControl 12c shows "Agent Unreachable" for Cluster Database

    Hello ,
    when clicking on "Targets -> Databases" our RAC database shows up as follows:
    Name Type Status
    PROD02 Cluster Database symbol for "Agent Unreachable"
    PROD021 Database Instance symbol "green arrow" for "Up"
    PROD022 Database Instance symbol "green arrow" for "Up"
    I don't understand why the symbol for the Cluster Database is not a green arrow, too. The agent on each node is up and running - and when either clicking on "PROD02" or "PROD021" (or PROD022) Cloud Control offers the full functionality. Therefore the status "Agent Unreachable" is missleading (from my point of view). I don't want to remove the complete Cluster Database and discover it once again - several jobs have already been defined and I don't want to do that once again.
    Did anybody else experience the same behaviour?
    Any help will get appreciated...
    Rgds
    JH

    ... seems like if I'm hitting bug "BUG 13865299".
    => "12c Cluster database or Cluster ASM in Pending or "Agent unreachable" for undetermined time [ID 1463196.1]"

  • DB console Agent Unreachable in Windows 2003 server

    Hi All,
    I am facing a problem with one of the production database's DB console. Database verison is 10.1.0.5.0.
    Once I logged in to the DB console I am noticing a status message saying Agent Unreachable.
    I am not getting any updated report about the database.
    I have done restart of DB OracleDB console<DB name> services. But no luck.
    Kindly help me in resolving this issue ASAP.
    regarrdsl.
    Aruna

    Hi,
    Please find the following last 100 lines taken from DB console log file
    -------------- [OracleDBConsoleTC08PRD] ------------
    EMDROOT=G:\oracle\product\10.1.0\db_1
    ORACLE_HOME=G:\oracle\product\10.1.0\db_1
    EMDSTATE=G:\oracle\product\10.1.0\db_1\IL16NTTCLDB1_TC08PRD
    CONSOLE_CFG=dbconsole
    TRACE_LEVEL=16
    TIMEOUT=15
    10/28/09 12:31:37 Job Process API is available
    10/28/09 12:31:37 Start pending...
    10/28/09 12:31:37 Verifying dbconsole is not started already. Command line "G:\oracle\product\10.1.0\db_1\bin\emctl.bat" istatus dbconsole
    10/28/09 12:31:40 dbconsole launch commandline is "G:\oracle\product\10.1.0\db_1\bin\emctl.bat" istart dbconsole
    10/28/09 12:31:40 Tracking process launch...
    10/28/09 12:32:12 Received exitCode 3 from emctl istatus
    10/28/09 12:32:12 dbconsole started
    10/29/09 06:43:19 Recieved ServCtrlHdlr command, 1
    10/29/09 06:43:19 Stopping dbconsole
    10/29/09 06:43:19 Launching stop EMD process...
    10/29/09 06:43:19 Waiting for stop EMD process to exit. numRetries=74
    10/29/09 06:43:23 Stop process has exited with exitCode: 0
    10/29/09 06:43:23 Waiting for emwd process to exit. numRetries=74
    10/29/09 06:43:23 Watchdog process exited with exit code 55
    10/29/09 06:43:23 Signal Shutdown event.
    10/29/09 06:43:23 Shutdown thread exited.
    10/29/09 06:43:23 ServiceMain wake up by ShutdownProc, emwd has exited. ServiceMain exits
    -------------- [OracleDBConsoleTC08PRD] ------------
    EMDROOT=G:\oracle\product\10.1.0\db_1
    ORACLE_HOME=G:\oracle\product\10.1.0\db_1
    EMDSTATE=G:\oracle\product\10.1.0\db_1\IL16NTTCLDB1_TC08PRD
    CONSOLE_CFG=dbconsole
    TRACE_LEVEL=16
    TIMEOUT=15
    10/29/09 06:43:57 Job Process API is available
    10/29/09 06:43:57 Start pending...
    10/29/09 06:43:57 Verifying dbconsole is not started already. Command line "G:\oracle\product\10.1.0\db_1\bin\emctl.bat" istatus dbconsole
    10/29/09 06:44:01 dbconsole launch commandline is "G:\oracle\product\10.1.0\db_1\bin\emctl.bat" istart dbconsole
    10/29/09 06:44:01 Tracking process launch...
    10/29/09 06:44:36 Did not hear back from emctl istatus.
    10/29/09 06:44:36 Waiting a further 5 secs...
    10/29/09 06:44:41 Did not hear back from emctl istatus.
    10/29/09 06:44:41 Waiting a further 5 secs...
    10/29/09 06:44:46 Did not hear back from emctl istatus.
    10/29/09 06:44:46 Waiting a further 5 secs...
    10/29/09 06:44:51 Did not hear back from emctl istatus.
    10/29/09 06:44:51 Waiting a further 5 secs...
    10/29/09 06:44:56 Did not hear back from emctl istatus.
    10/29/09 06:44:56 Waiting a further 5 secs...
    10/29/09 06:45:01 Did not hear back from emctl istatus.
    10/29/09 06:45:01 Waiting a further 5 secs...
    10/29/09 06:45:06 Did not hear back from emctl istatus.
    10/29/09 06:45:06 Waiting a further 5 secs...
    10/29/09 06:45:11 Did not hear back from emctl istatus.
    10/29/09 06:45:11 Waiting a further 5 secs...
    10/29/09 06:45:16 Did not hear back from emctl istatus.
    10/29/09 06:45:16 Waiting a further 5 secs...
    10/29/09 06:45:21 Did not hear back from emctl istatus.
    10/29/09 06:45:21 Waiting a further 5 secs...
    10/29/09 06:45:26 Did not hear back from emctl istatus.
    10/29/09 06:45:26 Waiting a further 5 secs...
    10/29/09 06:45:31 Did not hear back from emctl istatus.
    10/29/09 06:45:31 Waiting a further 5 secs...
    10/29/09 06:45:34 dbconsole exited with retCode 55.
    10/29/09 06:45:34 Check G:\oracle\product\10.1.0\db_1\IL16NTTCLDB1_TC08PRD\sysman\log\emdbconsole.nohup for details
    -------------- [OracleDBConsoleTC08PRD] ------------
    EMDROOT=G:\oracle\product\10.1.0\db_1
    ORACLE_HOME=G:\oracle\product\10.1.0\db_1
    EMDSTATE=G:\oracle\product\10.1.0\db_1\IL16NTTCLDB1_TC08PRD
    CONSOLE_CFG=dbconsole
    TRACE_LEVEL=16
    TIMEOUT=15
    10/29/09 06:47:52 Job Process API is available
    10/29/09 06:47:52 Start pending...
    10/29/09 06:47:52 Verifying dbconsole is not started already. Command line "G:\oracle\product\10.1.0\db_1\bin\emctl.bat" istatus dbconsole
    10/29/09 06:47:54 dbconsole may already be running. termStatus=3

  • 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?

  • DPM: Agent unreachable - Can not map machine account Resolution state

    Hello,
    We have 15 DPM servers with latest patches (3.0.8193.0). Currently we are having below error messages into two of our DPM servers. Could you help us to resolve these problems?
    Alert: DPM: Agent unreachable - Can not map machine account
    Source: DPMSERV011
    Path: DPMSERV011.xxx.xx.com;DPMSERV011.xxx.xx.com
    Last modified by: System
    Last modified time: 10/31/2013 2:00:02 PM Alert description: DPM agents on some of the protected servers are not reachable because machine account cannot be mapped.
    DPM Server: DPMSERV011.corpaa.aa.com
    Resolution steps:
    Verify that both protected server and the domain controller are responding. Then in Microsoft Management Console (MMC), open the Group Policy Object Editor snap-in for the local computer and verify the local DNS client settings in Local Computer Policy\Computer
    Configuration\Administrative Templates\Network\DNS Client.
    (Note: The DNS Client is disabled at both DPM and agent server)
    Alert view link: "http://DataSERV54021.xxx.xx.com:51908/OperationsManager?DisplayMode=Pivot&AlertID=%7b925c8b34-0d99-4bd2-a754-71354bd89f0e%7d"
    Notification subscription ID generating this message: {6EED81DB-935D-651F-4ACA-194C1FDBB428}
    Regards
    Abul Hasnat
    Abul Hasnat

    Hello,
    The servers are pingable and there is no local firewall. The servers are communicating but some sync jobs are failing. The Sync set to every 45 min.
    Thank ypu
    Abul Hasnat
    Abul Hasnat

  • How can i run a executable right after a rman job has run?

    How can i run a executable right after a rman job has run?
    I have a rman job that execute every night. The backup is local.
    I want to have a duplicate of the backup on another machine.
    I want the executable to sync the directory to execute right after the rman backup.
    How can i do this using the job scheduler?
    Normaly, i would configure rman to run the backup on both location. But im having trouble with rman regarding this:ORA-600 [2103] on RMAN Backup to NFS mounted file system

    Hi,
    If the rman job is in fact a Scheduler jobs (appears in the dba_scheduler_jobs view) then you can create a second event-based job that runs after the rman job (and set the raise_events attribute for the rman job).
    Instructions are here
    Create Event based job
    Hope this helps,
    Ravi.

  • Agent unreachable

    Hi,
    I have installed agent 10g on unix machine(HPUX-11.1) agent runs for 6-8 hrs
    after that it dies out and when i see the db through grid control it says agent unreachable but when grep for agent it shows up and running , iam not sure whats happening here.
    [oracle:leopard:NOSID] /oracle/product/agent10g/sysman/log > ps -ef|grep agen>
    root 2661 1 0 May 20 ? 0:00 /etc/opt/resmon/lbin/emsagent
    root 2617 1 0 May 20 ? 2:38 /usr/sbin/swagentd -r
    oracle 23822 23690 0 Nov 20 ? 13:24 /oracle/product/agent10g/bin/emagent
    oracle 23690 1 0 Nov 20 ? 2:54 /oracle/product/agent10g/perl/bin/perl /oracle/product/agent10g
    aduaslq 16850 22944 0 Nov 23 ? 4:58 /amuaslq01s/app/amuaslqdb/10.2.0/bin/emagent---->agent is for OAM
    [oracle:leopard:NOSID] /oracle/product/agent10g/bin > emctl status agent
    Oracle Enterprise Manager 10g Release 3 Grid Control 10.2.0.3.0.
    Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
    Agent is Not Running
    [oracle:leopard:NOSID] /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.
    Failed to start HTTP listener.
    Consult the log files in: /oracle/product/agent10g/sysman/log
    [oracle:leopard:NOSID] /oracle/product/agent10g/bin > ps -ef|grep agent
    root 2661 1 0 May 20 ? 0:00 /etc/opt/resmon/lbin/emsagent
    root 2617 1 0 May 20 ? 2:38 /usr/sbin/swagentd -r
    oracle 23822 23690 0 Nov 20 ? 13:23 /oracle/product/agent10g/bin/emagent
    oracle 3913 15344 0 21:42:27 pts/7 0:00 grep agent
    oracle 23690 1 0 Nov 20 ? 2:53 /oracle/product/agent10g/perl/bin/perl /oracle/product/agent10g
    aduaslq 16850 22944 0 Nov 23 ? 4:57 /amuaslq01s/app/amuaslqdb/10.2.0/bin/emagent
    /oracle/product/agent10g/sysman/log :vi emagent.trc
    2007-11-27 17:48:44 Thread-189993 ERROR util.files: ERROR: nmeufos_new: failed i
    n lfiopn on file: /oracle/product/agent10g/sysman/emd/agntstmp.txt.error = 24 (T
    oo many open files)
    2007-11-27 17:48:44 Thread-189993 ERROR pingManager: Error in updating the agent
    time stamp file
    2007-11-27 17:48:48 Thread-189994 ERROR util.fileops: ERROR: snmeuf_dirlist can'
    t list directory: /oracle/product/agent10g/sysman/emd/upload: Too many open file
    s (errno=24)
    2007-11-27 17:48:51 Thread-189995 ERROR engine: Failed when generating a new ECI
    D.
    2007-11-27 17:48:51 Thread-189995 ERROR fetchlets.healthCheck: GIM-00104: file n
    ot found
    LEM-00031: file not found; arguments: [lempgmh] [lmserr]
    LEM-00033: file not found; arguments: [lempgfm] [Couldn't open message file]
    LEM-00031: file not found; arguments: [lempgmh] [lmserr]
    2007-11-27 17:48:51 Thread-189995 ERROR engine: [oracle_database,leopard-amuaslq
    .am,health_check] : nmeegd_GetMetricData failed : Instance Health Check initiali
    zation failed due to one of the following causes: the owner of the EM agent proc
    ess 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 10
    g (10.1.0.2) and above.
    Please Any suggestions.

    As per note_id:430805.1
    3. We now need to focus also on the monitored database side. This section takes place in the monitored RDBMS Oracle Home:
    If the monitored database is 10gR1 (10.1.x):
    10.1.0.4: you need to apply Patch 5868695 on the RDBMS Oracle Home, otherwise the Healthcheck metric will still fail, despite the code fix applied on the Agent side.
    10.1.0.5: At this moment, this specific one-off patch is not available on top of RDBMS 10.1.0.5. Please contact support if you need this fix for RDBMS 10.1.0.5 on HP-UX.
    10.1.0.3, 10.1.0.2: consider patching / upgrading
    If the monitored database is 10gR2 (10.2.x):
    10.2.0.3 (and above): nothing to be done. The fix is already included.
    10.2.0.2: Apply the Patch 4559294 in the RDBMS Oracle Home by following instructions given in the README.
    My concern is what if we have 8i and 9i monitored databases?Please let me know.

  • EM 10g Database Control - Status: Agent Unreachable

    Hi,
    OS: AIX 5L
    Database: Oracle Database 10g Enterprise Edition Release 10.1.0.2.0 - 64bit
    We have installed 2 instances with EM 10g database control option.
    At the end EM was running over the second database.
    Then we switch it to look over the first one by reconfiguring these files:
    $ORACLE_HOME/sysman/config/emd.properties;
    $ORACLE_HOME/sysman/config/pref/dbastudio-oradba.crd.
    Now EM seems to work fine except for this error: Agent Unreachable.
    oradba@aix09(:SIGP)/u01/apps/oradba/product/10.1.0/aix09_SIGP/sysman/log > emctl status agent
    Oracle Enterprise Manager 10g Database Control Release 10.1.0.2.0
    Copyright (c) 1996, 2004 Oracle Corporation. All rights reserved.
    Agent Version : 10.1.0.2.0
    OMS Version : 10.1.0.2.0
    Protocol Version : 10.1.0.2.0
    Agent Home : /u01/apps/oradba/product/10.1.0/aix09_SIGP
    Agent binaries : /u01/apps/oradba/product/10.1.0
    Agent Process ID : 4284428
    Parent Process ID : 3399760
    Agent URL : http://aix09:1830/emd/main
    Started at : 2004-08-09 12:24:29
    Started by user : oradba
    Last Reload : 2004-08-09 12:24:29
    Last successful upload : (none)
    Last attempted upload : 2004-08-09 14:29:51
    Total Megabytes of XML files uploaded so far : 0.00
    Number of XML files pending upload : 1955
    Size of XML files pending upload(MB) : 50.12
    Available disk space on upload filesystem : 4.60%
    Agent is Running and Ready
    /aix09_SIGP/sysman/log/ emagent.trc:
    2004-08-09 14:31:53 Thread-1910 ERROR upload: Failed to upload file A0000001.xml, ret = -2
    2004-08-09 14:31:53 Thread-1910 WARN upload: FxferSend: received http error in header from repository: http:/
    /aix09:5500/em/upload/
    ERROR-400|ORA-04020: deadlock detected while trying to lock object 30x700000021709BF80x700000021B01D200x700000
    0267473A8
    2004-08-09 14:31:53 Thread-1910 ERROR upload: Failed to upload file A0000001.xml, ret = -2
    2004-08-09 14:31:53 Thread-1910 ERROR upload: 3 Failures in a row for A0000001.xml, we give up
    2004-08-09 14:31:53 Thread-1910 ERROR upload: Error in uploadXMLFiles. Trying again in 300.00 seconds.
    After connecting as sysman I’ve ran these statements:
    SQL> SELECT emd_url
    2 FROM mgmt_targets t
    3 WHERE t.target_name = 'aix09'
    4 AND t.target_type = 'host';
    EMD_URL
    http://aix09:1830/emd/main
    SQL> SELECT t.target_name, t.target_type,
    2 TO_CHAR(t.load_timestamp,'DD-MON-YYYY HH24:MI:SS') "discovery_time
    3 TO_CHAR(t.last_updated_time,'DD-MON-YYYY HH24:MI:SS') "last_metada
    ta_load",
    4 TO_CHAR(a.marker_timestamp,'DD-MON-YYYY HH24:MI:SS') "last_severit
    y_load",
    5 TO_CHAR(t.last_load_time,'DD-MON-YYYY HH24:MI:SS') "last_metric_lo
    ad"
    6 FROM mgmt_targets t, mgmt_availability_marker a
    7 WHERE t.target_guid = a.target_guid
    8 AND t.target_name = 'aix09'
    9 AND t.target_type = 'host';
    TARGET_NAME
    TARGET_TYPE discovery_time
    last_metadata_load last_severity_load last_metric_load
    aix09
    host 03-AUG-2004 14:47:55
    05-AUG-2004 18:28:45 05-AUG-2004 18:30:42 05-AUG-2004 17:13:55
    Does any one know what do I have to do to solve this problem ?
    Thanks in advance,
    Vitor

    Can you start a browser on the client machine?
    (netscape/mozilla) and try to load
    http://aix09:1830/emd/main
    Make sure both the client and the OMS server can resolve aix09 hostname
    Make sure the client can resolve the OMS server name.

Maybe you are looking for