SAP Basis Tech Supports

Symptom
Errors in the upgrade procedure or in the upgrade guide; preparations for the upgrade; additional information to the upgrade guide
Other terms
Update, migration, upgrade, release upgrade, maintenance level, SAPup, SAPJup, upgrade program, SAP NetWeaver PI 7.1 including EHP 1
Reason and Prerequisites
*
Solution

CAUTION:
This note is updated regularly!
Therefore, you should read it again immediately before starting the upgrade.

What information can I expect from this note?
This note contains additional information to the upgrade documentation.
This note describes problems that may occur during the system upgrade and provides information on how to solve them. This usually takes the form of references to other notes.
The main purpose of this note is to prevent data loss, upgrade shutdowns, and long runtimes.
It deals with database-independent problems only.
Each section of this SAP Note is divided up into three sub-sections:
a) GENERAL
This sub-section handles issues relevant for the upgrade in general, independently from the fact whether it is a an ABAP upgrade, a Java upgrade or a double-stack upgrade.
b) ABAP ONLY
This sub-section handles issues that only apply to upgrades of ABAP
systems.
c) Java ONLY
This sub-section handles issues that only apply to upgrades of Java
systems.

Which additional notes do I require in preparation for the upgrade?
This depends on the functions that you are using.
You will need at least the note that is specific to your database:
Database …………………………………………. Note number
______________________________________________________________________
SAP MaxDB (ABAP) ………………………………………950871
SAP MaxDB (Java) ………………………………………950873
IBM DB2 for i ………………………………………..1258882
IBM DB2 for Linux, UNIX and Windows …………………….1004920
IBM DB2 for z/OS ………………………………………943141
MS SQL Server …………………………………………976523
Oracle ……………………………………………….960790
You also need the following important SAP Notes:
Short text ……………………………………….. Note number
______________________________________________________________________
Central Note: Upgrade to Systems on SAP NetWeaver 7.1 EHP1…..1156185
OCS: Known problems with Supp. Packages in SAP NW 7.10 AS ABAP..954792

CONTENTS
I/ …… Upgrade Keyword
II/ ….. Important General Information
III/ …. Corrections to the Guide
IV/ ….. Errors on the CD-ROM
V/ …… Preparing the Upgrade
VI/…… Problems During the Preparation and Upgrade Phases
VII/ …. Problems After the Upgrade
VIII/ … Chronological Summary

I/ Upgrade Keyword
———————————————————————-
The upgrade keyword is: 20356441
This must be entered in the Extraction roadmap step (for Java only: Configuration roadmap step).
———————————————————————-

II/ Important General Information
a) GENERAL
———-

———————–< D023890 JUN/12/09 >————————-
Only CMS part of DI is supported for SAP NW PI 7.1 including EHP1
The usage type Development Infrastructure (DI) is delivered with SAP NetWeaver Process Integration 7.1 including EHP1 in case your are doing an upgrade for PI. If you have installed usage types PI and DI both on the same SAP NetWeaver 7.0 system, you can now upgrade your system to SAP NetWeaver PI 7.1 including EHP1.
Be aware that this is a limited delivery. Only the Change Management Service (CMS) in connection with PI is allowed to be used. The Design Time Repository (DTR) and the Component Build Service (CBS) are not supported for DI shipped with SAP NetWeaver PI 7.1 including EHP1.
CMS is not to be used for any other use case than transports of PI objects. We strongly recommend that after the upgrade, you switch to the enhanced Change Transport System (CTS+). Using CTS+ allows you to organize the transports of PI objects both in the ABAP and Java parts of your system landscape.
———————–< D021285 FEB/07/08 >————————
BPE Integration Processes – Upgrade Information
For more information on the upgrade of integration processes, see SAP Note1138713.
———————-< D043396 MAR/11/09 >—————————-
Diagnostics Agent – Installation Information
This only applies if the Diagnostics Agent has not been installed in your source release system:
If you need to implement End-to-End Root Cause Analysis in SAP Solution Manager, you must install the Diagnostics Agent after the upgrade using the tool SAPinst. For more information about the Diagnostics Agent installation, see SAP Note1234387.

b) ABAP ONLY
————

c) Java ONLY
————

———————————————————————

III/ Corrections to the Guides

a) GENERAL
———————————————————————
————————< D023890 19/MAR/09 >————————
Addition to “Upgrade of Distributed and High Availability Systems”
Microsoft Cluster Server: If you perform a dual stack upgrade in the cluster environment, change the parameter Maximum Start Time of the SAP cluster resource to at least 600, as follows:
1. Start the Cluster Administrator.2. Select SAP group on the left pane.3. Right-click SAP resource in the right pane (normally called SAP-R/3 SID) and choose “Properties”.4. Go to the Parameters tab and change Maximum Start Time (or Max Start Time) to at least 600.
———————————————————————
IV/ ….. Errors on the CD-ROM

———————————————————————-

V/ Preparing the Upgrade
a) GENERAL
———-
———————< I036707 12/MAR/09 >—————————-
Increased Space Requirements in the Database
Before starting the upgrade, you need to ensure that you have enough free space in the database. Besides the estimation given in the upgrade guide, you may need additional free space during the upgrade. In some cases, the tables XI_AF_MSG and XI_AF_MSG_AUDIT may consume a large part of the database. Therefore, we recommend that you calculate the space requirements including 2 times the size of these two tables.
———————–< D038245 16/JAN/09 >—————————
Downloading Kernel DVDs for the Upgrade
The software of the kernel is split up in two files with the following naming convention:
<product><version>
<product><version>Upgrade
When you download the kernel DVDs for the upgrade, you must download both files from SAP Service Marketplace and unpack them in the same directory as described in SAP Note1258173.
———————–< D021285 31/MAR/08 >————————–
Checks Before Starting the Upgrade
Before you start the upgrade, make sure to perform a special set of checks. This avoids problems due to inconsistencies in your database.
For more information, see Note1154961.

b) ABAP ONLY
————

c) Java ONLY
————
———————-< D023890 16/MAR/09 >—————————-
Source Release based on 6.40 Java only: Shut down IGS
Before starting the upgrade, shut down the IGS as described in SAP Note737099. This prevents errors during the upgrade.
———————-< I035760 11/MAR/09 >—————————-
Source Release NetWeaver 7.0 only: Check the SCS Instance Profile
Before starting the upgrade, make sure that your SCS instance profile
contains the following two parameters: ‘rdisp/msserv_internal’ and
‘rdisp/msserv = 0′. The value of ‘rdisp/msserv_internal’ points to the
correct Message server port (default value is “39<SCS instance
number>”). Normally, this parameter is entered by the installation and
upgrade tools for NetWeaver 7.0, so it is expected to be present.
In case your SCS instance profile does not contain these two parameters
originally, you need to add them and then prior to starting the upgrade
ensure that the system is starting successfully.
———————-< I035760 11/FEB/09 >—————————-
Cleaning Up the Profile Directory
Before starting the upgrade program, you need to clean up the profile directory. Remove any old, unused profiles and move any backup copies toanother directory. The profile directory must only contain active profile files. By default, it is located in the central file share:
For UNIX: /sapmnt/<SAPSID>
For Windows: <Drive>:\usr\sap\<SAPSID>\SYS
For IBM i: /sapmnt/<SID>
———————–< I024143 01/DEC/08 >—————————
Install the Latest CPU Driver on Windows Multiprocessor Machines
Before starting the upgrade on a Windows platform, check whether SAP Note1036194applies to you (especially for multiprocessor machines) and if so, download and install the latest processor driver for your CPU as described in the Note.

———————————————————————-

VI/ Problems During the Preparation and Upgrade Phases
This section addresses known problems that cannot be avoided using preventive measures. These problems will only occur under very specific circumstances.
In the following, the problems are ordered by the phases in which they appear. To identify the phase you are currently in during the upgrade, check the following log files:
<upgrade directory>/abap/log/UpgradeDialog.log (for ABAP upgrade phases)
<upgrade directory>/java/log/UpgradeDialog.log (for Java upgrade phases)
———————————————————————–
Problems During the Preparation Phases

a) GENERAL
———-

b) ABAP ONLY
————

c) Java ONLY
————-
———————–< D030182 11/FEB/09 >—————————
Disabling Assertion Errors when Starting the Upgrade GUI
You might get assertion errors if you try to start the upgrade GUI by executing the script DSUGui (for Windows: DSUGui.bat). In this case, proceed as described in SAP Note1301466and then restart the upgrade program.

———————————————————————–

VI/ Problems During the Upgrade Phases

a) GENERAL
———-
——————–< I024101 MAR/24/09 >—————————–
Phase: STARTSAP_PUPG
Description: You are upgrading a dual-stack distributed system (with SCS instance running on a remote host) and phase STARTSAP_PUPG fails. You can find the following error message in the ‘dev_icm’ trace file:
*** ERROR => can’t attach to message server (rc=-100)
Solution: Ensure that the remote SCS instance is started and repeat the phase.
On Windows platforms, you must install an SCS Windows service prior to starting the SCS instance. Proceed as described in the upgrade guide for Windows – step 3 in section “Phase DOWNTIME_END_”.

———————————————————————-
b) ABAP ONLY
——————–< D034302 MAR/19/09 >—————————–
Phase: MAIN_SHADOW/START_SHDI_FIRST
Description: The shadow system does not start. There is a message like: *** ERROR => CrtOsSemAdm: Semaphore Admin. Table not created In the DEVTRACE.LOG in <DIR_PUT>/log directory.
Solution:
1. Open the instance profile of the shadow system under <DIR_PUT>/<SAPSID>/SYS/profile/<SID>_DVEBMGS.2. Set the parameter enque/table_size = 40000.3. Repeat the phase.

—————————FEB/25/09————————————
Phase: XPRAS_UPG
Note: 1180041
Description: Error message in XPRAS phase while activating BW objects
If you have an error in report RS_TCO_ACTIVATION_XPRA
while activating BW objects during the XPRAS phase,
proceed as described in SAP Note 1180041.
———————————————————————-
c) Java ONLY
————

VII/ Problems After the Upgrade
This section addresses known problems that cannot be avoided using preventive measures. These problems will only occur under specific circumstances.
a) GENERAL
———-
———————-< D042500 FEB/24/09 >—————————-
NWDI-Controlled System Landscapes: CMS Restrictions
If you have upgraded a system that is part of a system landscape controlled by SAP NetWeaver Development Infrastructure (NWDI), be aware that as of SAP NetWeaver PI 7.1 including enhancement package 1, you are no longer allowed to configure a runtime system on the same host on which the Change Management Service (CMS) is running. For more information about the CMS restrictions, see SAP Note754143.

b) ABAP ONLY
————

c) Java ONLY
————
———————-< D021285 MAR/25/09 >—————————-
Non-Central Advanced Adapter Engine Must be Restarted
After the upgrade, you have to restart the non-central Advanced Adapter Engine so that it is re-registered in the SLD. This is a prerequisite for the proper message processing.
———————-< I024101 MAR/16/09 >—————————-
Deleting Directory “global.oldjars”
As a result of the global directory switch process, the Java upgrade program has backed up all *.jar files from your global directory. These backup jar files are available in the following directory:
For UNIX: /sapmnt/<SAPSID>/global.oldjars
For Windows: <Drive>:\usr\sap\<SAPSID>\SYS\global.oldjars
For IBM i: /usr/sap/<SID>/SYS/global.oldjars
After the upgrade, you may delete this directory together with its content but only after you have checked SAP Note1310442.
———————-< I036707 MAR/12/09 >—————————-
Source Release Tables with Prefix “OLD_” Can be Dropped
After the upgrade, some source release tables are not deleted from the database for debugging purposes. All these tables have the prefix “OLD_” and in some cases, these tables consume a large part of the database. If you want to cleanup your database, you can safely drop these tables.
For more information, see SAP Note1297856.
———————-< D021285 NOV/25/08 >—————————-
Large XSLT Stylesheets Cannot be Compiled to Java Methods
After the upgrade, document transformations using large XSLT stylesheets such as PI message mappings, may fail with the Java exception:
“com.sun.org.apache.bcel.internal.generic.ClassGenException:
Branch target offset too large for short”
when used with SAP JVM 5.1, 6.1 or other derivations of Sun JDK 5 or 6 (for example, HP JDK 1.5).
For more information and the solution, see SAP Note1273115.
———————————————————————-

VIII/ Chronological Summary

Date…..Topic..Short description
———————————————————————–
JUN/12/09…II..Only CMS part of DI is supported for SAP NW PI 7.1 EHP1
MAR/25/09..VII..Non-Central Advanced Adapter Engine Must be Restarted
MAR/24/09…VI..Phase: STARTSAP_PUPG
MAR/19/03…VI..Phase: MAIN_SHADOW/START_SHDI_FIRST
MAR/19/03..III..Microsoft Cluster Server: Increase Maximum Start Time
MAR/16/09….V..Source Release based on 6.40 Java only: Shut down IGS
MAR/16/09..VII..Deleting Directory “global.oldjars”
MAR/12/09..VII..Source Release Tables with Prefix “OLD_” Can be Dropped
MAR/12/09….V..Increased Space Requirements in the Database
MAR/11/09…II..Diagnostics Agent – Installation Information
MAR/11/09….V..Source Rel. NetWeaver 7.0 only: Check the SCS Instance
FEB/24/09…VI..Error message in XPRAS phase while activating BW objects
FEB/24/09..VII..NWDI-Controlled System Landscapes: CMS Restrictions
FEB/11/09…VI..Disabling Assertion Errors when Starting the Upgrade GUI
FEB/11/09….V..Cleaning Up the Profile Directory
JAN/16/09….V..Downloading Kernel DVDs for the Upgrade
DEC/01/08…VI..Install New CPU Driver on Windows Multiprocessor Machine
NOV/25/08..VII..Large XSLT Stylesheets Cannot be Compiled to Java Method
MAR/31/08….I..Upgrade Keyword
FEB/07/08…II..BPE Integration Processes – Upgrade Information
———————————————————————