-
Title
Forced relogin after session timeout not working correctly in editor -
Description
We are attempting to lock users out after 30 minutes of inactivity, we have changed the database settings and unchecked the boxes 'Save passwords for Oracle connections' and 'Remember passwords for Oracle reconnects' in the options. After the timeout period attempting to run a sql using ctrl+enter gives a message "ORA-02396: exceeded maximum idle time, please connect again". I click ok, and press CTRL+Enter again and get the message "ORA-01012: not logged on". I click OK again, press CTRL+Enter again and it allows me to run the selected SQL WITHOUT entering a password.
This is not the behavior is SQL*PLUS since after getting the ORA-01012, any subsequent attempts result in the same error message, as expected. -
Resolution
WORKAROUND
none
STATUS
Waiting for fix in a future release of Toad for Oracle -
Defect ID
ST66556