Solution Manager 7.2 SP03 upgrade Experience

[Former Member]

Hello All,

Greetings to all from my blog ...

Recently I had completed Solman 7.2 SP03 upgrade with both MOVE DB & KEEP DB scenarios. So, thought of bringing it up to SCN audience so as to add a cap in upcoming project challenges. Through out this blog, I will try to give you a complete understanding of the scenario is which upgrades were done in first phase and then in second phase I will depict all key points & important prerequisites which must need to be taken care of well in advance.

Scenario 1:

Source Solution Manager version: SOLMAN 7.1 SP 14

Target Solution Manager Version : SOLMAN 7.2 SP 03

DB : ASE DB 16.0 (Linux)

Application : Windows 2008 R2 SP01

Process followed for this upgrade : As above scenario has ASE DB , so it doesn't support MCOD functionality , hence have gone with MOVE DB option for splitting upgraded dual stack ASE DB into two instances each for ABAP & JAVA stacks.

Scenario 2:

Source Solution Manager version: SOLMAN 7.1 SP 14

Target Solution Manager Version : SOLMAN 7.2 SP 03

DB : DB2  (HP Unix)

Application : Windows 2008 R2 SP01

Process followed for this upgrade : DB2 database supports MCOD functionality , hence we have used KEEP DB option for DUAL STACK handling after completion of SP03 upgrade. Please note that if you have planned for HANA migration then you can go with MCOD scenario or else Multi-Tenant system can also be adhered , however for multi tenant you need to split dual stack with MOVE DB option first & then can go with Multi Tenant . (* Experts advice over here is most welcome).

Key Points To Be Taken Care Of :

1. Use latest SUM Guide : https://support.sap.com/sltoolset   >  System Maintenance > Software Update Manager (SUM) 1.0 SP17  > Guides

2. Use latest Dual Stack Split Guide : https://support.sap.com/sltoolset    > System Provisioning >  Split Option > Guide for Systems Based on SAP NW 7.0 / 7.0 EHPs > (Select OS type)

3. Read 2227300 note two to three times ( as I am a slow runner :sad: , hence I prefer to go two to three times to understand properly) . Also please go through 2328482 note which gives more information on SP 03 stack generation recommendations .

4. Perform kernel upgrade to latest level before upgrade.

5. ST-TAO, ST-OST, or ST-SPA, should not be installed in your SAP Solution Manager 7.1 till SP02 , however from SP03, ST-TST is compatible. Similarly the add-on ST-QCA would be compatible for SOLMAN 7.2 SP03 by end of November - 2016 .

6. Always select SAP_UI to 750 as it's having dependency with ST component . If you select SAP_UI to 740 as per Maintenance Planner recommendation then you can upgrade solution manager only till SP02 , but not to SP03.

7. Open SCS port <39XX>  from DB host to JAVA CI host [It's required if you change JAVA CI host or JAVA DB host].

8. Apply all relevant prerequisite notes as per recommendations mentioned in SUM guide & 2227300 note.

9. I would suggest to make a excel tracker with all prerequisite steps mentioned in SUM guide and 2227300 note and follow . One of the screen shot of such tracker used in our case :

Hope this information would help you all in your forthcoming upgrades !! Please let me know your views & concerns to make this blog more helpful.

Thanks & Regards,

Nilutpal.