Is DB migration needed to migrate from 2.0beta1 to 2.0 GA ?
4 answers
When you are upgrading to RTC 2.0 from a previous release, a database migration is usually required. Instructions on how to do so can be found at the following link,
http://publib.boulder.ibm.com/infocenter/rtc/v2r0m0/topic/com.ibm.team.install.doc/topics/c_upgrading.html?resultof=%22migrate%22%20%22migrat%22%20%22database%22%20%22databas%22
When you are upgrading the Jazz Team Server, where schema changes occur,you must also preform a repository migration. A repository migration is the process of converting the contents of the database from one format to another. Instructions on how to do so can be found atthe following link,
http://publib.boulder.ibm.com/infocenter/rtc/v2r0m0/topic/com.ibm.team.install.doc/topics/c_migrate_overview.html?resultof=%22database%22%20%22databas%22
Hope this helps,
http://publib.boulder.ibm.com/infocenter/rtc/v2r0m0/topic/com.ibm.team.install.doc/topics/c_upgrading.html?resultof=%22migrate%22%20%22migrat%22%20%22database%22%20%22databas%22
When you are upgrading the Jazz Team Server, where schema changes occur,you must also preform a repository migration. A repository migration is the process of converting the contents of the database from one format to another. Instructions on how to do so can be found atthe following link,
http://publib.boulder.ibm.com/infocenter/rtc/v2r0m0/topic/com.ibm.team.install.doc/topics/c_migrate_overview.html?resultof=%22database%22%20%22databas%22
Hope this helps,
Thanks for that
I was wondering how one determines whether these things are needed for a
particular existing version, going to 2.0GA
Where do I look to find out the situation for 2.0beta1 ?
On 7/2/2009 1:07 PM, sbagot wrote:
I was wondering how one determines whether these things are needed for a
particular existing version, going to 2.0GA
Where do I look to find out the situation for 2.0beta1 ?
On 7/2/2009 1:07 PM, sbagot wrote:
When you are upgrading to RTC 2.0 from a previous release, a database
migration is usually required. Instructions on how to do so can be
found at the following link,
http://publib.boulder.ibm.com/infocenter/rtc/v2r0m0/topic/com.ibm.team.install.doc/topics/c_upgrading.html?resultof=%22migrate%22%20%22migrat%22%20%22database%22%20%22databas%22
When you are upgrading the Jazz Team Server, where schema changes
occur,you must also preform a repository migration. A repository
migration is the process of converting the contents of the database
from one format to another. Instructions on how to do so can be found
atthe following link,
http://publib.boulder.ibm.com/infocenter/rtc/v2r0m0/topic/com.ibm.team.install.doc/topics/c_migrate_overview.html?resultof=%22database%22%20%22databas%22
Hope this helps,
Dave
During the 2.0 release cycle we communicated the need for repository migration in the release notes for each milestone. We set this in our great detail including exactly what versions we supported migration from. When we reached 2.0 GA, we didn't provide as much detail great detail because when we looked at it, pretty much any 2.0 early release (and of course 1.0) would require repository migration to 2.0. To answer your question, migration is definitely required from Beta 1 as you'll see in the release notes for M2, M3, Beta 2, etc.
Adrian
During the 2.0 release cycle we communicated the need for repository migration in the release notes for each milestone. We set this in our great detail including exactly what versions we supported migration from. When we reached 2.0 GA, we didn't provide as much detail great detail because when we looked at it, pretty much any 2.0 early release (and of course 1.0) would require repository migration to 2.0. To answer your question, migration is definitely required from Beta 1 as you'll see in the release notes for M2, M3, Beta 2, etc.
Adrian
I guess I didn't think to look in the release notes for another beta :-)
Thanks Adrian
On 7/2/2009 7:37 PM, acho wrote:
Thanks Adrian
On 7/2/2009 7:37 PM, acho wrote:
Dave
During the 2.0 release cycle we communicated the need for repository
migration in the release notes for each milestone. We set this in
our great detail including exactly what versions we supported
migration from. When we reached 2.0 GA, we didn't provide as much
detail great detail because when we looked at it, pretty much any 2.0
early release (and of course 1.0) would require repository migration
to 2.0. To answer your question, migration is definitely required
from Beta 1 as you'll see in the release notes for M2, M3, Beta 2,
etc.
Adrian