If that did not convey access to that table, then someone has modified your definition of DBA. DBA is just a role -- you can grant and revoke to/from it.

catalog.sql has the following:

create or replace view v_$database as select * from v$database;
drop public synonym v$database;
create public synonym v$database for v_$database;
grant select on v_$database to select_catalog_role;


So, anyone with select_catalog_role should have access to that view. DBA has select_catalog_role (this is done in sql.bsq which should be run when you create the database).

To see what exactly DBA has, you can use the view

create view user_role_hierarchy
as
select u2.name granted_role
from ( select *
from sys.sysauth$
connect by prior privilege# = grantee#
start with grantee# = uid or grantee# = 1) sa,
sys.user$ u2
where u2.user#=sa.privilege#
union all select user from dual
union all select 'PUBLIC' from dual
/
grant select on user_role_hierarchy to public;
create public synonym user_role_hierarchy for user_role_hierarchy;

(create that as SYS, it is a hierarchy of every role you have and every role that role has and so on)

and then, create a temp user (or use your OP user) and:

sys@DEV816> grant dba to xxx identified by xxx;
Grant succeeded.

sys@DEV816> connect xxx/xxx
Connected.

xxx@DEV816> select * from user_role_hierarchy;

GRANTED_ROLE
------------------------------
DBA
SELECT_CATALOG_ROLE
EXECUTE_CATALOG_ROLE
DELETE_CATALOG_ROLE
EXP_FULL_DATABASE
SELECT_CATALOG_ROLE
EXECUTE_CATALOG_ROLE
IMP_FULL_DATABASE
SELECT_CATALOG_ROLE
EXECUTE_CATALOG_ROLE
JAVA_ADMIN
XXX
PUBLIC

13 rows selected.

If your list is smaller -- someone has changed what is means to be a DBA in your database


YOU DON'T HAVE TO SHOUT. I can hear you just fine ;)