Expire_time Sqlnet.ora 19c [updated] May 2026

The value is in . A setting of 10 means the server will send a probe every 10 minutes. 3. Restart Listener (Not Required, but Recommended) Actually, sqlnet.ora changes take effect for new connections only . Existing sessions will not inherit the new setting.

In Oracle 19c, the classic Dead Connection Detection (DCD) mechanism, configured via expire_time in sqlnet.ora , remains the most reliable way to solve this.

One of the most frustrating issues for any DBA or application owner is the dreaded "hung session" — a database connection that appears active but is actually dead due to a network failure, firewall timeout, or client crash. expire_time sqlnet.ora 19c

lsnrctl stop lsnrctl start Check an active session’s DCD setting:

Check your 19c database servers:

lsnrctl reload Or for a clean start:

grep expire_time $ORACLE_HOME/network/admin/sqlnet.ora If it returns nothing, add expire_time = 10 and sleep better tonight. Have you seen unexpected session cleanup due to network latency? Or do you combine expire_time with DCD on the listener? Share your experience below! The value is in

To be safe: