Solution Manager 7.2 – Upgrade – V – SolMan Support Pack Stack 01 Correction
Hello Friends,
Hopefully you have read my Second document Solution Manager 7.2 – Upgrade – II – Actual Upgrade Process Now you have your solution Manager 7.2 ready to make some corrections in it regarding Support Pack Stack 01
Thia document will provide you detailed information regarding supportpack stack 01 Please go though SAP Note: 2229953 – Solution Manager 7.2 SP Stack 01: recommended corrections for more detailed information
Make sure you have gone through : SAP Note 2194918 – Release Restriction Note SAP Solution Manager 7.2
If you have followd my two previous documents you can start upgrading JAVA Patches as below
SAP Note: 2229953 | All OS independent: | |
J2EE ENGINE SERVERCORE 7.40 | Upgrade to | Patch 20 (or higher) for J2EE ENGINE SERVERCORE 7.40 SP 11 |
J2EE ENGINE LM-CORE 7.40 | Upgrade to | Patch 5 (or higher) for J2EE ENGINE LM-CORE 7.40 SP 11 |
J2EE ENGINE CORE TOOLS | Upgrade to | Patch 1 (or higher) for J2EE ENGINE CORE TOOLS SP 11 |
J2EE ENGINE APPLICATIONS | Upgrade to | Patch 4 (or higher) for J2EE ENGINE APPLICATIONS SP 11 |
J2EE ENGINE FRAMEWORK 7.40 | Upgrade to | Patch 6 (or higher) for J2EE ENGINE FRAMEWORK 7.40 SP 11 |
J2EE ENGINE FACADE 7.40 | Upgrade to | Patch 1 (or higher) for J2EE ENGINE FACADE 7.40 SP 11 |
LMNWABASICCOMP 7.40 | Upgrade to | Patch 1 (or higher) for LMNWABASICCOMP 7.40 SP 11 |
ENGINEAPI 7.40 | Upgrade to | Patch 6 (or higher) for ENGINEAPI 7.40 SP 11 |
LM NWA BASIC APPS 7.40 | Upgrade to | Patch 4 (or higher) for LM NWA BASIC APPS 7.40 SP 11 |
UME ADMINISTRATION 7.40 | Upgrade to | Patch 6 (or higher) for UME ADMINISTRATION 7.40 SP 11 |
LM CONFIGURATION WIZARD 7.40 | Upgrade to | Patch 1 (or higher) for LM CONFIGURATION WIZARD 7.40 SP 11 |
In case you do operate Introscope 9.5 (and not yet 9.7) WILY INTRO AGT 9.5 MIN J5VIASM | Upgrade to |
Patch 1 (or higher) for WILY INTRO AGT 9.5 MIN J5VIASM SP 06 |
Update JAVA Patches using SUM
Now our system is ready to run solution manager setup wizard.
Thank you for reading
Yogesh
Solution Manager 7.2 – Upgrade – I – Technical Checks and Preparations
Solution Manager 7.2 – Upgrade – II – Actual Upgrade Process
Solution Manager 7.2 – Upgrade – III – Dual Stack Split
Solution Manager 7.2 – Upgrade – IV – Correction After Dual Stack Split
Solution Manager 7.2 – Upgrade – V – SolMan Support Pack Stack 01 Correction
Hi Yogesh,
Your link to your 1st doucment "Solution Manager 7.2 – Upgrade – I – Technical Checks and Preparations" isn't working properly.
Its showing " Page cannot found ".
Best Regards,
Brijesh Shah
Its working now. Please check
-Yogesh
Hello Yogesh Patel,
First, thank you very much for the Blogs you posted here. There are much more information as all the "Guides" I have too read before.
For my point of view, I understood that there are two ways that I can choice to Upgrade a Solution Manager 7.1, in my case SP8, as Dual-Stack System with Oracle Databese on Windows to Solution Manager 7.2 as ABAP+JAVA stacks with Oracle DB.
There is possible to be a minimum SPs 12 for upgrade process? As I accounted, You started with SPs 13. If so, then I have to update first Solution Manager from SPs8 to Sps12.
For the Upgrade Process:
First, I can Upgrade to Solution Manager 7.2 SP01 with SUM*.SAP (here I'm not sure with SP) as Dual-Stack-System and then I can Split the System to the latest SPs as ABAP stack and Java stack with SWPM*.SAP.
Second, I use the Split Option of Software Provisioning Manager 1.0 as described in Note 1797362 (Run<Installation Media>/sapinst) and so on....
Coud you please, approve that the steps are correct. With way would you adviced me to take?
Many Thanks and best Regards,
GP
Hello Gabriela Pieper,
When you run maintenance optimizer and select an upgrade of your system it will calculate all for you.
-Yogesh
Hello Yogesh,
thank you for your quick reply.
Oh yes, I've already do the step as you advise me.
Unfortunately, SUM is hung during the Extraction phase on the ABAP Stack, in the PREP_INIT/SETSYNC_PREP_STARTED with the error "No synchronization mechanism available". I read Notes like 2312141 and 2297309 but didn't realy understand the reason of the problem.
I restart the HostAgent and today in the morning, as I started SUM, I got some more Information and an "Database connection failed" error. There is also a Note 1622837 that I schould check.
So, I'll came back with information when I check the Note and the log-Files.
Thanks again, I'll be back!
GP