Re: What happens when a table has over 200 extents?

I agree with other posters that prevention is the best cause. Unload the table, and reload it. This process will put all your data in 1 big extent, and save you lots of headache. According to the Online manual, we use a page ( 2048 or 4096 ) to store information about a table. The first 24 bytes will be the compulsory header. Slot 1 of the table will contain 56 bytes about this table, such as extent size . blah blah blah. Slot 4 will store information about the indexes on this table, and slot 5 will contain all the extent information. In other words, if you have more indexes, you will have less space for slot 5. From field experience, 200 sounds about the approx number. Of course, if you have page size 4096, you can store much much more extents information. To see this page information, do the following : type tbcheck -pt <dbase>:<tabname>. look out for the physical address suppose the physical address is 0x10039, give the command tbcheck -pP 0x1 0x39. Hope this helps.