SQL Window - Query using DBlink causes the program to be not responding

Sgnao

Member²
Hi All,

I have experienced this problem :

- I open a new sqlwindow;
- I type in a query that uses a DBlink;
- I execute it and it returns its results;
- If I let the window there for some minutes, when I try to close that specific window, it causes the program to hang and be not responding, so I have to kill it from task manager. If I close that window immediately, no problem.

EDIT : If you use a synonym pointing an object in another database instead of the dblink, no problem.

EDIT 2 : Why, when executing a query using a dblink, after it returns results I have commit and rollback buttons active? The query is a simple select statement without inserts or updates or deletes. And when I close it asks for commit or rollback.

Anyone experienced something like this?

Version is 10.0.5.1710

Thank You
Marco
 
Last edited:
Regarding the commit/rollback, it's not caused by the PL/SQL Developer, it's the Oracle DB that starts a transaction when dblink is used. This should not depend on the dblink being used explicitly or by a local synonym - in both cases the DB will start a transaction.
PL/SQL Developer notices that the SQL Window DB session has an open transaction pending and that's why it activates the buttons and/or complains about the transaction when window/application is being closed.

Not sure about the cause of PL/SQL Developer hanging after dblink being explicitly used. I had issues with using dblink in a session that used it before and went idle for a long time (regardless if the link was used explicitly or not), as the connection between linked DB was left open (from the first use) and died (timed out?) before second use and it took the Oracle a lot of time to notice this.
 
Back
Top