When the application is not used for a significant amount of time, the firewall setting between database & application server closes physical connection between application & database.

This will invalidate the connection in connection pool. To detect such dead connections we can make use of EXPIRE_TIME parameter.

So if the value of this parameter is specified as 1, sqlnet will send a probe after every 1 minute to check the connection validity. Oracle recommends setting the value of this parameter to a non-zero value.

August 15th – Network guys updated Cisco switches and routers with software/firmware upgrades with planned downtime. Life seems normal up to this point.

I start getting complaints from endusers that our ERP is slow, freezing, etc. At this point we suspect the switchover to new hardware.  But we had made so many changes which one could it be?  I see a 10% increase in waits related to the redo logs (log file parallel write). So I moved the redo logs to unencrypted filesystem area….made no difference, moved them back.   I could reset the DB_ULTRA_SAFE to improve performance but that requires a database cycle.

By the way when mentioning encrypted native filesystems…this is Oracle’s answer to a Support ticket asking about compatibility.

Missed an Office Hours session?. That's OK - we record them and publish them so you can catch up at your leisure. See recorded sessions here . Question and Answer Thanks for the question, Om.

When the application is not used for a significant amount of time, the firewall setting between database & application server closes physical connection between application & database.

This will invalidate the connection in connection pool. To detect such dead connections we can make use of EXPIRE_TIME parameter.

So if the value of this parameter is specified as 1, sqlnet will send a probe after every 1 minute to check the connection validity. Oracle recommends setting the value of this parameter to a non-zero value.

When the application is not used for a significant amount of time, the firewall setting between database & application server closes physical connection between application & database.

This will invalidate the connection in connection pool. To detect such dead connections we can make use of EXPIRE_TIME parameter.

So if the value of this parameter is specified as 1, sqlnet will send a probe after every 1 minute to check the connection validity. Oracle recommends setting the value of this parameter to a non-zero value.

August 15th – Network guys updated Cisco switches and routers with software/firmware upgrades with planned downtime. Life seems normal up to this point.

I start getting complaints from endusers that our ERP is slow, freezing, etc. At this point we suspect the switchover to new hardware.  But we had made so many changes which one could it be?  I see a 10% increase in waits related to the redo logs (log file parallel write). So I moved the redo logs to unencrypted filesystem area….made no difference, moved them back.   I could reset the DB_ULTRA_SAFE to improve performance but that requires a database cycle.

By the way when mentioning encrypted native filesystems…this is Oracle’s answer to a Support ticket asking about compatibility.

Dead Connection Detection | Oracle Database Internal Mechanism


sqlnet_expire_time and dead connection detection

Posted by 2018 article

518kwZKpT+L