My Oracle Support Banner

EM 13c: ASM Incident Reported with Message=Failed To Connect To ASM Instance. The Connection Is Closed: The Connection Is Closed (Doc ID 2251591.1)

Last updated on SEPTEMBER 23, 2020

Applies to:

Enterprise Manager for Oracle Database - Version 13.2.0.0.0 to 13.4.0.0.0 [Release 13.2 to 13c]
Information in this document applies to any platform.

Symptoms

Following incidents are generated intermittently from EM 13c Cloud Control

Host=host.company.com
Target type=Automatic Storage Management
Target name=+ASM_host.company.com
Categories=Availability
Message=Failed to connect to ASM instance. The connection is closed: The connection is closed
Severity=Fatal
Event reported time=Feb 10, 2017 12:40:54 AM EST
Target Lifecycle Status=Test
Customer Support Identifier=9999999
Operating System=AIX
Platform=powerpc
Associated Incident Id=1669
Associated Incident Status=New
Associated Incident Owner=
Associated Incident Acknowledged By Owner=No
Associated Incident Priority=None
Associated Incident Escalation Level=0
Event Type=Target Availability
Event name=Status
Availability status=Down

$AGENT_INST_HOME/sysman/gcagent.log reports following errors:

[65336:GC.Executor.126 (osm_instance:+ASM__host.company.com:ofs_performance_metrics) (osm_instance:+ASM__host.company.com:ofs_performance_metrics:Instance_Volume_Performance)] ERROR - The connection is closed: The connection is closed
java.sql.SQLException: The connection is closed: The connection is closed
at oracle.ucp.util.UCPErrorHandler.newSQLException(UCPErrorHandler.java:464)
at oracle.ucp.util.UCPErrorHandler.newSQLException(UCPErrorHandler.java:448)
at oracle.ucp.jdbc.proxy.JDBCConnectionProxyFactory.invoke(JDBCConnectionProxyFactory.java:307)
at oracle.ucp.jdbc.proxy.ConnectionProxyFactory.invoke(ConnectionProxyFactory.java:50)
at com.sun.proxy.$Proxy27.prepareCall(Unknown Source)

 
Also, if a thread dump is taken on the EM agent process, a huge number of "Timer-" threads are observed (which are increasing over time and never getting closed/finished).

Example:

$jstack <Agent PID>|grep "Timer-"|wc -l
983

Note: as a rule of thumb, the number of "Timer-" threads should be pretty constant over time, less than 50, however this is an approximate value as it depends on the number of targets, monitoring settings, jobs executed and many other factors. The key factor is to see an approximately constant number of such threads over time (days).

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.