I took a small package AT_TEST_PKT, 294 total lines, 24 test procedures-functions.
Opened the Quest sql tracker to see what’s going on. I typed the name in code editor and did Ctrl+Enter on it to open. As the package was initially not compiled with debug, the queries to the database were as in the attachment result_no_debug.txt. The query in the first post ran once. Then i closed the package and executed
alter package at_test_pkt compile plsql_debug = true;
And again clicked ctrl+Enter on it. And the result is in result_debug.txt. The query ran three times at first with some other queries in the middle and then finally 187 more times. There are not that many executable lines in the package!.
Here one query took in average 0.0x seconds. I just finshed waiting for another package where each query took 1.2-1.3 seconds. And i waited for over an hour for a 8000-line package to open, where each query took 2-60(!) seconds! Can this please be fixed so that the query will run once (ok, three times, but not hundreds).
I also have the body and spec of AT_TEST_PKT here, but you probably have to comment out some of it in order to compile the package with no errors.
And about the reconnect thing, you’ll have to find out that how (when the session is executing these queries from all_probe_objects) SQLNavigator is able to reconnect without asking and continue to run these queries (in different database session), when killed from another session. But that’s not that critical if you can just skip the queries altogether…
result_debug.txt (106 KB)