Troubleshooting the Debugger

This section describes how to troubleshoot the Oracle PL/SQL Debugger:

Problems debugging PL/SQL for the very first time

There are several steps required to configure PL/SQL debugging for use. If one of the steps is skipped, one of several errors can occur. To make sure that you have performed all configuration steps, please use the Debugging Setup Checklist.

Why can't I start my debugger?

The problem can be caused by one or all of the following:

  • No available port for debugging.

    To solve the problem, you must specify the PL/SQL debug port number range in the PL/SQL Debug Option Page.

  • The TCP port is not open for external access. This usually happens if you are connecting to a remote database.

    To solve the problem, you must specify all the ports in the debug port range that can be opened for external access. For Visual Studio running on a Windows XP computer, you need to do one of the following:

    • Add Visual Studio in the Exception list for the Windows Firewall.

    • Add all the ports from the PL/SQL debug port number range in the Exception list.

    • Turn off the Windows Firewall (Not recommended).

Why can't I debug the PL/SQL program?

The problem can be caused by one or all of the following:

  • Appropriate debug privilege is not granted to the connected user.

    To solve the problem, see PL/SQL Debugging Setup.

  • The PL/SQL program is not compiled with debug information.

    To solve the problem, compile the PL/SQL program with debug information. See PL/SQL Debugging Setup.

  • Why can't the debugger locate the PL/SQL source during debugging.

    To solve the problem, you have to specify connection source in the PL/SQL Debug Option Page. See PL/SQL Debugging Setup.

Why are my breakpoints gone?

Breakpoint information is saved in the solution. You have to explicitly save the solution to save the breakpoint. See Using Breakpoints.

The debugger is hanging

In certain cases, for example, when Visual Studio has crashed, it may be necessary to search for and kill extraneous OracleDebugger.exe processes. This process can continue to run even if Visual Studio has been closed.

Close Visual Studio, press control-alt-delete and choose Task List. Locate and any kill OracleDebugger.exe processes that are still running. Then restart Visual Studio.