By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,730 Members | 1,540 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,730 IT Pros & Developers. It's quick & easy.

restricting a user to access his own tables

P: 24
Hi all,

as a super user i want to restrict a user created by me to access only the tables created by him/her.

i.e he only can access or change the data in the tables created by him.and can not do anything on other's tables.

is there any grant command to do this. or is this the case by default.

pls help me out.

thanks in advance.
Mar 2 '07 #1
Share this Question
Share on Google+
3 Replies


P: 16
Hi all,

as a super user i want to restrict a user created by me to access only the tables created by him/her.

i.e he only can access or change the data in the tables created by him.and can not do anything on other's tables.

is there any grant command to do this. or is this the case by default.

pls help me out.

thanks in advance.
if the tables are'nt in this user schema you can revoke the updates privileges to to user from this tables (a user must have a privilege to do an operation in another schema tables)

if the tables are in the user schema so you can write a system trigger that fires updates on tables and thereso block the updates for this user



you can write a system trigger that fires updates in the tables and ver
Mar 2 '07 #2

100+
P: 153
Hi all,

as a super user i want to restrict a user created by me to access only the tables created by him/her.

i.e he only can access or change the data in the tables created by him.and can not do anything on other's tables.

is there any grant command to do this. or is this the case by default.

pls help me out.

thanks in advance.
Yes, by default a user can only see/modify his/her own objects and must be granted privileges to even view data from another schema (user).

Of course there are some dictionary tables and views that the user can select from, but they cannot alter the dictionary tables by default.
Mar 3 '07 #3

P: 16
Yes, by default a user can only see/modify his/her own objects and must be granted privileges to even view data from another schema (user).

Of course there are some dictionary tables and views that the user can select from, but they cannot alter the dictionary tables by default.

another way is the policy

you can do a policy that restrict the access for a user
Mar 4 '07 #4

Post your reply

Sign in to post your reply or Sign up for a free account.