Problem debugging in different schema

[RogerK]

Though having the "debug any procedure" privilege and the debug object privilege (through a role),
debugging a package in a different schema does not work. When using the test-window, the debugging process calls and correctly processes the function, but does not step into it, even when i try to set a breakpoint. Is there any way do solve that problem ?

 

[epost]

You have to add debug information on that package in the other schema.

 

[ScottMattes]

The way I do it is to compile with debug in my own schema, do my debugging and fixing, then submit the changed code to be compiled in the target schema.

 

[Marco Kalter]

Another user's package bodies will only be visible if you have select privileges on the sys.dba_objects and sys.dba_source views. The "Use DBA views if available" preference (Tools > Preferences > Options tab page) needs to be enabled.

 

[RogerK]

Thanks for your comments. But all the prerequisits
you mentioned are fullfilled (Debug Info added, dba_objects, dba_source accessible, USE DBA Views enabled).
Any ideas ?
--------------------------
Roger

 

[RogerK]

I forgot one thing. My Oracle version is 9.2.0.6
----------------------
Roger

 

[Marco Kalter]

Can you obtain the "alter any procedure" system privilege and try again?

 

[RogerK]

No impossible, my DBA won't give me that privilege
-------------------------
Roger

 

[RogerK]

Hi,
i was able (unfortunaltly only in a test environment) to obtain the create any procedure privilege, which is necessary to see package bodies in different schemas when using all_xx views and it works !
Does that mean PL/SQL-Developer does not use dba_views though requested in that case ?
The same thing applies to "compare objects" when specifying a different schema name on the target database.
----------------------------------
Roger

 

[Marco Kalter]

It's actually a restriction of the Oracle Debugger. PL/SQL Developer can show the objects if you have select privileges on the dba_objects and dba_source views, but the debugger won't step into these objects if you don't have this system privilege on 9.2.