Hi There,
I created 3 different table spaces as default schema for 3 Oracle user,
What's the easiest way to give them full permission
on their schema to create, update,delete ... all kind of objects and
add,delete,... records to their objects
but minimum possible permissions on the system and other schemas,

Thank you in advance - Sam

Sam wrote:
> Hi There,
> I created 3 different table spaces as default schema for 3 Oracle user,
> What's the easiest way to give them full permission
> on their schema to create, update,delete ... all kind of objects and
> add,delete,... records to their objects
> but minimum possible permissions on the system and other schemas,
>
> Thank you in advance - Sam

Can't imagine why you would create different tablespaces for different
users as Oracle != SQL Server.

But when you create users you assign the quota:

CREATE USER ...
IDENTIFIED BY ...
DEFAULT TABLESPACE ...
TEMPORARY TABLESPACE ...
QUOTA ... ON ...;

--
Daniel A. Morgan
University of Washington
damorgan@x.washington.edu
(replace x with u to respond)
Puget Sound Oracle Users Group
www.psoug.org

On Feb 16, 8:39 pm, DA Morgan <damor...@psoug.org> wrote:
> Sam wrote:
> > Hi There,
> > I created 3 different table spaces as default schema for 3 Oracle user,
> > What's the easiest way to give them full permission
> > on their schema to create, update,delete ... all kind of objects and
> > add,delete,... records to their objects
> > but minimum possible permissions on the system and other schemas,
>
> > Thank you in advance - Sam
>
> Can't imagine why you would create different tablespaces for different
> users as Oracle != SQL Server.
>
> But when you create users you assign the quota:
>
> CREATE USER ...
> IDENTIFIED BY ...
> DEFAULT TABLESPACE ...
> TEMPORARY TABLESPACE ...
> QUOTA ... ON ...;
>
> --
> Daniel A. Morgan
> University of Washington
> damor...@x.washington.edu
> (replace x with u to respond)
> Puget Sound Oracle Users Groupwww.psoug.org

You will also want to grant the users object creation permissions like

create session <== so they can connect
create table <== to create tables
create view <== if you want them to be able to define views
create procedure <== if the user is to be allowed to create stored
procedures including functions and packages
....
See the SQL manul for a complete list of available object privileges

Avoid the use of the obsolete role connect and resource. These exist
for backward compatiability.

HTH -- Mark D Powell --