State of the agent - HostName

Is it possible to change the host name to the agent (WindowsAgent), located under AgentStatus? Are you forced to remove the agent and add it with the new host name?

Under Administration | Agents | State of the agent.
Select an agent
Select Edit properties.
The host at the top of the page (not the hostname on the bottom).

The host name that appears at the top of the page is discovered by the agent's host name.

It is an agent of property that cannot be changed. If you want to change it, you must delete and re-create the agent.

As you note, the hostname associated with the measures collected is editable. This is the name that appears in the monitoring dashboards.

Kind regards

Brian Wheeldon

Tags: Dell Tech

Similar Questions

  • State of the agent showed ODI in Weblogic

    Hello

    I installed FDMEE 11.1.2.4. When I start services, everything is ok except agent ODI Java EE. I have not configured (I think it is preconfigured).


    I tried to start the ODI agent of the Manager of the company, but I get an error message; stick below.

    I have seen that in weblogic server under Integrator Server erpi my console to odi status is active and odi agent status is ready. I don't know how to start JAVA EE officer.

    Any help?

    Error:

    Operation call Start Up for application oraclediagent on the ErpIntegrator0 target.

    [Deployer: 149193] Operation 'start' on request 'oraclediagent' failed on 'ErpIntegrator0 '.

    [Deployer: 149034] An exception has occurred for task [Deployer: 149026] start application oraclediagent on ErpIntegrator0. : [HTTP:101216] Servlet: 'AgentServlet' failed by preloading at startup in a Web application: "oraclediagent."

    com.tangosol.net.RequestTimeoutException: timeout during the startup of the service: ServiceInfo (Id = 0, name is Cluster, Type = Cluster

    Set of members = MasterMemberSet)

    ThisMember = null

    OldestMember = null

    ActualMemberSet = MemberSet (Size = 0

    )

    Member ID | ServiceVersion | ServiceJoined | Member State

    RecycleMillis = 1200000

    RecycleSet = MemberSet (Size = 0

    )

    )

    )

    at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onStartupTimeout(Grid.CDB:3)

    at com.tangosol.coherence.component.util.daemon.queueProcessor.Service.start(Service.CDB:28)

    at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.start(Grid.CDB:6)

    at com.tangosol.coherence.component.net.Cluster.onStart(Cluster.CDB:58)

    at com.tangosol.coherence.component.net.Cluster.start(Cluster.CDB:11)

    at com.tangosol.coherence.component.util.SafeCluster.startCluster(SafeCluster.CDB:4)

    at com.tangosol.coherence.component.util.SafeCluster.restartCluster(SafeCluster.CDB:10)

    at com.tangosol.coherence.component.util.SafeCluster.ensureRunningCluster(SafeCluster.CDB:26)

    at com.tangosol.coherence.component.util.SafeCluster.start(SafeCluster.CDB:2)

    at com.tangosol.net.CacheFactory.ensureCluster(CacheFactory.java:427)

    at com.tangosol.net.DefaultConfigurableCacheFactory.ensureServiceInternal(DefaultConfigurableCacheFactory.java:968)

    at com.tangosol.net.DefaultConfigurableCacheFactory.ensureService(DefaultConfigurableCacheFactory.java:937)

    at com.tangosol.net.DefaultConfigurableCacheFactory.ensureCache(DefaultConfigurableCacheFactory.java:919)

    at com.tangosol.net.DefaultConfigurableCacheFactory.configureCache(DefaultConfigurableCacheFactory.java:1296)

    at com.tangosol.net.DefaultConfigurableCacheFactory.ensureCache(DefaultConfigurableCacheFactory.java:297)

    at com.tangosol.net.CacheFactory.getCache(CacheFactory.java:204)

    at com.tangosol.net.CacheFactory.getCache(CacheFactory.java:181)

    to oracle.odi.runtime.agent.coherence.OdiAgentCoherenceCache. < init > (OdiAgentCoherenceCache.java:52)

    at oracle.odi.runtime.agent.servlet.AgentServlet.initCoherence(AgentServlet.java:812)

    at oracle.odi.runtime.agent.servlet.AgentServlet.initializeClusterCache(AgentServlet.java:762)

    at oracle.odi.runtime.agent.servlet.AgentServlet.startup(AgentServlet.java:437)

    at oracle.odi.runtime.agent.servlet.AgentServlet.init(AgentServlet.java:250)

    at javax.servlet.GenericServlet.init(GenericServlet.java:242)

    to weblogic.servlet.internal.StubSecurityHelper$ ServletInitAction.run (StubSecurityHelper.java:283)

    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)

    at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)

    at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)

    to weblogic.servlet.internal.StubLifecycleHelper. < init > (StubLifecycleHelper.java:48)

    at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)

    at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1981)

    at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1955)

    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1874)

    at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3155)

    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1518)

    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:487)

    to weblogic.application.internal.flow.ModuleStateDriver$ 3.next(ModuleStateDriver.java:427)

    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)

    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)

    at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:201)

    at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:249)

    to weblogic.application.internal.flow.ModuleStateDriver$ 3.next(ModuleStateDriver.java:427)

    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)

    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)

    at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:28)

    to weblogic.application.internal.BaseDeployment$ 2.next(BaseDeployment.java:672)

    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)

    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)

    at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:59)

    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)

    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)

    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)

    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)

    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)

    at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:149)

    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)

    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)

    at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)

    at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)

    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:164)

    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)

    in weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$ 100 (DeploymentReceiverCallbackDeliverer.java:13)

    to weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$ 2.run(DeploymentReceiverCallbackDeliverer.java:69)

    to weblogic.work.SelfTuningWorkManagerImpl$ WorkAdapterImpl.run (SelfTuningWorkManagerImpl.java:545)

    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)

    at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)

    : com.tangosol.net.RequestTimeoutException:Timeout during the startup of the service: ServiceInfo (Id = 0, name is Cluster, Type = Cluster

    Set of members = MasterMemberSet)

    ThisMember = null

    OldestMember = null

    ActualMemberSet = MemberSet (Size = 0

    )

    Member ID | ServiceVersion | ServiceJoined | Member State

    RecycleMillis = 1200000

    RecycleSet = MemberSet (Size = 0

    )

    )

    ).

    Operation on target oraclediagent Failed. Check the logs of errors for more details.

    Concerning

    Resolved in this thread.

    Cannot start the agent of the ODI JAVA EE on Linux

    Concerning

  • Discover the State of the agent (16) composer initialization error: impossible to activate the license of the software (expected 1650 seconds)

    Hello

    I have problem in View 4.5. When I create the new office with Windows 7 32 bit pool, pool automatic, floating, connected clone, fast prep. After the deployment of Windows 7 machines they had to customize report. After a few minutes's status has changed error (error state View Composer agent initialization (16): impossible to activate the license of the software (expected 1650 seconds))

    Could you please help me, where is the problem?

    I bought licenses for the view with the composer.

    My environment are:

    2 x vCenter server 4.0.0 build 258672 (windows 2008 r2 + Composer 2.5.0 - 291081)

    4 x 4 ESX u2 (2xESX by vCenter server)

    2 x display connection servers x86_64 - 4.5.0 - 293049 (Windows 2008r2) as a single environment. View environment using the server vCenter + 2 composers

    Thank you

    You have KMS license in effect for your Windows 7 Machines.  If this isn't the case, that is the question.

    You have 4 options:

    Option 1: Get KMS licenses in place for Microsoft Win7. -by far the easiest.

    Option 2: Use SYSPREP instead of QuickPrep

    Option 3: Add 1 at a time and activate the link manually clones b4 customization finishes - pain in the rear. Or be creative if it's your test env.

    Option 4: Hack the key "reg" activate this supossedly a composer. Here is the info:

    HKLMsystem/CurrentControlSet/services/vmware-viewcomposer-ga/SkipLicenseActivation to '1'.

    Of course the Win7 Office will be up to the period-eval evaluation mode expires but can be useful in a temporary unit or POC.

    The foregoing is not tested I tried it in my environment but do not know if it works because I don't want to mess with my installing any further until my POC is complete.  But it seems to work.  I found no key but went ahead and created.  Seems to work.

    Larry

  • Discover the State of the agent (18) composer initialization error: could not join the domain (expected 815 seconds)

    Hi all

    My Active Directory, View Manager, composer and vmware vcenter are all on windows 2008 R2.

    I took a spanshot of Windows XP SP3 with DHCP setting, installed vmware tools, see agent installed, firewall disabled, the Member of domain etc.

    When I tried to clone the snapshot XP to several XPs with the pool creation process it get error in personalization with error, below

    *03/10/10 18:01:49 IST: View Composer agent State (18) initialization error: could not join the domain (expected 815 seconds)*.

    Help, please.

    Thank you

    Selim Desai

    VCP410

    Take a look at http://communities.vmware.com/message/1613937

    the solution has been http://support.microsoft.com/kb/944043/en-us

    André

  • IPCC "the extension of the agent is out of service."

    We use IPCC 4.0 (3) _Build080, we have a new user in the system like everyone else. When this user tries to enter a ready state in the agent's Office, he gets the following error:

    13:16:20 cannot go to the ready state, while the phone is out of service. Other status changes are possible.

    --------------------------------------------

    13:16:20 that the extension of the agent is out of service.

    Ready state change and call control operations can be performed.

    I have the same problem occasionally. I use version 3.5. (2) and the solution for me was that I have deassociated users with user rm extensions and the agent itself. Then the extension associated with my id and then logged on to office and go into the ready state without any problem on the affected expansion.

    After I did I associate the extension with the rm user and the agent itself again, and it worked every time.

    I have no idea but why this happens, but it might have something to do with replication / connectio nbetween systems of IPCC and CCM.

    I hope that helps you!

  • Incompatibility of meter in the Agent in Foglight 5.6.4

    Hello

    We use Foglight 5.6.4 and there seems to be a problem with the meter of the Agent in the Performance Dashboard. When we look at the State of the Agent, it is show that 181 but when we have a glance at the dashboard of Performance it is showing that only 18.

    Could someone explain please the cause of this?

    Kind regards

    Guenoun

    Additional accessories:

    Don't know if you have made a lot of changes recently, but you should probably hit the "Refresh button" in the Agent status page without worrying that the status is a few days old. If that does nothing, maybe you stumbled upon a bug/glitch. Your DB_SQL_Server should be present under 'Other' in the second performance overview screen. There was also a second category, "OS", which contains all the former agents. That's assuming it's the same in 5.6.5 as 5.6.4 which I believe is the case.

  • How to start the agent on the database host computer that is being monitored

    Hi all
    I installed OEM 11.2.1.0. I stopped getting alerts after the 1 server node is restarted. I followed RAC database.
    When I checked the status of the host agent I get the following output
    [oracle@rs1pre91dvdba01 bin] $ pwd
    / u01/app/Oracle/agent11g/bin
    State of the agent emctl [oracle@rs1pre91dvdba01 bin] $
    ORACLE_UNQNAME environment variable not defined. Please install ORACLE_UNQNAME in unique name of database.
    [oracle@rs1pre91dvdba01 bin] $ export ORACLE_UNQNAME = MDM11
    State of the agent emctl [oracle@rs1pre91dvdba01 bin] $
    The MA Configuration problem. /U01/app/Oracle/product/11.2.0/dbhome_1/rs1pre91dvdba01_MDM11 not found.
    [oracle@rs1pre91dvdba01 bin] $

    And even on node 2
    [oracle@rs1pre91dvdba02 bin] $ pwd
    / u01/app/Oracle/agent11g/bin
    [oracle@rs1pre91dvdba02 bin] $ export ORACLE_UNQNAME = MDM12
    State of the agent emctl [oracle@rs1pre91dvdba02 bin] $
    The MA Configuration problem. /U01/app/Oracle/product/11.2.0/dbhome_1/rs1pre91dvdba02_MDM12 not found.

    Please can I know how to start the agent on the nodes and also auto how the boot process of the agent on the server restart

    Thank you.

    I assume that you have installed your agent in the directory

    / u01/app/Oracle/agent11g/bin

    If this is correct then run the following commands

    Export ORACLE_HOME = / u01/app/oracle/agent11g /.
    export LD_LIBRARY_PATH = / u01/app/oracle/agent11g/lib

    PATH = $ORACLE_HOME/bin:. : $PATH; export PATH

    As a matter of fact, you need to set the environment variables separate for the agent to execute commands
    which are related to the agent. These distinct environment must be set correctly to ensure that the
    commands can be found in the appropriate directories...

    Then, run the status command emctl agent...

  • Office State is waiting for the agent

    Dear all,

    I manually installed agent to view a VM comments (ESX4.1), which is managed by a Virtual Center.

    And then I add an individual office by the Administor Console view.

    The status of office is still waiting for the agent.

    Could you give points for this problem?

    Thank you

    Dennis Dai

    Two common reasons is firewall or DNS problems.

    Disable the local firewall and make sure nameresolution works in two ways.

    Best regards

    Linjo

    If you find this information useful, please give points to "correct" or "useful".

  • Increase the time of the ring on the phones of the Agent

    Hi Pros,

    I have an IPCC Express 4.0 Setup with CAD 6.1. When calling gets queued to an agent, if he does not respond within 3 rings, calls is redirected to a next available agent & agent moves to the State is not ready.

    Now, I want to increase the 3 rings to 5 rings. Is this possible? And if yes, then how do I do the same thing?

    Kind regards

    Pratik

    In the properties of the 'resource step select' or 'Connect' If you 'Connect', false to step "Select resource" you will see a 'Timeout' field The default value is 10 seconds. It is what controls how long the phone will ring at the Office of agents.

    Make sure that the timer is less than the response of IP phone ring if you have voice mail online agents (I recommend to have no voicemail on the line of the agent).

    See attached screenshot.

    Please evaluate the useful messages.

    adignan-

  • script checks to see if the agents are registered in

    Running of the IPCC 4.04

    Is there a way to do an if statement check to see if there is no agent connected to decide whether or not to send it to the queue, or send it to vmail. The case set out in General redirection and vmail, I can do. This is the part about checking to see if the agents are registered in what I need help with. Anyone have any ideas?

    You will need to use 'Get the Statisic of Reporting' and write the value in a field "int". Then, use an "if" statement to verify this value.

    From the 'get Statisic Reporting' use report object CSQ IPCC Express, field is logged resources. Row identifier is CSQ, you want to watch. Result of SEO is the "int" field you can watch with the "if" statement The attachment has an example.

    I hope this helps. Please rate if it does.

  • Rule to get the agent logs

    Hello

    I am trying to create a rule that generates an alarm whenever the data collection is stopped. I tried to choose the type of topology as "Agent of the State" to the scope of the variable as being "running but does not collect not data ' and 'AgentManagementSystemEventType' with the variable scope of 'stop data collection' but cannot write the condition that there is no specific property that can be learned from 'the Agent logs.

    I want to shoot the officer of newspapers so that each time, the agent is stopped, the alarm should be triggered.

    Kindly, let me know what "type of topology" should I choose and under "current execution status query" what condition and function must we tell to shoot to the top of all the agent logs that collect data.

    Thank you best regards &,.

    Shiva G

    Regarding "agent agent hosts.png", I would recommend that you upgrade to the current version of FglAM.

    Regarding "Fixing Agent showing X.png", I would recommend that you migrate far officers inherited from the BONES to the agent of the Infrastructure. When you select these agents and press "Start data collection", it does not work or stops again the agent? If it stops, the log file should tell you why.

    About scenario 1, a possibility would be to rule that fires if a particular measure has not been updated for a specific period of time. That could meet your needs?

    For scenario 2, you can set an alarm that goes off when he run the agent who does not collect data. It might be loud rule, since the stopping and starting of data collection can be considered a normal administration activity. If agents are stop on their own, I would rather find out you why and correct the underlying problem.

    Kind regards

    Brian Wheeldon

  • The current state of the target is down and it displays red arrow down in OEM 12 c. But in fact the database is running

    Hi all

    my instance of database shows down in OEM 12 c but in fact the database is running and status of the listener is unknown. What steps should I take to make the database appear?

    FYI,.

    The error is:

    The current state of the target is down. (I checked events tab in the incident handler here, it is showing error as "inaccessible agent (reason = unable to connect to the agent to https://sunshine.mad:3872/emd/main / [connection refused]).") host is accessible.

    A week before I made switch to digital, the basics of data, is that this is the reason why it shows this error? do we need to change any configuration after switching to the databases on OEM 12 c. at this point time of the database instance shows down and the listener to the top but suddenly the database and listener went wrong.

    Please help me, give your suggestions in this regard.

    Verify that the agent is in place and suggested downloading like Antonio. For the target of the database, the home page, go to the (Oracle database > Configuration target >) Configuration of the analysis page, check the monitoring parameters are correct and do a test connection. You can check the parameters of surveillance for the target of the listener as well.

    Kind regards

    -Loc

  • Try to collect events to a log file and the Agent installed Linux and work - need help.

    I modified liagent.ini by documentation... If I understand well it... actually I changed so many times my eyes hurt.

    Here it is:

    ; Configuration of the Agent of VMware Log Insight. Please save it in UTF-8 format if you use non-ASCII names / values!

    ; The actual configuration is this file that is associated with the server settings to form animal - effective .ini

    ; Note: The agent is not necessary to restart after making a configuration change

    ; Note: It may be more efficient to configure Server Agents page!

    [Server]

    hostname = 192.168.88.89

    ; Name of host or IP of your Server Log Insight / load balancing cluster. By default:

    ; hostname = LOGINSIGHT

    ; Protocol can be cfapi (Log Insight REST API), syslog. By default:

    proto = cfapi

    ; Server port connect Insight to connect to you. Default ports for protocols (TCP all):

    ; syslog: 514; syslog with ssl: 6514; cfapi: 9000; cfapi with ssl: 9543. By default:

    port = 9000

    ; Use SSL. By default:

    SSL = no.

    ; Example of configuration with the certification authority:

    ; SSL = yes

    ; ssl_ca_path=/etc/PKI/TLS/certs/CA.PEM

    ; Time in minutes to force the reconnection to the server.

    ; This option reduces the imbalances caused by the long lifetime as TCP connections. By default:

    Reconnect = 30

    [record]

    ; Logging detail level: 0 (no debug messages), 1 (essentials), 2 (verbose with more impact on performance).

    ; This option should always be 0 in normal conditions. By default:

    debug_level = 1

    [storage]

    ; Local max storage expiration (data + logs) in the valid range MBs.: 100-2000 MB.

    max_disk_buffer = 2000

    ; Uncomment the appropriate section to collect log files

    ; The recommended method is to activate the content pack Linux server LI

    [filelog | bro]

    Directory = / data/bro/newspapers/2015-03-04

    ; include = * .log

    parser = auto



    I post it here, I have created a support pack?


    Post edited by: I added a screenshot of the status of the personnel of kevinkeeneyjr

    Post edited by: kevinkeeneyjr added liagent.ini

    Ah! Yes, the agent is to collect real-time events. If no new event is written then it won't work. If you want to collect logs that have been generated before you use the importer of Log insight which was published with LI 3.3. I hope this helps!

  • the agent versions report

    Is there a report that lists the versions of Appassure Agent running in an environment?

    THX

    Hi Alice,.

    There is no report, but you can use the API to get the version of the agent

    https://[core IP]: 8006/apprecovery/api/base/agents / [agent id] / metadata

    To get the IDs of the agents, you can use next API call

    https://[core ip]: 8006/apprecovery/api/base/agents.

    Here is the example of the Powershell script to show agents version

    $ids = call restmethod "https://[Core IP]: 8006/apprecovery/api/base/agents / ' - GET method - usedefaultcredentials

    for ($i = 0; $i - lt $ids.agents.agent.count; $i ++)

    {

    $link = "https:// [Core IP]:8006/apprecovery/api/core/agents/"+$ids.agents.agent[$i].id+"/metadata"

    $metadata = call restmethod $link - GET method - usedefaultcredentials

    $output = $metadata.agentMetadata.hostName + ":" + $metadata.agentMetadata.version._Major + "." + $metadata.agentMetadata.version._Minor + "." + $metadata.agentMetadata.version._Build + "." + $Metadata.agentMetadata.version._Revision ".

    $output

    }

    Output of the script will be

    Host name: Version

    NOTE: in the script used "-usedefaultcredentials" parameter. This is Dell-AppAssure based credentials. If Powershell isn't running for admin you must specify administrative credentials.

    NOTE: The request may fail with the "the underlying connection was closed: could not establish trust relationship for the SSL/TLS.

    That indicates topics with certificate validation.

    You can disable the validation of certificate with order

    [System.Net.ServicePointManager]: ServerCertificateValidationCallback = {$true}

    Thank you

    Anton Kolomiiets

  • Cloud new control panel - unable to connect to the agent

    I'm done just to install the last control of cloud 12.1.0.3 by following oracle document e22624.

    Everything installed fine and I am able to connect to the cloud control. I manually added a target (our test server). The installation was successful without error.

    However the cloud control shows: error of assessment metrics start - unable to connect to the agent to https://server:3872/emd/main / [Connection timed out: connect]


    I ran the following on the test server to make sure that the management agent runs:

    /opt/app/oracle/product/12.1.0/agent/core/emctl status agent

    and I see this:

    Oracle Enterprise Manager 11g Database Control Release 11.2.0.3.0

    Copyright (c) 1996, 2011 Oracle Corporation.  All rights reserved.

    ---------------------------------------------------------------

    Agent version: 10.2.0.4.4

    Version of the WHO: 10.2.0.4.4

    Protocol version: 10.2.0.4.4

    Agent home: /opt/app/oracle/product/11.2.0/dbhome_1/server_test

    File binary agent: /opt/app/oracle/product/11.2.0/dbhome_1

    Agent process ID: 24514

    Parent process ID: 23632

    Agent URL: https://server:3938/emd/main

    Repository URL: https://server:1158/em/upload /

    Starts at: 2013-11-15 13:16:53

    Started by user: oracle

    Last reload: 2013-11-15 13:16:53

    Last download successful: 2013-11-15 14:34:02

    Total megabytes of XML files uploaded so far: 2.68

    Number of XML, waiting for loading files: 0

    Size of the XML files in the upload wait (MB): 0.00

    Available disk space on the file upload system: 81.34%

    Directory to upload Data channel: /opt/app/oracle/product/11.2.0/dbhome_1/server_test/sysman/recv

    Last pulse in SGD: 2013-11-15 14:36

    ---------------------------------------------------------------

    Agent is running and ready

    According to state that something is wrong. The test server is currently installed OEM Database Control. The directions said nothing about not being able to install Cloud control and have control OEM database.


    My question is this: can I have the OEM Database Control and control of Cloud? If this is not the case, what should I do to get the Cloud control to work?


    Thank you

    I opened a support ticket with Oracle. It was that the firewall is blocking communication from the SGD server to the agent. Everything works now as expected.

Maybe you are looking for