It's all about the answers!

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

×42,856

question asked: Jun 20 '11, 9:04 a.m.
question was seen: 9,599 times
last updated: Jun 20 '11, 9:04 a.m.

Related questions

3.0.1 upgrade failure

0
Robin Parker (326●3●37●39) | asked Jun 20 '11, 9:04 a.m.
repotools.sh -addTables failed with the following errors: 
Adding tables to the database "//rhel:50000/JTS:user=xxxxxxxx;password=xxxxxxxx;". 

CRJAZ1442I The component model of "com.ibm.team.repository" was updated from "21" to "24".

CRJAZ1441I A new component model for "com.ibm.team.diagnostictests" was added.

CRJAZ1441I A new component model for "com.ibm.team.repository.discovery" was added.

CRJAZ1441I A new component model for "com.ibm.team.applicationmigration" was added.

CRJAZ1093I The following service class was not activated: "com.ibm.team.repository.service.internal.license.LicenseService"

The user "ADMIN" has logged in to the database "//rhel:50000/JTS:user=xxxxxxxx;password=xxxxxxxx;".

CRJAZ1445E There was an error processing the migration handler named "JFS Migration Handler" for the package "com.ibm.team.jfs.resource".

CRJAZ1445E There was an error processing the migration handler named "Repository Migration Handler to migrate data from version M to M" for the package "com.ibm.team.repository".

CRJAZ1445E There was an error processing the migration handler named "Reports Migration Provider" for the package "com.ibm.team.reports".

CRJAZ1445E There was an error processing the migration handler named "Repository Migration Handler to migrate data from 2.0" for the package "com.ibm.team.repository".

CRJAZ1445E There was an error processing the migration handler named "Repository Migration Handler to migrate data from version 3.0.1 RC1 to 3.0.1 RC2" for the package "com.ibm.team.repository".

CRJAZ1445E There was an error processing the migration handler named "Repository Migration Handler to migrate data from 3.0" for the package "com.ibm.team.repository".

CRJAZ1972E The service "com.ibm.team.jfs.indexing.service.internal.IndexDataMigrationHandler" failed to activate because a service it depends on, "com.ibm.team.jfs.indexing.service.IIndexingService", failed to be activated.

CRJAZ1972E The service "com.ibm.team.datawarehouse.service.internal.DataWarehouseMigrationHandler" failed to activate because a service it depends on, "com.ibm.team.datawarehouse.service.IInternalDataWarehouseService", failed to be activated.

Running post addTables for "com.ibm.team.process"...

Running post addTables for "com.ibm.team.dashboard"...

Running post addTables for "com.ibm.team.links"...

Running post addTables for "com.ibm.team.repository.friends"...

The user "ADMIN" has logged out of the database "//rhel:50000/JTS:user=xxxxxxxx;password=xxxxxxxx;".

Database tables were added successfully.



the log file contains the following (have tried to include the most relvant looking bits)... 

2011-06-20 13:56:05,030 CRJAZ1093I The following service class was not activated: "com.ibm.team.repository.service.internal.license.LicenseService"

com.ibm.team.repository.common.transport.TeamServiceRegistryException: CRJAZ1092I The service class "com.ibm.team.repository.service.internal.license.LicenseService" failed during activation.

        at com.ibm.team.repository.common.transport.internal.registry.AbstractActivationManagerOwner.bindRequiredServices(AbstractActivationManagerOwner.java:246)

        at com.ibm.team.repository.common.transport.internal.registry.AbstractActivationManagerOwner.performActivation(AbstractActivationManagerOwner.java:603)

        at com.ibm.team.repository.common.transport.internal.registry.AbstractActivationManagerOwner.doActivate(AbstractActivationManagerOwner.java:665)

        at com.ibm.team.repository.common.transport.internal.registry.AbstractActivationManagerOwner.activate(AbstractActivationManagerOwner.java:168)

        at org.eclipse.soda.sat.core.internal.framework.bundle.BundleActivationManager.activate(BundleActivationManager.java:290)

        at org.eclipse.soda.sat.core.internal.framework.bundle.BundleActivationManager.performActivation(BundleActivationManager.java:1589)

        at org.eclipse.soda.sat.core.internal.framework.bundle.BundleActivationManager.access$2(BundleActivationManager.java:1574)

        at org.eclipse.soda.sat.core.internal.framework.bundle.BundleActivationManager$3.acquired(BundleActivationManager.java:573)

        at org.eclipse.soda.sat.core.internal.record.container.ImportServiceRecordContainer.serviceAcquired(ImportServiceRecordContainer.java:582)

        at org.eclipse.soda.sat.core.internal.record.container.ImportServiceRecordContainer.access$1(ImportServiceRecordContainer.java:566)

        at org.eclipse.soda.sat.core.internal.record.container.ImportServiceRecordContainer$5.serviceAcquired(ImportServiceRecordContainer.java:352)







Caused by:

java.lang.IllegalArgumentException: Two policies can only be merged if their operation rules are exactly the same, but the two policies had a different number of rules

        at com.ibm.team.repository.service.internal.license.MergedContributorLicenseType.assertRulesMatch(MergedContributorLicenseType.java:127)

        at com.ibm.team.repository.service.internal.license.MergedContributorLicenseType.assertValidMerge(MergedContributorLicenseType.java:103)

        at com.ibm.team.repository.service.internal.license.MergedContributorLicenseType.<init>(MergedContributorLicenseType.java:47)

        at com.ibm.team.repository.service.internal.license.MergedContributorLicenseType.addKeyToType(MergedContributorLicenseType.java:42)

        at com.ibm.team.repository.service.internal.license.LicenseState.processPolicy(LicenseState.java:426)

        at com.ibm.team.repository.service.internal.license.LicenseState.refreshContributorPolicies(LicenseState.java:267)

        at com.ibm.team.repository.service.internal.license.LicenseState.removeRemoteFloatingLicenses(LicenseState.java:145)

        at com.ibm.team.repository.service.internal.license.LicenseService.restartFloatingLicenseUpdater(LicenseService.java:375)

        at com.ibm.team.repository.service.internal.license.LicenseService.activate(LicenseService.java:212)

        at com.ibm.team.repository.service.AbstractService.bindRequiredServices(AbstractService.java:188)

        at com.ibm.team.repository.common.transport.internal.registry.AbstractActivationManagerOwner.bindRequiredServices(AbstractActivationManagerOwner.java:240)

        ... 111 more









2011-06-20 13:56:05,302 The user "ADMIN" has logged in to the database "//rhel:50000/JTS:user=xxxxxxxx;password=xxxxxxxx;".

2011-06-20 13:56:05,471 CRJAZ1445E There was an error processing the migration handler named "JFS Migration Handler" for the package "com.ibm.team.jfs.resource".

com.ibm.team.repository.common.transport.TeamServiceRegistryException: CRJAZ1972E The service "com.ibm.team.jfs.storage.internal.importmigration.JFSMigrationHandler" failed to activate because a service it depends on, "com.ibm.team.jfs.resource.service.IResourceService", failed to be activated.

        at com.ibm.team.repository.common.transport.internal.registry.AbstractActivationManagerOwner.buildServicesMap(AbstractActivationManagerOwner.java:319)

        at com.ibm.team.repository.common.transport.internal.registry.AbstractActivationManagerOwner.doActivate(AbstractActivationManagerOwner.java:652)

        at com.ibm.team.repository.common.transport.internal.registry.ExtensionServiceActivationManagerOwner.doActivate(ExtensionServiceActivationManagerOwner.java:89)

        at com.ibm.team.repository.common.transport.internal.registry.ExtensionServiceActivationManagerOwner.forceActivate(ExtensionServiceActivationManagerOwner.java:111)

        at com.ibm.team.repository.common.transport.registry.ExtensionServiceElementDescriptor.getImplementation(ExtensionServiceElementDescriptor.java:356)

        at com.ibm.team.repository.migration.internal.util.ItemMigrationHandlerRegistry.getMigrationHandler(ItemMigrationHandlerRegistry.java:240)

        at com.ibm.team.repository.migration.internal.util.ItemMigrationHandlerRegistry.getMigrationHandlers(ItemMigrationHandlerRegistry.java:225)

        at com.ibm.team.repository.migration.internal.service.MigrationHandlerDispatcher.initializeMigrationHandlers(MigrationHandlerDispatcher.java:78)









Caused by:

com.ibm.team.repository.common.transport.TeamServiceRegistryException: CRJAZ1972E The service "com.ibm.team.jfs.resource.service.internal.ResourceService" failed to activate because a service it depends on, "com.ibm.team.repository.common.oauth.IOAuthProviderService", failed to be activated.

        at com.ibm.team.repository.common.transport.internal.registry.AbstractActivationManagerOwner.buildServicesMap(AbstractActivationManagerOwner.java:319)

        at com.ibm.team.repository.common.transport.internal.registry.AbstractActivationManagerOwner.doActivate(AbstractActivationManagerOwner.java:652)

        at com.ibm.team.repository.common.transport.internal.registry.ServiceProviderActivationManagerOwner.getService(ServiceProviderActivationManagerOwner.java:133)

        at com.ibm.team.repository.common.transport.internal.registry.OsgiServicesManager.getService(OsgiServicesManager.java:248)

        at com.ibm.team.repository.common.transport.internal.registry.OsgiServicesManager.getService(OsgiServicesManager.java:257)

        at com.ibm.team.repository.common.transport.internal.registry.AbstractActivationManagerOwner.buildServicesMap(AbstractActivationManagerOwner.java:316)

        ... 35 more

Caused by:

com.ibm.team.repository.common.transport.TeamServiceRegistryException: CRJAZ1972E The service "com.ibm.team.repository.service.internal.oauth.OAuthServiceProvider" failed to activate because a service it depends on, "com.ibm.team.repository.common.service.IContributorService", failed to be activated.

        at com.ibm.team.repository.common.transport.internal.registry.AbstractActivationManagerOwner.buildServicesMap(AbstractActivationManagerOwner.java:319)

        at com.ibm.team.repository.common.transport.internal.registry.AbstractActivationManagerOwner.doActivate(AbstractActivationManagerOwner.java:652)

        at com.ibm.team.repository.common.transport.internal.registry.ServiceProviderActivationManagerOwner.getService(ServiceProviderActivationManagerOwner.java:133)

        at com.ibm.team.repository.common.transport.internal.registry.OsgiServicesManager.getService(OsgiServicesManager.java:248)

        at com.ibm.team.repository.common.transport.internal.registry.OsgiServicesManager.getService(OsgiServicesManager.java:257)

        at com.ibm.team.repository.common.transport.internal.registry.AbstractActivationManagerOwner.buildServicesMap(AbstractActivationManagerOwner.java:316)

        ... 40 more

Caused by:

com.ibm.team.repository.common.transport.TeamServiceRegistryException: CRJAZ1972E The service "com.ibm.team.repository.service.jts.contributor.internal.JtsContributorService" failed to activate because a service it depends on, "com.ibm.team.repository.service.internal.IInternalDbContributorService", failed to be activated.

        at com.ibm.team.repository.common.transport.internal.registry.AbstractActivationManagerOwner.buildServicesMap(AbstractActivationManagerOwner.java:319)

        at com.ibm.team.repository.common.transport.internal.registry.AbstractActivationManagerOwner.doActivate(AbstractActivationManagerOwner.java:652)

        at com.ibm.team.repository.common.transport.internal.registry.ServiceProviderActivationManagerOwner.getService(ServiceProviderActivationManagerOwner.java:133)

        at com.ibm.team.repository.common.transport.internal.registry.OsgiServicesManager.getService(OsgiServicesManager.java:248)

        at com.ibm.team.repository.common.transport.internal.registry.OsgiServicesManager.getService(OsgiServicesManager.java:257)

        at com.ibm.team.repository.common.transport.internal.registry.AbstractActivationManagerOwner.buildServicesMap(AbstractActivationManagerOwner.java:316)

        ... 45 more

Caused by:

com.ibm.team.repository.common.transport.TeamServiceRegistryException: CRJAZ1972E The service "com.ibm.team.repository.service.internal.ContributorService" failed to activate because a service it depends on, "com.ibm.team.repository.common.ILicenseAdminService", failed to be activated.

        at com.ibm.team.repository.common.transport.internal.registry.AbstractActivationManagerOwner.buildServicesMap(AbstractActivationManagerOwner.java:319)

        at com.ibm.team.repository.common.transport.internal.registry.AbstractActivationManagerOwner.doActivate(AbstractActivationManagerOwner.java:652)

        at com.ibm.team.repository.common.transport.internal.registry.ServiceProviderActivationManagerOwner.getService(ServiceProviderActivationManagerOwner.java:133)

        at com.ibm.team.repository.common.transport.internal.registry.OsgiServicesManager.getService(OsgiServicesManager.java:248)

        at com.ibm.team.repository.common.transport.internal.registry.OsgiServicesManager.getService(OsgiServicesManager.java:257)

        at com.ibm.team.repository.common.transport.internal.registry.AbstractActivationManagerOwner.buildServicesMap(AbstractActivationManagerOwner.java:316)

        ... 50 more







2011-06-20 13:56:05,477 CRJAZ1445E There was an error processing the migration handler named "Repository Migration Handler to migrate data from version M to M" for the package "com.ibm.team.repository".

com.ibm.team.repository.common.transport.TeamServiceRegistryException: CRJAZ1972E The service "com.ibm.team.repository.service.migration.RepositoryMigrationHandlerMToM" failed to activate because a service it depends on, "com.ibm.team.repository.service.jts.migration.IJTSRepositoryMigrationCLMHandler", failed to be activated.

        at com.ibm.team.repository.common.transport.internal.registry.AbstractActivationManagerOwner.buildServicesMap(AbstractActivationManagerOwner.java:319)

        at com.ibm.team.repository.common.transport.internal.registry.AbstractActivationManagerOwner.doActivate(AbstractActivationManagerOwner.java:652)

        at com.ibm.team.repository.common.transport.internal.registry.ExtensionServiceActivationManagerOwner.doActivate(ExtensionServiceActivationManagerOwner.java:89)

        at com.ibm.team.repository.common.transport.internal.registry.ExtensionServiceActivationManagerOwner.forceActivate(ExtensionServiceActivationManagerOwner.java:111)


Many Thanks,

Robin

11 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Ralph Schoon (63.3k●3●36●46) | answered Sep 07 '11, 4:22 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Situation: Customer PoC project no longer working since upgrade from RTC3.0 iFix1/DB2 V9.5 to RTC3.0.1/DB39.5 Fix Pack 3A on Windows Server 2003

DB backup available: RTC3.0 iFix1/DB2 V9.5
Alternative server available: RTC3.0 iFix1 / Derby / XP

Proposal: To restore the DB2 V9.5 on the alternative RTC3.0 iFix1 / Derby / XP server and migrate that to RTC3.0 iFix1/ DB2 V9.5/XP

Advice needed:
Q1 - is it possible to restore the backed up database for 3.0 ifix1on this other server ?
Q2- if so how to do this recovery and migration ?
Q3 - will we lose any project information ? i.e are there any additional files needed other than the DB2 archive ?


Hi,

you should post this as a new entry.

Here some information about backup/restore https://jazz.net/library/article/547 including files you want to back up also to avoid a complete reinstall setup and then hooking up the restored database. Please note, there are changes in the files to back up for 3.0.1. They are in the general location of the files mentioned however.

You probably want to read the help and search the library https://jazz.net/library/ for "upgrade" for tips to upgrade to 3.0.1.

In general you can restore on a different machine and also migrate between different databases. However you can't change the URI of the server (see http://jazzpractices.wordpress.com/2011/07/21/you-cant-change-the-public-uri-really-you-cant/). That means you will have to change the hostname of the new server to the hostname of the old server. You can test the backup on the new machine in isolation if you change its name in the etc/hostname. Please be aware, you also need to keep the port number for the app server on the new machine, because it contributes to the URI.

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.