It's all about the answers!

Ask a question

Migration error: CRJAZ1150I context id must match owner


Christina Kettenacker (561) | asked Jun 24 '09, 4:05 a.m.
Hello,

I tried to import to Derby, but I get the following error during migration:

2009-06-23 18:56:03,433 CRJAZ1150I ** ERROR ** context id must match owner
com.ibm.team.repository.common.TeamRepositoryException: context id must match owner
at com.ibm.team.reports.service.internal.ReportVerifier.verifySharable(ReportVerifier.java:139)
at com.ibm.team.reports.service.internal.ReportVerifier.verifyReport(ReportVerifier.java:105)
at com.ibm.team.reports.service.internal.ReportVerifier.verifyReports(ReportVerifier.java:113)
at com.ibm.team.reports.service.internal.ReportVerifier.verify(ReportVerifier.java:42)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:378)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:364)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
at $Proxy559.verify(Unknown Source)
at com.ibm.team.repository.service.internal.verifiers.RepositoryVerificationService.verifyComponent(RepositoryVerificationService.java:96)
at com.ibm.team.repository.service.internal.verifiers.RepositoryVerificationService.verify(RepositoryVerificationService.java:78)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:378)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:364)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
at $Proxy289.verify(Unknown Source)
at com.ibm.team.repository.migration.internal.service.AbstractMigrationService.verifyRepository(AbstractMigrationService.java:1221)
at com.ibm.team.repository.migration.internal.service.AbstractMigrationService.importRepositoryOptionalVerifyPreserve(AbstractMigrationService.java:714)
at com.ibm.team.repository.migration.internal.service.AbstractMigrationService.importRepositoryOptionalVerify(AbstractMigrationService.java:651)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:378)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:364)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
at $Proxy361.importRepositoryOptionalVerify(Unknown Source)
at com.ibm.team.repotools.rcp.internal.command.ImportCommand.importData(ImportCommand.java:153)
at com.ibm.team.repotools.rcp.internal.command.ImportCommand.execute(ImportCommand.java:114)
at com.ibm.team.repotools.rcp.AbstractCommand.execute(AbstractCommand.java:158)
at com.ibm.team.repotools.rcp.internal.RepositoryToolsApplication.run(RepositoryToolsApplication.java:671)
at com.ibm.team.repotools.rcp.internal.RepositoryToolsApplication.start(RepositoryToolsApplication.java:702)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193)
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:386)
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:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
at org.eclipse.equinox.launcher.Main.main(Main.java:1212)


Further, at the end of the migration process following message is shown:

2009-06-23 18:56:20,981 ###############################################
2009-06-23 18:56:20,981 CRJAZ0656I **ERROR** Migration completed with errors. The imported database is in an inconsistent state and should not be used without further analysis
2009-06-23 18:56:20,981 ###############################################


This happened in Version 2.0Beta RC2.

Can anyone please explain what exactly this error means for us?

Thanks a lot for your help

One answer



permanent link
Rafik Jaouani (5.0k16) | answered Jun 24 '09, 4:03 p.m.
JAZZ DEVELOPER
You can ignore the error. Someone probably had deployed a private report template that failed to migrate completely so it ended up with the wrong context id (used for read permission reasons). Report templates designed with 1.0.1.1 need to be revisited and retested any way due to RTC 2.0 adopting a newer version BIRT. The report templates that shipped with RTC 1.0.1.1 should be migrated automatically by the tool.

Can you please try with the GA release version of RTC.

Again the error is minor and should only affect the private report template.

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.