This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
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.
Table of contents Table of contents ................................................................................................................................................2 Issues during Upgrade........................................................................................................................................9
Related Contents ..............................................................................................................................................11 Disclaimer and Liability Notice..........................................................................................................................12
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
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.
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.
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:
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.
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.