Debug trigger code of other schema

[comknw]

Hello,

I know that you mention in one of your articles

"You can only debug PL/SQL-Objects which re yours.
Orca".

But I've the following problem:

Pre-infromation:

There is a user(schema) let's say 'APPLICATION_OWNER' which owns all objects. The user is logging in by its own name let's say 'APPLICATION_USER' which only has one role granted. Further, we have several locations where our application's running. Only in one location we have the following problem, although all location should have the same conditions.

Problem:

Table Table4711 is stored within 'APPLICATION_OWNER' and has one trigger which fires before INSERT and UPDATE for each row.

Now, when I do an Update as user 'APPLICATION_OWNER' the trigger fires and is making the correect thing.

But when I do an Update as user 'APPLICATION_USER' it seems that the trigger makes nothing.

I've no chance to figure out where the problem is, because within the PL/SQL Developer as user 'APPLICATION_USER' the trigger code won't be displayed when debugging.

Do you have any idea how to find out the problem? Maybe there will be an enhancement of the PL/SQL Developer?

Thanks and regards
Johannes

 

[Marco Kalter]

Another user's triggers will only be visible if you have select privileges on the sys.dba_objects and sys.dba_triggers views. The "Use DBA views if available" preference (Tools > Preferences > Options tab page) needs to be enabled though. To debug another user's triggers you additionally need the "create any procedure" system privilege.

------------------
Marco Kalter
Allround Automations

 

[comknw]

Originally posted by mkalter:
Another user's triggers will only be visible if you have select privileges on the sys.dba_objects and sys.dba_triggers views. The "Use DBA views if available" preference (Tools > Preferences > Options tab page) needs to be enabled though. To debug another user's triggers you additionally need the "create any procedure" system privilege.

 

[comknw]

Hello Mr.Kalter,

Thanking you for your help again. It's actually possible to debug packages, procedures etc. from other users. But the trigger which is calling the packages could not be stepped thru. I even could not see the trigger code. On the first step into, the first package called is displayed. If I set a breakpoint within the trigger during debugging, the following error occurs:

Error setting breakpoint at line 235 in OPLU.XG065_70:

Bad handle

Do you have any idea?

Kind regards
Johannes Flandorfer

 

[Marco Kalter]

I tested this and it works just fine. I can step into another user's trigger and also set breakpoints. Can you try this using the SYS account, so that it we are certain that this is not a privilege issue?

------------------
Marco Kalter
Allround Automations