Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
SaTriGuy — — source: Informix-list mailing list archive (1991-1998)
>I have recently found that the system catalog of one of my databases
>is fragmented with more than 10 extents. While I have performed
>numerous INFORMIX extent defragmentation on "databases" prior to this,
>I have totally no clue on how to handle the fragmented system catalog.
>Is there a need to defragment system catalogs? If yes, how? Pls
>enlighten.
>
>syscolumns 11 extents
>sysconstraints 8 extents
>sysobjstate 11 extents
It's probably not necessary to bother with this, especially on the 7.x product.
Most of the catalogue is actually going to reside in the in-memory cache pool
and will only be reloaded as needed.
Also, in 7.x all of the extent information is loaded in memory when the table
is opened. In 5.x only the first 8 extents were loaded. This is why the "more
than 8 extents" business was such a big deal. This means that the main
performance reason for keeping the extents less than 8 has been eliminated.
Madison Pruet
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.