CRJAZ1791E The migration completed with errors. The imported database is unstable e and should not be used without further analysis.
CRJAZ1791E The migration completed with errors. The imported database is unstabl
e and should not be used without further analysis.
Items with a protected read access policy must use a valid context that appears
in the context tables. The provided context, "_9Kd07yb-EeKunLKkS8t0pQ", does no
t appear in the context tables.
WorkItem Migration Status . See the log file "E:\IBM\JazzTeamServer_4.0.
5\server\repotools-ccm_addTables.log" for details.
Synchronization . See the log file "E:\IBM\JazzTeamServer_4.0.5\
server\repotools-ccm_addTables.log" for details.
Items with a protected read access policy must use a val
id context that appears in the context tables. The provided context, "_9Kd07yb-
EeKunLKkS8t0pQ", does not appear in the context tables. Items with a protected r
ead access policy must use a valid context that appears in the context tables.
The provided context, "_9Kd07yb-EeKunLKkS8t0pQ", does not appear in the context
tables.. See the log file "E:\IBM\JazzTeamServer_4.0.5\server\repotools-ccm_addT
ables.log" for details.
Running post addTables for "com.ibm.team.workitem.linkClosure"...
One answer
I believe you have hit the issue discussed in other posts:
If a server contains a project area that is set to private (an access control setting other than "Everyone") and the list of members with access is empty (such as the project area hierarchy, or an access list), along with the administrator list, then that project area can sometimes be seen as an invalid context. This causes errors during upgrading.
See this conclusion from IBM:
http://www-01.ibm.com/support/docview.wss?uid=swg1PM96399
and workaround as well:
https://jazz.net/library/article/1311#00001