This content has been marked as final. Show 22 replies
I got the same error. Version 18.104.22.168
How come we can not debut PL/SQL package?
Can teh db server ping the ip address in the log ?
It works for me after check the "Prompt for Debugger Host for Database Debugging" checkbox.
Oracle 10.1.0.4 on RH linux.
It's not user friendly.
Yes, the DB Server can ping the PC where SQL Developer is running.
Had a person send me an e-mail that the debugger only works if the connection to the database is set up using the 'basic' tab and not the 'TNS' or 'Advanced' tab. Be it good or bad information still cannot get the debugger to work.
Debugger works whether you have connected via the tns tab or the basic tab. So that's not your error.
Check that your machine, and any firewall around it, accepts incoming connections to SQL Developer on the ports the debugger is using (4000 in your example - configure the port range in Tools | Preferences | Debugger under "Debugging Port Range".
I also came across the same error and could not do anything about it. Can anyone tell me how to rectify the error.
I checked "Prompt for Debugger Host for Database Debugging". Then specified my own computer's IP.
I'm having the same issue ..
I think it's because the db server can't access my PC, and I can't change that ...
But it works when I connect to Oracle 8i db.
I guess it's because it will then use local debug instead of remote debug.
Is there a way to force sqldevelopper to user local debug on oracle 9i servers ??
Well I had the same problem on one of my databases. Just tried connecting using the basic tab, and I just don't beleive it, its working !!!!!!!
I am running SQL Developer on Windows XP Professional and I was experiencing the same problem.
When I started the debugger I got the message from Win XP that Windows Firewall will block some features of the program (being the PC at work I don't have admin privileges on it). I accepted this, not knowing which features would be blocked.
Then, the debugger was just hanging. After a while it timed out and came back with exactly this error message.
I restarted the SQLDeveloper and tried again without much success. This time though I didn't get the Windows Firewall message.
After another few trial and errors I figured out that the Firewall must be blocking connection establishement on the client site i.e. on my PC.
It was the CALL DBMS_DEBUG_JDWP.CONNECT_TCP that was hanging.
As the system admin disabled the Windows Firewall on my PC the debugger started working. We have a luxury to disable local firewalls as there is one that protects our network from outside traffic. People who cannot afford to disable the Windows firewall will have to tinker with the firewall itself and configure it in such a way that it allows traffic on certain port range (4000...4999). Then in SQLdeveloper you will have to go to Tools->Preferences->Debugger and tick Debugging Port Range. The chosen range should match the port range on the Windows Firewall side.
By the way, in the call to CALL DBMS_DEBUG_JDWP.CONNECT_TCP the first parameter is the IP address of your PC and the second one is the port used for debugger connection with the database server. If for some reason the IP address chosen by the debugger is not your IP address (you can find your IP address as follows: Start->Run->cmd; then use command ipconfig), you will have to tick "Prompt for Debugger Host for Database Debugging" on your Debugger Preferences. This way you'll be able to chose the IP address yourself.
The only you have to do is to use "Basic" Tab instead of "TNS" tab in connection properties. It worked for me.
I had the same problem all i did was.
Tools | Preferences | Debugger - i set the Prompt for debugger host for database debugging.
I set my machine ip address when it prompt and it worked.