When viewing objects, such as Procedures, PLSQL Developer is hanging after 10g Upg

[PaulW]

I'm currently running PLSQL Version 7.0.3.1123 (MBCS), and we have just upgraded our Development environment from Oracle 8i to Oracle 10g (Enterprise Edition Release 10.2.0.2.0 - 64bit Production). Now PL/SQL developer stops responding whenever an attempt to expand an object in the object window is attempted, i.e. Procedures, Packages etc.

The thing is, our test and production environments were upgraded a few months ago and the same PL/SQL application works fine with those databases.

Is there a setting in Oracle that could be causing this behaviour in PLSQL Developer?

Thanks

 

[Marco Kalter]

Can you go to Help > About, press the 'Info' button, press the 'Copy all pages' button on this info screen, and paste this text into an e-mail reply?

 

[fernanda]

I have the same problem, we have just create a database Oracle 10g (10.2.0) Standard Edition and PL/SQL developer stops responding whenever an attempt to expand an object in the object window is attempted, or when we try to logout. Is this a bug of oracle 10.2.0? Does anyone find a solution to this problema?

Thanks

 

[Marco Kalter]

Can you switch from "All objects" to "My objects" and check if this helps?

 

[fernanda]

Hi, I switched from "all objects" to "my objects" and now I can expand an object in the object window, thank you ! However, I still can't log out, the PL/SQL developer stops responding when I log out and the session don't die. Do you know what can I do to resolve this problem?

 

[Marco Kalter]

Can you let me know your PL/SQL Developer version?

 

[olof]

Hi,

I have the same problem, but only in the Query Builder. With 'All objects', the server hangs but with a filter, it's ok.

Oracle DB : 10.2.0.2.0
PL/SQL Developer : 7.0.3.1123 (MBCS)

With older DB (9.2.0.7.0 for example), it works fine.

Thank you !

 

[fernanda]

The version is 7.0.3.1123

 

[fernanda]

Hi Marco, Did you find what can I do to resolve this problem? I still can`t logout of plsql because when I do the program stop responding. Thanks.

 

[Marco Kalter]

To obtain some more diagnostic information, can you modify the shortcut and add the debugsql parameter? For example:

"C:\Program Files\PLSQL Developer\plsqldev.exe" debugsql

Reproduce the problem and send me the debug.txt file that is generated in the PL/SQL Developer directory.

 

[olof]

Hi Marco, in my case (the problem occurs only in Query Builder, with 'All objects' selected), here is the end of the debug.txt file (the query hangs and the database (10.2.0.2.0) sees his CPU at 100% !) :

select object_name, owner object_owner, status, object_type, created, last_ddl_time
from sys.all_objects o1
where object_type = bject_type
and (object_type != 'SYNONYM' or
(
(owner = user or owner = 'PUBLIC') and
exists (select * from sys.all_objects o2,
sys.all_synonyms s2
where s2.owner = o1.owner
and s2.synonym_name = o1.object_name
and o2.owner = s2.table_owner
and o2.object_name = s2.table_name
and o2.object_type in ('TABLE', 'VIEW')))
)
order by decode(owner, user, 0, 1),
owner,
object_name
:OBJECT_TYPE = TABLE

 

[fernanda]

Hi, I sent you the log by mail. Thank you, Fernanda.