TRUNCATE ???

Hi All

Ok, this could be just me being silly, but I came across the following (in summary):

1. A developer was loading table X and hit the MAXEXTENTS value of 121 for that table.
2. No problem - I changed the MAXEXTENTS storage parameter to 150 for table X and changed the NEXT value to 500K (from 20k - the default) to avoid too many extents...
3. Then we TRUNCATED the table and reloaded the data. MAXEXTENTS 150 reached. I queried DBA_SEGMENTS and the NEXT storage parameter for the table had reverted to 20K !

So it seems that a TRUNCATE of a table reverts the STORAGE parameters that have been changed just before the TRUNCATE...

Is it just me ?

Any comments are welcome

Cheers,

Andreas Received on Thu Nov 06 1997 - 00:00:00 CST