RE: Best method for moving a database

With only the information you provide I would use dbexport/dbimport becouse it is not too big (600MBytes) a system and becouse you will have all the controls at your disposal to place every object into the dbspace that you want whether is a table or an index, etc. etc. You can test the export/import process in the backup machine also: do dbexport copy into the backup machine edit the xxxx.sql that results from the export and put ...... in dbspace ..... where it is needed verify the extent sizes and locking then create the new dbspaces in the backup machine acording to the schema do the import When the result is ok save the script for reference and prepare the final move With the help of a backup in another machine AND on tape you should do OK > -----Original Message----- > From: Tony Flaherty [SMTP:aef@mfs.misys.co.uk] > Sent: Thursday, March 18, 1999 7:28 AM > To: informix-list@iiug.org > Subject: Best method for moving a database > > Hi, > > I'm reorganising my system, creating new dbspaces and moving the > databases. > > What's the most efficient way of doing this? I have to drop all of the > existing dbspaces prior to creating the new ones. I was planning on using > dbexport/dbimport but I do have a back-up machine, so I could create the > schema for the databases in the new dbspaces and then use sql scripts to > load the databases across the network from the copies on the back-up > machine. Hope this makes sense! > > Also, I could use onunload, if I do, do I need to create the > database/tables > before using onload? > > I guess whatever I do I need to turn off logging for the databases to > prevent long transaction and out of locks errors. One or two of the > transaction tables have aprox. 500,000 rows. > > The biggest database is about 600Mb according to the tbl_usage prog. > downloaded form the IIUG. > > HP-UX 10.20 > Online 7.24.UC5 > > > Thanks, > Please no RTFM replies, I am, but this is a screw it up and get a job > somewhere else event and I kinda want to be sure I know what I'm doing. > That's why I'm inclined to use dbimport, its what I know. > > --------------------------------------- > Tony Flaherty aef@mfs.misys.co.uk > Analyst Programmer > Misys Financial Systems > All statements and opinions are my own, > Misys don't pay me enough to have opinions > on their behalf > > . >