Migrating RTC server to 3.0RC2
![]()
Hi to all,
i tried to migrate the server from 2.x version to 3.0RC2 version. To do this, i followed the guide in this page https://jazz.net/wiki/bin/view/Main/RTCtoCCM30MigrationSteps I found an error in this step: https://jazz.net/wiki/bin/view/Main/RTCtoCCM30MigrationSteps#RTC_repository_Database_Migratio both using the automatic and the manual method. When i import user information into the JTS server i have this error: "CRJAZ0596I - Migration handler not registered for migrating "{0}" namespace URI". In the step "Export user information from the RTC database", i believe that i must create the jtsData.tar from the RTC server 2.x. However, i noted that this step performs correctly only if i do this step creating the .tar from the server 3.0RC2. I must create the jtsData from RTC server 2.x, isn't true? If yes, any suggestions to resolve the CRJAZ0596I error ? Thanks, Giu |
17 answers
![]()
Ralph,
Would you be willing to explain the exact steps that it takes to upgrade from 2.0 to 3.0 using the Derby databases? I can't find any clear instructions on how to upgrade from 2.0 to 3.0 with only the Derby databases anywhere, but you mention above that you have done it and that copying the repositoryDB file and changing the property is all it takes. I tried that, but I received an ominous error when running rtc_migration.bat or repotools_jazz.bat. I can't even do a repotools_jazz.bat -verify without getting the error. Here it is:
Any thoughts? Thanks, jay Jay |
![]()
Ralph Schoon (63.3k●3●36●46)
| answered Dec 02 '10, 1:10 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Hi Jay,
we have made sure that the help contains a lot of information about upgrading. I have followed it myself and it works. In addition http://jazz.net/library/article/524 was created to complement the help. I have also outlined the steps in prior posts. Copying the Derby DB is only a very small step you will also be guided to migrate data from your old DB to the new one. Ralph Ralph,
Any thoughts? Thanks, jay Jay |
![]()
Ralph,
Thanks for your response. I've looked at those pages and through the help extensively, but repotools always posts this error: CRJAZ1204I The database "C:/IBM/JazzTeamServer3.0/server/conf/jazz/derby/repositoryDB" does not exist, the dat I'll give it another try this morning and if anything significant comes out of it, I'll be sure to post it. Thanks again, Jay Hi Jay, Ralph,
Any thoughts? Thanks, jay Jay |
![]()
Ralph Schoon (63.3k●3●36●46)
| answered Dec 02 '10, 7:44 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Hi Jay,
I am not sure at what step you are. In general one of the first steps is to (after backup) migrate the old database over. This step would create the derby database for JTS and modify (backup the old data before you do that) the existing one to serve for RTC. This is described here http://publib.boulder.ibm.com/infocenter/clmhelp/v3r0/topic/com.ibm.jazz.install.doc/topics/t_update_repo_data_mig.html. For Derby you have to copy the old database over to its new location - you have to check the two teamserver.properties files where the Derby DB is supposed to go. You can also modify that location. I am pretty sure that something went wrong in this step. Thanks, Ralph Ralph, |
![]()
Ralph,
Sorry to bother you with this again, but could you verify the steps I am taking? 1.) Install, check the upgrade box at the end. (Works) 2.) Start the migration with repotools (Works). Run: repotools-jazz -migration_updateConfigurationFiles oldJazzHome=<RTC2>/server/conf 3.) Check the files and fix the database properties. Point the jts database to server/jtsRepositoryDB and the jazz database to server/jazzRepositoryDB. 4.) Copy the RTC2.0 repositoryDB to <RTC3>/server/jazzRepositoryDB. 5.) Run repotools_jazz.bat -addTables (or use rtc_migration.bat file) (fails after connecting to the database with the previous posted error) Are those steps correct? I'm starting to wonder if it is because I am on Windows Server 2008R2. Thanks again, Jay Jay |
![]()
Everyone,
I wanted to post a message on the forum and let you know that I figured out the problem. For whatever reason, migrating from RTC 2.0.0.2 iFix 3 to RTC 2.0.0.2 iFix 5 before migrating to RTC 3.0 fixed the problem. I don't know why this would be an issue, but I noticed that the size of the Derby databases differed by a megabyte between iFix 3 and iFix 5. After migrating to iFix 5, everything worked perfectly when migrating to 3.0. Thanks for you help! Jay |
![]()
Thanks rschoon,
I had the same problem and following the steps you described did the trick. Al www.biedsnel.com Hi, Hi to all, |
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.