Re: Users Question

The MAIN reason, as pointed out by the other two respondants is fragmentation of the SYSTEM tablespace. When users create and drop objects, expand and contract tables etc. the tablespace will get fragmented. In other tablespaces this can be undone by exporting objects from it dropping and recreating the tablespace and importing the objects again (bit more involved than this really). YOU CANNOT DROP THE SYSTEM TABLESPACE so you cannot easily defragment it.

To guard against fragmentation of the SYSTEM tablespace, keep users away from it.

Regards Pete

In article <36C3FFC9.87E3BDC4_at_berlin.de>,   "Rüdiger J. Schulz" <r.schulz_at_berlin.de> wrote:
> the system tablespace contains all system tables.
> it´s better to store user-data into another tablespace an leave the
> system-tablespace allone.
> the advantage of this is, that you can backup and restore the
> data-tablespace on its own.
>
> so you should create the user with the following options: (i.e.)
>
> Create User xyz identified by abc
> default tablespace TS_DATA temporary tablespace TS_TEMP
> quota unlimited on TS_DATA quota unlimited on TS_TEMP
> quota unlimited on TS_INDEX;
> grant connect, resource to xyz;
> grant create procedure to xyz;
> grant create sequence to xyz;
> commit;
>
> Diego schrieb:
>
> > Hi to everybody
> >
> > If I create a user with
> > create user ....... identified by ....
> > This takes at default tablespace the system tablespace. Is this
> > dangerous or not?? Why??
> >
> > Thanks,
> > Diego
>
> Rüdiger J. Schulz
>
>

-----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own Received on Thu Mar 11 1999 - 00:00:00 CET