Upgrading CLM 4.0.5 to CLM 5.0
We are planning to upgrade CLM 4.0.5 to CLM 5.0 in November. We are using Windows Server 2008 and SQL Server 2008. Since CLM 5.0 does not support SQL Server 2008, we are planning to upgrade upgrade SQL server to 2012. And I believe CLM 4.0.5 does not support SQL server 2012. How can I proceed in this situiation? Our department has asked to go in phase base approach. Just thinking to upgrade CLM 4.0.5 to CLM 4.0.7 and then upgrade SQL server from 2008 to 2012. Then upgrade CLM 4.0.7 to CLM 5.0 |
Accepted answer
That is your best option, open a PMR and engage with the support contact and request a webex or con call to review your upgrade strategy. We always send in with our PMR our written procedure we plan to execute for the upgrade or other significant change. We then have a call and we have a test system we use to execute first. For the scheduled upgrade ensure you have a PMR open indicating you are upgrading so that the escalation for assistance is ready on IBM side should things not work as planned. Within our plan we submit we also ask for backout plan should things not go well. We have had success with doing the first server migration with 4.0.0.1 with IBM assistance and have had a few other upgrade scenarios where they have been most helpful in keeping us from experiencing unnecessary downtime. We have not had to execute any PMR's opened during 4.x upgrades since 4.0.0.1 we are on 4.0.6 using Websphere and SQL 2008. But its a great safety net. Hope this helps
Pradeep Basnet selected this answer as the correct answer
|
4 other answers
Well I would try it in a sandbox first if you can - seems a lot of extra work to go to 4.0.7 to get to 5.0. I don't use windows or SQL server but I would expect the transition to 2012 to be fairly painless - I would definitely make full backups of the 4.0.5 system before starting just in case something goes wrong. I would upgrade the db server then make sure you can connect to it. You could actually connect with 4.0.5 - it will give you a warning on the db server mismatch but I believe it will still work. Then shutdown 4.0.5 and proceed to upgrade to 5.0. I have done it this way with DB2 so I would expect SQL Server to behave similarly.
|
I think that's a reasonable phased approach that will allow you to upgrade your backend database and then upgrade your application.
Don't forget if you use SCM, you'll have to upgrade the database schema when you move from 4.0.7 to 5.0
Good luck!
|
We are on CLM 4.0.3 and "Database version: Microsoft SQL Server 11.00.3373" which is SQLserver 2012 SP1.
Hence you should not have any issue upgrading to SQLserver 2012 while on CLM 4.0.5 :) unless compatibility could go in reverse from 4.0.3 to 4.0.5 :(
Comments I did find on the DB compatibility chart: Microsoft SQL Server Enterprise Edition 2012 & future fixpack 64 bit New and only supported for version for CLM v4.0.7 which is puzzling, as IBM was heavily involved with our 4.0.3 upgrade Now I am worrying about our plan to upgrade to 4.0.5 (from 4.0.3): what if SQLserver 2012 working fine now but will not work with 4.0.5
If I were in your shoes, I will put in a PMR for the upgrade early as recommended by IBM, and as recently practiced by a lot of orgnizations, according to IBM.
|
|
Thank you every one for your suggestion.
|
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.