Thank you for reply. We have application DBA’s who are not allowed privileges like SELECT_CATALOG_ROLE but want to use the full functionality of toad for investigating problems and performance issues across many schemas. We have tried creating wrapper packages for all the sensitive views so we can filter out the sensitive fields but Toad does this check
select sum(decode(table_name, ‘DBA_SYNONYMS’, 1, 0)) dba_syns,
sum(decode(table_name, ‘DBA_OBJECTS’, 1, 0)) dba_objs
where owner = ‘SYS’
and table_name in (‘DBA_SYNONYMS’, ‘DBA_OBJECTS’)
and select_priv in (‘Y’, ‘G’);
After it checks to see if the user has SELECT_CATALOG_ROLE.
So it appears there is no way of getting around granting the SELECT_CATALOG_ROLE.
We have 3000 databases and lots of potential toad users who would like this functionality but until we find a solution we cannot roll this properly out.
Any thoughts or help would be greatly appreciated.