Re: dbexport/dbimport problems
And, do tbchek -pt to find size of all those tables, so you can set-up
right size extents for each table when you modify [database-name].sql.
William Zhu
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~bzhu@copley.com~~~~~~
On Mon, 23 Jan 1995, Jon C. Vemo wrote:
} At 08:51 AM 1/23/95, Naomi Walker 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.
} >}
} >} INFORMIX-OnLine Version 4.10.UE1
} >I would suspect that the tables are now in a zillion extents, since
} >they were not specifically set. Dbschema does not capture extents.
} >tbunload/tbload will greatly lessen the extents.
}
} Tbunload/tbload at this point would not do any good, since it performs a
} binary unload of all tables. I would suggest re-running export/import, with
} one change. After exporting, edit the [database-name].sql file created
} during the export, and add the appropriate extent size information for each
} table. This way when performing the import, the tables will be re-created
} with the extent sizes you want.
}
} Also, after completing the import, DON'T FORGET to run update statistics!
}
} Jon
} ==================================================================
} Jon Vemo Internet: jvemo@cyberspace.com
} Bothell, WA USA
} ------------------------------------------------------------------
} Watch out for road-kill on the information superhighway....SPLAT!!
} ==================================================================
}
}