0 Replies Latest reply on Oct 8, 2013 9:49 PM by BillW

    Agent Status Reports OMS Version : (unknown)


      I upgraded our 11g OEM installation to and just completed patching to Some of the 11g agents were on platforms not supported by (part of the motivation fro the upgrade, now complete).


      Following the instructions in Chapter 7, Installing Oracle Management Agent in the Oracle Enterprise Manager Cloud Control Basic Installation Guide 12c Release 3 ( I was able to get the agent installed and started on one of the servers I was not able to upgrade during the upgrade process. The new agent is up and running but reports OMS Version : (unknown) -


      cmspweb:app/agent12g/agent_inst/bin->./emctl status agent
      Oracle Enterprise Manager Cloud Control 12c Release 3
      Copyright (c) 1996, 2013 Oracle Corporation.  All rights reserved.
      Agent Version     :
      OMS Version       : (unknown)
      Protocol Version  :
      Agent Home        : /usr/local/oracle/app/agent12g/agent_inst
      Agent Binaries    : /usr/local/oracle/app/agent12g/core/
      Agent Process ID  : 3821
      Parent Process ID : 3767
      Agent URL         : https://garmin.ucdavis.edu:3872/emd/main/
      Repository URL    : https://oracle-emrep1.ucdavis.edu:4904/empbs/upload
      Started at        : 2013-10-08 11:56:26
      Started by user   : oracle
      Last Reload       : (none)
      Last successful upload                       : (none)
      Last attempted upload                        : (none)
      Total Megabytes of XML files uploaded so far : 0
      Number of XML files pending upload           : 0
      Size of XML files pending upload(MB)         : 0
      Available disk space on upload filesystem    : 69.43%
      Collection Status                            : Collections enabled
      Heartbeat Status                             : OMS is unreachable [bad response]
      Last attempted heartbeat to OMS              : 2013-10-08 14:30:13
      Last successful heartbeat to OMS             : (none)
      Next scheduled heartbeat to OMS              : 2013-10-08 14:30:43

      Agent is Running and Ready


      and the upload fails with the error EMD upload error:full upload has failed: uploadXMLFiles skipped :: OMS version not checked yet. If this issue persists check trace files for ping to OMS related errors. (OMS_DOWN) which makes sense. Searching the web I found a number of suggestions including securing the agent, which I was able to do and resynching the agent from the console which I am *not* able to do as the agent and targets are not showing in the console.


      The targets.xml file on the agent host has one line -

      <Targets AGENT_TOKEN="CB22F0CA441C8CDECF3CA3ABA0D8C02C9AACFF98A41D653CFB2F41B7BC41EE0D"/>


      and I realize that is not at all a complete file. In the gcagent.log file I see ping errors -

      2013-10-08 14:29:43,596 [319:8C08BF97] INFO - attempting initial heartbeat

      2013-10-08 14:29:43,805 [319:8C08BF97] WARN - improper ping interval (EM_PING_NOTIF_RESPONSE: ERROR- Failed to update Target type Metadata)

      2013-10-08 14:29:43,810 [319:8C08BF97] WARN - Ping protocol error

      o.s.gcagent.ping.PingProtocolException [OMS sent an invalid response: "ERROR- Failed to update Target type Metadata"]


      The firewall is open and the agent is using the correct port and I am stumped. If anyone has any suggestions I would certainly appreciate them.


      Thank you.

      Bill Wagman