[EM 13.2]: Agent On Windows Server Monitoring SQL Server Target Shows High Java Memory Usage

(Doc ID 2397137.1)

Last updated on JULY 07, 2018

Applies to:

Enterprise Manager Base Platform - Version 13.2.0.0.0 and later
Information in this document applies to any platform.

Symptoms

High memory usage is observed on window server running 13.2 agent monitoring SQL server targets.

Following are the frequent errors seen in <AGENT_INST_HOME>/sysman/log/gcagent_errors.log:
===============
2018-05-01 22:22:04,749 [148414:GC.Executor.66248 (microsoft_sqlserver_database:tdcmstabsql:Locks) (microsoft_sqlserver_database:tdcmstabsql:Locks:Locks)] ERROR - Result set exceeded max flood control level
2018-05-01 22:22:04,750 [148414:GC.Executor.66248 (microsoft_sqlserver_database:tdcmstabsql:Locks) (microsoft_sqlserver_database:tdcmstabsql:Locks:Locks)] ERROR - microsoft_sqlserver_database:tdcmstabsql:Locks:Locks
java.lang.UnsupportedOperationException: Collection Result Maximum Flood Control Level Exceeded
at oracle.sysman.emSDK.agent.datacollection.CollectionResult.performFloodControl(CollectionResult.java:445)
===================

Changes

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