#352 Schema Browser

[maddogskip]

I just wanted to document that I have been having
some problems with the SQuirreL to get it to show me
the SYSADM and SYS Schemas in Oracle.

The only way around this now is to go into the Object
Tree Filter and add SYSADM to the filter. That seems
to work.

Thanks in advance...

Tom

[Rob Manning]

Logged In: YES
user_id=1287991

I believe the Oracle Plugin which limits the schemas
that are shown in the object tree to only those that
the user has been granted permission to (according to
user_tab_privs) is the culprit. It explicitly adds
SYS and should probably also add SYSADM as well.

Rob

[Rob Manning]

Logged In: YES
user_id=1287991

After further investigation it's not clear what objects
one should find in the SYSADM table. Both of my 9i and 10g
databases yield the following:

SQL> select table_name from dba_tables where owner = 'SYSADM';

no rows selected

It appears that both of my databases don't even have a
schema called 'SYSADM'. If they did, then the system
account would be able to see them because we test
USER_ROLE_PRIVS for DBA role of the current user and
system always has this role. If the user has the DBA
role, then no object filtering is done automatically.

It appears that you have created the schema called 'SYSADM'
and placed objects there yourself, and not as part of the
Oracle server installation. So, shouldn't the user whom you
are expecting to see those object actually have privileges
to see them? We explicitly add SYS to every session's
object tree regardless of the user since SYS contains
various views (like user_tables) that the user has access
to but doesn't appear in USER_TAB_PRIVS. Any other schema
(in your case SYSADM) should then have an entry for some
table in USER_TAB_PRIVS for the current user. This happens
whenever you grant privilege to select on some object in
that schema to a user other than the owner. Can you
tell me a little about the origin of the SYSADM schema?

Rob