Repository Migration possible missing step for M3 to Beta 2
Looking at https://jazz.net/learn/LearnItem.jsp?href=content/docs/repo-migration/MigrateData0.6Beta2.html
When using DB2, one should first drop the database (as stated in steps for Beta1 to Beta2 migration) and recreate, right? Or will the repotools handle importing data into a database that already has the same data but with potentially different schema? |
4 answers
Hi Steve,
repotools usually handles recreation of a new schema over an existing schema. But Beta1 to Beta2 is little special. Our schema creation routines have changes a lot. So, after you export your Beta1 data using Beta1 repotools, you need to manually drop the DB2 database and recreate the database connection. Then run Beta2 repotools -import to create the new Jazz schema and the data. ----- Balaji "sspeiche" <sspeiche@us.ibm-dot-com.no-spam.invalid> wrote in message news:fkbeff$acn$1@localhost.localdomain... Looking at |
Balaji
Are you suggesting that doing a migration from M3 to B2 doesn't require dropping the database? I think Steve's point was that the way the M3 instructions are written is confusing. First is says that exporting the database is "just in case" something goes wrong. But the last step is to re-import the backup. Seems like the M3 migration instructions are missing the "IMPORTANT WARNING" section from the B1 to B2 instructions. Balaji Krish wrote: Hi Steve, |
Balaji
Are you suggesting that doing a migration from M3 to B2 doesn't require dropping the database? I think Steve's point was that the way the M3 instructions are written is confusing. First is says that exporting the database is "just in case" something goes wrong. But the last step is to re-import the backup. Seems like the M3 migration instructions are missing the "IMPORTANT WARNING" section from the B1 to B2 instructions. Balaji Krish wrote: Hi Steve, |
We changed the schema metadata in M2. M3 is using the new schema metadata.
So, if you migrating from M3 to Beta2, you don't need to manually delete the database. repotools would delete the tables and recreate the new schema. ---- Balaji "Mark D. Parry" <parrym@us.ibm.com> wrote in message news:476ABD29.2040004@us.ibm.com... Balaji |
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.