RE: Onload with detached indexes

Thanks alot for your response! Your suggesion raises a question in my mind... Would dbcopy unload data to ascii files which can later be loaded into the target or would it just do a insert into select from table kind of a thing? Thx, Shehla > -----Original Message----- > From: mosserp@WellsFargo.COM [SMTP:mosserp@WellsFargo.COM] > Sent: Wednesday, January 12, 2000 3:06 PM > To: SArshad@purolator.com > Cc: informix-list@iiug.org > Subject: RE: Onload with detached indexes > > Suggestion: > 1) Get Art Kagel's "dbcopy" program in his utils2_ak package on > http://www.iiug.org > 2) set up empty database on target instance, but without indexes > 3) make sure you have sufficient connectivity (I'm pretty sure you need > trusted relationship) between source and target servers > 4) run dbcopy to copy all data from source to target > 5) create detached indexes on target > 6) update stats on target (better yet, use Art's "dostats" program, also > in > utils2_ak package) > > I recently used roughly this approach to re-organize a db instance -- > worked > very well, and much faster than dbexport/dbimport. > > HTH > Paul Mosser > > -----Original Message----- > From: Arshad, Shehla [mailto:SArshad@purolator.com] > Sent: Wednesday, January 12, 2000 12:28 PM > To: informix-list@iiug.org > Subject: Onload with detached indexes > > > Hi > > Anybody with onload/onunload experience, please help! > > We are facing a problem copying a production database from one server to > another using onload utility. Both servers are running same version of IDS > (i.e. 7.30.FC7) and O/S (HP-UX 11.0). > > The database we are trying to copy has detached indexes. When we run > onload> utility to import the database, it complains about missing dbspaces. All > missing dbspaces are infact the ones that hold the detached indexes at the > source. We have tried creating all the dbspaces at the target server in > attempt to go around this problem after which onload failed complaining > about no more space in dbspace (one that holds the detached indexes). > > We want onload/onunload because its faster than dbexport/dbimport. It will > take approx 8 hours to dbexport and we dont have that kind of a window > available. Also, HPL is cumbersome and it will take quite an effort to > setup > jobs for 350 tables. Any smart suggestions!! > > PS: I know onload/onunload works between the two servers as we have copied > other database many times > > Thx, > > Shehla