Migrating the jazz repository from 1.0.1.1 to 20 M3D1
I didn't see any instructions in the 2.0 M3D1 install/upgrade doc that mentions a migration of the repository (db2) from 1.0.1.1 to 2.0 M3D1. I see there are instructions on migrating between vendor databases. Are there instructions for migrating a db2 repository from 1.0.1.1 to 2.0 M3D1. I'm currently getting this error after installing M3D1 over 1.0.1.1..
CRJAZ1050I There is a version mismatch between the installed code and the database. See the product documentation for migrating theJazz repository.
CRJAZ1050I There is a version mismatch between the installed code and the database. See the product documentation for migrating theJazz repository.
4 answers
After some more digging I did find this article on migrating repositories from version x to version y.
https://jazz.net/learn/LearnItem.jsp?href=content/docs/repo-migration/index.html.
I followed the instructions and the export with 1.0.1.1 was successful but the import using M3D1 produced this error.
C:\Program Files\IBM\JazzTeamServer\server>repotools -import fromFile=c:\export_from_version_1.0.1.1.tar
Repo Tools, Version 2.0 M3D1 - I20090327-1303
Provisioning using "C:\Program Files\IBM\JazzTeamServer\server\\provision_profiles".
CRJAZ1218I The bundle "com.ibm.team.repository.servlet" with the id 45 is invalid, it is not "RESOLVED".
CRJAZ1218I The bundle "com.ibm.team.repository.service.monitoring" with the id 46 is invalid, it is not "RESOLVED".
CRJAZ1218I The bundle "com.ibm.team.repository.jdbcdriver.oracle" with the id 49
is invalid, it is not "RESOLVED".
CRJAZ1218I The bundle "com.ibm.team.repository.jdbcdriver.sqlserver" with the id 51 is invalid, it is not "RESOLVED".
CRJAZ1218I The bundle "com.ibm.icu" with the id 62 is invalid, it is not "RESOLVED".
To ignore invalid bundles, re-run repotools with the following property definition enabled in the script:
-Dcom.ibm.team.repotools.rcp.allowInvalidBundles=true
CRJAZ1225I Migration failed.
Is this normal and if so how do I enable this property?
https://jazz.net/learn/LearnItem.jsp?href=content/docs/repo-migration/index.html.
I followed the instructions and the export with 1.0.1.1 was successful but the import using M3D1 produced this error.
C:\Program Files\IBM\JazzTeamServer\server>repotools -import fromFile=c:\export_from_version_1.0.1.1.tar
Repo Tools, Version 2.0 M3D1 - I20090327-1303
Provisioning using "C:\Program Files\IBM\JazzTeamServer\server\\provision_profiles".
CRJAZ1218I The bundle "com.ibm.team.repository.servlet" with the id 45 is invalid, it is not "RESOLVED".
CRJAZ1218I The bundle "com.ibm.team.repository.service.monitoring" with the id 46 is invalid, it is not "RESOLVED".
CRJAZ1218I The bundle "com.ibm.team.repository.jdbcdriver.oracle" with the id 49
is invalid, it is not "RESOLVED".
CRJAZ1218I The bundle "com.ibm.team.repository.jdbcdriver.sqlserver" with the id 51 is invalid, it is not "RESOLVED".
CRJAZ1218I The bundle "com.ibm.icu" with the id 62 is invalid, it is not "RESOLVED".
To ignore invalid bundles, re-run repotools with the following property definition enabled in the script:
-Dcom.ibm.team.repotools.rcp.allowInvalidBundles=true
CRJAZ1225I Migration failed.
Is this normal and if so how do I enable this property?
After some more digging I did find this article on migrating repositories from version x to version y.
https://jazz.net/learn/LearnItem.jsp?href=content/docs/repo-migration/index.html.
I followed the instructions and the export with 1.0.1.1 was successful but the import using M3D1 produced this error.
C:\Program Files\IBM\JazzTeamServer\server>repotools -import fromFile=c:\export_from_version_1.0.1.1.tar
Repo Tools, Version 2.0 M3D1 - I20090327-1303
Provisioning using "C:\Program Files\IBM\JazzTeamServer\server\\provision_profiles".
CRJAZ1218I The bundle "com.ibm.team.repository.servlet" with the id 45 is invalid, it is not "RESOLVED".
CRJAZ1218I The bundle "com.ibm.team.repository.service.monitoring" with the id 46 is invalid, it is not "RESOLVED".
CRJAZ1218I The bundle "com.ibm.team.repository.jdbcdriver.oracle" with the id 49
is invalid, it is not "RESOLVED".
CRJAZ1218I The bundle "com.ibm.team.repository.jdbcdriver.sqlserver" with the id 51 is invalid, it is not "RESOLVED".
CRJAZ1218I The bundle "com.ibm.icu" with the id 62 is invalid, it is not "RESOLVED".
To ignore invalid bundles, re-run repotools with the following property definition enabled in the script:
-Dcom.ibm.team.repotools.rcp.allowInvalidBundles=true
CRJAZ1225I Migration failed.
Is this normal and if so how do I enable this property?
https://jazz.net/learn/LearnItem.jsp?href=content/docs/repo-migration/index.html.
I followed the instructions and the export with 1.0.1.1 was successful but the import using M3D1 produced this error.
C:\Program Files\IBM\JazzTeamServer\server>repotools -import fromFile=c:\export_from_version_1.0.1.1.tar
Repo Tools, Version 2.0 M3D1 - I20090327-1303
Provisioning using "C:\Program Files\IBM\JazzTeamServer\server\\provision_profiles".
CRJAZ1218I The bundle "com.ibm.team.repository.servlet" with the id 45 is invalid, it is not "RESOLVED".
CRJAZ1218I The bundle "com.ibm.team.repository.service.monitoring" with the id 46 is invalid, it is not "RESOLVED".
CRJAZ1218I The bundle "com.ibm.team.repository.jdbcdriver.oracle" with the id 49
is invalid, it is not "RESOLVED".
CRJAZ1218I The bundle "com.ibm.team.repository.jdbcdriver.sqlserver" with the id 51 is invalid, it is not "RESOLVED".
CRJAZ1218I The bundle "com.ibm.icu" with the id 62 is invalid, it is not "RESOLVED".
To ignore invalid bundles, re-run repotools with the following property definition enabled in the script:
-Dcom.ibm.team.repotools.rcp.allowInvalidBundles=true
CRJAZ1225I Migration failed.
Is this normal and if so how do I enable this property?
Got one step further. Edited the repotools.bat to enable the -Dcom.ibm.team.repotools.rcp.allowInvalidBundles=true . It had a colon (:) in column 1 which I removed.
I then re-ran the import command and ran into the issues described in this work item defect https://jazz.net/jazz/web/projects/Jazz%20Foundation#action=com.ibm.team.workitem.viewWorkItem&id=74765 .
I dropped my existing database (had a backup) and recreated it with PAGESIZE 8K as per the work-around in the above defect.
My import then worked fine.
I then re-ran the import command and ran into the issues described in this work item defect https://jazz.net/jazz/web/projects/Jazz%20Foundation#action=com.ibm.team.workitem.viewWorkItem&id=74765 .
I dropped my existing database (had a backup) and recreated it with PAGESIZE 8K as per the work-around in the above defect.
My import then worked fine.
Tom,
Looks like your repotools is not provisioned correctly. (use -clean option to reprovision the repository tools)
Use repotools -clean -import ...
(Remove -Dcom.ibm.team.repotools.rcp.allowInvalidBundles=true from your scripts )
--- Balaji
Jazz Server Team
Looks like your repotools is not provisioned correctly. (use -clean option to reprovision the repository tools)
Use repotools -clean -import ...
(Remove -Dcom.ibm.team.repotools.rcp.allowInvalidBundles=true from your scripts )
--- Balaji
Jazz Server Team
Got one step further. Edited the repotools.bat to enable the -Dcom.ibm.team.repotools.rcp.allowInvalidBundles=true . It had a colon (:) in column 1 which I removed.
I then re-ran the import command and ran into the issues described in this work item defect https://jazz.net/jazz/web/projects/Jazz%20Foundation#action=com.ibm.team.workitem.viewWorkItem&id=74765 .
I dropped my existing database (had a backup) and recreated it with PAGESIZE 8K as per the work-around in the above defect.
My import then worked fine.