Move from M2 to M2a
When upgrading from M2 to M2a, can I just install M2a and copy our existing database (or do I need a database upgrade/conversion) ?
thx Daan. |
13 answers
After migration from M2 to M2a (using export/import) there was no I could think of two reasons: 1) The re-indexing is now triggered by the migration tool itself, so make sure you were using the latest version. 2) The index location is specified in the teamserver.properties. Make sure that the migration tool creates the index at the same location (I think there is a parameter to point the tool to the teamserver.properties file). Maybe the migration created the index, but not at the correct location (so the server creates a new one at the location specified in its teamserver.properties file). HTH, Patrick |
|
I have "re-played" the M2 -> M2a migration, but with the same results. After repotools -import, no workitemindex directory is created.
(I did a search on the local disk to make sure the directory was not created in some other location). repotools printed the following lines w.r.t. indices: Begin rebuilding indices End rebuilding indices (I have saved the output of both repotools commands and I have the export.tar file available if you are interested). regards Daan. |
Hello Patrick,
I have the same problem as Dan when using the migration tool. Having a Derby DB and using repotools does not re-create the workitemindex. Version of repotools installed with M2a: 0.6.0.I20070811-1447 Is that the latest version? The empty WorkitemIndex folder gets populated when I i.e edit or create a WI after the migration and are searchable. There is no other workitemindex folder. Regards, Elisbeth |
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.