12c Cloud Control: Agent Target is not Seen in the Console After a Successful Installation (Doc ID 1384802.1)

Last updated on AUGUST 19, 2016

Applies to:

Enterprise Manager Base Platform - Version 12.1.0.1.0 and later
Information in this document applies to any platform.
Checked for relevance on 15-Oct-2013

Symptoms

12.1.0.1 Agent has been newly installed on a machine using one of the installation methods like Push-Agent or silent Agent installation. Agent installation is successfully completed and is able to start but the Agent target is not visible in the 12c Cloud Console.

-  The Agent is started and running:

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/app/oracle/12.1.0
Agent Binaries : /u01/app/oracle/12.1.0/core/12.1.0.1.0
Agent Process ID : 7643
Parent Process ID : 7603
Agent URL : https://<agentmachine.domain>:3872/emd/main/
Repository URL : https://<omsmachine.domain>:4900/empbs/upload
Started at : 2011-11-26 11:47: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 : 1
Size of XML files pending upload(MB) : 0
Available disk space on upload filesystem : 21.66%
Collection Status : Collections enabled
Last attempted heartbeat to OMS : 2011-11-26 11:47:33
Last successful heartbeat to OMS : 2011-11-26 11:47:33
---------------------------------------------------------------
Agent is Running and Ready

-  The communication between the Agent and OMS machine is fine as seen in:

emctl pingOMS
Oracle Enterprise Manager 12c Cloud Control 12.1.0.1.0
Copyright (c) 1996, 2011 Oracle Corporation. All rights reserved.
---------------------------------------------------------------
EMD pingOMS completed successfully

The communication between Agent and OMS is working both the ways. Also the OMS upload port and the Agent port is open and accessible i.e no firewall blocking the communication.

-  Attempting a manual upload from the Agent fails with:

cd <AGENT_HOME>/bin
emctl upload agent
Oracle Enterprise Manager 12c Cloud Control 12.1.0.1.0
Copyright (c) 1996, 2011 Oracle Corporation. All rights reserved.
---------------------------------------------------------------
EMD upload error:full upload has failed: Upload timed out before completion.
Number of files to upload before the uploadNow call: 1, total size (MB): 5.1784515E-4
Remaining number of files to upload: 1, total size (MB): 5.1784515E-4 (TIMEOUT)

-  The <AGENT_INST>/sysman/log/gcagent.log file shows:

<timestamp> [54:A60A3E87] INFO - >>> Dispatching request: UploadRequest (waitTime:-1) <
<timestamp> [54:A60A3E87] INFO - >>> Reporting exception: oracle.sysman.emSDK.agent.client.exception.UploadException: Upload timed out before completion.
Number of files to upload before the uploadNow call: 1, total size (MB): 5.1784515E-4
Remaining number of files to upload: 1, total size (MB): 5.1784515E-4 (TIMEOUT) (request id 1) <

-   The <EM_CONFIG_HOME>/em/EMGC_OMS1/sysman/log/emoms_pbs.trc on the OMS machine shows:

<timestamp> [[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'] ERROR gcloader.Receiver logp.251 - Couldn't get agent guid with given emdUrl:https://agentmachine.domain:3872/emd/main/
java.sql.SQLException: ORA-01403: no data found
ORA-06512: at "SYSMAN.EMD_LOADER", line 713
ORA-06512: at line 1

In DEBUG level, the emoms_pbs.trc shows:

<timestamp> [[ACTIVE] ExecuteThread: '22' for queue: @ 'weblogic.kernel.Default (self-tuning)'] DEBUG gcloader.ResourceManager logp.251 - Received priority value as 2 of data type:metadata for emd:https://<agentmachine.domain:<port>/emd/main/
<timestamp> [[ACTIVE] ExecuteThread: '22' for queue: @ 'weblogic.kernel.Default (self-tuning)'] DEBUG gcloader.ResourceManager logp.251 - Failed to get resource for agent:https://<agentmachine.domain:<port>/emd/main/priority2 dataTypemetadata

Changes

All existing Agents in the Cloud Console have one or more targets whose Lifecycle Status is set to Production or Mission Critical.

To verify, login to the Repository Database as the sysman user and execute:

SQL> SELECT COUNT(*), priority
FROM ( SELECT t.emd_url as emd_url, nvl(min(pe.priority),3) as priority
FROM em_global_Target_properties tp, mgmt_Targets t, gc_lifecycle_states pe
WHERE t.target_guid=tp.target_guid and t.emd_url is not null
and tp.lifecycle_status = pe.display_name(+) group by t.emd_url)
group by priority;

count(1) priority
-------- --------
       1        1
       1        2


where priority 1= Mission Critical and 2=Production.

To get the list of targets which have the above lifecycle status:

SQL> select target_name, target_type, emd_url from mgmt_targets where target_guid in (select target_guid from em_global_target_properties where lifecycle_status in ('Production', 'MissionCritical'));

TARGET_NAME           TARGET_TYPE  EMD_URL
--------------------  -----------  ---------------------------------------
agentmachine1.domain  host         https://agentmachine1.domain:1830/emd/main/
agentmachine2.domain  host         https://agentmachine2.domain:3873/emd/main/


In this particular setup, there are only 2 Agents discovered in the Cloud Console and each Agent has one target each where the Lifecycle Status is set to Production or Mission Critical.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms