I also notice that another application was creating user with a temporary tablespace SYSTEM.
Shouldn't it all users be assigned TEMPORARY as their temporary table space. After all, isn't the reason the tablespace is defined as of type temporary?
And this USR tablespace, is
it really necessary? The only one assigned to it is SYSTEM and there
is no objects in the table. Shouldn't system be using the SYSTEM
tablespace as default?
SYS probably defaults to the
SYSTEM tablespace 'cause that's where we want the
data dictionary and it saves
having to put a tablespace clause on lots of object
creation statements.
SYSTEM is probably safe to change from its defaults, but as
always, err on the side of
caution and change it back again before an upgrade,
"just in case".
The consensus was that SYSTEM is just a DBA id that Oracle comes with that Oracle products like Forms and ReportWriter expect to be their owner. It is safe to change the default and temporary tablespace parameters for it.
SYS on the other hand should
be left alone. It is the database owner and is used to start, stop,
recover, and upgrade the database and should not be used for anthing else,
except running queries or doing grants on sys owned objects like the dbms
packages and v$tables as a part of normal operations and procedures.
Oracle standard, feel free to change.
> I also notice that another
application was creating user with a temporary
> tablespace SYSTEM.
Not a good thing if the SYSTEM
table space fills up, you database is
liable to stop working.
> Shouldn't it all users be assigned TEMPORARY as their temporary table space.
No realy, but it is a good
idea.
> After all, isn't the reason
the tablespace is defined as of type temporary?
>
Yes, but you can define multiply
temporary tablespace to distribute IO.
> And this USR tablespace,
is it really necessary? The only one assigned to it
> is SYSTEM and there is no
objects in the table. Shouldn't system be using the
> SYSTEM tablespace as default?
I don't bother about USR, I
just use SYSTEM.