-
Title
Intermittent Oracle usability alarms with "Network Adapter could not establish the connection" error messages -
Description
DBO Usability alarms fire however when checking the instances there does not appear to be any connection issues.
The database agent logs indicate a networking issue between the FglAM and host with the connection reestablished five minutes later (DBO_Usability):
com.quest.qsi.fason.core.errorhandling.AgentConnectionException: The Network Adapter could not establish the connection- Profile:OracleProfile{host='HOSTNAME.DOMAIN.COM', instance='INSTANCE', username='USERNAME', asSysDBA=false, ports='49125', Socket read timeout=900000, QueryTimeout=600} Caused by: java.net.ConnectException: Connection refused
-
Cause
All agent logs show that a single connection attempt failures, and the next attempt being successful. The reasons for these failures appear to be network-related, such as timeouts or connection resets. This is probably caused by short network glitches or Oracle listener not allowing new connections at that particular point of time.
-
Resolution
In the agent properties (Administration | Agents | Agent Status), the change the DB Connection Timeout (milliseconds) was increased from 60000 to 180000.
- Navigate to the Administration | Agent Status page
- Edit the Properties for the DB_Oracle_RAC_Instance agent
- Modify the properties for the current agent
- Change the setting for "DB Connection Timeout " to 180000
- Click Save at bottom right of the page.