Database Link Session remains active despite network failure
updated on October 4, 2024By Christian Pfundtner
An application uses a procedure call via a database link. If a network failure occurs, the database link remains open and the session waiting for the result of the procedure hangs.
This behavior is basically due to the TCP/IP protocol, which works stateless (i.e. without ongoing verification). If this were not the case, the Internet would be overloaded by permanent session verifications.
Oracle offers a solution for this. If you SQLNET.EXPIRE_TIMEconfigure it in SQLNET.ORA, this means that when a client connects, the server checks every specified number of minutes to see if the client is still responding. Typically, iraq telegram data values in the range between 5 and 30 (minutes) are used here. This is also important because otherwise a firewall between the client and the database server would eventually discard the session - usually after 1-2 hours of inactivity.
between two databases, the setting is unfortunately SQLNET.EXPIRE_TIMEnot taken into account.