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

I came across this bug in Q2 1999. I had hoped it might be fixed by now. I have never in fact worked with a version of IDs v7.x that DOES have a serviceable onload/onunload. Now, where's that Oracle brochure ....?!! Arshad, Shehla wrote in message <85inds$1uu$1@news.xmission.com>... > >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