SQLNET RECV TIMEOUT and SEND TIMEOUT cause end of file communication

SQLNET RECV TIMEOUT and SEND TIMEOUT cause end of file communication

I am getting the end of file communication error to one of my client, On checking the SQLNET files on both Client and DB server we found the following two parameter set:

SQLNET.SEND_TIMEOUT=600
SQLNET.RECV_TIMEOUT=60000

Solution
“end of file communication” error that client were getting, which was resolved after I commented out the following 2 parameter in sqlnet.ora

#SQLNET.SEND_TIMEOUT=600
#SQLNET.RECV_TIMEOUT=60000

SQLNET.RECV_TIMEOUT and SQLNET.SEND_TIMEOUT, we can have them both on client and server side.

Explain about both Parameter
SQLNET.RECV_TIMEOUT
If we have on the server side SQLNET.RECV_TIMEOUT=1, it means that if the database doesn’t receive a request, package exchange in 1 seconds from the client,
the connection with that client is terminated or timeout.

SQLNET.SEND_TIMEOUT
If SQLNET.SEND_TIMEOUT=1 and if the database cannot complete the send operation to the client in 1 second, the connection is timeout.

Note:
The general troubleshoot for this issue is to increase the value of those parameter or don’t use it.
but if still you want to use them you need to increase the SQLNET.SEND_TIMEOUT=600 to a higher value.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.