My question is did you add the required three lines of code to your vb app (see
red line below) in order for external debug to work:
From the Toad help:
Requirements for attaching to an external application
Before initializing the debugger on the external session, disable server output
by issuing the ‘set serveroutput off’ command. If server output capture is
enabled, Oracle will freeze on calls to the DBMS_OUTPUT package so that these
calls can be debugged. This will give the displayance that the application has
frozen for no particular reason.
To initialize Debug mode, the external application must execute three commands:
ALTER SESSION SET PLSQL_DEBUG=TRUE
id := dbms_debug.initialize(‘TOAD’)
where TOAD can be replaced by any ID string. If this parameter is omitted, the
return value of initialize will be used as the Session ID. This ID string also
must be entered into Toad from Debug menu | Attach External Session.
The ALTER SESSION command (SQL) should be executed separately, while
dbms_debug.initialize and dbms_debug.debug_off (PL/SQL) can be placed in the
same PL/SQL block.
You can omit the ALTER SESSION command if you have all your procedures compiled
After running external application
After the external application is finished executing the code that needs
debugging, it should execute the command:
Otherwise, all subsequent PL/SQL code that this application submits for
execution will be run in debug mode. This will cause the application to hang
until Toad attaches to it again.