Errors on import of tar from Beta2a migrating to M5
I went through the steps to migrate my server from Beta 2 (actually
Beta2a) to M5 and everything worked as it should until I performed the import - I get the following messages displayed during that import - so I am assuming I did something wrong - just not sure what. I would like some guidance before I try to go any further with this. I am using Tomcat with Derby as my database for this server: # ./repotools.sh -import fromFile=/tmp/beta1export.tar teamserver.properties=./teamserver.properties Repo Tools, Version 0.6.0.I20080223-1237 The file "./profile.ini" was not found. Provisioning will not be performed. The bundle "com.ibm.team.apt.service" with the id 4 is invalid, it is not RESOLVED. The bundle "com.ibm.team.repository.common.transport" with the id 5 is invalid, it is not RESOLVED. The bundle "com.ibm.team.interop.service.managers.clearquest" with the id 8 is invalid, it is not RESOLVED. The bundle "com.ibm.team.scm.service" with the id 11 is invalid, it is not RESOLVED. The bundle "com.ibm.team.repository.common" with the id 12 is invalid, it is not RESOLVED. The bundle "com.ibm.team.repository.jdbcdriver.db2" with the id 17 is invalid, it is not RESOLVED. The bundle "com.ibm.team.scm.svn.service" with the id 18 is invalid, it is not RESOLVED. The bundle "com.ibm.team.apt.common" with the id 20 is invalid, it is not RESOLVED. The bundle "com.ibm.team.fulltext.service" with the id 25 is invalid, it is not RESOLVED. The bundle "com.ibm.team.dashboard.service" with the id 29 is invalid, it is not RESOLVED. The bundle "com.ibm.team.interop.service" with the id 31 is invalid, it is not RESOLVED. The bundle "com.ibm.team.log4j.ui" with the id 34 is invalid, it is not RESOLVED. The bundle "com.ibm.team.scm.admin.common" with the id 38 is invalid, it is not RESOLVED. The bundle "com.ibm.team.dashboard.common" with the id 39 is invalid, it is not RESOLVED. The bundle "com.ibm.team.reports.service" with the id 40 is invalid, it is not RESOLVED. The bundle "com.ibm.team.coverage.common" with the id 41 is invalid, it is not RESOLVED. The bundle "com.ibm.team.filesystem.service.workitems" with the id 42 is invalid, it is not RESOLVED. The bundle "com.ibm.team.foundation.common" with the id 45 is invalid, it is not RESOLVED. The bundle "com.ibm.team.repository.provision" with the id 52 is invalid, it is not RESOLVED. The bundle "com.ibm.team.process.service.migration" with the id 53 is invalid, it is not RESOLVED. The bundle "com.ibm.team.interop.common" with the id 55 is invalid, it is not RESOLVED. The bundle "com.ibm.team.datawarehouse.common" with the id 57 is invalid, it is not RESOLVED. The bundle "com.ibm.team.reports.common" with the id 58 is invalid, it is not RESOLVED. The bundle "com.ibm.team.filesystem.service" with the id 59 is invalid, it is not RESOLVED. The bundle "com.ibm.team.workitem.service" with the id 60 is invalid, it is not RESOLVED. The bundle "com.ibm.team.datawarehouse.service.analysis" with the id 62 is invalid, it is not RESOLVED. The bundle "com.ibm.team.filesystem.common.workitems" with the id 63 is invalid, it is not RESOLVED. The bundle "com.ibm.team.scm.admin.service" with the id 64 is invalid, it is not RESOLVED. The bundle "com.ibm.team.analysis.common" with the id 69 is invalid, it is not RESOLVED. The bundle "com.ibm.team.opaque.service" with the id 72 is invalid, it is not RESOLVED. The bundle "com.ibm.team.datawarehouse.service" with the id 74 is invalid, it is not RESOLVED. The bundle "com.ibm.team.build.service" with the id 76 is invalid, it is not RESOLVED. The bundle "com.ibm.team.workitem.common" with the id 80 is invalid, it is not RESOLVED. The bundle "com.ibm.team.repository.service" with the id 81 is invalid, it is not RESOLVED. The bundle "com.ibm.team.process.common" with the id 82 is invalid, it is not RESOLVED. The bundle "com.ibm.team.build.common" with the id 86 is invalid, it is not RESOLVED. The bundle "com.ibm.team.repository.jdbcdriver.oracle" with the id 87 is invalid, it is not RESOLVED. The bundle "com.ibm.team.repository.jdbcdriver.derby" with the id 91 is invalid, it is not RESOLVED. The bundle "com.ibm.team.datawarehouse.service.build" with the id 95 is invalid, it is not RESOLVED. The bundle "com.ibm.team.scm.svn.common" with the id 96 is invalid, it is not RESOLVED. The bundle "com.ibm.team.datawarehouse.service.scm" with the id 98 is invalid, it is not RESOLVED. The bundle "com.ibm.team.datawarehouse.service.workitems" with the id 99 is invalid, it is not RESOLVED. The bundle "com.ibm.team.foundation.service" with the id 101 is invalid, it is not RESOLVED. The bundle "com.ibm.team.fulltext.common" with the id 106 is invalid, it is not RESOLVED. The bundle "com.ibm.team.process.service" with the id 110 is invalid, it is not RESOLVED. The bundle "com.ibm.team.repository.common.serialize" with the id 112 is invalid, it is not RESOLVED. The bundle "com.ibm.team.repotools.rcp" with the id 115 is invalid, it is not RESOLVED. The bundle "com.ibm.team.interop.service.managers.kernel" with the id 116 is invalid, it is not RESOLVED. The bundle "com.ibm.team.gateway.service" with the id 125 is invalid, it is not RESOLVED. The bundle "com.ibm.team.scm.common" with the id 126 is invalid, it is not RESOLVED. The bundle "com.ibm.team.filesystem.common" with the id 132 is invalid, it is not RESOLVED. The bundle "com.ibm.team.datawarehouse.service.coverage" with the id 134 is invalid, it is not RESOLVED. The bundle "com.ibm.team.interop.service.managers.workitem" with the id 137 is invalid, it is not RESOLVED. The bundle "com.ibm.team.analysis.service" with the id 138 is invalid, it is not RESOLVED. To ignore invalid bundles, re-run repotools with the following property defined: -Dcom.ibm.team.repotools.rcp.allowInvalidBundles=true Migration failed # ./repotools.sh -import fromFile=/tmp/beta1export.tar teamserver.properties=./teamserver.properties |
5 answers
Scott,
It looks like the TeamServer.zip is not complete. Some of the bundles are not resolved. We had some problems with jazz.net wrt downloads. Can you please download the TeamServer.zip again and try it. If it doesn't fix the problem, we can use the osgi console to find the root cause of the problem. ------ Balaji "Scott Jacobs" <srjacobs@us.ibm.com> wrote in message news:fq3uke$3kb$1@localhost.localdomain... I went through the steps to migrate my server from Beta 2 (actually Beta2a) |
|
OK -
I can certainly go through that download and unzip again. Just one question though - these errors indicate to you that there are missing files under the jazz directory on the server? Is the M5 zip a complete replacement for the files from the beta2a zip? Thanks. |
|
yes, the M5 zip replaces beta2 zip. We ran a migration on jazz.net last
week; we did not have any problems with the M5 zip. Thanks Balaji "Scott Jacobs" <srjacobs@us.ibm.com> wrote in message news:fq45j5$8hp$1@localhost.localdomain... OK - |
|
OK - well - I tried the download, unzip process again - but when I ran
the import I received the same errors. Since I have a complete backup of my beta2 /usr/jazz directory contents I am going to try blowing all of that away and unzipping the M5 zip and starting from scratch. I didn't have that much created already anyhow - so it is not a big deal to lose it. Doing this should also confirm that at least I have a good M5 zip file. If there is something else that you want to have me specifically look at that might help diagnose what the problem could be - let me know. It could very well be something I have not done correctly - but I thought I followed the migration stuff pretty closely. |
|
OK -
I blew everything away again under the /usr/jazz folder and unzipped my M5 zip file - and basically redid the server install and then the client install on my Windows box for M5 as well - and do not have any obvious problems - server started up just fine, client was able to talk to the server, I was able to create a new project area, set up teams, users, etc. So - something must have been wrong with my installation prior to the migration is the only thing I can think of. Strange thing was - I had been using that beta2 level server and client as recently as the day before I tried the upgrade to M5 - so I am not sure what could have caused what I was seeing on the import. |
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.