It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,882
×7,478
×2,352
×267

question asked: Nov 20 '12, 8:49 a.m.
question was seen: 4,297 times
last updated: Nov 20 '12, 4:35 p.m.

Related questions

error while upgrading CCM from 3011 to 4001

0
Indradri Basu (1.8k●1●5●14) | asked Nov 20 '12, 8:49 a.m.
retagged Nov 20 '12, 1:04 p.m. by Bo Chulindra (1.3k●2●7●18)

While doing an upgrade of CCM application (by running the ccm_upgrade.bat ) which has custom operation advisors, from 3011 to 4001, I received the below error, although the JTS upgrade went fine.

==========================================

2012-11-20 13:24:26,171 CRJAZ1363I Loading the configuration from "bundleresource://364.fwk388372262/teamserver.properties".
2012-11-20 13:24:26,234 Validating JTS configuration files...
2012-11-20 13:24:26,249 Checking the old application version...
2012-11-20 13:25:56,796 The version string " -Dcom.ibm.team.repotools.rcp.allowInvalidBundles=true" is not properly formatted.
java.lang.IllegalStateException: The version string " -Dcom.ibm.team.repotools.rcp.allowInvalidBundles=true" is not properly formatted.
 at com.ibm.team.repotools.commands.upgrade.util.AbstractVersionChecker.getVersionStringFromOutput(AbstractVersionChecker.java:192)
 at com.ibm.team.repotools.commands.upgrade.util.AbstractVersionChecker.getVersionString(AbstractVersionChecker.java:125)
 at com.ibm.team.repotools.commands.upgrade.util.ApplicationVersionChecker.getOldApplicationVersion(ApplicationVersionChecker.java:66)
 at com.ibm.team.repotools.commands.upgrade.AbstractUpdateConfigurationFilesCommand.getOld30xApplicationVersionStringFromRepotools(AbstractUpdateConfigurationFilesCommand.java:3005)
 at com.ibm.team.repotools.commands.upgrade.AbstractModelledApplicationUpdateConfigurationFiles.initializeOldApplicationVersion(AbstractModelledApplicationUpdateConfigurationFiles.java:505)
 at com.ibm.team.repotools.commands.upgrade.AbstractUpdateConfigurationFilesCommand.validateOldApplicationVersion(AbstractUpdateConfigurationFilesCommand.java:821)
 at com.ibm.team.repotools.commands.upgrade.AbstractModelledApplicationUpdateConfigurationFiles.validatePreviousVersion(AbstractModelledApplicationUpdateConfigurationFiles.java:480)
 at com.ibm.team.repotools.commands.upgrade.AbstractUpdateConfigurationFilesCommand.validateJTSAndApplicationConfigurationFiles(AbstractUpdateConfigurationFilesCommand.java:1085)
 at com.ibm.team.repotools.commands.upgrade.AbstractModelledApplicationUpdateConfigurationFiles.validateJTSAndApplicationConfigurationFiles(AbstractModelledApplicationUpdateConfigurationFiles.java:86)
 at com.ibm.team.repotools.commands.upgrade.AbstractModelledApplicationUpdateConfigurationFiles.execute(AbstractModelledApplicationUpdateConfigurationFiles.java:36)
 at com.ibm.team.repotools.command.AbstractCommand.execute(AbstractCommand.java:66)
 at com.ibm.team.repotools.rcp.internal.RepositoryToolsApplication.run(RepositoryToolsApplication.java:768)
 at com.ibm.team.repotools.rcp.internal.RepositoryToolsApplication.start(RepositoryToolsApplication.java:843)
 at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
 at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
 at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
 at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
 at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:600)
 at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:620)
 at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)
 at org.eclipse.equinox.launcher.Main.run(Main.java:1408)
 at org.eclipse.equinox.launcher.Main.main(Main.java:1384)

==========================================

Any ideas ? 

Accepted answer

0
permanent link
Bo Chulindra (1.3k●2●7●18) | answered Nov 20 '12, 10:46 a.m.
JAZZ DEVELOPER
edited Nov 20 '12, 1:05 p.m.
Upgrade is running repotools -version from your 3011 install to determine the version. However, it looks like your 3011 repotools has invalid bundles so the command is not working. I don't know why it would have invalid bundles.

To get upgrade to work despite the invalid bundles, pass in the parameter oldApplicationVersion with the value 3.0.1.1 when running the upgrade script.

For example,
upgrade/ccm/ccm_upgrade.sh oldApplicationHome <someLocation> oldApplicationVersion 3.0.1.1
or
upgrade/ccm/ccm_upgrade.bat oldApplicationHome=<someLocation> oldApplicationVersion=3.0.1.1

Indradri Basu selected this answer as the correct answer
Comments
Indradri Basu commented Nov 20 '12, 4:35 p.m.

Hi Bo,

Thanks for the information. Yes, you are right, I was trying with operation advisors which has missing bundles. Before looking at your comments, I removed the ini file from the provision_profiles and did a .../ccm/admin/cmd/requestReset, restarted the server, logged in to ccm.admin and then the upgrade went fine.

Then I tried your suggestion and it worked fine as well. Thank you!

Your answer

Register or to post 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.