Re: dbexport/dbimport problems

> We have a production database that has been live for about a > year. Application performance on this database has been fine. > > 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. > > Has anyone had similar experiences following a dbimport, or can > anyone explain what the problem may be. Well, if you'd placed the tables in different dbspaces (which any OnLine person worth his salt always should do), you'd end up with them all back in the root dbspace because dbexport loses all the engine-specific syntax. That could be causing disk thrashing. You'd also lose any LOCK MODE ROWs, so maybe some processes are having to wait for locks to be released which weren't blocking them before. Reason: dbexport/ dbimport were originally intended to be SE-to-OnLine migration tools. Wouldn't it be nice if they gave dbexport a '-ss' (special syntax) option like they have done for dbschema. akent@cix.compulink.co.uk (Andy Kent) -------------------------------------