Oracle Net SQLNET.SEND_TIMEOUT and SQLNET.RECV_TIMEOUT Parameters and errors ORA-12170 TNS-12535 ORA-12609 ORA-12608
(Doc ID 1335630.1)
Last updated on JANUARY 16, 2025
Applies to:
Oracle Net Services - Version 11.1.0.6 and laterOracle Database - Enterprise Edition - Version 11.1.0.7 and later
Oracle Cloud Infrastructure - Exadata Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Gen 2 Exadata Cloud at Customer - Version N/A and later
Information in this document applies to any platform.
Symptoms
The Alert log is reporting the error codes.
(Please note from 11g onwards Sqlnet.log for RDBMS side, reports net errors in the Alert.log due to ADR)
But this does not mean the issue is solely a TCP one. Socket was attempted to be used and failed.
Changes
SQLNET.RECV_TIMEOUT and / or SQLNET.SEND_TIMEOUT set in the client / server SQLNET.ORA files
SQLNET.RECV_TIMEOUT is not set by default. It introduces an idle timer when used on the server side. This is often not understood when implemented.
Since the server side process is in RECV mode whenever it is waiting on work from the client, if the client is to go idle then that timer is clocking and can be hit therefore causing idle disconnections.
Therefore the parameter really should not be set on the server side.
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 |
| Changes |
| Cause |
| Solution |