Grid Control Performance: Troubleshooting OMS Restarts due to CacheManager thread Timeout
(Doc ID 1291954.1)
Last updated on NOVEMBER 09, 2019
Applies to:Enterprise Manager Base Platform - Version 10.2.0.5 to 10.2.0.5 [Release 10.2]
Information in this document applies to any platform.
This is a continuation of Note 1184124.1.
Base on the diagnostic messages collected from users following Note 1184124.1, we have identified that the hung connection is connected to one of databases (target databases) the user is monitoring through OMS, not the repository database. That explains why we can never see the hung connection in the session table of the repository database.
At this point, we have concluded that the cause of the hang is related to the firewall setup between the OMS server and the target databases. We have observed a pattern that a connection is always left idle for a long period of time varies from 5 to 24 hours before it is closed and hung. Firewall timeout for idle connections may have severed the connection sockets. This can cause JDBC applications to hang while waiting for the communications to finish.
Most users are unable to provide the information about their firewall settings. We recommend the following exercise to further troubleshoot the issue.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!