Solution Manager 7.0 Ehp1 Upgrade
Transcript of Solution Manager 7.0 Ehp1 Upgrade
Solution Manager 7.0 Ehp1 Upgrade
Applies to: SAP NetWeaver Solution Manager 7.0 Ehp1 Upgrade. For more information, visit the Application Management homepage.
Summary This Document describes the preparatory measures, complete procedure for upgrading SAP Solution Manager 7.0 to SAP Solution Manager 7.0 Enhancement Package 1 (Ehp1) using transaction SAINT and Java Support Package Manager (JSPM) and also the errors during this upgrade
Author: Ajay Kande
Company: Accenture Services Private Ltd
Created on: 12 Apr 2009
Author Bio Ajay Kande has around 4+ years of experience in software as SAP NetWeaver Technical Consultant in the areas of EP,XI and Solution Manager. Working for Accenture Services Pvt Ltd from past 3 years.
SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2008 SAP AG 1
Solution Manager 7.0 Ehp1 Upgrade
Table of contents Table of contents ................................................................................................................................................2 Issues during Upgrade........................................................................................................................................9
Issue 1:............................................................................................................................................................9 Solution: .......................................................................................................................................................................9
Issue 2:............................................................................................................................................................9 Solution: .......................................................................................................................................................................9
Issue 3:............................................................................................................................................................9 Solution: .....................................................................................................................................................................10
Related Contents ..............................................................................................................................................11 Disclaimer and Liability Notice..........................................................................................................................12
SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2008 SAP AG 2
Solution Manager 7.0 Ehp1 Upgrade
Prerequisites:
Take Backup of the existing development system,File system(FS) and Database(DB)
Get Approval from System Owner for Solution Manager Ehp1 Upgrade
Switch off Archive logs before Starting Upgrade
For Java Stack: Minimum Support Package Level should be SP17
Installation and Configuration Procedure:
Java Stack
Download the Support Package Stack for SPS17
Update Java Stack to SPS17 using JSPM (Kernel also gets updated to SPS17)
Place the complete Media along with SPSTab.xml in /usr/sap/trans/EPS/in folder
Login to JSPM with SDM user
Select the Support Package Stack from the below screen which can be seen after you login
You can see the Target SP Stack level as 17. Press Next
SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2008 SAP AG 3
Solution Manager 7.0 Ehp1 Upgrade
Now we can see all the components. Click Start if status of all components are
OK/Warning:
Once the update is started we can see the status of each software component as shown in the below screen
SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2008 SAP AG 4
Solution Manager 7.0 Ehp1 Upgrade
Once the Deployment is finished please Exit by pressing Exit button
Now download the Ehp1 media for Java stack and place in /usr/sap/trans/EPS/in.
Now start JSPM and update Java stack exactly similar to the above steps.
Now take the backup of FS and DB
ABAP Stack
Download the Support Package Stack until Ehp1, extract them and place in trans folder
First update SPAM/SAINT to latest available patch
Change the value of parameter to rdisp/max_wprun_time to 4000 before starting SAINT update. If we don’t set this parameter, a TIME_OUT error will occur during SPDD_SPAU_CHECK phase or start the SAINT update in background.
Even though as per SAP Note 1169247, ABAP Stack should be at any support package stack for SAINT update, it’s better to update to SPS17 first and then do Ehp1 installation
Saint Update:
Login to transaction SAINT, and click on start
SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2008 SAP AG 5
Solution Manager 7.0 Ehp1 Upgrade
b) Select the following components in the queue and press continue
PI_BASIS 701
SAP_ABA 701
SAP_BASIS 701
SAP_BW 701
BI_CONT 704
CRMUIF 500
ST-A/PI 01L_CRM570
ST-PI 2008_1_700
ST-SER 701_2008_2
SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2008 SAP AG 6
Solution Manager 7.0 Ehp1 Upgrade
c) In the next screen select the following components from dropdown list
SAPKITL428
SAPK-1507HINSTPL
d) After you do this, at least the following component Support Packages are automatically included in the SAINT queue. To start the installation, choose Continue.
SAPKB70102
SAPKA70102
SAPK-70102INPIBASIS
SAPKW70102
SAPK-50001INCRMUIF
SAPK-70401INBICONT
SAPKNA7012
SAPKU50012
SAPK-40013INCPRXRPM
SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2008 SAP AG 7
Solution Manager 7.0 Ehp1 Upgrade
NOTE: If all necessary conditions for importing the add-ons are met, the system will display the relevant queue. The queue consists of installation packages, upgrade packages, Support Packages and Conflict Resolution Transports (CRTs).
e) The system prompts you to enter a password. Please refer SAP Note for the passwords.
SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2008 SAP AG 8
Solution Manager 7.0 Ehp1 Upgrade
Issues during Upgrade
Issue 1:
JSPM hangs because it is unable to copy kernel files to kernel directory
Solution:
Change the ownership of the kernel and JSPM directory to <sidadm>: sapsys and give full permissions (777), then Resume JSPM again.
Issue 2:
Syntax error occurs in SAINT during IMPORT phase:
The following syntax error occurred in the program SAPLSUNI : "The type "FBINFO1" is unknown. " The current ABAP/4 program "SAPLSXST " had to be terminated because one of the statements could not be executed. This is probably due to an error in the ABAP/4 program.
Solution:
Apply SAP Note 572117
Issue 3:
Unable to proceed with SAINT queue. It pop ups the below error:
SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2008 SAP AG 9
Solution Manager 7.0 Ehp1 Upgrade
Solution:
Check the component which is not matching component vector and make sure that all the patches for this component required for Ehp1 are there in trans folder. If not download and copy them.
SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2008 SAP AG 10
Solution Manager 7.0 Ehp1 Upgrade
Related Contents For more information, visit the Application Management homepage.
SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2008 SAP AG 11
Solution Manager 7.0 Ehp1 Upgrade
SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2008 SAP AG 12
Disclaimer and Liability Notice This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade.
SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk.
SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document.