My Oracle Support Banner

Changing Thresholds In Metric And Collection Settings Page Fails With Unable To Communicate With The Agent (Doc ID 2641400.1)

Last updated on APRIL 03, 2020

Applies to:

Enterprise Manager for Oracle Database - Version 13.1.0.0.0 and later
Information in this document applies to any platform.

Symptoms

While updating thresholds in Metric and Collection settings for db target fails with error "Unable to communicate with the agent.The agent may be down",

but the agent is up and running fine. noticed following error messages in gc_inst/em/EMGC_OMSn/sysman/log/emoms.log

020-01-14 02:16:54,840 [EMUI_02_16_40_/console/metrics/target/metricThresholds] ERROR target.TargetSettings save.653 - TargetSettings : save : Exception : Target Name = <DB_Name> Target Type = rac_database Exception in target settings
oracle.sysman.emSDK.emd.comm.CommException: Client http request is improper [413 : Request Entity Too Large]
at oracle.sysman.eml.metrics.target.CollectionUtil.restoreMextsOnTargetComponent(CollectionUtil.java:2028)
at oracle.sysman.eml.metrics.target.CollectionUtil.syncReposAgents(CollectionUtil.java:2295)
at oracle.sysman.eml.metrics.target.CollectionUtil.syncReposAgents(CollectionUtil.java:2457)
at oracle.sysman.eml.metrics.target.CollectionUtil.syncReposAgents(CollectionUtil.java:2533)
at oracle.sysman.eml.metrics.target.TargetSettings.save(TargetSettings.java:459)
at oracle.sysman.eml.metrics.target.MonitoringSettingsController.handleOKEvent(MonitoringSettingsController.java:738)
at oracle.sysman.eml.metrics.target.MonitoringSettingsController.handleEvent(MonitoringSettingsController.java:307)

2020-01-14 02:16:54,958 [EMUI_02_16_40_/console/metrics/target/metricThresholds] WARN target.MonitoringSettingsController handleOKEvent.742 - Client http request is improper [413 : Request Entity Too Large]
oracle.sysman.emSDK.emd.comm.CommException: Client http request is improper [413 : Request Entity Too Large]
at oracle.sysman.eml.metrics.target.CollectionUtil.restoreMextsOnTargetComponent(CollectionUtil.java:2028)
+++++++++

On the monitoring agent, /agent/agent_inst/sysman/log/gcagent.log

2020-01-18 00:59:15,691 [1079015:9A57E12:HTTP Listener-1079015] DEBUG - *jetty*: HEADER --> HEADER_IN_NAME

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
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.