My Oracle Support Banner

No Performance Related Data Showing In OEM13c For 12.2.1.3 Standalone OHS Monitoring (Doc ID 2565651.1)

Last updated on OCTOBER 17, 2019

Applies to:

Enterprise Manager for Fusion Middleware - Version 12.2.1.3.0 to 12.2.1.3.0 [Release 12c]
Oracle HTTP Server - Version 12.2.1.3.0 to 12.2.1.3.0 [Release 12c]
Oracle WebLogic Server - Version 12.2.1.3.0 to 12.2.1.3.0 [Release 12c]
Information in this document applies to any platform.

Symptoms

No performance related data showing in oem13c for Standalone OHS
OHS version->12.2.1.3
OEM version-> 13.2.0.0.0

 

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

[<OEM_AGENT_USER>@<HOSTNAME> bin]$ ./emctl getmetric agent <OHS_TARGET_NAME>,oracle_apache,ResourceUsage
Oracle Enterprise Manager Cloud Control 13c Release 2
Copyright (c) 1996, 2016 Oracle Corporation.  All rights reserved.
cpuTime.value,upTime.value,numProcessors.value,memory.component,memoryPercentage.component,cpu.component
,,,0,0,

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

[<OEM_AGENT_USER>@<HOSTNAME>1 bin]$ ./emctl control agent runCollection <OHS_TARGET_NAME>:oracle_apache general_collection
Oracle Enterprise Manager Cloud Control 13c Release 2
Copyright (c) 1996, 2016 Oracle Corporation.  All rights reserved.
---------------------------------------------------------------
EMD runCollection error:
general_collection:ohs_server:em_result=Error:
 Initializing WebLogic Scripting Tool (WLST) ...

 Welcome to WebLogic Server Administrat...be non-empty
 STATUS=FAIL|FAILED TO CONNET TO NODE MANAGER

 Exiting WebLogic Scripting Tool.

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

Filename: gcagent.log

2019-07-09 19:30:15,825 [2304:90A6BED8:GC.OnDemand.137 (Real-Time Metric Request;xxxxxxxx;ohs_server)] INFO - em_result=Error:
 Initializing WebLogic Scripting Tool (WLST) ...
 
 Welcome to WebLogic Server Administrat...be non-empty
 STATUS=FAIL|FAILED TO CONNET TO NODE MANAGER
 
 
 Exiting WebLogic Scripting Tool.
 
 oracle.sysman.emSDK.agent.fetchlet.exception.FetchletException: em_result=Error:
 Initializing WebLogic Scripting Tool (WLST) ...
 
 Welcome to WebLogic Server Administrat...be non-empty
 STATUS=FAIL|FAILED TO CONNET TO NODE MANAGER
 
  Exiting WebLogic Scripting Tool.
 
    at oracle.sysman.gcagent.addon.fetchlet.osfetchlet.BaseOSFetchlet.getOSMetric(BaseOSFetchlet.java:1041)
    at oracle.sysman.gcagent.addon.fetchlet.osfetchlet.BaseOSFetchlet.getMetric(BaseOSFetchlet.java:459)
    at oracle.sysman.gcagent.target.interaction.execution.FetchletFactory.getMetric(FetchletFactory.java:433)

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

Tried to connect wlst with OEM user and it is throwing

<OHS Home>/oracle_common/common/bin/wlst.sh

wls:/offline> nmConnect(domainName='<OHS_DOMAIN_NAME>', username='<NM_USERNAME>', password='<NM_PASSWORD>', host='', port=<NM_PORT>, nmType='ssl')

Connecting to Node Manager ...
Traceback (innermost last):
  File "<console>", line 1, in ?
  File "<iostream>", line 111, in nmConnect
  File "<iostream>", line 240, in raiseWLSTException
WLSTException: Error occurred while performing nmConnect : Cannot connect to Node Manager. : java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty
Use dumpStack() to view the full stacktrace :
wls:/offline>

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

When tried to connect NM with ohs process user, then it is connecting successfully.

 

 

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Changes
Cause
Solution
References


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