Apologies if this has been covered before but metalink is not clear on the reasons behind it....
The database is running version 9204 EE on WinNT Sp6; and the statement is a parallel direct load into partitioned table selecting from a 12.2GB source table.
ALTER SESSION ENABLE PARALLEL DML ;
INSERT /*+ APPEND PARALLEL(TRANSACTION_NEW,4) */ INTO TRANSACTION_NEW
(select * from TRANSACTIONS);
I'm seeing segments created in the temp tablespace (from v$sort_usage)
Sess# User Name TABLESPACE CONTENTS ext BLOCKS SZ_MB
----- --------- ------------------------------- --------- -------- ---------- ----------
9 SYS TEMP2 TEMPORARY 1629 208512 1629
11 SYS TEMP2 TEMPORARY 1629 208512 1629
12 SYS TEMP2 TEMPORARY 1629 208512 1629
13 SYS TEMP2 TEMPORARY 1629 208512 1629
I've enough space and it'll finish by tomorrow morning which is the deadline but does anyone know why TEMP is required and what the end to end process is?
I would have expected to have seen temporary segments created, but in the partitions own tablespace. It doesnt seem optimal to me.
Thanks in advance for your help,
Regards,
Adrian
