When debugging Package procedures and functions which are running DML (Insert, Update, Delete) statements against tables, Oracle automatically places a lock on the table until this resource is finished and/or the Debug session has completed its execution. The Debug session can hang if it surpasses the Debug Timeout while waiting for this resource/table to be unlocked by another session. If the Debug Session hangs, this will leave an orphaned session in limbo affecting any subsequent Debug sessions until Oracle's PMON process kills this process.
1. To recover from a hung process in a Debug Session, perform an End Task and/or reboot the client PC.
2. To increase the Debug Timeout Session, go to View | Options | Debugging and increase Debug Timeout session in seconds.
Note: This will help prevent the Debugger from hanging immediately when waiting for a resource [Table) to be unlocked by another session.
3. To kill a session that is holding a lock on a Table - use the Session Browser to find the session locking the resource and click the Kill Session button.
For version prior to Toad 9.0 - go to DBA | Session Browser
For version after Toad 9.0 - go to Database | Monitor | Session Browser
