Re: Unable to extend temp on non temp tablespace

"Jonathan Lewis" <jonathan_at_jlcomp.demon.co.uk> wrote:

>
>Following on from Niall's comment -
>it isn't really very convenient to have a
>single 48GB tablespace for your indexes,
>so you may take this opportunity to
>create several small tablespaces and
>distribute the indexes sensibly between them.

I am a little bit surprised by this statement since I always thought that a tablespace is more a logical concept in order to ease management as long as all files belonging to it share suitable common properties. I really can't understand why having several tablespaces of the same "type" would be better in any way. But I am very willing to learn.

>Do a google groups (and the FAQ) search for
>locally managed tablespaces for futher ideas
>of improving the ease of management at the
>tablespace level.

I already know the essential advantages of locally managed tablespaces and still can't figure out why one tablespace should be broken down into a number of similar tablespaces. I don't know about any physical constraint applicable to a tablespace as a whole, files can be distributed on different devices while still belonging to the same tablespace.

I would appreciate your comments.

Thanks
Rick Denoire Received on Mon Jan 06 2003 - 16:58:25 CST