Patching from 7.01 SP22 to SP23

[Former Member]

Hi all,

I have a few questions about the patching.

1. I found that the information of the Solution manager in the marketplace and actully installed is not synchronised. The marketplace show that my patching level is SP00 but I have patched to SP22. Does it means my Solution manager is not the one stated in the marketplace? Or should I update the marketplace manually instead of automatically synchronised? The one in marketplace is assigned by SAP and the one actually installed is downloaded from SAP Download.

2. My currect version of Solution manager is ABAP SP22 and JAVA SP00. If I need to upgrade to ABAP SP23 but keep JAVA as SP00, Am I correct that I need to download the patches from Mopz and execute the patches via SPAM/ SAINT? If do, which one should I use?

3. I found that SPAM and SAINT require maintenance certificate. I confirmed that maintenance certificate is valid in my marketplace, but it cannot be found in the Solution Manager. What happen?

4. If I need to upgrade to ABAP SP23 and JAVA SP23, Am I correct that I need to download the patches from Mopz and execute the patches via JSPM? However I found the .xml generated in Mopz cannot be recognised in JSPM. If I generate the .xml in Marketplace, JSPM can recognise. But the problem is that I cannot choose my starting point as ABAP SP22 and JAVA SP00 in marketplace, and therefore the content in .xml generated in marketplace is not correct. How can I do?

Thank you very much.

[Former Member]

Hi,

- Please check in SMSY -> Landscape -> Product Systems -> <SID> -> Tab ' System data in SAP Support Portal'. Under this tab, check the synchronize settings. Ideally should be automatic and if required do a manual sync. This should send the solution manager system data to the SAP Support portal and update the information there.

- I am not sure if it is possible to have ABAP stack on SP22 and Java stack on SP00. Could you please post a screenshot of the System component Information from the SolMan Java home page: http://<hostname>:<port>/index.html -> System Information. Ideally ABAP and Java components should be at the same level.

- Regarding the maintenance certificate, the latest valid certificate needs to be downloaded from the SMP and installed in the SolMan via tcode slicense. Have you already rtied this?

- For Java update, in the worst case you could select the single support package update option in the JSPM and proceed.

Regards,

Srikishan

[Former Member]

Hi Srikishan,

1. Synchronization is done. Thank you.

2. I follow your link and find that the JAVA SP version is SP02. It's quite strange because when I perform managed system configuration, it pop up that my sp level of JAVA is SP00 and does not meet the prerequisite. Do you know why there is a conflict and how to solve it?

3. Thanks, the maintanence certificate is downloaded and installed in SolMan.

4. Does it mean that if I only patch the ABAP, I need SPAM or SAINT. If I patch both ABAP and JAVA, I need JSPM? Should I use the Software Lifecycle Manager to download the patch if I use SPAM or JSPM to patch the SolMan?

[Former Member]

Hi,

- Perhaps the Solution Manager Java stack definition in SMSY is not updated. Check in SMSY -> Landscape -> Product Systems -> <SID> -> Solution Manager Java stack -> Software Components. Here does the actual SP version reflect? If not then the Java SP levels are usually updated from the SLD. Check in the SLD if your solution manager java SP levels are reflected properly. You may need to perform a SLd Data triggere from Visual Administrator -> SLD Data Supplier.

- ABAP patching needs SPAM/SAINT. Whereas Java patching needs JSPM. JSPM cant patch ABAP and SPAM/SAINT cannot patch Java components. The tools are entirely different.

Regards,

Srikishan

[Former Member]

Hi,

I find that SLD is working normally and contain the correct stack info for JAVA. I trigger the data transfer to SLD in VA.

However, the JAVA stack info is blank in SMSY. (But the ABAP stack info is correctly shown)

Are there any possible reasons that the SMSY JAVA stack info is blank?

Thank you.

[Former Member]

Hi,

I would suggest to run the tcode smsy_setup with option 'read from SLD'. This would schedule a landscape fetch job - should get the Java stack info from the SLD and update the SMSY section. Please check if this works.

Regards,

Srikishan