Re: alter next size on sysmaster tables

On Mon, 29 Sep 1997 16:35:10 -0600, richard_kofler@edvg.co.at wrote: >We are running INFORMIX DSA V7.12 UC1 on SNI (Siemens Nixdorf) V5.43 > >I need advice how to avoid excessive (>12) number of extents on > a) sysmaster:informix.<tablename> tables > resinding in the root dbspace > b) databasename:owner.sys.... tables > residing in datadbs > >I tried the following procedure > >a) oninit -i > Got the sysmaster database, fextsize and nextsize 8 pages (16KB) >b) alter table syscolumns next size 128 >c) I do see now in onstat -pT sysmaster output the expected > first extent size of 8 and next extent size of 64 pages > >d) BUT: > when we then create the databases, our server is still using > 8 pages for the (next) extents to be allocated (for instance in > sysmaster:informix.syscolumns) > and I do not understand why - it should use 64 pages > >e) Analogous behavior is seen in the > databasename:user.syscolumns table where we changed > the next size before there were any tables created and still > only the default size 8 pages is seen for the extents to follow > >Why is that so and how to avoid many extents with >offsets very far from each other > [...] Sysmaster is not a template for the other databases, that is why the change has no effect. -- Although maybe some catalog tables should contain values for this purpose (hint-hint Informix). Create your database, then alter the nextsize in the local database catalogs. Depending on how you set up user permissions, you may want to look at systabauth. -Erik Jones