Re: Changing First extent size by updating systables

Hi, You can probably do it, but it has no effect because by the time the information is in SysTables, the first extent has been allocated, never to be changed -- unless, perhaps, you rebuild the table with ALTER TABLE or ALTER INDEX. The actual extent information is held in separate storage -- in the dbspace dbspace, if I remember my nomenclature correctly. It is now available as part of the SysMaster database in the more recent versions of Online, meaning 6.0 and later, or maybe 7.0 and later -- my memory's rusty. Yours, Jonathan Leffler (johnl@informix.com) #include <disclaimer.h> }From: tgp@news.surfin.com (Tony G. Peterman) }Date: 14 Nov 1995 09:39:36 -0600 }X-Informix-List-Id: <news.18851> } }We are trying to change the size of the first extent on many of our tables. }I know we can unload the tables, and reload them; however, the amount of }downtime we are allowed is much less than required to do that. One of the }people I work with found that if we update fextsize in systables and alter }index to cluster that the new size tkes effect. I have talked with informix, }and what they say (basically) is that it is not supported, but they have no }documented cases of problems being caused by this. It seems that many people }are doing this exact same thing. } }So what I am looking for are peoples experience with this, what problems they }have run across, and what benifits they have gained. } }What we currently do is set the next size to be large enough to hold the entire }table, then alter to cluster, then set next size back to a modest growth factor. }this should at best give us 2 extents per table.