large extent created in index dbspace?

Hi All, Question I have created a table with First extent size 1600000 Next extent size 160000 The indexes are kept in a seperate dbspace All seems to go well until I noticed that extents are getting gradually smaller with a massive extent being created recently in the index dbspace the extents in the data dbspace seems to be correct. Can someone explain how this situation has occured or what is wrong with my logic. The output of oncheck -pt on the table is below TBLspace Report for oetrn Physical Address df6613 Creation date 06/19/2003 19:04:23 TBLspace Flags 802 Row Locking TBLspace use 4 bit bit-maps Maximum row size 878 Number of special columns 0 Number of keys 0 Number of extents 7 Current serial value 8289595 First extent size 1600000 Next extent size 160000 Number of pages allocated 1952969 Number of pages used 1831147 Number of data pages 1830692 Number of rows 3661384 Partition partnum 4194819 Partition lockid 4194819 Extents Logical Page Physical Page Size 0 d00003 712536 712536 a9861b 160000 872536 accdc3 160000 1032536 c00003 320000 1352536 c76777 320000 1672536 cd2aff 149943 1822479 dae125 130490 Index oetrn_key1 fragment in DBspace ihtl1dbs Physical Address 21f9cc5 Creation date 06/19/2003 22:12:11 TBLspace Flags 802 Row Locking TBLspace use 4 bit bit-maps Maximum row size 878 Number of special columns 0 Number of keys 1 Number of extents 54 Current serial value 1 First extent size 45558 Next extent size 36440 Number of pages allocated 103593 Number of pages used 67186 Number of data pages 0 Number of rows 0 Partition partnum 9437545 Partition lockid 4194819 Extents Logical Page Physical Page Size 0 246c7a8 45558 45558 2459400 4555 50113 264848f 4555 54668 273ab9c 4555 59223 28e1d43 4555 63778 272bfe6 1040 64818 26f8c6e 624 65442 2559c28 336 65778 257ab68 192 65970 2499d4c 256 66226 2531fb6 128 66354 25e06f0 128 66482 25406c0 104 66586 253f706 68 66654 24d9f53 64 66718 254866b 64 66782 25b8a8d 64 66846 27616ac 64 66910 24d868e 32 66942 276d9bf 16 66958 24dac78 12 66970 257785f 12 66982 2355887 8 66990 24d4fce 8 66998 24f826c 8 67006 2517da1 8 67014 25413f4 8 67022 255baf0 8 67030 2581c41 8 67038 25b62f9 8 67046 25df468 8 67054 2745253 8 67062 24e4a0a 7 67069 24b4fc0 6 67075 24c1208 6 67081 23547e3 4 67085 24a7cc6 4 67089 24a86aa 4 67093 24a91de 4 67097 24aa2a2 4 67101 24ac0be 4 67105 24ae0b2 4 67109 24b12dc 4 67113 24b5d62 4 67117 24be6f8 4 67121 24cf7ad 4 67125 24d1fda 4 67129 24d353f 4 67133 25007ad 4 67137 252d492 4 67141 2557cb0 4 67145 2571b81 4 67149 25a1fbb 4 67153 31e52f6 36440 Index oetrn_key10 fragment in DBspace ihtl1dbs Physical Address 22d5c96 Creation date 06/20/2003 01:38:51 TBLspace Flags 802 Row Locking TBLspace use 4 bit bit-maps Maximum row size 878 Number of special columns 0 Number of keys 1 Number of extents 1 Current serial value 1 First extent size 41913 Next extent size 4191 Number of pages allocated 41913 Number of pages used 26073 Number of data pages 0 Number of rows 0 Partition partnum 9437596 Partition lockid 4194819 Extents Logical Page Physical Page Size 0 272008a 41913 Index oetrn_key11 fragment in DBspace ihtl1dbs Physical Address 22d5c9b Creation date 06/20/2003 14:06:56 TBLspace Flags 802

On 25 Sep 2003 02:13:59 -0700, robert.smith@huntleigh-healthcare.com (Rob Smith) wrote: >Hi All, >Question > >I have created a table with >First extent size 1600000 >Next extent size 160000 > >The indexes are kept in a seperate dbspace >All seems to go well until I noticed that extents are getting >gradually smaller with a massive extent being created recently in the >index dbspace >the extents in the data dbspace seems to be correct. Can someone >explain how this situation has occured or what is wrong with my logic. >The output of oncheck -pt on the table is below > Maybe not much free space in the dbspace left (hence the smaller extent sizes), then an allocation to the dbspace with a large number of inserts??