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; upgrade to SAP systems based on SAP NetWeaver 7.1 including enhancement package 1
Other terms

Update, migration, upgrade, release upgrade, maintenance level, SAPup, SAPJup, upgrade program
Reason and Prerequisites

*
Solution

This is the central Note for upgrades to SAP systems based on SAP NetWeaver 7.1 including enhancement package 1.
CAUTION:
This Note is updated regularly!
You should read it again immediately before starting the upgrade.
_______________________________________________________________________
_______________________________________________________________________

CONTENTS

Part A: Upgrade Notes and Keywords

Part B: New SAPup Version

Part C: Correction Package for the Upgrade Program

Part D: General Problems / Information on all Upgrades

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
Sections II/ to VII/ are divided 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 dual-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.
_______________________________________________________________________
_______________________________________________________________________

Part A: Upgrades Notes and Keywords

For more information about the upgrade of your specific application and thecurrent keyword, see one of the followingSAP Notes:
Upgrade to SAP NetWeaver PI 7.1 including EHP 1 ……. Note 1252365

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
_______________________________________________________________________
_______________________________________________________________________

Part B: New SAPup Version
Before you start the upgrade program, check if there is a new version of SAPup. The current version is:
SAPup version 7.10/5
Note: The current version of SAPJup is contained in the correction package of the upgrade program.

1. To determine the currently used SAPup version, proceed as follows:UNIX: Go to /abap/bin and call ‘./SAPup -V’.
Under UNIX, you have to enter the ABAP upgrade directory to allow SAPup to use the correct OS libraries.Windows: Go to \abap\bin and call ‘.\SAPup.exe -V’.IBM i: ADDLIBLE
SAPup UPGDIR() PARMLIST(’ -V’)2. SAPup displays the following message:
This is SAPup version 7.10/ , patch level .

To download SAPup from SAP Service Marketplace, go to http://service.sap.com/swdc. Choose Download -> Support Packages and Patches -> Entry by Application Group -> Additional Components -> Upgrade Tools -> SAPUP UNICODE -> SAPUP 7.10 UNICODE -> -> SAPUP710.SAR.
CAUTION: Always use the Unicode SAPup version regardless of your SAP system being Unicode or non-Unicode!
Place the archive in the download directory. In roadmap step “Extraction”, the upgrade program asks you to specify the path to the new SAPup.
To get a list of all patches contained in a specific SAPup, call
SAPup -V

_______________________________________________________________________
_______________________________________________________________________

Part C: Correction Package for the Upgrade Program

The correction package is provided as SAR archive that you must integrate into the upgrade. Each SAR archive is valid for only one product (= exactly one delivered DVD set).
The upgrade control program displays the correct name of the correction package you have to apply.
The SAR archives are available at the following SAP Service Marketplace area:
http://service.sap.com/swdc -> Download -> Support Packages and Patches -> Entry by Application Group -> Additional Components -> Upgrade Tools -> CORRECTIONS FOR UPGRADE -> CORRECTIONS FOR UPGRADE 7.11 -> #OS independent
The following table explains which correction package you need:
Product……………SAR Archive Name ………Correction Package Name
______________________________________________________________________
SAP NW PI 7.1 EHP1….NW711_.SAR….FIX_NW711.UPG

Comments:
The archive names on SAP Service Marketplace have a slightly different naming convention:
The prefix “FIX_” is not displayed. In addition, they have an extension representing the patch level and – an 8 digit number. The extension varies with each patch level of the archive.For all products there exists exactly one correction package.Some products are known under different names and can be used differently. For example, NW-AS 7.00 which is part of NetWeaver 7.0, is the successor product to WEB-AS as well as to the BW product family. However, there is onlyonefix archive regardless of the use of the system.Similarly, other products are based on Netweaver, but there are separate correction packages for each of them. In essence, onlyonearchive must be used.

Integration into the upgrade
1. Download the correction package for your product.2. Store the SAR archive in the main upgrade directory.3. Unpack the SAR archive using “SAPCAR -xvf .SAR” You will get two files, one of them is .UPG, the other one contains a history of changes.4. During the KEY_CHK phase, the upgrade program searches the upgrade directory for the correct correction package. If it is successful, the package is automatically integrated into the upgrade. If the upgrade program does not find a valid package, it displays a user dialog requesting that you place the correction package in the upgrade directory. You can use “Retry” to repeat the search.

The UPG archive contains data files and cofiles for the transport requests and the corresponding buffer files (ABAP upgrade only), and control files of the upgrade.
The corrections to the ABAP tools of the source release are imported in the TOOLIMP4_FIX, TOOLIMP6_FIX phases (provided these exist), while the corrections for the shadow system are imported in the SHD_FIX_IMP phase. The transport requestsareimportedautomatically.
You must not import requests into the system manually!
The corrections to the Java upgrade program and control files are included automatically and the program is restarted to make the changes become active.

_______________________________________________________________________
_______________________________________________________________________

Part D: General Problems / Information on all Upgrades

I/ Upgrade Keyword

———————————————————————-
For the upgrade keyword, see the relevant product-specific Note listed
in part A of this Note.
———————————————————————-

II/ Important General Information

a) GENERAL
———-

———————–< D024077 JAN/29/08 >——————–
AIX only: Check the C++ runtime level
Check the C++ runtime level with the following commands:
AIX 6.x :
# lslpp -L xlC.aix61.rte
The output must be at least 9.0.0.1.
# lslpp -L xlC.rte
The output must be at least 9.0.0.1.
AIX 5.x :
# l slpp -L xlC.aix50.rte
The output must be at least 8.0.0.5.
# lslpp -L xlC.rte
The output must be at least 8.0.0.5.
——————————————————————

b) ABAP ONLY
————

———————–< D028310 JUL/19/02 >——————–
Problems with the Shadow Instance.
The following Notes contain information about problems with the shadow instance:
525677: Problems when starting the shadow instance430318: Remote shadow instance on a different operating system

————————< D042621 FEB/02/05 >————————-
LSMW now part of SAP_BASIS
As of SAP Web AS 6.20, LSMW is part of SAP_BASIS. If you are using LSMW
and your source release is based on SAP Web AS 6.10 or lower, do not
implement LSMW after the upgrade.
For more information, seeNote 673066.

c) Java ONLY
————

————————< I045711 JAN/15/09 >————————-
Support Package Stack Level Equivalence
Depending on the Support Package Stack level of your source release, you must include Support Packages of the correct level (equivalent or higher) for all components into the upgrade. You must include these Support Packages in the BIND_SUPPORT_PACKAGES phase of the Configuration roadmap step (”Support Packages” screen). If you do not include the correct SP Stack level, you may experience severe failures during the upgrade or malfunction of certain applications after the upgrade.
For information about the equivalent SP Stack levels, seeSAP Note 1288656.

III/ Corrections to the Guides

a) GENERAL
——-
————————< D031901 DEC/02/05 >————————–
Copying Commands From the Upgrade Guide
When you copy a command from the upgrade guide in order to paste it in to a tool or command line, it can occur that some hyphens are not recognized correctly by the tools and therefore get lost. This can lead to severe errors when you execute the command. Therefore, if you copy and paste commands from the upgrade guide, check carefully that all hyphens are preserved before you execute the command.
———————————————————————

IV/ ….. Errors on the CD-ROM

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

V/ Preparing the Upgrade
a) GENERAL

———-
———————< D050445 09/MAR/09 >—————————-
HA on Windows only: Apply Note 828432 Before Starting the Upgrade
For source release systems on SAP NetWeaver 04 only: If you run a high availability system on Windows and your kernel patch level is lower than 169, you need to patch your kernel to at least PL 169 and apply SAP Note828432prior to starting the upgrade.
———————–< D039661 15/JUL/08 >—————————
Prevent Calculation of Incorrect Stack XML
When you are upgrading a dual-stack system that has been configured by using upper and lower letter case inconsistently in the Solution Managersystem landscape, it is possible that an incorrect stack XML file is calculated as a result. Currently, the Maintenance Optimizer considers SID or HOST that only differ in letter case as different systems.
To prevent the calculation of an incorrect stack XML file in the Maintenance Optimizer, you need to implement the solution described in SAP Note1229555.
———————–< 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 data.
For more information, see Note1154961.
———————————————————————
Windows only: Upgrade Directory
If you want to use a different upgrade directory than the default one, make sure that you specify a directory that is on the same drive as the SAPLOC share. Otherwise, the upgrade program cannot start.

b) ABAP ONLY

————
———————–< D038006 02/NOV/05 >————————–
Source Release on Kernel 6.40 with SuSE SLES 9 IA64 / RedHat 4.0 IA64
If you are using the above combination on your source release and have set environment variable LD_ASSUME_KERNEL 2.4.21 according to SAP Note 797084, proceed as follows:
Before you start the upgrade, you need to delete the environment variable LD_ASSUME_KERNEL 2.4.21 and deactivate component icman by setting the following instance profile entry: rdisp/start_icman=false
Restart the system.
After the upgrade, delete the instance profile entry again.
————————–< D003327 15/SEP/05 >————————
Back up customer-specific entries in table EDIFCT
If you have maintained customer-specific entries in table EDIFCT, they may get lost during the upgrade. If you do not want to lose these entries, export them before the upgrade and reimport them after the upgrade.
For more information, see Note865142.
————————–< D034302 07/JUN/05 >———————–
Windows only: Stop SAP MMC during the upgrade downtime
Make sure that SAP MMC is not running during the upgrade downtime. Otherwise, the files in the kernel directory will be in use and the phase KX_SWITCH is not executed successfully.
————————–< D034302 07/JUN/05 >———————–
Windows only: Comment out parameter DIR_SERVER_ORAHOME
Check the default profile of your system. If you find the parameter DIR_SERVER_ORAHOME, comment it out. Otherwise the phase KX_SWITCH is not executed successfully.
———————————————————————–

c) Java ONLY

———–
Checking the Consistency Between Primary Application Server Instance ID and Box Number
When the primary application server instance is created during the SAP system installation, the tool which creates the instance configuration in the config manager generates a string, called box number. It is used as base for calculating the primary application server instance ID.
For the upgrade of an SAP system it is essential that you have not changed the above mentioned system parameters or if you have changed them, that they are still consistent. This is a prerequisite for the correct installation of the shadow instance and for the proper migration.
To check the consistency of the primary application server instance ID and box number of the system you want to upgrade, use the attached tool ‘instanceidcheck.jar’.
To run the instanceidcheck.jar, you need at least Java Runtime
Environment version 5.
Proceed as follows:
1. Download the attached tool to your computer.2. Execute the following command with the required parameters from the directory where you have downloaded the tool:
java -cp instanceidcheck.jar com.sap.sdt.check. InstanceIdChecker : This is the primary application server instance ID. Depending on your source release, determine it as follows:
SAP NetWeaver 2004: Open the file /usr/sap// /j2ee/cluster/bootstrap/bootstrap.properties and search for the value of the instance.prefix property.
SAP NetWeaver 7.0: Open the central instance profile /usr/sap//SYS/profile/__ and search for the value of the j2ee/instance_id entry.: This is the central instance number. For example, if the instance name is JC12, then the instance number is 12.: This is a string used by the installation to calculate the instance ID. To get the box number, open the instance.properties file
/usr/sap///j2ee/cluster/instance.properties and search for the value of the instance.box.number property.3. Check the results:The following message is displayed, when the box number was changed without changing the primary application server instance ID.
WARNING!!! The source system ID that you provided is different than the one calculated
To solve this, restore the original box number.If no message is displayed, the system is consistent with regards to the primary application server instance ID and box number.

———————< I024158 DEC/13/07 >—————————-
Upgrading Third-Party and Non-SAP Components
If third-party or non-SAP components are installed in your system and you want to upgrade them, put only one successor component in the EPS inbox of the system your are upgrading. If you provide more than one archive for the component that you want to upgrade, the phase DEPLOY_ONLINE_SHD will fail.

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

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:
/abap/log/UpgradeDialog.log (for ABAP upgrade phases)
/java/log/UpgradeDialog.log (for Java upgrade phases)
———————————————————————–

Problems During the Preparation Phases

a) GENERAL
———-

———————< D038245 08/JAN/08 >—————————-
Disabling the Archive Mode of your Database in Step Preprocessing
When you chose to disable archiving at the beginning of the downtime, in some cases disabling is not possible because the parallel running JAVA upgrade still accesses the database. However, as the system is already in the downtime, we recommend to force disabling archive mode.

b) ABAP ONLY

————

c) Java ONLY
————-

———————< D038245 05/AUG/05 >—————————-
Failure of Module “General Checks”
The module “General Checks” fails if either your database or operating system or JDK version is not within the allowed range. If you have fixed the error, you have to repeat the module with option “INIT”. Otherwise, the versions are not determined again.

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

Problems During the Upgrade Phases
a) GENERAL

———-
————————–< D026178 JAN/24/08 >———————–
Phase: UPG_POSTP/REQSTARTSRV
Note: 823941
Description: UNIX only
The upgrade does not automatically configure the autostart of the SAP Service (sapstartsrv) as a daemon when starting the operating system on UNIX platforms.
———————————————————————-

b) ABAP ONLY

————
———————-—————————-
Phase: STOPSAP_IUPG
Description: You are upgrading in an MSCS setup and SAPup fails with error message “system stop failed” although the system has stopped. You can ignore the message.
———————-—————————-
Phase: STARTSAP_NLUPG
Description: You are upgrading in an MSCS setup and SAPup fails with error “Connect to SAP Gateway failed”. Check if the parameters are correct and if yes, repeat the phase until the system is started.
————————< D025988 JUN/16/00 >————————–
Phase: PARDIST_SHD
Description: For Windows NT only
The upgrade is terminated during the PARDIST_SHD phase. The PCONUPG.ELG log file contains an incomplete error text which was extracted from the DS. log file. Repeat the phase.
————————–< D034302 07/OCT/05 >———————–
Phase: REQJOBRES
Description: Windows only – SAPup issues the error message value returned by call sappfpar.exe Start_Program_01 pf=…is incorrect.
Please analyze the content of …\put\log\NTPARVAL.LOG
You can ignore this error. Repeat the phase to continue.
————————–< D034302 16/AUG/05 >———————–
Phase: KX_SWITCH (Windows only)
Description: Upgrade stops with an error message which asks you to check file NTPARVAL.LOG. In this file, messages like the following are displayed: fopen(…): Invalid argument
Check that the last text line in all profiles ends with a line feedback. To check the profile, open a profile file with a text editor, go down with the cursor, and ensure that the last line is empty. If it is not, add an empty line at the end of the file and save it.
————————–< D034302 07/JUN/05 >———————–
Phase: KX_SWITCH (Windows only)
Description: Because SAP MMC is running, SAPup stopped with the following error message: SAPup> SEVERE ERROR: Could not delete file ‘…\sapstartsrv.exe’ …
Reason: ‘ErrorMessage: Access is denied.
In this case, shutdown SAPMMC and SAP service of your system and repeat the phase.
————————–< D034302 07/JUN/05 >———————–
Phase: KX_SWITCH (Windows only)
Description: If parameter DIR_SERVER_ORAHOME has not been commented out, SAP up will stop with the following error message: Error: value returned by call sappfpar.exe Start_Program_01 pf=…is
incorrect. Please analyze the content of …NTPARVAL.LOG.
The NTPARVAL.LOG states: immediate …\sapcpe.exe pf=…Illegal Parameter in Default Profile:
“DIR_CLIENT_ORAHOME”.
sapparam: Illegal Parameter in Default Profile: “DIR_SERVER_ORAHOME”.
(no Default-Value)
sapparam: Illegal Parameter in Default Profile:
“DIR_SERVER_ORAHOME”. (no Default-Value)
In this case, comment the parameter out and repeat the phase.
———————-< D003551 07/NOV/05 >—————————-
Phase JOB_RSTLANUPG
Note: 626272
Description: Termination; the log file for job RSTLAN_UPGRADE contains the following error message: “..Job terminated after system exception ERROR_MESSAGE.”
———————-< D028310 NOV/28/07 >————————–
Phase: CHANGEPROF_UPG
Description: If there is an profile line entry with more than 1024 characters, the phase aborts and the following error message is displayed:
Error modifying profile: Missing delimiter ‘=’ in line ‘**’
Shorten the line and repeat the phase.
———————————————————————-
Phase: CHK_POSTUP
Note: 1017840
Description: LONGPOST.LOG displays the following message (in German):
A2PDSEEF_BADI 103 BAdI-Implementierung “FSBP_TREASURY_TO_BW muss noch migriert werden.
————————–< D028597 NOV/27/07>————————
Phase: CHK_POSTUP
Description: If you have applied SPAM/SAINT version 0025 on you source release and have not included this version or a higher version into the upgrade, LONGPOST.LOG displays the following message:
3PETG447 Table and runtime object “PATHISTORY” exist without DDIC reference (”Transp. table”)
3PETG447 Table and runtime object “PATHISTQ” exist without DDIC reference (”Transp. table”)
When you apply SPAM/SAINT update 710/0025 to your target system, you can ignore the error messages, as the sources of tables PATHISTORY and PATHISTQ are reimported.
————————–< D025323 MAY/23/02 >—————–
Phase: CHK_POSTUP
Note: 197886
Description: If you have imported Notes 178631, 116095 or 69455 into your system before the upgrade, error messages for objects without DDIC reference appear in the log LONGPOST.LOG. Proceed as described in the Note.
————————–< D038245 APR/23/07 >———————–
Phase: CHK_POSTUP
Description: If you have restarted the SL Controller, the link to the Upgrade Evaluation does no longer work.
———————————————————————-

c) Java ONLY

————
———————–< I028226 OCT/19/05 >—————————
SAPJup Hangs in an AS Java Restart Phase
The upgrade program may hang in one of the phases in which the AS Java is restarted. This problem only occurs if your source release system has a Support Package level lower than NW ?4 SP15 and you use an IBM JDK.
For the solution, see SAP Note878909.

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
———-

———————–< D000587 25/FEB/08---------------------------
Error when Converting Print Parameters
After the upgrade, in some clients the printing parameters have either
gone or been replaced by other parameters. For more information, see
Note1142364.
The problem is solved with SAP Basis Support Package 06.
----------------------------------------------------------------------

b) ABAP ONLY
------------

-----------------------< D042454 27/APR/07---------------------------
Update Configuration of Transport Domain
You can only update the configuration of the transport domain if you
have defined a last name for user TMSADM.
For more information, see Note1047762.
--------------------———————-
———————–< D003551 02/MAY/05---------------------------
Check Primary Index of Table MEMGMT_DEPLOYMNT
After the upgrade, check that the primary index of table MEMGMT_DEPLOYMNT exists. If not, create the index manually.
If you still get the message that MEMGMT_DEPLOYMNT00 is an unknown object in the dictionary, drop it on the database level.
------------------------< D020815 AUG/23/02 >————————
SPAU: Names of interface methods are truncated
Some methods (ABAP objects) that were modified and overwritten by the upgrade can be displayedin transaction SPAU with their names shortened to 30 characters.
As a result, the system may also incorrectly sort methods in SPAU under “Deleted objects”.
Caution: Deleted objects are not displayed in the standard selection in SPAU. It is easily possible to overlook these!
For more information about the correction, seeNote 547773.

c) Java ONLY

————-
————————< I035760 JUL/17/06 >————————-
Out of swap space error in std_server0.out
When running the SAP system, std_server0.out may display the following error message:
===
java.lang.OutOfMemoryError: requested XXXXX bytes for Handle in
(some location pointing to .ccp file). Out of swap space?
===
In this case, implement the /3GB option as described in Note313347.

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

VIII/ Chronological Summary

Date…..Topic..Short description
———————————————————————–
MAR/09/09….V..HA on Windows only: Apply Note 828432 Before the Upgrade
JAN/15/09…II..Support Package Stack Level Equivalence
JUL/15/08….V..Prevent Calculation of Incorrect Stack XML
MAR/31/08….I..Upgrade Keyword
MAR/31/08….V..Checks Before Starting the Upgrade
MAR/25/08….V..Checking Consistency Between Instance ID and Box Number
FEB/25/08..VII..Error when Converting Print Parameters
JAN/29/08…II..AIX only: Check the C++ runtime level
JAN/24/08…VI..Phase: UPG_POSTP/REQSTARTSRV – sapstartsrv
JAN/08/08…VI..Disabling the Archive Mode of your Database
DEC/19/07….V..Windows only: Upgrade Directory
DEC/13/07….V..Java: Upgrading Third-Party or Non-SAP Components
NOV/28/07…VI..Phase: CHANGEPROF_UPG – Missing delimiter
NOV/27/07…VI..Phase CHK_POSTUP: SPAM/SAINT version 0025
APR/27/07..VII..Update Configuration of Transport Domain
APR/27/07…VI..Phase: STARTSAP_NLUPG – System start fails
APR/27/07…VI..Phase: STOPSAP_IUPG – System stop fails
APR/23/07…VI..Phase: CHK_POSTUP – Upgrade Evaluation not displayed
JAN/24/07…VI..Phase CHK_POSTUP: BAdI FSBP_TREASURY_TO_BW
NOV/07/05…VI..Phase: JOB_RSTLANUPG
NOV/02/05….V..Kernel 6.40 with SuSE SLES 9 IA64 / RedHat 4.0 IA64
OCT/07/05…VI..Phase: REQJOBRES
AUG/22/05….V..SAP NetWeaver 2004s Product Availability Matrix
AUG/16/05…VI..Windows only: KX_SWITCH – Check file NTPARVAL.LOG.
JUL/17/06..VII..Out of swap space error in sdt_server0.out
JUN/07/05….V..Windows only: Stop SAP MMC during the upgrade downtime
JUN/07/05….V..Windows only: Comment out parameter DIR_SERVER_ORAHOME
JUN/07/05…VI..Windows only: KX_SWITCH – SAP MMC is running
JUN/07/05…VI..Windows only: KX_SWITCH – parameter DIR_SERVER_ORAHOME
MAY/02/05..VII..Check Primary Index of Table MEMGMT_DEPLOYMNT
MAR/15/06..VII..Settings for Information Broadcasting are Overwritten
MAR/15/06…VI..Deployment Errors
FEB/02/05…II..LSMW now part of SAP_BASIS
DEC/02/05…II..Copying Commands From the Upgrade Guide
OCT/19/05…VI..SAPJup Hangs in an AS Java Restart Phase
OCT/05/05….V..Free Space Requirements in the Database
AUG/05/05…VI..Failure of Module “General Checks”
AUG/23/02..VII..SPAU: Names of interface methods are truncated
JUL/19/02…II..Problems with the shadow instance
MAY/24/02…II..Corrections and repairs for the upgrade
MAY/23/02…VI..Phase CHK_POSTUP – objects without DDIC reference
———————————————————————-