So far we found out that:
– this is the problem with Oracle on Windows 2003 / XP
– we could not reproduce the problem running Oracle on Windows 2000 (SP4)
– it doesn’t seems to affect Windows 2003 EMT64*

[Comment added, 2 November, 2007]
* Actually, it does affect Windows 2003 EMT64 as well. Last week we put in production Oracle (+Patch 12) on 64-bit Windows 2003 EE with SP2. After a week in a production we noticed dead client connections as described above.

A real bummer…
We found out that the same problem appear on Windows 2000 (SP4) as well. Not only is this bug wasting system resources but it causes instance crashes as well.

Dead Connection Detection | Oracle Database Internal Mechanism

sqlnet_expire_time and dead connection detection

Posted by 2018 article