Question about result set grid behavior

[B_P_100]

Hello,

I'm using a trial version to evaluate. In general I like this tool but I have a few concerns/questions.

I have noticed a potential problem.

When I run a query from the SQL Window it produces the result set and displays it in a nice grid at the bottom of the window.

Very often I want to take some data from the result set and cut and paste that data element elsewhere.

I have noticed that fairly often I observe a hanging/lockup behavior when I 'touch' a data element in the grid (via mousing into the cell).

The lockup behavior freezes the entire IDE for a minute or so.

For me this behavior is fairly consistent. If I rerun the same SQL statement it doesn't happen the second time but when I run a different query I get the lockup behavior.

Do you have any suggestions about this?

********

Here is some environment info:
PL/SQL Developer
Version 7.0.3.1123 (MBCS)
Windows 2000 version 5.0 (build 2195) Service Pack 4

Physical memory : 523,704 kB (200,580 available)
Paging file : 1,273,164 kB (975,036 available)
Virtual memory : 2,097,024 kB (1,996,192 available)
OCI: Version 8.0
Oracle Database 10g Enterprise Edition Release 10.2.0.2.0

 

[Marco Kalter]

This indicates a problem with the Oracle Dictionary performance. When you enter the grid, PL/SQL Developer will get information about the columns/fields in the result set. Apparently this is very slow in your case. There are 2 solutions:

1. Disable this feature.

Go to Tools > Preferences > Window Types / SQL Window, and disable the "Show dictionary info in result grid" option.

2. Investigate the dictionary performance.

When PL/SQL Developer seems to hang, verify which query is executed and why it is so slow.

 

[B_P_100]

Thanks for the information. So far, disabling the feature seems to have helped.

I didn't see what value that option/feature was trying to provide. The grid looked the same with it off or on. In this case the overhead was definitely not worth whatever value the feature can deliver.

I am working in an instance that has Oracle Apps installed. As you probably know, this creates 10s of thousands of database objects. Perhaps this clutter slows down dictionary queries.