moving a database

hie guys i have the following setup on may database. The database is about 13gigs big, the problem is that i have 7 dbspaces and out of those 7 , three of them are made up of chunks using the actual physical name including the root dbspace. i want to use the onunload and onload utilities to export the entire database, my question to you is the when i want to load back the database will it remember which dbspace each table was located and put it there. I am hesitating to use the dbexport and dbimport becauze it could take me days to do it. Any help or suggestions will be appreciated. -- Blessing K. Sagonda Networks Ok Zimbabwe Sent via Deja.com http://www.deja.com/ Before you buy.

bsagonda@my-deja.com wrote: > hie guys i have the following setup on may database. > The database is about 13gigs big, the problem is that i have 7 dbspaces > and out of those 7 , three of them are made up of chunks using the > actual physical name including the root dbspace. > > i want to use the onunload and onload utilities to export the entire > database, my question to you is the when i want to load back the > database will it remember which dbspace each table was located and put > it there. > > I am hesitating to use the dbexport and dbimport becauze it could take > me days to do it. > > Any help or suggestions will be appreciated. > -- > Blessing K. Sagonda > Networks > Ok Zimbabwe > > Sent via Deja.com http://www.deja.com/ > Before you buy. onunload/onload is fast, but cannot handle multiple dbspaces. If you onload a database, all tables go into a single dbspace. If you have onunloaded a table, you could place that in a specific dbspace. So, you could onunload your big tables independantly, drop them from your database, then onunload what remains, recreate your instance, onload your database into its dbspace, and finally onload your big tables one at a time into their own dbspaces. dbexport/dbimport with the -ss option, on the other hand, will restore your database the way it was . ontape is not an option since you are going to be changing chunk names. You could estimate the length of time and the space requirements of dbexport by writing a script to unload tables from your database sequentially using dirty read (OLTP performance will be affected). To speed up dbimport, make sure its not logged (default), and use appropriate values of PDQPRIORITY & PSORT_NPROCS. You may want to change parameters in your ONCONFIG as well (MAX_PDQPRIORITY, LRU_MAX & MIN). HTH Rudy

If you have IDS7.2 or higher, use high performance loader. bsagonda@my-deja.com wrote: > hie guys i have the following setup on may database. > The database is about 13gigs big, the problem is that i have 7 dbspaces > and out of those 7 , three of them are made up of chunks using the > actual physical name including the root dbspace. > > i want to use the onunload and onload utilities to export the entire > database, my question to you is the when i want to load back the > database will it remember which dbspace each table was located and put > it there. > > I am hesitating to use the dbexport and dbimport becauze it could take > me days to do it. > > Any help or suggestions will be appreciated. > -- > Blessing K. Sagonda > Networks > Ok Zimbabwe > > Sent via Deja.com http://www.deja.com/ > Before you buy.