Oracle FAQ Your Portal to the Oracle Knowledge Grid

Home -> Community -> Mailing Lists -> Oracle-L -> Re: Partitions each in a separate tablespace ?

Re: Partitions each in a separate tablespace ?

From: Emine ATES <>
Date: Wed, 13 Dec 2000 09:33:37 +0000
Message-Id: <>

Dear Djordje,
I haven't applied Oracle's partitioning features in my dbs, in case there is no need, But if I were you -it is a wish really- I would do like that According to you systems' disk configuration create some tablespaces each on different disk or disk set, user composite partioning for that table and put historical and active partition(s) in different rage contains Historical data have all hash sub-partitions on the same tablespace, those of the other(s) active partition(s) share all remaining tablespaces gaining management and performance improvements.

I hope I can explain my suggestion, because my english is not quite good ;)

Good luck
On Tue, 12 Dec 2000 18:50:58 -0800 "djordjej" <> wrote:
> Friends,
> I am creating partitions on a table, and need to decide whether to put
> partitions in separate tablespace (a tablespace for each partition) or to
> put them all together.
> Here is my reasoning:
> Main advantages of partitions is better performance, and easier maintenance.
> As far as performance goes in my case only the last (most recent) partition
> will be used by the application, so there is no big advantage of spreading
> the load between different tablespaces (btw my database is on a filer so I
> am not spreading load between physical disks anyway). As far as maintenance
> goes, for dropping of the old (historic) partitions I don't see any
> difference whether they are in separate tablespaces or in the same one. As
> far as a possible recovery (file corruption, etc.) goes it seems to me that
> for data partitions there is just a minor advantage of having each partition
> in separate tablespace, so that only that one corrupted partition datafile
> has to be copied for the backup, instead of a bigger datafile (for all
> partitions). As far as index tablespaces go there might be a significant
> difference if one of the local index partitions is corrupted, only that
> index need to be rebuilt, comparing to rebuilding all the local indexes in
> case they are all in the same partition.
> So I am inclined to put index partitions each in a separate tablespace, and
> I am not sure about data partitions.
> Any other thoughts, experience, suggestions ?
> Thanks.
> Djordje
> --
> Please see the official ORACLE-L FAQ:
> --
> Author: djordjej
> Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
> San Diego, California -- Public Internet access / Mailing Lists
> --------------------------------------------------------------------
> To REMOVE yourself from this mailing list, send an E-Mail message
> to: (note EXACT spelling of 'ListGuru') and in
> the message BODY, include a line containing: UNSUB ORACLE-L
> (or the name of mailing list you want to be removed from). You may
> also send the HELP command for other information (like subscribing).
Received on Wed Dec 13 2000 - 03:33:37 CST

Original text of this message