-
Accessing Table of other owner
Hi,
I using Oracle 8.1.7 and have the following problem:
I Have two users, User1 and User2, and a have one tablespace TS_DATA.
User1 have full access on TS_DATA (Create Tables, Drop Tables and others). User1 have created the table below:
CREATE TABLE USER1.TB_TEST1
( CODE NUMBER NOT NULL PRIMARY KEY,
DESC VARCHAR2(50) NOT NULL);
How can I grant permission to USER2 to do SELECT on TB_TEST1 without put the owner before the table name?
For example:
SELECT * FROM TB_TEST1
Thiago Campos Pereira
-
Create a synonym for the table.
Jim
Oracle Certified Professional
"Build your reputation by helping other people build theirs."
"Sarcasm may be the lowest form of wit but its still funny"
Click HERE to vist my website!
-
I have 10 user and 250 tables. I have to create 2500 synonym. This solution don’t solve my problem.
I need other solution that don’t use synonym.
Thiago Campos Pereira
-
there is not other solution, create synonyms
-
Create public synonyms, that way you only need to create 250 and why does that not solve the problem?
Jim
Oracle Certified Professional
"Build your reputation by helping other people build theirs."
"Sarcasm may be the lowest form of wit but its still funny"
Click HERE to vist my website!
-
Originally posted by tpereira
I have 10 user and 250 tables. I have to create 2500 synonym. This solution don’t solve my problem.
I need other solution that don’t use synonym.
What Jim meant was create public synonyms which is accessible to all. Additionally create a role, grant select on user1's tables to that role and grant that role to the other 10 users.
Last edited by adewri; 06-15-2005 at 08:03 AM.
Amar
"There is a difference between knowing the path and walking the path."
-
You have two options (apart the one mentioned by jovery):
- create PUBLIC synonyms for that tables (so you'll have only 250 synonyms, not 2500)
- allow your users to perform the following : ALTER SESSION SET CURRENT_SCHEMA = USER1;
Jurij Modic
ASCII a stupid question, get a stupid ANSI
24 hours in a day .... 24 beer in a case .... coincidence?
-
Originally posted by jmodic
You have two options (apart the one mentioned by jovery):
- create PUBLIC synonyms for that tables (so you'll have only 250 synonyms, not 2500)
- allow your users to perform the following : ALTER SESSION SET CURRENT_SCHEMA = USER1;
does that then allow users to change data in tables in that schema?
-
Originally posted by davey23uk
does that then allow users to change data in tables in that schema?
If they have permission to, yes.
As for public synonyms, I would really stay away from them unless you know this is the ONLY application that will ever be on that database.
Jeff Hunter
-
Originally posted by marist89
If they have permission to, yes.
As for public synonyms, I would really stay away from them unless you know this is the ONLY application that will ever be on that database.
Totally agree Jeff but as the original poster did not say whether the user would/would not have objects of there own I offered the synonym route.
Jim
Oracle Certified Professional
"Build your reputation by helping other people build theirs."
"Sarcasm may be the lowest form of wit but its still funny"
Click HERE to vist my website!
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|