When working on a debug package, we have a failure in our code that causes an issue
VS Code & Extension Version
Version: 1.103.2 (user setup)
Commit: 6f17636121051a53c88d3e605c491d22af2ba755
Date: 2025-08-20T16:45:34.255Z
Electron: 37.2.3
ElectronBuildId: 12035395
Chromium: 138.0.7204.100
Node.js: 22.17.0
V8: 13.8.500258-electron.0
OS: Windows_NT x64 10.0.26100
Extension Version: 25.2.2
VS Code Extension Error:
DBTU-00001: Missing message key: com/oracle/dbtools/server/dap/DapErrors/DBTU_04701_MESSAGE
Legacy SQL Developer Error:
Executing PL/SQL: CALL DBMS_DEBUG_JDWP.CONNECT_TCP( '10.50.186.47', '4001' )
ORA-01031: insufficient privileges
ORA-06512: at "SYS.DBMS_DEBUG_JDWP", line 68
ORA-06512: at line 1
This session requires DEBUG CONNECT SESSION and DEBUG ANY PROCEDURE user privileges.
Process exited.
I did verify with the DBA team that indeed our user was not granted the required DEBUG roles so I did not share the code we tried to execute (immaterial to the issue).
A seperate interesting note in a difference in behavior from Classic to the new Extension. With the new extension, when debugger fails to connect, it still runs the code anyway. Classic/Legacy ends the process immediately when the debugger cant connect. Maybe that is another bug?