In Percona’s white paper “Performance at Scale: Keeping Your Database on Its Toes,” we take a high-level approach to what you need to think about when planning for database scalability.
Solved
Grant access to READ-ONLY Oracle Database
Posted on 2009-06-30
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?
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
3 Comments
Active today
Some of your privileges will make the all_xxxx views work for the other users.
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
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
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?
Active today
"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.
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
These days socially coordinated efforts have turned into a critical requirement for enterprises.
For cloud, the “train has left the station” and in the Microsoft ERP & CRM world, that means the next generation of enterprise software from Microsoft is here: Dynamics 365 is Microsoft’s new integrated business solution that unifies CRM and ERP fun…
This video shows, step by step, how to configure Oracle Heterogeneous Services via the Generic Gateway Agent in order to make a connection from an Oracle session and access a remote SQL Server database table.
This video shows setup options and the basic steps and syntax for duplicating (cloning) a database from one instance to another. Examples are given for duplicating to the same machine and to different machines
Suggested Courses
Course of the Month5 days, 6 hours left to enroll
670 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.