How can I upgrade a test database?
Hi,
I've a test database created with a launch configuration (called [SDK] Create RTC Test Database.launch) in order to debug the extensions on which I'm working on. It's in standalone mode so it contains both ccm and jts (or so I'm supposing).
Now my customer has upgraded his RTC infrastructure from version 3.0.1 to version 4.0.3. I'd like to maintain this debug database in order to not recreate the entities needed for some test (projects, build definitions and so on).
I've tried to set a teamserver.properties file pointing to this database and run the repotools -addTables for both CCM and JTS without any error but when I try to start it on debug mode I still have mismatch version errors.
Is there a way to upgrade this kind of database?
Thanks,
Michele.
One answer
Hi Michele,
There in an interactive upgrade guide which you can use to help with this process:
https://jazz.net/help-dev/clm/topic/com.ibm.jazz.install.doc/topics/roadmap_clm_upgrade.html
You just need to select the version you're using, and your target upgrade version, and it will guide you through the steps.
I hope this helps,
John
There in an interactive upgrade guide which you can use to help with this process:
https://jazz.net/help-dev/clm/topic/com.ibm.jazz.install.doc/topics/roadmap_clm_upgrade.html
You just need to select the version you're using, and your target upgrade version, and it will guide you through the steps.
I hope this helps,
John
Comments
Hi John,
thanks for the answer but this is not what I'm looking for. I'm not going to upgrade an RTC installation. I'd already done this procedure in my real environment and it works. What I'm trying to do is to upgrade the database created using SDK (as part of creation of development environment), which is a STANDALONE database and probably not so similar to standard ones (CCM/JTS). I was supposing that running repotools -addTables command would be sufficient but it seems that I was wrong.
Michele.
Hi Michele,
Sorry, I misunderstood your requirements. The only option I can think of might be to migrate the required data to a standard database using repotools -export/-import, however, you may already have tried that approach.
Hopefully some of the others in the forum have some experience to help you.
Regards,
John
The guide says to run the upgrade script, which will run the repotools plus some other things for the upgrade. Maybe that's what you're missing from updating your database and config files.