This content has been marked as final. Show 2 replies
I suppose it's possible there is some special issue with 220.127.116.11 and you've encountered something new; however, this is typically a performance issue rather than a hang. See the following thread:
3.1 - Public Synonyms - Hanging
I would add that the cancellation issue has been fixed, but that the window of opportunity is very brief -- just a few seconds at most -- since cancellation only applies to the SQL query. As you note, that is very fast. Once SQL Developer has the result of the query, it begins to render all those individual nodes in the navigator tree. That is what really takes so long and, unfortunately, cannot be cancelled. Use the filter trick mentioned in the other thread to protect yourself from such 'accidental' delays.
SQL Developer Team