-
Title
"An existing connection was forcibly closed by the remote host" errors for Oracle within 0ms of authentication -
Description
The Oracle agent fires usability connection availability alarms within zero milliseconds of making a connection to the Oracle host.
The connection to the instance XXX failed. Failed to establish a Oracle JDBC connection protocol to Host [HOSTNAME], user account [sys]. Reason: [IO Error: An existing connection was forcibly closed by the remote host, Authentication lapse 0 ms.- Profile:OracleProfile{host='HOSTNAME', service='service_name', username='sys', asSysDBA=true, ports='1521', useSSL=false, properties={oracle.jdbc.ReadTimeout=900000}}]. . [Oracle Error Code = 17002. SQL state : 08006]
-
Resolution
RESOLUTION 1
Configure the security group in Oracle correctly for access to the instance and database.
RESOLUTION 2
Check the SQLNET.ORA file to see if it has tcp.validnode_checking=yes. Valid node checking allows or denies access from specified IP addresses to Oracle services. Set tcp.validnode_checking=no and restart the database listener.
RESOLUTION 3
Change the connection setting to use SID instead of service name
RESOLUTION 4
Review the TNS listener log and correct any errors found.
RESOLUTION 5
Check if SQLNET.IGNORE_ANO_ENCRYPTION_FOR_TCPS=TRUE on the database. Double encryption is not allowed in JDBC. Turn off this setting or do not use TLS encryption in combination.
RESOLUTION 6
Workaround
When oracle databases are forced to use SSL, Dataguard fails to connect using SSL, Please contact Support for a hot-fix.
Status
Defect ID FOG-5260 has added in the 6.3 and higher releases of the Oracle cartridge -
Defect ID
FOG-5260