tag:blogger.com,1999:blog-13265058.post6984509211899977356..comments2011-11-05T09:25:19.722+11:00Gary Myershttps://profiles.google.com/116132019768637593422noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-13265058.post-30376360564570051512011-11-05T09:25:19.722+11:002011-11-05T09:25:19.722+11:00Gary,<br />Nice post about this plugin.<br />However, many firewalls have default timeout period, regardless you are pinging or not they will disconnect you. <br />Worth of deeper investigation with sysadmins ...<br />Rg,<br />DamirDamir Vadashttp://www.blogger.com/profile/15963017378937428976noreply@blogger.comtag:blogger.com,1999:blog-13265058.post-66253896179270125732011-11-05T09:22:50.006+11:002011-11-05T09:22:50.006+11:00Yes this was a network kill rather than a resource manager kill. The network admins seemed unable to work out which bit of the network was doing it though.<br /><br />We did set EXPIRE_TIME in SQLNET eventually.Gary Myershttp://www.blogger.com/profile/10404756950638119562noreply@blogger.comtag:blogger.com,1999:blog-13265058.post-91861801737345666902011-11-05T09:14:56.244+11:002011-11-05T09:14:56.244+11:00The disconnect must have ben on the network devices - if the instance terminate a session, there is no need to kill/rollback. <br />For such problems Dead Conection Detection in sqlnet.ora on server side is fine - at least the rollback will be earlier and less resources are wasted.Martin Bergerhttp://www.blogger.com/profile/16504572924713610305noreply@blogger.com