Cloud Control can't patch an agent

This week I have successfully upgraded our Cloud Control 12.1.0.2 to 12.1.0.3. Since this was my first experience with Cloud Control configuration, it went pretty good. I have noticed now in Patch recommendations that it's possible to patch an agent which is working on Windows Server 2008.
This is the available patch:
Patch 14335896: BUG FOR PATCH OF PERFORMANCE BUNDLE 2 ON EM 12C BP1 (AGENT)
So i have downloaded it, uploaded in "Saved patches", created a plan, configured it, and during the plan analysing i get a status Failed. First few checks go without problems, but then I get this:
========================================================
Performing check for CheckPatchShipHome
Is the Patch Shiphome correct?
Result: [E:\ded_agent\p14335896_9800371121011_2000_0\Administrator\com\trend\etc\config path does not exist or is not a directory]
I have checked the path on target, it exists until E:\ded_agent\p14335896_9800371121011_2000_0\Administrator\com\trend\
There I can find only a folder with iwss name. Etc is not there...
Any known issues about this Problem?

I think you forgot one step: you must first download the latest agent software for Windows, see Prerequisites in Upgrading Oracle Management Agents
The new management agent software (for Windows in this case) must be available in the software library before you can upgrade an agent.
Eric

Similar Messages

  • Oracle Cloud Control 12c and licensing

    Hey Guys, Can someone please elucidate on the Cloud Control 12c licensing requirements?
    Following are all the licenses we currently hold:
    1. Oracle Enterprise Edition DB
    2. Oracle RAC
    3. Oracle Active Data Guard
    4. Diagnostic and Tuning Pack
    5. Partitioning Option
    6. Advanced Security Option
    7. GoldenGate
    My understanding is that I could install and access Grid/Cloud control as long as I have the Diagnostic and Tuning Pack - and of course to all products we are licensed for.
    Questions:
    1. Do I need any license for Weblogic server?
    2. Can I setup OMS in a clustered architecture?
    3. Can I have the RAC database for the repository?
    4. Can I access the High Availability options - DG etc?
    5. Can I administer RAC and GI services from Cloud Control?
    I would've thought that as long as I have access to the underlying DB options, Grid/Cloud control can be used to administer over them.
    Could someone please help in clearing this up?
    Regards
    Sridhar

    I highly recommend you to read the Enterprise Manager Licensing Information:
    http://docs.oracle.com/cd/E24628_01/doc.121/e24474/toc.htm
    Quick answers for your questions:
    1) No, as long as you use it only for EM
    2) Yes you can.
    3) You need to buy licenses for RAC option (for both nodes) and DB licenses for second node.
    4) You mean accessing DG pages on EM pages right? Yes you can. They do not need any license pack. Btw you can check if a page requires additional licensing using "setup > management packs > packs for the page" menu.
    5) Yes you can.
    But as I said, it's better to read the licencing document by yourself, and contact Oracle sales for more information.

  • Differences between EM Database Control and Grid Control/Cloud Control

    Hi everybody,
    just a short question: To show my colleagues and my boss, which one is the better one I would like to have a view about what the differences between Database Control and Cloud Control Versions of EM are and which functions would like the monitoring work more comfortable for us DBA's. Does anybody know a link or document for that?
    Thanks a lot!
    Regards,
    David

    Is this the own advantage of between Cloud Control and DB Control, that Cloud Control can monitor more than one instance?Someone that are using Grid control will tell you that it is a great avantage.
    We've just one database instance. But I've read about SNMP functions, that are only supported in Cloud Control. Are there more advantages?if you only have one database instance, Enterprise Manager is your best way at this moment.
    At some time, for example when 12g arrives, will Cloud Control be the standard installation?for the moment...nobody knows what is coming with 12c database...

  • Can EM12c Cloud Control agent be installed in a solaris zone?

    Can EM12c Cloud Control agent be installed in a solaris zone?
    If so, are Solaris 8 and Solaris 9 zones supported?
    thanks

    Yes we can...
    Solaris 9 is supported...I have installed agents on solaris 9 and 10

  • Can Cloud Control 12c connect to existing 12c agent?

    Can Cloud Control 12c connect to the existing 12c agent? Can't find any information about the subject. Everywhere explained how I can deploy agent from OEM...

    If you want to redirect an EM12c agent to a different EM12c site, see the doc below. If not, please clarify on what you want to do.
    http://docs.oracle.com/cd/E24628_01/install.121/e24089/appdx_repoint_agent.htm#BABICJCE
    Regards,
    - Loc

  • 1390717.1 - 12c Cloud Control Agent: Is it possible to Re-configure ...

    Can anyone get to this note "1390717.1: 12c Cloud Control Agent: Is it possible to Re-configure a 12c Agent to a Different 12c OMS Without Re-installation?"
    I do a search in Metalink and I see it listed in "How to Point a 10g/11g Grid Agent to a Different Grid Control OMS and Repository without Re-installation? [ID 413228.1]" but that is the only doc a search returns.
    I have a test environment with agents pointed to an old OMS 12c. I'd like to utilize the same agents but point them to our new, production, OEM 12c environment. Has anyone had any success with this? I've followed the 10g/11g OEM steps without luck, thus far (early testing).
    I was excited to see "emctl switchOMS REPOSITORY_URL" in the emctl options until I read the next line...
    This command is not supported.
    Drat :-)
    Regards,
    Rich

    Hi,
    The steps you need to follow are documented here:-
    http://docs.oracle.com/cd/E24628_01/install.121/e24089/appdx_repoint_agent.htm#BABICJCE
    Regards, Mark.

  • Installation guide Oracle cloud Control Agents on a Windows failover cluste

    Hello Experts,
    i have to install Oracle cloud control agent on windows fail-over cluster. i could not found any document on oracle support site/ internet.
    here are the requirement:
    i have two hosts (host1 and host2) which are in windows cluster environment (active/passive). means, one node will hold the cluster service/resource at a time.
    if primary node (host1) is down, Microsoft cluster ware will fail-over cluster resource to host2 automatically.
    any one deployed 12c Agents on windows fail-over clustered environment. if yes, please provide hints / procedure.
    Thanks
    pavan

    Hi Pavan,
    Please find the following document:
    How to Configure Grid Control Agents in Windows HA - Failover Cluster Environments (Doc ID 464191.1)
    For 12C Agent install, you can proceed with the silent install passing a virtual hostname in silent method also using the following document:
    How to Install EM 12c Agent using Silent Install Method with Response File (Doc ID 1360083.1)
    Best Regards,
    Venkat

  • Can Cloud Control 12c be on the Exadata client network?

    Hi, there,
    We’re trying to configure our brand new X3 machine but we’re having a problem with connecting our Cloud Control OMS to it (the install of the agents fails because it can't connect to the hostname we provided on the management interface). We’re running the latest and greatest Exadata stack (11.2.3.2.1, 11.2.0.3.18) and we’re running Cloud Control 12.1.0.2
    The OMS server – oem12oms – is on the same subnet as the client network on the Exadata comp nodes. However, when we try to ping the management hostname of the comp nodes (the docs say using the client hostname is not supported until 12.1.0.3) from the OMS server, we have no success:
    For instance:
    oem12oms – 10.50.50.122 (running on eth0)
    exadbclient1 – 10.50.50.123 (running on eth1 on the first comp node)
    exadbclient2 – 10.50.50.124 (running on eth1 on the second comp node)
    exadbadm1 – 10.75.100.23 (running on eth0 on the first comp node)
    exadbadm2 – 10.75.100.24 (running on eth0 on the second comp node)
    From oem12oms, when both eth0 and eth1 are up on the comp nodes, it fails:
    traceroute exadbadm1 (10.75.100.23)
    10.50.50.1 (the default gateway for both the client network and the Exadata comp node itself)
    Then goes nowhere
    When we shut down the eth1 interface, I am able to access the management interface from my OMS server:
    traceroute exadbadm1 (10.75.100.23)
                                 10.50.50.1 (the default gateway for both the client network and the Exadata comp node itself)
    exadbadm1 (10.75.100.23)
    We have rules/routes which set on the comp node (by default) that dictate all traffic from:
    the management interface (eth0) uses routing table 220 and comes from 10.75.100.xxx and goes out the same interface on 10.75.100.xxx.
    the client (eth1) uses routing table 221 and comes from 10.50.50.xxx and goes out the same interface on 10.50.50.xxx
    Essentially, while we want to tell incoming traffic NOT to go out a different interface to which it came in, I think we want to workaround this for one exception: the OMS server’s IP address (10.50.50.122) should come in from the MANAGEMENT interface (not the client) and go out the MANAGEMENT interface.
    There are a lot of references to advanced Linux network policies, etc. And we’ve read 1306154.1. However, it doesn’t seem to solve our problem and we’ve tried all the ways that we can think of: essentially, it looks like Exadata cannot connect to clients over the management interface which live on its client network (obviously, it will still be able to be accessed through the SCAN addresses), so your Cloud Control cannot be on the client network.
    I haven’t read anything which states this, but that’s how it looks to us.
    Anyone had this issue before? Our ACS engineer is stumped and has asked around internally to no avail.
    Mark

    Mark,
    I read your article about this - it's the best article out there by a LONG way, but it still confuses me because of my eye-popping ignorance. Well done, though, because I almost understood it so you're clearly skilled in explaining complex stuff to untrained monkeys
    Oracle don't appear to know about this issue, which astounds me. We can't be the only customer who has their client network on their 'main' network. We've had two ACS engineers who have been flummoxed by this and have tried to reach out to the 'internal guru' network in Oracle with joy.
    I tried to type out what I should do (the configuration is in a mess right now, so I haven't tried this out yet). This is to get things clear in my mind.
    OMS server: 10.50.50.122 (client interface - uses the same subnet as the 'general Production' network)
    DB Comp Node 1: 10.75.100.23 (management interface - uses an exclusive subnet for Exadata management hostnames)
    First, we add a custom routing table 230 to the /etc/iproute2/rt_tables
         echo 230 >> /etc/iproute2/rt_tables
    Then we need to inform the magical, mysterious routing database of this new table and what we want to do with it:
    Add a route to direct traffic from the OMS server (client network) to the comp node (management network) using table 230
    Add a rule which tells traffic from the OMS server to use table 230 (with higher priority than other rules)
    Add a rule which tells traffic from the comp node to use table 230 (with even higher priority)
              ip route add 10.50.50.122/32 via 10.75.100.23 dev eth0 table 230
              ip rule add from 10.50.50.122 prio 32750 table 230
              ip rule add to 10.75.100.23 prio 32751 table 230
    The ifcfg files look OK so I didn't see the need to change them.
    I thought I'd add a route associated with routing table 230 to the rule-eth0 file so that it has two entries (added the last two lines)
    The first entry uses table 220 to route traffic coming in on the management interface to the management interface
    The second (new) entry uses table 230 to route traffic coming from the OMS server (client network) to the management interface
              from 10.75.100.23 table 220
              to 10.75.100.23 table 220
              from 10.50.50.122 table 230
              to 10.75.100.23 table 230
    Then I'd change the route-eth01 to add the new rule (added the last line)
    The first entry tells anything coming in from the management interface to use the eth0 NIC and table 220 (which instructs anything coming from the management network to stay on the management network)
    The second entry tells anything coming in from the management interface gateway to do the same (eth0 NIC and table 220)
    The third entry (new) tells anything coming from that specific IP address to route to the management IP of the comp node via eth0 but using our new table 230
              10.75.100.0/24 dev eth0 table 220
              default via 10.75.100.1 dev eth0 table 220
              10.50.50.122/24 via 10.75.100.23 eth0 table 230
    This should mean that the rules/routes will be statically configured so when we restart the network services or the entire box, it should save them?
    Does that look as it would make sense? The whole thing SEEMS to make perfect sense and seems easy when reading about it, but doesn't seem to play nicely when you come to actually implement it.
    Mark

  • Installing Cloud Control 12c agent on other blades thru RPM and response file sets wrong cluster name

    Hi,
    Hopefully someone can help me with this. We installed em Cloud Control 12c and its agents on miscellaneous machines.
    We first proceeded with two target-nodes part of a Grid Infra cluster (let's call it proclu_1). OS is RH6.
    Then, using the same method (1/ yum -y install /tmp/oracle-agt-12.1.0.3.0-1.0.x86_64.rpm and then
    2/ /etc/init.d/oracle-agt RESPONSE_FILE=/usr/lib/oracle/agent/agent.properties) we installed the agent on 2 other
    blades that are part of another cluster (proclu_2). The agent.properties file above just contained the usual key-value lines:
    OMS_HOST=omsmachine.stuff.be
    OMS_PORT=4889
    AGENT_REGISTRATION_PASSWORD=ametemp
    AGENT_USERNAME=oracle
    AGENT_GROUP=oinstall
    AGENT_PORT=3873
    ORACLE_HOSTNAME=promachine.stuff.be
    Now if I change dir to /usr/lib/oracle/agent and search for the name "proclu*" from there, I find the name of the
    first install (on first cluster proclu_1):
    [oracle@bladb0406 agent]$ pwd
    /usr/lib/oracle
    [oracle@bladb0406 oracle]$ find . -name "proclu_1*"
    ./agent/agent_inst/sysman/emd/state/has/proclu2/cluster/proclu
    ./agent/agent_inst/sysman/emd/state/configstate/cluster/proclu_1
    ./agent/agent_inst/sysman/emd/state/statemgmt/cluster/proclu_1
    ./agent/agent_inst/sysman/log/targets/cluster/proclu_1
    My questions:
    1/ on the first two nodes (blada0204 & blada0406) of our first cluster doing this 'find' returns the
    same directory names with "proclu_1", this is what we expected: where did the oracle-agt script pick up
    our cluster name ?
    2/ why has it set the same -and wrong- "proclu_1" name on our two other nodes (bladb0204 & bladb0406) ??
    (we would've expected "proclu_2"...)
    Is there a way to correct this, or should I reinstall the agent (after configuring/modifying something somewhere
    so that it picks up the correct cluster name...) ??
    Thanks a lot.
    Regards,
    Seb

    Unfortunately, this goes back to the RAC install procedures.   Check the cluster name for each cluster.   If they're all installed the same, then you'll need to manually discover/edit name when you promote so that your clusters are unique in EM.
    To verify name set for clusterware installation:
    <CRS_HOME>/bin/cemutlo -n

  • 12c Cloud Control - Agent Unreachable

    Hello,
    I am quite new to 12c cloud control and I am unable to resolve an "Agent Unreachable" issue.
    I could find Agent does not upload to OMS in OEM 12c as relevant
    but nothing in that worked for me.
    The setup is as follows:
    1) 12c cloud control is installed on a box and is up and running (both OMS and agent)
    2) The agent on the same host as OMS can talk to OMS and the agent status is shown as "available" in OMS console
    3) There is another box that has a 11.2 database installed as well as 12c agent installed (called as DEVBOX for convenience)
    4) DEVBOX has database up and running and 12c agent also up and running. In the past, it was probably being able to "talk" to OMS but I can't remember
    However, at present, on OMS console, this agent is shown as "unreachable". I tried few things but only possible issue I could find is
    when I try to use Setup -> Add Target -> Add Targets Manually -> Add non-Host targets using guided process, on the "specify Host" page
    when I click on "Select Host" option, the hostname in the agent URL for the DEVBOX is different than the actual host name.
    As the agent URL for DEVBOX is not reachable (because the hostname is invalid), I can't do anything with this agent.
    Can somebody please help?

    Loc Nhan wrote:
    To remove an agent from the console:
    - Go to the homepage of the host where the agent reside
    - From the Host menu under the host name, select Related Targets
    - Remove all non-agent targets
    - Remove the host target by selecting Host > Target Setup > Remove Target
    - Stop the agent
    - Remove the agent target by going to the agent homepage and selecting Agent > Target Setup > Remove TargetLoc,
    Once again thanks for looking into this. I followed your advice above and removed the host and the agent from OMS console.
    Now, with the 12c agent already running on the DEVBOX, I was hoping that OMS will automatically detect the agent but I
    can't find it in OMS console.
    On DEVBOX:
    [oracle@devbox agent_inst]$ ./bin/emctl status agent
    Oracle Enterprise Manager 12c Cloud Control 12.1.0.1.0
    Copyright (c) 1996, 2011 Oracle Corporation.  All rights reserved.
    Agent Version     : 12.1.0.1.0
    OMS Version       : 12.1.0.1.0
    Protocol Version  : 12.1.0.1.0
    Agent Home        : /u01/app11g/oracle/agentHome12c/agent_inst
    Agent Binaries    : /u01/app11g/oracle/agentHome12c/core/12.1.0.1.0
    Agent Process ID  : 8945
    Parent Process ID : 8893
    Agent URL         : https://devbox.dev.abc.com:3872/emd/main/
    Repository URL    : https://gridbox.prd.abc.com:4901/empbs/upload
    Started at        : 2012-08-17 09:47:30
    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    : 17.52%
    Collection Status                            : Collections enabled
    Last attempted heartbeat to OMS              : 2012-08-17 09:48:51
    Last successful heartbeat to OMS             : 2012-08-17 09:48:51
    Agent is Running and Readyon OMS box:
    [oracle@gridbox middleware]$ ./oms/bin/emctl status oms -details
    Oracle Enterprise Manager Cloud Control 12c Release 12.1.0.1.0
    Copyright (c) 1996, 2011 Oracle Corporation.  All rights reserved.
    Enter Enterprise Manager Root (SYSMAN) Password :
    Console Server Host : gridbox.prd.abc.com
    HTTP Console Port   : 7789
    HTTPS Console Port  : 7801
    HTTP Upload Port    : 4890
    HTTPS Upload Port   : 4901
    OMS is not configured with SLB or virtual hostname
    Agent Upload is locked.
    OMS Console is locked.
    Active CA ID: 1
    Console URL: https://gridbox.prd.abc.com:7801/em
    Upload URL: https://gridbox.prd.abc.com:4901/empbs/upload
    WLS Domain Information
    Domain Name      : GCDomain
    Admin Server Host: gridbox.prd.abc.com
    Managed Server Information
    Managed Server Instance Name: EMGC_OMS1
    Managed Server Instance Host: gridbox.prd.abc.comAs I mentioned earlier, gridbox and devbox can communicate with each other on necessary ports.
    I would prefer to resolve this issue without having to re-install the agent.
    Would appreciate some help.
    Thanks.

  • Cloud control 12c and management agent 11.1

    Hello everyone!
    I have installed oracle cloud control 12c (12.1.0.2) on Win platform.
    and it does not have an access to the internet yet.
    I have database targets only on Linux hosts. In my case CC does not have approriate Agent software for linux hosts.
    So the question is :
    How can I configure cloud control with datbases hosts on linux ?
    Can I use 11.1 agent software ?
    Thanks.

    1- For CC 12c you have to use 12c agents. Lower agent versions will not work.
    2- A " how to" on downloading agent software and adding it to your OMS can be found here: http://www.gokhanatil.com/2012/03/how-to-download-new-agent-software-for-oracle-cloud-control-12c-in-offline-mode.html
    Push the agent to *UX servers: http://www.gokhanatil.com/2011/10/how-to-deploy-oracle-management-agent.html
    If you want to push the agent to the Linux servers you have to install CYGWIN on the (Windows) OMS server.
    Eric

  • Where can I download the agent for 11g database for 10.2.0.4 grid control?

    where can I download the agent for 11g database for 10.2.0.4 grid control? i can't find the link.

    I don't think there is one yet, but you can use Grid Control 10gR4 to monitor a 11g database. Please refer the certification matrix in Note 412431.1 Oracle Enterprise Manager 10g Grid Control Checker

  • In EM Cloud control 12c, How to enable SSL between agent and OMS?

    As title. Thanks!

    Did you checkout MOS note 12c Cloud Control Security: How to Secure a 12c Agent from Console / Command Line? [ID 1390222.1] ?
    Regards
    Rob
    http://oemgc.wordpress.com

  • Cloud Control 12c patching problem

    Hi,
    I have uploaded in the Software Library 14335896 and 6880880 patches.
    I have created a new plan that includes the following patches:
    14335896 and 6880880
    When I analyze the plan the output gives the the following messages:
    Output Log
    [Oct 15, 2012 5:01:16 PM] PatchDownloadJob Exception, while creating the Patch Component in Software library: COULD_NOT_DOWNLOAD_PATCH_IN_OFFLINE_MODE
    PREREQ_NAME: Check Patch Downloading
    PREREQ_DESC: Check if patch downloading succeeds
    PREREQ_TYPE:PATCH_STATE
    PREREQ_STATUS:FAILED
    PREREQ_MESG: Fail to download patch(es) from My Oracle Support.
    Please notice that I am in Offline mode and I have tried to delete everything (also purging from the Software Library) and recreate from the scratch.
    Any ideas???
    Thank you
    Edited by: user11369597 on Oct 22, 2012 12:29 AM

    is there already a solution or an SR for that ?
    I have the same problem.
    I don't understand Oracle at all. They provide an offline patch which tries to download from Oracle Support !?
    I have uploaded the manually downloaded patch and the metadata xml file. So far so good. But trying to deploy the patch, the Cloud Control console tries again to download the already uploaded patch (uploaded to my software library).
    Ingreadible.

  • How can I use two midi keyboards to control two different patches?

    I would like to use two midi keyboards in my setup, each controlling a different patch or track.

    Hi,
    Follow the steps in this guide:
    http://www.logicprohelp.com/forum/viewtopic.php?f=5&t=32201
    J.

Maybe you are looking for