A way to check a project area access policy issue before upgrading from v4.0.3 or older
Upgrade from v4.0.3 to v4.0.6 failed with error message "CRJAZ1791E”. This issue most probably due to the article.
Workarounds: Jazz Team Server problems in CLM 4.0.3
https://jazz.net/library/article/1311
Then we had checked repotools-ccm_addTables.log and found this message.
-- Error message in repotools-ccm_addTables.log ----
Items with a protected read access policy must use a valid context that appears in the context tables. The provided context, "_xxxxxxxx", does not appear in the context tables.
---------------------------------------------------------------------------
_xxxxxxx is project ID, so we were able to find the project area However, we had to restore our Database to recover from this issue.
So, the question is: Is there a simple way to check whether we face this issue before running upgrade?
Failing upgrade and run rollback is a disaster to us and most of users.
It coast to much because we had to stop our production a whole day.
Note:
We can check <publicVisible> status with this OSLC and false means we need to take an action. However, with this, we have to check all projects one by one.
https://<server>:<port>/ccm/service/com.ibm.team.process.internal.service.web.IProcessWebUIService/projectAreaByUUIDWithLimitedMembers?processAreaItemId={UUID}&maxMembers=20
Workarounds: Jazz Team Server problems in CLM 4.0.3
https://jazz.net/library/article/1311
Then we had checked repotools-ccm_addTables.log and found this message.
-- Error message in repotools-ccm_addTables.log ----
Items with a protected read access policy must use a valid context that appears in the context tables. The provided context, "_xxxxxxxx", does not appear in the context tables.
---------------------------------------------------------------------------
_xxxxxxx is project ID, so we were able to find the project area However, we had to restore our Database to recover from this issue.
So, the question is: Is there a simple way to check whether we face this issue before running upgrade?
Failing upgrade and run rollback is a disaster to us and most of users.
It coast to much because we had to stop our production a whole day.
Note:
We can check <publicVisible> status with this OSLC and false means we need to take an action. However, with this, we have to check all projects one by one.
https://<server>:<port>/ccm/service/com.ibm.team.process.internal.service.web.IProcessWebUIService/projectAreaByUUIDWithLimitedMembers?processAreaItemId={UUID}&maxMembers=20
Accepted answer
In DB2,
for RTC,
select NAME_COL from PROCESS.PROCESS_AREA where JZ_DISCRIMINATOR=1 and CONTEXT_ID not in (select X.CONTEXT_UUID from REPOSITORY.CONTEXT_MEMBERS X UNION select Y.CONTEXT_UUID from REPOSITORY.CONTEXT_SUBCONTEXTS Y)
to determine what the correct value for JZ_DISCRIMINATOR is, run this command to determine the possible values:
db2 "select ITEM_ID, JZ_DISCRIMINATOR from PROCESS.PROCESS_AREA" > /tmp/process_areas_by_type.txt
Then, run this command to get the name of one of the process areas:
db2 select NAME_COL from PROCESS.PROCESS_AREA where ITEM_ID='<enter item id from previous SQL here'
Comments
Jared Burns
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER Mar 25 '14, 5:34 p.m.Unless you're doing something programatically to add data to your RTC database, you shouldn't see errors like this during upgrade. I recommend either reaching out to your IBM Support contact or opening a workitem on jazz.net: https://jazz.net/jazz/web/projects/Jazz%20Foundation#action=com.ibm.team.workitem.newWorkItem&type=defect&ts=13957829784840
Krzysztof Kaźmierczyk
Mar 26 '14, 4:21 a.m.Hi Jared,
Ryosuke means this defect:
https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/262994. Despite it is said that it has been fixed, the users still have this issue when migrating from 4.0.5 to 4.0.6. I believe that this is still valid question.
@mandrew I know that you was working on that. Do you know the answer?