Recent content by Dylan_K

I have tried both for querying the catalog. It doesn't short circuit in either case. The only way I have found to make catalog queries fast is to force RULE based optimization.

I did a full POC of how to repair this problem in that Query from dba_type_attrs_upon logon takes cca 50 seconds thread. After that I created an enhancement request here Enhancement Request - execute script on Primary Connection prior to querying catalog That was more than a year ago. I'm...

My experience with Oracle Database 12.2.0.1 is the optimizer_mode=RULE was in and of itself insufficient to fix the problem. I combined that with a recommendation earlier in this thread and that solved the problem.

Full details to justify this request can be found here: Detailed proof of concept for improving PLSQL Developer connect time More recent versions of Oracle database take an extraordinary amount of time just to select zero rows from dba_ views. Many of us need to use the option "Use DBA...

Okay, so I came back to this connect time problem. It was not simple, but I finally cracked it. I will make an official enhancement request to allow for a script to be run on the Primary Connection before any of the catalog queries. I wanted to avoid hex editing altogether but could not find...

Nothing seems to help, not the parameters you provided, not changing rownum < 1 to 0=1. I was just getting fooled by the library cache having recently parsed the same query. After a while, it ages out and goes back to dead slow. I did consider doing an ALTER SESSION SET CURRENT_SCHEMA=ME in...

select count(1) from dba_objects; 97240 I changed my function to just set your parameters and it had little to no effect on the connect time. We are running 12.2.0.1. I will try the Hex Edit thing to change rownum < 1 to 0=1 because I actually do seem to be seeing an improvement in runtime...

I should have also said - if you do the above and then run plsqldev.exe DebugSQL, you can see in the debug log that the function gets called before any references to the dictionary views. Dylan.

So I tried an alternative to hacking the executable because 0=1 is just as slow for me as rownum < 1. I found that you can edit CANames.sql in the C:\Program Files\PLSQL Developer ## folder, wipe everything out and leave this: /* The name + type results of these queries will be used by the...

T-Gergely, How did you patch this? I need to use DBA_ views and I'm sick of waiting almost a minute to get connected in PL/SQL Developer. I'm willing to Hex-Edit the binary but cannot find where these queries are coming from! Any hints would be greatly appreciated. The DBA_ views keep...