Query on Export/Import

We are planning to move our production database (Online V5.04) to a new database server. The disk configuration on the new server will will be different from the current one ( new dbspaces, larger chunks) and we will be carrying out an export/import to handle the migration. Before carrying out the final migration, we are planning a test run ( Export the database from a copy of the production database, edit the sql script to include extent sizing, dbspace placement and lock mode info and import the test database into the newly configured database server). To minimize production downtime for the migration, I would like to use the sql script used in the test run for the final migration. ( Donot want to edit the sql script just before the final import). The problem I see is that the sql script generated by dbexport contains the unload file names like the one below: { unload file name = tablenam_100.unl number of rows = 1163 } I am not sure how the unload file names are generated. ( I am guessing tablename_tabid.unl ). If the unload file names generated by the two dbexports are different, then I have no choice but to edit the sql script generated by the second dbexport. My question is: What is the best way to accomplish this database migration with minimal downtime?. If I ensure that the tabids of the tables in the test database are the same as those in the production database, can I use the sql script modified for the test import, for the final import? Thanks for all responses. Raj