Re: dbexport/dbimport problems

In article <3g0ng9$9i7@cssun.mathcs.emory.edu> matuscak@rohrer.com (Joe Matuscak) writes: >On Mon, 23 Jan 1995, Tony Desborough wrote: > >> As the number of extents for some tables was becoming excessive, >> a full dbexport/dbimport was carried out on the database. Although >> no problems were experienced during the export/import, once the >> system was live again, the performance had degraded *significantly*. >> After a days use, the performance is still awful. I had expected >> the performance to increase. > >Did you use the SQL that dbexport generated directly without editing it? >Dbexport/dbimport looses all manner of useful information. Including, for >example, extent sizes, table locations in specific dbspaces and lock mode. >If you do nothing, the tables all get created in the root dbspace, with >page mode locking and an extent size of 8 pages. This tends to be pretty... ^^^^^^^^^^^^^^^^^^^^^^ I believe that although an extent size of 8 pages is used by dbimport while it is creating a table, these extents are contiguous, and so are combined and treated as a single extent when the table's load is finished. -- Keith Davies Internet: keith@keithd.demon.co.uk Tel.: +44 1582 833651