Title: RE: Nosort parallel dml uses TEMP tablespace
You're welcome, please let me know the
results.
It was news to me as well, that so much temp space
would be used in your type of parallel direct load insert...
Btw, you can use nologging hint as well in your DML
if you haven'
Title: RE: Nosort parallel dml uses TEMP tablespace
Thanks
for having a look Tanel; that makes great sense.
I'll
have a quick play to convince myself but I'd say its a lesson
learned.
BTW
did you too experience more temp allocation than you would have
expected?
Thanks
aga
Title: RE: Nosort parallel dml uses TEMP tablespace
Hi!
Btw, I did a little testing with PARALLEL 2, and
yes it seems to be a parallel slave communications issue, despite the segments
show type "SORT".
When i traced sorting with 10032 & 10033, I saw
sort segment allocatio
Title: RE: Nosort parallel dml uses TEMP tablespace
Hi!
It could be that parallel slaves are passing
intermediate results using TEMP tablespace for some reason. (When table queues
are full in some cases or smth like that). It can depend on parallel execution
plan as well (whether it
S02/Solihull/[EMAIL
PROTECTED]
cc:
Subject: RE: Nosort para
Title: RE: Nosort parallel dml uses TEMP tablespace
I'm even more confused now.
TEMP ran out of space at 20GB - I'm only inserting 12.2GB!
So I kicked it off again with the hint just as /*+ APPEND */ and it completed successfully in 1/6th the time to failure of the paral
Title: Nosort parallel dml uses TEMP tablespace
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