Yes, it's dangerous. You shouldn't allow anything in the system
tablespace other than system objects. For one thing, if the system
tablespace fills up, the entire database will hang. Another problem is
that you'll run the risk of fragmenting the system tablespace more AND
with other users objects in the system tablespace, you run the risk of
affecting database performance if one of the users is doing something
against one of their objects. All in all, it's not a good idea.
> -----Original Message-----
> From: Diego [SMTP:dpafumi_at_yahoo.com]
> Posted At: Thursday, February 11, 1999 6:10 PM
> Posted To: comp.databases.oracle.server
> Conversation: Users Question
> Subject: Users Question
>
> 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
Received on Fri Feb 12 1999 - 08:48:02 CST
