Laura,
Temp tablespace with tempfile and locally managed with uniform extent size
is the best practice with 8i onward.
The right place to check temp usage is V$sort_usage. After reaching high
watermark those extents are not released and kep for future use and it is a
normal behaviour.
Always
you can't have any dictionary managed tablespaces that are open for write
operations... dictionary managed read only tablespaces will still
work.
I think you're right, temp isn't being freed up... or is something else
using it, or is the index creation just that huge?
April Wells Oracle
Thanks,
Yes I have 200,000 millions row table ... I belive my tempoary tablespace is way too small.
-lizzApril Wells [EMAIL PROTECTED] wrote:
you can't have any dictionary managed tablespaces that are open for write operations... dictionary managed read only tablespaces will still work.
I
Hi,
There
are a couple of issues here. Firstly you need to know that when you get the
error about the "temp" segment when building the index, the segment in question
is the index. It is just that when building the index Oracle creates a temp
segment to sort the data in and to create the
wondering why did you do it.
--Mladen GogalaOracle DBA
-Original Message-From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of April
WellsSent: Friday, September 05, 2003 10:10 AMTo:
Multiple recipients of list ORACLE-LSubject: RE: Oracle9iR2 -
temporary tablespace
recipients of list ORACLE-L [EMAIL PROTECTED]
cc:
Subject:RE: Oracle9iR2 - temporary tablespace usage error
You can always try DBMS_SPACE_ADMIN.TABLESPACE_MIGRATE_FROM_LOCAL. I've never tried it,
it might be buggy, but in theory, the procedure would go like this:
1) Create
Oracle9iR2 -
temporary tablespace usage error
you can't have any dictionary managed tablespaces that are open for
write operations... dictionary managed read only tablespaces will still
work.
I think you're right, temp isn't being freed up... or is something else
using it, or is the index cre
