Hi Jeff:

If I don't specify the storage parameter for table then it will take tablespace's storage parameter
as default storage parameter. Once the intial extents fills up then it will take next extent (next extent size is 1M). So, I am having so much extents in my production database. As far as I know
having a so many extent can impact on performance.

So, I want to change the next extent size big enough so I wan't have so many extents.
Also, I want to reduce the number of extents which I have at this point.

If I am going to use tablespace's storage parameter as default then I need to
change the next extent size. Otherwise I have to create an object with it's own
storage parameter to overwrite tablespace storage parameter.

Let me know.

Thanks for your help.