Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.
Grant access to READ-ONLY Oracle Database
I am the owner of the Oracle schema. I tried to grant read only access of all my objects to other users. However, when other users login they can not see all the objects (e.g the definitions of tables or views) on their session. They are using either Toad or Oracle SQL Developer to view the database objects. How do I give them access to view the definitions of my OBJECTS?
Asked:
2 Solutions
I am not concerning about the Dictionanray tables or views. My question is how come other users can not see the tables or views that I created in their sessions. What priveleges do I need to gave for them to see?
"how come other users can not see the tables or views that I created in their sessions".
Oracle does not support creating objects "in their sessions". If you have the "create any table" system privilege (or the DBA role which includes this system privilege) you can create objects in any schema (but not in another session).
For other users to see objects in your schema, two things are required:
1. You must "grant select on [object_name] to [other users or roles they have]"
2. They must either use fully-qualified object names: [schema].[object_name] or there must be a synonym for your objects. This could either be a public synonym (that works for all other users) or it must be a priviate synonym in each uers's schema.
Synonyms (whether public or private) do *NOT* take the place of grants. Synonyms just allow for objects to be referenced with shorter names, but if there is no grant on the actual object the synonym refers to, the other user will still get the "object does not exist" error.
Oracle does not support creating objects "in their sessions". If you have the "create any table" system privilege (or the DBA role which includes this system privilege) you can create objects in any schema (but not in another session).
For other users to see objects in your schema, two things are required:
1. You must "grant select on [object_name] to [other users or roles they have]"
2. They must either use fully-qualified object names: [schema].[object_name] or there must be a synonym for your objects. This could either be a public synonym (that works for all other users) or it must be a priviate synonym in each uers's schema.
Synonyms (whether public or private) do *NOT* take the place of grants. Synonyms just allow for objects to be referenced with shorter names, but if there is no grant on the actual object the synonym refers to, the other user will still get the "object does not exist" error.
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
Join & Write a Comment Already a member? Login.
Featured Post
Tackle projects and never again get stuck behind a technical roadblock.
Join Now
but some objects will require access to dba_xxxx views
by default toad doesn't use dba_xxxx views, you must configure it to check for access to those views