Tom wrote:
>>Can do with out taking it down - create a new one (and cap it, if you
>>don't like large files, using the maxsize parameter), alter all users
>>to use the new one as temporary ts, and drop the old one, after
>>making sure it's not used by (long-)running transactions
>
>
> thanks Frank however do you know what might cause what i'm seeing.
>
> This is what i have done so far......
>
> CREATE TABLESPACE TEMP2 DATAFILE '/u02/oradata/XXXX/temp2_01_SOL.dbf' SIZE 10M REUSE
> DEFAULT STORAGE ( INITIAL 256K NEXT 256K MINEXTENTS 1 MAXEXTENTS UNLIMITED PCTINCREASE 0) TEMPORARY;
> ALTER DATABASE DATAFILE '/u02/oradata/XXXX/temp2_01_SOL.dbf' AUTOEXTEND ON MAXSIZE 1024M;
>
> ALTER USER XXXX TEMPORARY TABLESPACE TEMP2;
>
> but then when logging in with that user i do a ...
>
> SQL> select tablespace_name from user_tablespaces;
>
> TABLESPACE_NAME
> ------------------------------
> TEMP
> USERS
> MAIN
>
> the TEMP tablespace has not altered.
>
> Any ideas as to what i'm doing wrong? This is a test system and there are no other connected users.
>
> thanks
>
>
What does
select username, temporary_tablespace from dba_users;
reveal?
user_tablespaces are those tablespaces the current user
has grants on - what privileges does this user have?
IIRC, no user should have quota on temp tablespace explicitly -
you are automatically granted that.
But - when using quota, and you don't explicitly grant,
it won't show up in user_tablespaces.
--
Regards,
Frank van Bortel
Received on Sun Jan 25 2004 - 07:51:29 CST
