Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Mailing Lists -> Oracle-L -> Locally managed tablespaces
We are currently on an AIX RS6000 box using Oracle 8.1.6.
I created a locally managed tablespace (to be used for indexes). I then issued an alter index rebuild command specifying the new tablespace as the destination (without using a storage clause). The rebuild went OK, but when I checked the initial and next for the index (in dba_indexes and dba_segments) it shows it as having an initial extent the same as it was before the move. Looking in dba_extents, all extents associated with the index are the correct size.
Why does dba_segments and dba_indexes show an incorrect initial extens? Is it necessary to specify the storage clause to see the correct initial extent? Received on Thu Nov 02 2000 - 08:59:53 CST
![]() |
![]() |