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
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 |
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. |
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 |
After migration from M2 to M2a (using export/import) there was no "workitemindex" directory.
During the export/import there were no errors in the log (output from repotools commandline) regards Daan. |
There is allready a "workitemindex" directory in our The index format has changed during M2, that's why a new index directory is created. The migration tool basically takes care of recreating the index, so after an export/import, the full text search should work. If this was not the case, maybe there was something in the migration log? -- Patrick |
Not sure work-item 6504 is adresses this issue. The workitem concerns indexing on database level.
The "workitemindex" directory for the jazz fulltext-search feature looks like something outside the derby databse. regards Daan. |
Dan,
Check Work Item 6504 https://jazz.net/jazz/web/projects/Jazz%20Project#action=com.ibm.team.workitem.viewWorkItem&id=6504 Remember you can always subscribe to WI that you are interested in. Elisabeth |
There is allready a "workitemindex" directory in our migrated M2a jazz directory. From the looks of it, this was created after changes were made in our new (M2a) environment.
Not knowing the internals of the fulltext search feature, my guess would be that the index is only updated when you change/add something in the jazz-repository. In our case where we did not copy the "workitemindex" directory during the migration from M2 to M2a, only changes done after the migration are included in fulltext searches. A command/feature is needed which scans the complete repository and creates/fills the "workitemindex" from scratch. regards Daan. |
Well, I thought that there might be some service running to create the fulltext serach indexes, which requires some manual override after an upgrade.
(a bit like the "locate" database on unix systems, which also needs to index the filesystem before you can actualy use it) regards Daan. |
Hmm, looks like fulltext search is not working anymore. It's a good point! I didn't notice this issue, but it appeared the same in my case. However in the server folder you will find folder named 'workitemindex', there is the index kept. I just copied this folder from the old version of the server to the new one and fulltext search started working again. Do you mean the same by saying that you wanted to 'manualy recreate indexes'? or did you mean something else? kind regards, Jakub |
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.