I created a locally managed tablespace with a uniform extent size of 1M. I moved several tables into this tablespace that had many different extent sizes. I thought that moving them into a tablespace with uniform extent sizes would alleviate the need to modify the storage parameters to 1M extents during the move. However, when I query dba tables I see that the initial and next extent sizes are not all 1M. Can anyone explain?

thanks,
lacey