Prev: Constraint problem
Next: Spam
From: Arun Srinivasan on 29 Oct 2009 05:07
1. Why would set integrity use system temporary tablespace?
2. I created one system temp tablespace with 5 g on all nodes - and my
table has table partitioning enabled ALONG WITH hash partitioning
while the exception table is normal (but still hashed using the same
keys),
Still it is using the system temp tablespace and reporting no
available pages!!! How can I know whats it doing? rebuilding index or
whatever? There is like 10 million rows in the table waiting to be run
in production.

Your help is highly appreciated
From: mirof007 on 29 Oct 2009 13:33
Have you tried running an explain on it? It might give you some clues
as to what it is doing. Also, try increasing the size of the
bufferpool associated with the tablespace you want it to use, I think
the choice is cost based if there are multiple temp tablespaces
available.

Regards,
Miro

From: Willem Fischer on 9 Nov 2009 17:30
On Oct 29, 6:33 pm, mirof007 <mirof...(a)gmail.com> wrote:
> Have you tried running an explain on it? It might give you some clues
> as to what it is doing. Also, try increasing the size of the
> bufferpool associated with the tablespace you want it to use, I think
> the choice is cost based if there are multiple temp tablespaces
> available.

I had a similar issue with log space, maybe the two are related. I ran
out of transaction log space when generated columns had to be re-
generated. DB2 won't need transaction log, and possibly tempspace, if
you order DB2 not to regenerate the contents of the generated columns.
Try playing with

set integrity for xx immediate unchecked;
 | 
Pages: 1
Prev: Constraint problem
Next: Spam