When two db server sessions are open (two different servers) and one is at idle for a while (around 10-20 min), when the idle db is accessed again (i.e. click on a taskbar item for that db server), it locks up, hang, or crashes Toad. Toad can just disappear as well. This happens on one specific db only. The other db is fine. There might be an idle timeout setting on the problem database. Toad may not be handling the idle timeout properly, hence it crashes.
1) ORA-03113: end-of-file on communication channel
2) Access violation at address 000000000419C77B in module 'Toad.exe'. Read of address FFFFFFFFFFFFFFFF
You need to be signed in and under a current maintenance contract to view premium knowledge articles.