Developers facing issues with viewing triggers from objects browser drop-down.

[HemantParalkar]

Users are facing issues with viewing

 

[Marco Kalter]

Can you let me know what the issue is?

 

[HemantParalkar]

Users are facing issues with viewing "triggers" from the object browser, although the user is granted select privileges to underlying table for the concerned trigger. Same trigger code is visible to users when accessed with the specific table view option and then by clicking on triggers tab->view sql .
This is working perfectly fine for the dba users.

 

[Marco Kalter]

Note that to view trigger code that is owned by a different user, you need to have select privileges on the sys.dba_objects, sys.dba_source and sys.dba_triggers views. You will also need to enable the "Use DBA views is available" option from the Oracle / Options preference screen.

 

[HemantParalkar]

Thanks Marco for the updates.I Will test the same and will let you know for any issues.

Thanks for the support.

 

[HemantParalkar]

Hi Marco,

We have tried the option provided by you, but it doesn't seem to show all the triggers in the dropdown.

Thanks.

 

[Marco Kalter]

Can you verify that the User Selector and Filter Selector of the Object Browser do not exclude the triggers you are missing?

Can you also check if the missing triggers are reported when explicitly querying the sys.dba_objects and sys.dba_triggers views?

 

[Paolinik]

Can you verify that the User Selector and Filter Selector of the Object Browser do not exclude the triggers you are missing?

Can you also check if the missing triggers are reported when explicitly querying the sys.dba_objects and sys.dba_triggers views?

Same (huge!) problem here... no triggers displayed.

User selector and filter of the object browser don't exclude triggers and querys on sys.dba_triggers and sys.dba_objects views show all the triggers.

I'm facing issues with packages specs and bodies too by the way: I only see a part of the list for packages spec and even a smaller part for packages bodies

It seems to be an interface display issue.

PL/SQL Developer version: 12.0.7.1837 (64 bit)
Windows 10 Build 17134

 

[Marco Kalter]

If you think this is an interface display issue, can you send me a screenshot?

Can you also check if the "Use DBA views if available" preference is enabled on the Preferences > Oracle / Options page?