Re: Correcting Next Extent problems.

Jonathan Leffler writes: |> Jack Parker had written: |> >... On system catalogs. |> > |> >On one of our engines, syscolumns and systables have over 8 extents. Now this |> >is going to be interesting - how can I drop and re-create a table that |> >defines itself? |> |> You can't alter the system catalog -- error -511 ensues. You can however |> alter the next extent size if you are sufficiently privileged. I can't |> remember of the top of my head whether that means you have to be informix or |> whether being the principal DBA (the one who created the database and has |> priority 9 in sysusers) is sufficient. |> |> Syntax: ALTER TABLE Systables MODIFY NEXT SIZE 128; While Jonathan is correct, I will venture to say that this entire discussion is misguided. Contrary to what the manuals lead you to believe, having more than 8 extents will not have any significant impact on the performance of your system. The reason 8 is used is that 8 extents are tracked in the tblspace shared memory structure. When there are >8, the tblspace tblspace page for the table will be checked. For frequently accessed tables, this will cause the TT page to sit in cache, so there is no great loss. For system tables, it is even less of a problem, because they are read into *local* cache when sqlturbo is started up, so accessing that data is really not an issue. So I wouldn't bother trying to change those extent sizes. Dave