Description of the phenomenon:
It is normal to compile procedure with Plsql developer connection. Once the test starts to enter debug mode, it is stuck.
The initial guess is that there is no permission, but the DBA role, if not the right will directly report the error without permission.
The later guess is the version of Oracle or PL SQL Developer, tested with the same plsql on different machines of the same version, and the other machine can debug.
Start guessing is not the cause of RAC.
Search to this explanation: http://forums.allroundautomations.com/ubb/ubbthreads.php?ubb=showflat&Number=47544
The Oracle Debug API (Sys.dbms_debug) internally uses Dbms_pipe messages to communicate between the controlling session an d The debug session, which apparently can fail on RAC systems.
The only workaround are to modify the Tnsnames.ora file to connect to only 1 node of the cluster without load balancing and Failover.
The explanation is very reliable, try to connect to a single instance.
Test Debug, that's it!
Hang with PL/SQL Developer debug procedure in an Oracle RAC environment