Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: How it works alter tablespace X default Storage...?

Re: How it works alter tablespace X default Storage...?

From: Kenneth C Stahl <BluesSax_at_Unforgettable.com>
Date: Mon, 12 Jul 1999 08:51:59 -0400
Message-ID: <3789E4EF.2C7B2D6A@Unforgettable.com>


Once a table exists you really cannot change INITIAL because by that time the initial extent has already been created. The only way you can effect this change is to export the table, create the table with the desired INITIAL value and then import the table.

With NEXT it is different. If you change the NEXT value then the next time that the table needs a new extent it will use that value. However, if you know that the table has already gone past the initial extent then you will have a table with an initial extent of whatever size it was when the table was created and extents 2-n (where n is the current extent count) will have been created at the NEXT value that existed up until you made the change. Often this is not desireable, so the best thing is to drop the table and recreate it with whatever settings you want for the table.

Ken

Huy Vu wrote:

> I did the command
>
> Alter tablespace tbsA
> default storage
> ( initial 1M
> next 512K
> pctincrease 0
> minextents 1
> );
> to fix the old value of tabsA
> default storage
> ( initial 4K
> next 4K
> pctincrease 0
> minextents 1
> );
> but I still not finger out how it change inside the tablespace tbsA
> Do I need to backup the tablespace before executing this command ?
> The same question for resizing the tablespace...
> But how can we know the current value INITIAL & NEXT using in the
> tablespace?
Received on Mon Jul 12 1999 - 07:51:59 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US