It's all about the answers!

Ask a question

RM upgrade error while upgrading from 6.0.6.1 iFix 028 to 7.0.2 SR1 iFix 18


Arun Kumar (1139) | asked Dec 24 '22, 8:21 a.m.

 Dears,


Setting committed timestamp to 2017-05-18 14:29:57.865 in change set [UUID _8NO9mju0EeeuxYoh7ZLdSw]
Setting committed timestamp to 2019-07-25 17:01:51.23 in change set [UUID _XnVh7K7cEem4w4hEXdWvlA]
Finished setting missing committed timestamps in change sets. Updated 882,028 change sets.
Migrating change set delivery information...
Finished migration of delivery records
Starting validation of delivery records
Initialization complete.
Collecting database statistics for table CHANGE_SET_PRIMAL...
Finished collecting database statistics for table CHANGE_SET_PRIMAL in 64.46 ms.
Collecting database statistics for table STREAM_PRIMAL...
Finished collecting database statistics for table STREAM_PRIMAL in 6.090 ms.
Collecting database statistics for table CHANGE_SET...
Finished collecting database statistics for table CHANGE_SET in 1.857 s.
Finished validation of delivery records - validation success
-----------------------------------------------
Starting recordtype migration to 0.6 model...
Interim performance metric interval is set to 20 minutes
Producer recordtype executing query


Commands gets hung after "Producer recordtype executing query " for RM 


Anybody facing same issue for RM upgrade with SQl server database ?



Thanks


Comments
Ian Barnard commented Dec 28 '22, 4:02 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

"hung" is different from "error", and you don't show there is an error - upgrade can take a long time and appear silent - suggest you leave it running and create a support case.

One answer



permanent link
Davyd Norris (2.9k217) | answered Dec 25 '22, 10:01 p.m.
Have you looked at the detailed System Requirements for 7.0.2? Check that your version of SQL Server is compatible and that you have the latest drivers as mentioned in the requirements.

I know that SQL Server is not a preferred back end due to its lack of ability to scale so check that your DB server isn't running out of resources in some way

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.