EM 12c: Enterprise Manager 12.1.0.3 Cloud Control Targets are Showing Pending Status after Discovery (Doc ID 1617162.1)

Last updated on FEBRUARY 19, 2020

Applies to:

Symptoms

• Enterprise Manager (EM) Cloud Control 12.1.0.3
• Some targets are showing pending status after promotion or discovery from EM console
• Targets do not appear as valid targets from agent side, no relevant target entries in <AGENT_INST_HOME>/sysman/emd/targets.xml
• The following error message appear in <AGENT_INST_HOME>/sysman/log/gcagent.log
  
  
  2014-01-23 12:30:11,801 [33:5A529028] INFO - >>> Reporting exception: oracle.sysman.emSDK.agent.client.exception.NoSuchTargetException: the <target_type> target target_name> does not exist (request id 1) <<<
  oracle.sysman.emSDK.agent.client.exception.NoSuchTargetException: the <target_type> target <target_name> does not exist
      at oracle.sysman.gcagent.dispatch.cxl.GetCollectionLevelsAction.satisfyRequest(GetCollectionLevelsAction.java:63)
   
• No discovery entries for affected targets appear in <AGENT_INST_HOME>/sysman/log/gcagent_mdu.log (Just Agent and Host targets discovery entries appear)
  
  
  2014-01-17 10:41:12,194 [34:B652AE52] INFO - SAVE TARGET(S)
  <Target TYPE="host" NAME="<target_name>" DISPLAY_NAME="<target_name>" ON_HOST="" EMD_URL="<AGENT_URL>" TIMEZONE_REGION="" IDENTIFIER="TARGET_GUID=<TARGET_GUID>"/>
  <Target TYPE="oracle_emd" NAME="<target_name>" DISPLAY_NAME="<target_name>" ON_HOST="" EMD_URL="<AGENT_URL>" TIMEZONE_REGION="" IDENTIFIER="TARGET_GUID=<TARGET_GUID>"/>
  2014-01-17 10:41:15,207 [34:B652AE52] INFO - SUCCESS
  2014-01-17 10:41:15,207 [34:B652AE52] INFO - SUCCESS
• The following error(s) appear in "repvfy verify -level 9" dump
  
  
  2006. Duplicate target promotion jobs
  =--------- ---------- ---------- ---------- ---------- ---------- ---------=
  = Action:
  = - Run the fix routine:
  =   $ repvfy verify jobs -test 2006 -fix
  =--------- ---------- ---------- ---------- ---------- ---------- ---------=
  
  6007. Insufficient number of job workers db connection
  =--------- ---------- ---------- ---------- ---------- ---------- ---------=
  = Action:
  = - Set the OMS property on each OMS to the recommended value:
  =   $ emctl set property -name oracle.sysman.core.conn.maxConnForJobWorkers -value <recommended>
  =--------- ---------- ---------- ---------- ---------- ---------- ---------=
  OMS_NAME                                               OMS_ID    SYSSIZE   LONGSIZE      CONNS RECOMMENDATION
  -------------------------------------------------- ---------- ---------- ---------- ---------- --------------
  <oms_host>                                                          1         25         10         25             50
  1 row selected.
  
  7004. Obsolete worker trace parameters
  =--------- ---------- ---------- ---------- ---------- ---------- ---------=
  = Action:
  = - Run the fix routine:
  =   $ repvfy verify repository -test 7004 -fix
  =--------- ---------- ---------- ---------- ---------- ---------- ---------=
  
  7007. Obsolete job metric staging data
  =--------- ---------- ---------- ---------- ---------- ---------- ---------=
  = Action:
  = - Run the fix routine:
  =   $ repvfy verify jobs -test 7007 -fix
  =--------- ---------- ---------- ---------- ---------- ---------- ---------=

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.