It's all about the answers!

Ask a question

Problems during execution of jts_upgrade.sh for RTC upgrade 4.0.4 to 5.0.2


Tommy Moris (1145) | asked Jul 22 '15, 5:57 a.m.
I am currently busy with the migration from RTC 4.0.4 to 5.0.2 on a new server.
I copied the full installation folder + indices from the old server to the new server.
Then, on the new server, I installed RTC5.0.2 but didn't run setup. (As I am doing an upgrade)

I follow the interactive upgrade guide for upgrading RTC, but encounter problems during the "Run the upgrade script", specifically during step 2. (0 and 1 were finished successfully)
Each time the step fails, I am asked to check file /opt/IBM/WebSphere/JazzTeamServerV5/server/repotools-jts_upgradeWarehouse.log, correct the problem and rerun the script from that step.

My first error:
CREATE VIEW RIDW.VW_REQUIREMENT
(COMPONENT_ID, COMPONENT_NAME, CREATION_DATE, CUSTOMER_PRIORITY, DIFFICULTY, EXTERNAL_ID, NAME, PLATFORM, PRIORITY, PROJECT_ID, PROJECT_NAME, REFERENCE_ID, RELEASE_ID, RELEASE_NAME, REQUIREMENT_CLASS_ID, REQUIREMENT_CLASS_NAME, REQUIREMENT_ID, OWNER_ID, RESPONSIBLE_NAME, REQUIREMENT_STATE, REVISION_NUMBER, STABILITY, STATUS, URL,  ACTUAL_ITERATION_ID, ACTUAL_ITERATION_NAME, PLANNED_ITERATION_ID, PLANNED_ITERATION_NAME, REQUIREMENT_TYPE, REVISION_DATE, EXTERNAL_KEY1, EXTERNAL_KEY2, REC_DATETIME, ISSOFTDELETED, PRIMARY_TEXT)
AS (SELECT R.COMPONENT_ID, C.NAME AS COMPONENT_NAME, R.CREATION_DATE, R.CUSTOMER_PRIORITY, R.DIFFICULTY, R.EXTERNAL_ID, R.NAME, R.PLATFORM, R.PRIORITY, R.PROJECT_ID, PJ.NAME AS PROJECT_NAME, R.REFERENCE_ID, R.RELEASE_ID, RL.NAME AS RELEASE_NAME, R.REQUIREMENT_CLASS_ID, RC.NAME AS REQUIREMENT_CLASS_NAME, R.REQUIREMENT_ID, R.OWNER_ID,P.FULL_NAME AS RESPONSIBLE_NAME, R.REQUIREMENT_STATE, R.REVISION_NUMBER, R.STABILITY, R.STATUS, R.URL, R.ACTUAL_ITERATION_ID,AC.NAME AS ACTUAL_ITERATION_NAME,R.PLANNED_ITERATION_ID,PL.NAME AS PLANNED_ITERATION_NAME,R.REQUIREMENT_TYPE,R.REVISION_DATE,R.EXTERNAL_KEY1,R.EXTERNAL_KEY2,R.REC_DATETIME,R.ISSOFTDELETED, COALESCE(PT.PTEXT, 'No primary text')
FROM RIODS.REQUIREMENT R
JOIN RIODS.COMPONENT C ON C.COMPONENT_ID =R.COMPONENT_ID
JOIN RIODS.PROJECT PJ ON PJ.PROJECT_ID=R.PROJECT_ID
JOIN RIODS.RELEASE RL ON RL.RELEASE_ID=R.RELEASE_ID
JOIN RIODS.REQUIREMENT_CLASSIFICATION RC ON RC.REQUIREMENT_CLASS_ID=R.REQUIREMENT_CLASS_ID
JOIN RIODS."RESOURCE" P ON P.RESOURCE_ID=R.OWNER_ID
JOIN RIODS.ITERATION AC ON AC.ITERATION_ID=R.ACTUAL_ITERATION_ID
JOIN RIODS.ITERATION PL ON PL.ITERATION_ID=R.PLANNED_ITERATION_ID
LEFT JOIN RIODS.REQUIREMENT_PTEXT PT ON PT.REQUIREMENT_ID = R.REQUIREMENT_ID)

com.ibm.team.repository.common.TeamRepositoryException: CREATE VIEW RIDW.VW_REQUIREMENT (COMPONENT_ID, COMPONENT_NAME, CREATION_DATE, CUSTOMER_PRIORITY, DIFFICULTY, EXTERNAL_ID, NAME, PLATFORM, PRIORITY, PROJECT_ID, PROJECT_NAME, REFERENCE_ID, RELEASE_ID, RELEASE_NAME, REQUIREMENT_CLASS_ID, REQUIREMENT_CLASS_NAME, REQUIREMENT_ID, OWNER_ID, RESPONSIBLE_NAME, REQUIREMENT_STATE, REVISION_NUMBER, STABILITY, STATUS, URL, ACTUAL_ITERATION_ID,ACTUAL_ITERATION_NAME,PLANNED_ITERATION_ID,PLANNED_ITERATION_NAME,REQUIREMENT_TYPE,REVISION_DATE,EXTERNAL_KEY1,EXTERNAL_KEY2,REC_DATETIME,ISSOFTDELETED, PRIMARY_TEXT) AS (SELECT R.COMPONENT_ID, C.NAME AS COMPONENT_NAME, R.CREATION_DATE, R.CUSTOMER_PRIORITY, R.DIFFICULTY, R.EXTERNAL_ID, R.NAME, R.PLATFORM, R.PRIORITY, R.PROJECT_ID, PJ.NAME AS PROJECT_NAME, R.REFERENCE_ID, R.RELEASE_ID, RL.NAME AS RELEASE_NAME, R.REQUIREMENT_CLASS_ID, RC.NAME AS REQUIREMENT_CLASS_NAME, R.REQUIREMENT_ID, R.OWNER_ID,P.FULL_NAME AS RESPONSIBLE_NAME, R.REQUIREMENT_STATE, R.REVISION_NUMBER, R.STABILITY, R.STATUS, R.URL, R.ACTUAL_ITERATION_ID,AC.NAME AS ACTUAL_ITERATION_NAME,R.PLANNED_ITERATION_ID,PL.NAME AS PLANNED_ITERATION_NAME,R.REQUIREMENT_TYPE,R.REVISION_DATE,R.EXTERNAL_KEY1,R.EXTERNAL_KEY2,R.REC_DATETIME,R.ISSOFTDELETED, COALESCE(PT.PTEXT, 'No primary text') FROM RIODS.REQUIREMENT R JOIN RIODS.COMPONENT C ON C.COMPONENT_ID =R.COMPONENT_ID JOIN RIODS.PROJECT PJ ON PJ.PROJECT_ID=R.PROJECT_ID JOIN RIODS.RELEASE RL ON RL.RELEASE_ID=R.RELEASE_ID JOIN RIODS.REQUIREMENT_CLASSIFICATION RC ON RC.REQUIREMENT_CLASS_ID=R.REQUIREMENT_CLASS_ID JOIN RIODS."RESOURCE" P ON P.RESOURCE_ID=R.OWNER_ID JOIN RIODS.ITERATION AC ON AC.ITERATION_ID=R.ACTUAL_ITERATION_ID JOIN RIODS.ITERATION PL ON PL.ITERATION_ID=R.PLANNED_ITERATION_ID LEFT JOIN RIODS.REQUIREMENT_PTEXT PT ON PT.REQUIREMENT_ID = R.REQUIREMENT_ID)
...
Caused by: java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist


I logged on with my datawarehouse user and checked the select query for the view. I could execute the query (the select, not the create view) without any issue.

I then reran the jts_upgrade.sh script, but now I have another error:

2015-07-22 11:28:11,078 DROP VIEW RIDW.VW_RQRMNT_COVERAGE_LOOKUP
...
com.ibm.team.repository.common.TeamRepositoryException: DROP VIEW RIDW.VW_RQRMNT_COVERAGE_LOOKUP
...
Caused by: java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist


I checked this view and it indeed doesn't exist.
Do I need to restore any database schema's and rerun my script?
For the datawarehouse, we have a schema RTCDW, but I see now other schema's as RIDW in the queries. Do I need to restore these also?

One answer



permanent link
Francesco Chiossi (5.7k11119) | answered Jul 22 '15, 9:15 a.m.
Hello Tommy,

if the data warehouse migration fails, you need to restore the data warehouse backup before trying to run it again.
This because as you saw in your error it will try to drop objects that were already removed by the first run of the script and fail.

RTCDW is not one of the standard schema of the data warehouse, so I'm not sure what it contains.
Maybe it could be the name of the oracle user that connects to the data warehouse.

You can find more details on the data warehouse structure and its schemas here:

More Control over the Oracle Data Warehouse Setup
https://jazz.net/wiki/bin/view/Main/MoreControlOverTheOracleDataWarehouseSetup

Best Regards,

Francesco Chiossi

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.