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 188.8.131.52.0 to 184.108.40.206.0 [Release 13.2 to 13c]
Information in this document applies to any platform.
Following incidents are generated intermittently from EM 13c Cloud Control
Target type=Automatic Storage Management
Message=Failed to connect to ASM instance. The connection is closed: The connection is closed
Event reported time=Feb 10, 2017 12:40:54 AM EST
Target Lifecycle Status=Test
Customer Support Identifier=9999999
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
$AGENT_INST_HOME/sysman/gcagent.log reports following errors:
java.sql.SQLException: The connection is closed: The connection is closed
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).
$jstack <Agent PID>|grep "Timer-"|wc -l
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).
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