Re: Restarting a dbimport

Sorry to give you the bad news, but editting the *.sql files will not help. dbimport only runs if the DB does not exist. It will not "merge" w/existing DB. dbload will allow you to load into an existing DB/table (more than once so you can double up!). dbexport/dbimport are written to "save the user from themselves" in this case, it is not helpful... The only thing I can suggest is edit the *.sql file (make a backup copy) to remove the dup database so the whole thing will import clean, then copy the backup copy and edit "everything" but the dup database into another DB and use some SQL to merge them together... BTW: the *.sql file name must be the same as the DB, etc. You can copy/rename the directory and edit the *.sql file to match. Steve -- Steven L Cooper Manager, Systems Engineering --------------------------------------- The views expressed here are mine and you can't have them...unless you agree! David Williams <djw@smooth1.demon.co.uk> wrote in article <FYb0aLAz5yg0Ewp4@smooth1.demon.co.uk>... > In article <65rn0t$e56@newsserv.cs.sunysb.edu>, Joe Trubisz > <trubisz@cs.sunysb.edu> writes > >Hi... > > > >I had a dbimport fail after 12h because the dbimport exported > >2-tables with the same name, but different owners. Dbexport > >apparently didn't like that. Unfortunately, it happened almost > >at the end of the script. Without rerunning the whole thing > >all over again, is there a way to just 'pick up' where it left > >off, after the offending part of the script is removed? > > > Was the dbexport done to disk i.e. is there an <xxx>.exp > directory. If so it will contain a <xxx>.sql file. > > Try editing that.... > > NOTE: I have not tried this but this is what I would try next. > Removed everything up to where it failed and try again. > > NOTE 2: The comments in {} in the .sql file ARE SIGNIFICANT > ^^^ > > >Thanks in advance. > > > > > >Joe > > -- > David Williams >