Dead Connection Detection used to avoid firewall timeout between client and server
Hi,
in MOS Note "How to Check if Dead Connection Detection (DCD) is Enabled in 9i, 10g and 11g [ID 395505.1]" it is explained how Dead Connection Detection is triggered, by giving an example where SQLNET.EXPIRE_TIME=2.
Suppose there is a firewall between the client and the server which has configured a certain timeout, so the firewall cuts the TCP session between the client and the server after x minutes of inactivity (no packets send or received during x minutes).
If I understand well, I see it is possible that the session is cut even SQLNET.EXPIRE_TIME < x.
For example, after login there could be no activity for almost 4 minutes, as the DCD packet is not sent until minute 4. So if x=3, the firewall is going to cut the connection even though SQLNET.EXPIRE_TIME=2.
Suppose there is a firewall between the client and the server which has configured a certain timeout, so the firewall cuts the TCP session between the client and the server after x minutes of inactivity (no packets send or received during x minutes).
If I understand well, I see it is possible that the session is cut even SQLNET.EXPIRE_TIME < x.
For example, after login there could be no activity for almost 4 minutes, as the DCD packet is not sent until minute 4. So if x=3, the firewall is going to cut the connection even though SQLNET.EXPIRE_TIME=2.
0