SAP Basis Tech Supports

Symptom

Upgrade to SAP Systems based on SAP NetWeaver 7.0 including enhancement package 1 Support Release 1.
Other terms

Upgrade, SAP NetWeaver 7.0 EHP1, central Note
Reason and Prerequisites

*
Solution

This is the central Note for upgrades to SAP systems based on SAP NetWeaver 7.0 including enhancement package 1 Support Release 1.
———————————————————————-

CONTENTS

Part A: Upgrade Notes and Keywords
Part B: New Upgrade Program 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 Upgrade Phases
…………VII/ …. Problems After the Upgrade
…………VIII/ … Chronological Summary

________________________________________________________________
________________________________________________________________

Part A: Upgrades Notes and Keywords

For more information on the upgrade of your specific application and thecurrent keyword, see one of the followingNotes:
SAP NetWeaver 7.0 EHP1 SR1…Note 1293745
SAP CRM 7.0 SR1…………..Note 1292070
SAP ERP 6.0 EHP4 SR1………Note 1292069
SAP SCM 7.0 SR1…………..Note 1292071
SAP SRM 7.0 SR1…………..Note 1293387

Database………………………………………… Note number
______________________________________________________________________
SAP MaxDB ………………………………………….. 817463
IBM DB2 for i ……………………………………….1168235
IBM DB2 for Linux, UNIX, and Windows ………………….. 819876
IBM DB2 for z/OS ……………………………………. 815202
MS SQL Server ………………………………………. 825146
Oracle …………………………………………….. 819655
________________________________________________________________
________________________________________________________________

Part B: New Upgrade Program Version

Before you start the upgrade program, check if there is a new version of SAPup.
The current SAPup version is:
SAPup version 7.10/7

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/patches.
Choose Entry by Application Group -> Additional Components -> Upgrade Tools -> SAPUP UNICODE -> SAPUP 7.01 UNICODE -> -> SAPUP710.SAR archive.
CAUTION: Always use the Unicode SAPup version regardless of your SAP system being Unicode or non-Unicode!
Unpack the archive to a temporary location. 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

Before the upgrade, it isVITALthat you apply the correction package for the upgrade program, if available.
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/patches -> Entry by Application Group -> Additional Components -> Upgrade Tools -> Corrections for Upgrade -> CORRECTIONS FOR UPGRADE 7.01 -> #OS independent
There are two packages, one for ABAP and one for Java:
ABAP Package Name: FIX_NW701SR1.UPG
Java Package Name: FIX_J_NW04SEHP1.UPG

Comments:
Caution: All products (SAP NetWeaver 7.0 EHP1 and all products based on it) use the same correction package.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. Thisextension varies with each patch level of the archive.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 onlyonecorrection package regardless of the use of the system.

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

————————< 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.
———————–< D020904 MAR/15/07 >————————–
MSCS Configuration: Split the ABAP Central Instance
In an MSCS configuration, you must split the ABAP central instance into ABAP central services instance (ASCS) and central instance, as described in SAP Note1011190, if one of the following cases apply:
You have upgraded your SAP NetWeaver ‘04-based ABAP system to SAP NetWeaver 7.0-based ABAP systemYou have upgraded your SAP NetWeaver ‘04-based ABAP system to SAP NetWeaver 7.0-based ABAP system, and now want to install a Java Add-In. The split must done before the Java Add-In installation.
The split is required for the use of the enqueue replication server. If you run an MSCS configuration without enqueue replication server, which is the traditional MSCS configuration (where the clustered central instance runs the message server and enqueue work process), you will lose the enqueue lock table during a failover. The enqueue replication server configuration prevents this loss.
If you want to migrate an ABAP+Java system that is already upgraded to SAP NetWeaver 7.0 (or higher) to the new configuration with enqueue replication server, you must perform a homogeneous system copy.
———————————————————————

III/ Corrections to the Guides

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

IV/ ….. Errors on the CD-ROM

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

V/ Preparing the Upgrade

———————–< 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.
———————-——————-
————————< D001330 03/JUL/07 >————————
Parameter for the Central Syslog rslg/collect*
There may be conflicts with parameter values for the central syslog “rslg/collect*” of the default profile.
If the parameters are set with 39 and 40 , you must change them to 14 and 15. Make sure that the ports are not used by other applications. If so, choose some other number.
For more information, see Note1069225.
———————–< 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 16/AUG/05 >———————–
Windows only: Last profile text line must end with line feedback
Check that the last text line in all profiles ends with a line feedback.To check this, open a profile file with a text editor, go down with the cursor and ensure that the last line is empty. Otherwise there could be problems in the KX_SWITCH phase as some tools will not be able to handlethe profiles properly.
————————–< 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.
———————————————————————–

VI/ Problems During the Upgrade Phases

———————-———————
————————–< D026178 30/APR/09 >————————-
Check Note 1337378 Before Resettung your Upgrade
If you plan to reset your upgrade or if you face an ICNV error after having reset your upgrade, check Note1337378.
—————————–< D038245 22/APR/09 >———————-
AIX only: Required C++ Runtime Level
When you start the upgrade program, it checks whether you have the required C++ runtime level. You may get an error message like this:
ERROR: Your AIX 5.0 C++ runtime has version 7.0.0.x, but you need at least 8.0.0.5!
You can ignore this error and proceed with the upgrade.
————————< 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 checkfile 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)
In this case, comment the parameter out and repeat the phase.
———————–< I045364 17/APR/09 >————————–
Phase: XPRAS_UPG
Note: 1180041
Description: If error messages appear in the LONGPOST.LOG file while report RS_TCO_ACTIVATION_XPRA is activating SAP BW objects, you need to apply SAP Note1180041.
————————–< D021063 OCT/12/06 >———————-
Phase: XPRAS_UPG
Description: The phase issues the following short dump: “GEN_BAD_MACRO_SOURCE” for program /1BCDWB/
You can ignore this message.
———————-< D038245 FEB/28/06 >————————–
Phase: MODPROFP_UPG
Description: When you are performing a dual-stack upgrade (ABAP and Java system at the same time), in phase MODPROFP_UPG the ABAP system is started together with the Java system part for the first time. The phase may fail if the SAP J2EE Engine does not start fast enough.
Check manually if the SAP J2EE Engine is running and if so, choose “repeat” to repeat the upgrade phase.
———————————————————————-
Phase: CHK_POSTUP
Note: 996953
Description: Log file LONGPOST.LOG asks you to migrate a CMOD project although no project exists.
————————–< 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.
———————————————————————-

VII/ Problems After the Upgrade

———————–< I045364 17/APR/09 >————————–
Apply Note 1227759 After the Upgrade
Due to a program error, some SAP BW objects are not activated during the upgrade. Therefore, you must apply Note1227759after the upgrade has finished.
——————–———————-
———————–< 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 displayed in 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, see Note547773.
———————————————————————-

Date…..Topic..Short description
———————————————————————–
APR/30/09…VI..Check Note 1337378 Before Resetting your Upgrade
APR/22/09…VI..AIX only: Required C++ Runtime Level
APR/17/09..VII..Apply Note 1227759 After the Upgrade
APR/17/09…VI..Phase: XPRAS_UPG
MAR/09/09….V..Windows only: Apply SAP note 828432 Before the Upgrade
JUL/03/07….V..Parameter for the Central Syslog rslg/collect*
MAR/15/07…II..MSCS Configuration
FEB/28/07…VI..Applying Support Packages on the Source Release
FEB/28/07…VI..Phase CHK_POSTUP – CMOD/SMOD migration
OCT/12/06…VI..Phase XPRAS_UPG: short dump GEN_BAD_MACRO_SOURCE
FEB/28/06…VI..Phase MODPROFP_UPG fails – check J2EE Engine
NOV/02/05….V..Kernel 6.40 with SuSE SLES 9 IA64 / RedHat 4.0 IA64
OCT/07/05…VI..Phase: REQJOBRES
AUG/16/05…VI..Windows only: KX_SWITCH – Check file NTPARVAL.LOG.
AUG/16/05….V..Windows only: Last profile text line – line feedback
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
FEB/02/05…II..LSMW now part of SAP_BASIS
SEP/17/03….I..SAPup keyword
AUG/23/02..VII..SPAU: Names of interface methods are truncated

MAY/23/02…VI..Phase CHK_POSTUP – objects without DDIC reference