Extents

|>In article <2p0snc$cil@maicgn.SoftwareEngineering>, ar@mai.de (Achim Reiners) writes: |> |>|> |> Is it possible to change these for the system tables as well? These |> tables were the first ones exceeding the warning level of 8 extents! |>|>I know there is an answer to this one, but I don't remember, anyone else help? |>|> |>|>DCT |>|> |>|>From: billy.wheeler@digitec.co.za (Billy Wheeler) |>|> Yes, if you do a dbexport and change the .sql file produced. Before dbimporting you can set all your extent sizes. The syntax for cataalogue tables is as follows. ALTER TABLE syscolumns MODIFY NEXT SIZE 300 ; ALTER TABLE systabels MODIFY NEXT SIZE 300 ; and so on.. Changes to the catalogue tables should be made directly after the DATABASE command. You can size these extents by doing tbcheck -pT <dbname> and depending on the values in Number of extents, First extent Size and Next extent size then adjust your extent sizes accordingly. If doing a dbexport make sure that you reset your lock mode for each table as dbexport (all versions I've tried) tends to leave them out, Ithingk Release 6.0 has some improvements in this area but I'm not sure. Also I faintly remember leaving a backup (,dbxxx.sql) lying around, I think it was version 4.0, and this was also used by dbimport so watch out for that. Hope this Helps Tom Hogarty SNI Paderborn Germany <Standard Disclaimers Apply>