SAP Basis Tech Supports

Symptom

This note describes errors during the upgrade and in the upgrade guide as well as preparatory measures for upgrading SAP Solution Manager 7.0 to SAP Solution Manager 7.0 Enhancement Package 1 using transaction SAINT and Java Support Package Manager (JSPM).

Other terms

SAINT, add-on, ST, ST-SER, ST-ICO, ST-PI, ST-A/PI, CRMUIF, SAP Solution Manager 7.0, Enhancement Package 1, Stack 18, Support Package Stack 18, Stack 19, Support Package Stack 19, JSPM, Java Support Package Manager
Reason and Prerequisites

Note that the following names
Solution Manager 7.0 Enhancement Package 1
Solution Manager 7.0 Stack 18
Solution Manager 7.0 Enhancement Package 1 Stack 18
are used as synonyms.
Solution

CAUTION:
This note is updated regularly.
Therefore, it is essential that you read it again before starting the upgrade.

What information does this note contain?

This note describes problems that can occur during a system upgrade. It also provides information about correcting these problems. This usually takes the form of references to other notes.
The main purpose of this note is to prevent data loss, system failures, and long runtimes.
This note contains the enhancements for the
Update Guide for SAP Solution Manager 7.0 Enhancement Package 1
that is available at
http://service.sap.com/instguides -> SAP Components -> SAP Solution Manager -> Release 7.0 EHP 1

Contents

1. SAINT passwords
2. Important general information
3. Corrections to the guides
4. Errors on the CD
5. .Preparations for the upgrade
6. Performing the upgrade
7. After the upgrade
8. Language support
9. Change history

1. Passwords

The following remark applies only to SAP customers in German and Austria:
The extent of the usage of the software package “SAP Enhancement Package 1 for SAP Solution Manager 7.0″ depends upon the type of maintenance contract you have signed.
If you have signed a contract for:SAP Enterprise SupportSAP Product Support for Large EnterprisesSAP Premium Support, orSAP MaxAttention
you are authorized to use all functions in the software package without any restrictions.
If you have signed only standard support contracts, you are permitted to install this software package, but you are permitted to use only restricted functions. You are not permitted to use the following Enterprise Edition functions:Business Process Change AnalyzerQuality Gate ManagementCustom Development Management Cockpit

Before the installation, you will be asked to enter a password for each component you selected. This password is:
ComponentPackage namePasswordCRMUIF 500SAPK-500AGINCRMUIFD855FD497DPI_BASIS 701SAPK-701DHINPIBASIS3DD62AEC78SAP_ABA 701SAPK-701DHINSAPABA3DC721976ASAP_BASIS 701SAPK-701DHINSAPBASIS3EC433FE19SAP_BW 701SAPK-701DHINSAPBW3ED240976ABI_CONT 704SAPK-704DHINBICONT14158187D7BI_CONT 704SAPK-704IHINBICONT1415818AD7

2. Important general information
Obtain the following notes before you begin the installation:
Overview/release strategy note:394616Problems with transaction SAINT:822380

ABAP stack requirements
You can start the SAINT update from any Solution Manager 7.0 ABAP Stack.Java stack requirements
A direct JSPM update to Solution Manager 7.0 Java Stack 18 and higher is not possible from some of the Java stacks. Therefore, proceed as follows: First, use the JSPM update to update the Java stack only to Solution Manager 7.0 Java stack 17 and then update to the relevant Solution Manager 7.0 Enhancement Package 1 Java stack.Target configuration:
Always include the highest available SAP Solution Manager 7.0 Enhancement Package 1 stack in your upgrade.SAP Adapter for QC 1.0
If you are using the SAP Adapter for QC 1.0, it is essential that you refer to Note 1285941 before you perform the update.Additional information about the upgrade
CD material number add-on upgrade:51034385Net runtime12 hoursSpace required in the transport directory:20 GB

Space required in the database
OraclePSAPDB:1000 MBSYSAUX:50 MBSYSTEM:1 MBArchiving logs:1500 MBSAP MaxDB1000 MBArchiving log:1000 MBIBM DB2 for Linux, Unix and Windows#DBD:1500 MB#DBI + SYSCATSPACE:100 MBMS SQL Server1,500 MBArchiving log:500 MB3. Corrections to the guides
Preparations section (page
Unpack SAP_SOLUTION_MANAGER_70_EHP1.zip from the note attachment, and call the report RS_SMSY_PPMS_XML_UP_DOWNLOAD with the option “Upload = X”.”Update of a JAVA Stack” section (page 10)
The JSPM Support Package Stack level is based on the numbering of NetWeaver 7.0 Support Package Stack and is not based on the numbering of Solution Manager 7.0 Support Package Stack.

4. Errors on the CD

5. .Preparations for the upgrade
Download by the maintenance optimizer (MOPZ) (SAP Solution Manager 7.0 stack 09 to 17)Perform the download as described in the Update Guide.Download by stack download (optional)Log on to SWCenter on SAP Service Marketplace:
Support Packages and Patches -> Entry by Application Group -> SAP Technology Components -> SAP Solution Manager-> SAP Solution Manager 7.0 -> Support Package Stacks.
Target stack : SAP Solution Manager 7.0 EHP1-19 (03/2009)
Source stack : -> SAP Solution Manager 7.0 EHP1 -> Support Package Stacks
Target stack : 19 (03/2009)
Source stack : 18 (11/2008)Add all packages to your download basket.
Create the XML for the Java upgrade via JSPM (Note 884537) and the XML for the ABAP upgrade via transaction SAINT.
Get approval for the required packages in your basket.
Download all packages using the download manager.Unpack or copy the packages from your local download directory into your EPS inbox.Download ABAP and JAVA-Packages via DVD (SAP Solution Manager 7.0 Stack 08 and lower)We provide the DVDs electronically only. You can find the DVDs on SAP Service Marketplace at:
http://service.sap.com/installations -> Entry by Application Group -> SAP Technology Components -> SAP Solution Manager -> SAP Solution Manager 7.0 EHP1 -> UpgradeAdd all 12 download objects to your download basket.Download all packages using the download manager.Execute the program 51034865_PART01.EXE.Your local download directory now contains three directories with the following subdirectories:
51034865_1: DATA_STACK18_JAVA, DATA_STACK18_ABAP
51034865_2: DATA_STACK15_17_JAVA, DATA_STACK15_17_ABAP, DATA_STACK13
51034865_3: DATA_STACK09, DATA_STACK10, DATA_STACK12Copy the SAR files from the JAVA directory to your EPS inbox.Unpack the SAR files from the ABAP directory to your EPS inbox.
If you have not yet installed BI_CONT 703 in your SAP Solution Manager 7.0 system, you must delete the file CSR0120031469_0033274.PAT from your EPS inbox.
If you have unpacked the data from the directory DATA_STACK09, delete the following packages from your EPS inbox:
CSR0120031469_0031762.PAT SAPK-70101INPIBASIS
CSR0120031469_0031760.PAT SAPKA70101
CSR0120031469_0031758.PAT SAPKB70101
CSR0120031469_0032747.PAT SAPKB70102Downloading the kernel (SAP Solution Manager 7.0 Stack 08 and lower)You can find the kernel packages on SAP Service Marketplace at:
http://service.sap.com/installations -> Entry by Application Group -> SAP Technology Components -> SAP Solution Manager -> SAP Solution Manager 7.0 EHP1 -> SAP Kernel 7.01Add the packages Kernel Part I and Kernel Part II relevant to your DB/OS version to your download basket.Download all packages using the download manager.Copy the SAR files from your local download directory to your EPS inbox.

6. Performing the upgrade
Using the Enhancement Package Installer (EHPI)You can perform the upgrade only using SAINT and JSPM. Using the EHPI is not intended and is not supported. Ignore the corresponding message in transaction SAINT.Kernel updateYou can perform the kernel update either manually or using the JSPM.For AS/400 (iseries), also see Note 1284805.Java stackStack XML
Unpack the SPSTAB.zip from the note attachment into your EPS inbox.ABAP stackJob “LANDSCAPE FETCH”
Deschedule the job “LANDSCAPE FETCH”.User
Log on to your SAP system in client 000 as a user with SAP_ALL authorization. Do NOT use the SAP* or DDIC users.Kernel 7.01
If you want to include ST-ICO Support Packages in the upgrade, you require at least R3trans 701 patch 18 to avoid extremely long import times.SAINT
Call transaction SAINT and choose “Start” and “Load”.
Choose the left pushbutton to get the stack configuration from the Solution Manager (MOPZ process) or choose the right pushbutton to load the stack configuration (SW-Center Stack-XML).
Alternatively, you can also build the SAINT queue manually.
Select the following components and choose “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
On the next screen, for the component ST, manually select the package
SAPKITL429
and, for the component ST-ICO, select the package
SAPK-1507IINSTPL
from the dropdown list.
After you do this, at least the following component Support Packages are automatically included in the SAINT queue:
SAPKB70103
SAPKA70103
SAPK-70103INPIBASIS
SAPKW70103
SAPK-50001INCRMUIF
SAPK-70402INBICONT
SAPKNA7014
SAPKU50013
SAPK-40014INCPRXRPM
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).
To start the installation process, choose “Continue”.
For more information, call transaction SAINT and choose “Info” on the application toolbar.
The system prompts you to enter a password. This password is provided above.
Support Packages of components SAP_BASIS, SAP_ABA, PI_BASIS, and BBPCRM CANNOT be included in the SAINT queue individually. You always require the corresponding CRT of component ST that is made available with a time delay in the SAP Solution Manager Stack.
Note that you must restart the system while executing transaction SAINT (after the phase IMPORT and before the phase METHOD EXECUTION).

7. After the upgrade
Delivery Customizing
Delivery Customizing is imported into client 000 and may have to be copied to other clients. For more information, see Note 337623.Application-specific postprocessing
Perform postprocessing in accordance with Note 1244225.Introscope Agents
Refer to Note 1273028.

8. Language support
In addition to German and English, the following languages are supported: Chinese, Korean, Hebrew, French, Japanese, Portuguese, Russian and Spanish.All language-dependent parts are contained in the installation packages or upgrade packages. If the relevant standard language is in the system during the upgrade, the language part of the add-on is automatically imported. You do not have to import a language transport separately.If you import a new standard language into your system after the upgrade to SAP Solution Manager 7.0 EhP1, you must manually ensure that the corresponding language-dependent part of the add-on is also imported. See Note 195442 for further information.

9. Change history

DateTopicShort Description15.01.2009All27.01.20096Kernel update30.01.20096MOPZ download, stack download, DVD download10.02.20096Kernel, AS/40017.02.20092,6Database space, job, restart20.05.20092,6Stack 19