Error received when two Oracle sessions are opened on a production database.
"Access violation at address 00EDA8D0 in module 'TOAD.exe'."
Additional Errors received:
"ORA-02396 Exceeded maximum idle time.
A user has exceeded the maximum time allowed to remain idle. "
"ORA-02391: Exceeded simultaneous SESSIONS_PER_USER limit "
"Cause: An attempt was made to exceed the maximum number of concurrent sessions allowed by the SESSIONS_PER_USER clause of the user profile. "
Action: End one or more concurrent sessions or ask the database administrator to increase the SESSIONS_PER_USER limit of the user profile. For more information about SESSIONS_PER_USER and the database administrator's specific tasks of adjusting concurrent sessions.
WORKAROUND:
Disable the "Execute queries in threads" option in Toad:
1. In Toad go to View | Toad Options | Transactions | Oracle Transactions.
2. Disable the "Execute queries in threads" option and click Apply | OK.
3. Exit and restart Toad.
STATUS:
Waiting for enhancements to be included in a future released of Toad for Oracle.
As per SOL49502: https://support.quest.com/SUPPORT/index?page=solution&id=SOL49502&pmv=true&ct=1
Defect ID: ST56498 has been issued to enhance notification of Oracle needing to be re-connected.
