RE: Parallel index build....(how much tempspace)

Hi Norma Jean, one of the things to keep in mind is, that once a temp object got created in a particular temp dbspace, it then stays there for its life (the life of the object). If during this time the object grows very large, it can happen that you run out of space - in that particular dbspace. There's no mechanism (at least not that I'd know of) that such a temp object would then automatically be transferred to another temp dbspace that (momentarily) happens to have more space. Nor will such a temp object be automatically fragmented over the other temp dbspaces. Which temp dbspace to use when a new temp object gets created was decided in a round robin fashion in older versions. It might well be that we got smarter with that, i.e. that a temp dbspace is chosen by the space available in it and the estimated biggest size of the temp object. But I'm not sure on this. With that I guess the safest bet (for long term) is to first increase the size of the existing temp dbspaces. I.e. add a couple of chunks to (each of) them.