2.0.0.1 to 2.0.1 Upgrade taking a long time
Hi,
We're currently in the process of upgrading from 2.0.0.1 to 2.0.1. We're at the repotools import stage but this seems to be taking a long time. It's currently been running for 3 hours. The previous repotools export step only took 30 mins at most. Does anyone know how long this should take? We're running a DB2 database. Cheers, Cliff |
4 answers
Hi, Hi Cliff, How large is your DB2 database? Like any export/import operation this is highly dependent upon (a) the amount of data and (b) the speed of the hardware and network involved. I have seen repotools exports take as little as 60 seconds (for an almost empty database) and as long as 12 hours or more for large production environments. -Patrick |
|
Hi Patrick,
Thanks for the response. I guess we fall into the large production environment category. A number of projects and possibly around 1000 testcases with associated artefacts. The repotool does not really give you an idea of how far along it is (unless you've used it before and know what stage it's at) so I was basing my expectation on how long the db2 backup and repotools export took. The backup and export took less than an hour. We had it running overnight for around 17 hours and it looked like it had hung when we came in this morning so we cancelled it and re-submitted. Cheers, Cliff |
The repotool does not really give you an idea of how far along it is (unless you've used it before and know what stage it's at) You should submit that as an enhancement request. :-) |
|
It finally completed successfully after taking 20 hours. It's not that big an installation! I noticed there is an enhancement request to allow incremental migration due to concerns over migration times.
Cheers, Cliff |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.