jts_upgrade.sh failing [step 1]
Hello,
I'm upgrading JTS and CCM from 4.0.4 to 5.0.2 and the upgrade script is failing with this message:
On the log file (/app/rtc/IBM/JazzTeamServer502/server/repotools-jts_addTables.log), there's this:
Even thought I set the fulltext.indexLocation property over step 0 to:
/app/rtc/IBM/WebSphere/AppServer/profiles/AppSrv01/conf/jts/indices/workitemindex
It continues to use /app/rtc/IBM/JazzTeamServer502/server/conf/jts/indices
Not sure what's the best way to proceed in this one...
Thanks for any help,
Raf.
|
4 answers
It seems some problem in the index. Could you please try to run 'repotools-jts -reindex' in both RTC 4.0.4 and RTC 5.0.2?
If the same error reported, you can try if the solution in https://jazz.net/forum/questions/91541/rtc-database-reindexing-fails-and-the-database-is-unusable works for you. |
It looks very strange and you may need to contact Support to get it investigated further.
The error message says that duplicate values were found in column "APP_NAME" of table DISCOVERY.SERVICE_CONTRIBUTION_RESOURCE (SERVICE_CNTRBTN_RSRC) when the script tried to create a unique index on it. This column should have values such as "/ccm", "/qm" and/or "/rm", and etc. I can't imagine what duplicate values they will be. |
Hello,
I have tried to reindex through both versions. 404 updates the index all right and 502 doesn't let me execute as there are repository differences. Even removing the index directory and recreating it as Spencer Murata reply does not solve the issue.
So yes, it seems very odd indeed:
Gives:
I have opened PMR 80855,235,631 and will let this post updated with any resolution.
Regards,
Raf.
|
Nothing so far from IBM. The PMR is escalated to the DEV team. As this was our development environment we have wiped the DB and started the upgrade from scratch - all went well. I suppose this got into DEV environment by some wrong installation procedure or something alike.
Thanks,
Raf.
|
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.