RQM export takes too long: is there any way to tuning repotools for RQM export?
![]() Our current RQM 2.0.1.1 fixpack 3 database is 70GB, the extract took 50+ hours. We will still need to run the import and then the upgrade to 3.0.1.5 and upgrade again to 4.0.2. If the first step took 50+ hours we will not have a large enough outage window for the change and upgrade. The straight Oracle dump took less than 1 hour. The VM running the extract has 32 GBR RAM ad 8 cpus, test to the shared disk we can write 10 - 20 mb / second. 1) as per http://jazz.net/library/article/206 which is for RTC upgrade benchmark(from 1.x to 2.x) it suggests the import should be estimated as 3 times of export, does that apply to RQM migration or not? Is there any benchmark for RQM upgrade? 2) More importantly, is there any way to tuning the RQM export/import repotools to reduce the time? Any suggestions are appreciated. |