I have upgraded Toad for Oracle and the new behavior shows 301:Timeout, after I move away from the window. Toad has not disconnected from the database.
Toad for Oracle Pro DB Admin Subscription (64-bit)
Add-Ons: DB Admin Module, Sensitive Data Protection
25.2.376.6086
Does this happen every time you move away from Toad or only once soon after starting?
Please enable logging by setting the following options. Toad will need to be restarted. Reproduce the issue and zip all files from the Logs folder and you can email them to me at michael.staszewski@quest.com
The Logs folder is a subfolder off of the application data directory.
Thanks,
Michael
Will Do. As normal, now that I've done this the issue doesn't appear. I'll continue to have the logging enabled
Sounds good, thanks.
If you only saw the error once after moving away from the window shortly after opening Toad it may have been a temporary issue reaching the licensing or authentication services. Toad will use previously cached licenses if any such error occurs. If you saw the error multiple times within a Toad session when moving to another app then it's likely something else.
