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, maintenance level, SAPup
SAPJup, upgrade program,
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 one or several of the following notes:
Short text………………………………………… Note number
______________________________________________________________________
MaxDB: Upgrade to SAP NW 7.1 AS ABAP …………………….950871
MaxDB: Upgrade to SAP NW 7.1 AS Java……………………..950873
IBM DB2 for i5/OS: Upgrade to SAP NW PI 7.1… ……………950725
DB2 for LUW: Supplements for upgrades based on SAP Basis 710.1004920
DB2-z/OS: Additions upgrade to SAP NW AS 7.10 …………….943141
MS SQL: Upgrade to NetWeaver 7.1 ABAP/Java ……………….976523
Oracle: Upgrade to SAP NetWeaver 7.1 AS ABAP/AS Java ………960790
_____________________________________________________________________
Repairs for upgrade to SAP NW 7.10 .. ……………………949463
Known problems with Support 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: 13929363
This must be entered in the Extraction roadmap step (for Java only: Configuration roadmap step).
———————————————————————-

II/ Important General Information
a) GENERAL

———————–< I035760 MAR/18/09 >————————-
Source Release NetWeaver 7.0 only: Handling DI_CMS and DI Usage
If you have installed the enhanced Change and Transport System (CTS+) on top of your source release (7.0) system, you need to select the operation “Remove” for the software component DI_CMS during the BUILD_COMPONENT_LIST upgrade phase. This will result in an upgraded PI system without Change Management Service (CMS).
If you have installed the complete DI usage type in your source release system and not only CTS+, be aware that you cannot remove the DI usage type. In that case, you need to use the upgrade to SAP NetWeaver PI 7.1 including EHP1 as it enables you to upgrade systems with usage type DI.
———————–< D039661 FEB/11/09 >————————-
Upgrade Path from SAP NW 7.0 EHP1 to SAP NW PI 7.1 is not Supported
If your source release system is on SAP NetWeaver 7.0 including EHP1, you can perform an upgrade to SAP NetWeaver PI 7.1 including EHP1 (or higher) but not to SAP NetWeaver PI 7.1. An upgrade to SAP NetWeaver PI 7.1 would be a functional downgrade, therefore this upgrade path is not supported.
———————–< D038245 MAY/24/02 >————————-
CAUTION: Corrections and Repairs for the Upgrade
Before the upgrade, it is vital that you check whether there arerepairsto the upgrade program. For more information, seeNote 949463.
It is ESSENTIAL that you apply this Note to avoid severe problems during the upgrade.
———————–< D028310 Jan/01/09 >————————
Upgrade Strategy Resource-Minimized is not supported by PI
The Upgrade guide does not mention that upgrade strategy
“resource-minimized” is not supported by PI 7.1.
You can only choose upgrade strategy “down-time minimized.”
———————–< D021285 APR/24/08 >————————
Upgrade Source System must be a Dedicated PI System
The prerequisite for an upgrade to SAP NetWeaver PI 7.1 is that the PI source systemonly consists of the following usage types:
Integration ServerPI – Process IntegrationAS – Application Server Java (AS Java)AAS – Application Server ABAP (AS ABAP)Partner Connectivity Kit (PCK)AS – Application Server Java (AS Java)PI-PCK – Partner Connectivity Kit (PCK)Adapter Engine (Java EE)AS – Application Server Java (AS Java)
You cannot upgrade systems that consist of more than the above usage types.
———————–< D023890 APR/02/08 >————————
Information for High Availability Environments
If you upgrade an SAP system, which has been configured to run
inside a highly available (switch over) hardware environment, SAP Note
1012486conatins additional information on how to plan the
upgrade in such an environment.
———————–< 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.
———————–< D021285 FEB/07/08 >————————
BPE Integration Processes – Upgrade Information
For more information on the upgrade of integration processes, see
Note1138713
——————————————————————

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

————————< D023890 NOV/16/05 >————————-
Include Equivalent Support Package Level in the Upgrade
Depending on the Support Package level of your source release, you must include Support Packages of the correct level for all components in 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 level, you may experience severe failures during the upgrade or malfunction of certain applications after the upgrade.
For detailed information about the required Support Package levels, seeSAP Note 1167937.

III/ Corrections to the Guides
a) GENERAL

———————–< D038245 03/FEB/09 >————————–
Limited Length of the DDIC Password
During the Configuration Roadmap step, you need to enter the DDIC
password. The upgrade guide does not mention that the length of the
DDIC password is limited to 10 characters.
———————–< I035760 09/JAN/09 >————————–
Upgrade – Step by Step
The minimum amount of free disk space in the file system required for the upgrade directory, which is mentioned in the section “Upgrade – Step by Step”, is insufficient.
You need at least 15 GB temporary disk space in the file system for thejavasubdirectory of the upgrade directory, excluding the size of the directory upg/java/epsinbox.
———————–< D001330 06/AUG/08 >————————–
Making Entries for the Parameter Input Module
Note that the maximum length of the mount directory path is 42 characters (not 50 as mentioned in the guide).
————————< D022030 08/JUL/08 >————————
Upgrade – Step by Step
In some of the upgrade guides, the section that describes the minimum database level includes a text that only applies to IBM DB2 for UNIX, Linux and Windows:
If your database has been migrated from Version 7 or from Version 8 with a FixPak level lower than 7 (Version lower than 8.2), then perform the actions described in SAP Note 823019 to avoid errors during the upgrade.
If you are using a different database, the text is not relevant to you.
————————< D021285 08/JUL/08 >————————
PI: Changing the User Type
After switching the users from Service to System, you also need to assign new composite roles to some of the users in transaction SU01:
User………………Role
________________________________________________
PI(XI)AFUSER …….. SAP_XI_AF_SERV_USER_MAIN
PI(XI)DIRUSER ……. SAP_XI_ID_SERV_USER_MAIN
PI(XI)REPUSER ……. SAP_XI_IR_SERV_USER_MAIN
PI(XI)ISUSER …….. SAP_XI_IS_SERV_USER_MAIN
PI(XI)RWBUSER ……. SAP_XI_RWB_SERV_USER_MAIN

————————< D042786 22/APR/08 >————————
PI: Rescheduling PI-Specific Background Jobs
As of SAP NetWeaver PI 7.0 SPS15, you no longer need to reschedule the following job: “Background Job for Deadline Monitoring”.
————————< D031901 DEC/02/05 >————————–
Copying Commands From the Upgrade Guide
When you copy a command from the upgrade guide in order to paste it into 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.
————————< D038245 APR/18/08 >————————–
Windows only: Restarting the Upgrade Program
There is only one way to restart the upgrade program. You must restart it from the upgrade directory.
———————————————————————-
IV/ ….. Errors on the CD-ROM
———————————————————————-

V/ Preparing the Upgrade

a) GENERAL

———————< D038377 19/JUN/09 >—————————-
Create Internal Service User with UME Role Administrator
Before starting the upgrade, you need to create a user with the Security Policy ‘Internal Service User’ and assign the user to the UME role “Administrator”. For more information, see Note1349854.
———————< 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.
———————< 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.
———————-< D033903 28/JAN/09 >—————————-
Required JVM for Starting the Upgrade GUI
The upgrade GUI requires at least Java Virtual Machine (JVM) 1.5. On the host where the upgrade program is running, this JVM is provided by the SL Controller. If you start the GUI on a remote computer, make sure that JVM 1.5 is installed.
———————–< 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 the SAP Service Marketplace and unpack them in the
same directory as described in SAP note1258173.
———————–< D026562 17/NOV/08 >—————————
Downloading Logically-Split Volumes
When you download DVDs from SAP Service Markeptplace that are split in several ZIP files, proceed as described in Note1258173.
——————-< changed I036707 05/NOV/08 >———————–
———————–< I036707 18/AUG/08 >—————————
Apply the Latest Patches for ESR 7.10, J2EE ENGINE FRAMEWORK 7.10
If you are upgrading your PI system to a Support Package level 7.10 SP4, you need to download the latest patches for the components ESR 7.10 SP4 and J2EE ENGINE FRAMEWORK 7.10 SP4 from SAP Service Marketplace and include them in the BIND_SUPPORT_PACKAGES phase of the Configuration roadmap step. The patches are available for download at http://service.sap.com/swdc -> Download -> Support Packages and Patches -> Entry by Application Group -> SAP NetWeaver -> SAP NETWEAVER -> SAP NETWEAVER PI 7.1 -> Entry by Component -> Process Integration, then chooseESR 7.10orJ2EE ENGINE FRAMEWORK 7.10.
If you are upgrading to an SP level higher than SP4 as we strongly recommend, make sure that you have included the latest patches of the respective SP level for these components into 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 Solution Manager System Landscape, it is possible that an incorrect stack XML file is calculated as a result. Currently, the Maintenance Optimizer considers SID or HOST with only difference in letter case as different systems.
To prevent calculation of incorrect stack XML file in the Maintenance Optimizer, you need to implement the solution described in SAP Note1229555.
———————–< I035760 20/JUN/08 >————————–
Check the Password for User DDIC
If the Java users, such as J2EE_ADMIN, J2EE_GUEST, etc., are not available in your ABAP client 000 but in another client (for example, client 030), make sure that the user DDIC has the same password in client 000 and the client where the Java users are available (client 030 as an example).
This is needed for the upgrade in order to prevent RFC connection failures during the downtime.
———————–< D021285 29/MAY/08 >————————–
Upgrade of SEEBURGER Components
If you have SEEBURGER components running in your system, you need to perform several steps before and after the upgrade of the SAP server components.
For more information, see Note1167474.
———————–< D024409 16/MAY/08 >————————–
Check Availability of Equivalence Support Package
Source Release SAP NetWeaver 7.0: Before you apply SAP NetWeaver 7.0 Support Package 16 on the source release, check the availability of the equivalent SAP NetWeaver 7.1 Support Package 07. The dates of delivery are several months apart. If you do not include at least the equivalent Support Package level in the upgrade, you will lose data.
For more information, see SAP Service Marketplace at service.sap.com/solutions -> SAP NetWeaver -> SAP NetWeaver 7.0 – Release-Specific Information -> Support Package Stacks Information.
———————–< 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.
———————————————————————
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

———————-< D023890 18/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/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 to another 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>
———————–< I035760 20/JUN/08 >————————–
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 “36<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.
———————————————————————-
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 <instance-id> <instance-number> <instance-box-number><instance-id>: 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/<SID>/<instance-name> /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/<SID>/SYS/profile/<SID>_<instance-name>_<host> and search for the value of the j2ee/instance_id entry.<instance-number>: This is the central instance number. For example, if the instance name is JC12, then the instance number is 12.<instance-box-number>: 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/<SID>/<instance-name>/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:
<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

———————-< D038245 14/Jan/09 changed>———————-
Resetting the Upgrade During the Preprocessing Step
Make sure that the upgrade GUI displays the “Back” or “Next” buttons,
which indicate that SAPup is not in a dialog phase.
If it is in a dialog phase, the upgrade GUI displays the “Repeat”, Init,
and Exit buttons. In this case choose Exit before resetting the upgrade.
If you reset the upgrade while the shadow system is running, the shadow
system service will not be automatically uninstalled.
You have to uninstall the shadow system service manually.
Otherwise, you are not able to delete the upgrade directory since
the service still accesses an executable located in this directory.
End of the note.——< D038245 29/APR/08 >—————————-
ERROR: AIX 5.0 C++ runtime is not installed
If you get the error that AIX 5.0 C++ runtime is not installed although it is installed, choose “y” to continue the upgrade.
———————-< I024101 03/APR/08 >—————————-
Setting the Parameter fixdirectory in the STARTUP Script
In a scenario where the profile directory is located on a host different than the central instance host and the central instance is installed on Windows, make sure that when you start the upgrade from the Upgrade Master DVD for the first time, the following parameter is passed to the STARTUP script:
STARTUP -fixdirectory=<fixpack-directory>
where <fixpack-directory> is the directory in which the fix archive, downloaded from SAP Service Marketplace, is located.
———————-< D038245 03/APR/08 >—————————-
AIX 6.x: Error in the STARTUP script
On AIX 6.x, the STARTUP script issues a dialogue that the C++ runtime is not installed. You can ignore the check and enter “y” to continue.
———————-< D038245 23/JAN/08 >—————————-
Resetting the Upgrade During the Preprocessing Step
When you need to reset the upgrade during the Preprocessing step, you need to perform the following actionsafteryou have performed the actions described in the upgrade documentation:
1. Stop the SL controller.2. Remove the upgrade directory “/usr/sap/<SID>/upg”.3. Start the upgrade from the beginning as described in the upgrade documentation.
———————< 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 fixedthe 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 operational system on UNIX platforms.
———————————————————————-

b) ABAP ONLY

———————-<D030431 27/APR/07 >—————————-
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.
———————-<D030431 27/APR/07 >—————————-
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<date>.<SID> 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
——————–< D021285 AUG/06/08 changed >———————-
——————–< I035760 APR/08/08 >——————————
Error in Phase RUN_APPLICATION_MIGRATION
You may encounter an error during the migration of the application sap.com/com.sap.xi.repository in phase RUN_APPLICATION_MIGRATION. The following error message can be found in /usr/sap/<SID>/<central_instance>/j2ee/cluster/server0/log/system/server_00.0.log:
===
com.sap.engine.services.deploy.exceptions.ServerDeploymentException:
[ERROR CODE DPL.DS.5104] The migration of sap.com/com.sap.xi.repository failed, because migrator MigrationContainer threw an exception.
…
Caused by: java.sql.SQLException: ORA-01000: maximum open cursors exceeded
===
In this case, proceed as described in SAP Notes1235247and1238561.

——————–< I036707 JAN/14/08 >——————————
Reentering Passwords
After the Configuration roadmap step has finished, you have the option to reenter passwords that you had either entered in the Configuration roadmap step or that the upgrade program read from the secure store. This option is realized through the PASSWORD_REENTER module. Only use it if the upgrade has failed because you changed a password after the Configuration roadmap step or you entered a wrong password in the Configuration roadmap step.
You can update the following passwords using the PASSWORD_REENTER module :
Standard database schema password: If you have changed the standard database schema password after the Configuration Roadmap step, you have to run the PASSWORD_REENTER module in order that the upgrade program reads the new password from the secure store.SAP* user password: only required during ABAP+Java dual-stack upgradeDDIC password: only required during ABAP+Java dual-stack upgradeSAPService<SID>: only for Windows operating systemsDatabase system user: for Oracle onlyUser ID and password of database administrator: for IBM DB2 for z/OS only
Proceed as follows:
1. Stop the upgrade program.2. On the upgrade GUI, choose “Java EE” -> “Start with Options”. The Start Program screen is displayed.3. In the Program Options field, add “run PASSWORD_REENTER” to the existing rootdir option as follows:
rootdir=<root>/usr/sap/<SID> /upg/java run PASSWORD_REENTER4. Choose “Execute”.5. On the following screens, enter the passwords.6. Restart the upgrade.
————————< I036707 FEB/09/06 >————————-
SDM Timeout in DEPLOY_ONLINE Phase
The upgrade can abort in the DEPLPOY_ONLINE phase due to an SDM timeout. See SAP Note756084for the solution.
———————–< I028226 OCT/19/05 >—————————
SAPJup Hangs in a J2EE Engine Restart Phase
This problem occurs only when your source release system has a Support Package level lower than NetWeaver ?4 SP15 and when you use an IBM JDK. The upgrade hangs in one of the phases in which the J2EE Engine is restarted.
See SAP Note878909for the solution.

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 an last name for user TMSADM.
For more information, see Note1047762.
———————–< D028310 29/JUN/05—————————
SAP XI: Delete three empty tables
If you get an error message after the upgrade concerning the following
tables, you can delete them:
/SDF/RZ20_TMPL_P/SDF/RZ20_TMPL_N/BDL/CUST_TREE
If there are error messages on different tables, do not delete them but contact SAP support.
———————–< D023890 29/JUN/05—————————
SHORT DUMPS: XI: RFC_NO_AUTHORITY (XILDUSER)
After an XI upgrade the following short dump is written every few seconds: RFC_NO_AUTHORITY:
User “XILDUSER” has no RFC authorization for function group “SYST”.
Regenerate Roles for SAP_XI and SAP_SLD as described in upgrade documentation section ” SAP XI: Generating Roles for SAP_XI and SAP_SLD”.
——————–<enhanced D038245/JUNE/05 >———————-
———————–< 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

———————-< I036707 JAN/28/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.
———————- <D031901 FEB/19/08 >—————————
PCK: Checking aii properties
The Partner Connectivity Kit requires the aii.properties file to be able start. The aii.properties file must be present in the root directory of your AS Java.
For information about checking the aii.properties file and how to create it, if necessary, see SAP Note746328.
———————– < D021285 DEC/04/07 >————————-
Components not Registered in SLD
After the upgrade to SAP NetWeaver PI 7.1 SP04, the components might not be registered completely in the system landscape directory. See SAP Note1117249to solve the problem.

————————< 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
———————————————————————–
JUN/19/09….V..Create Internal Service User with UME Role Administrator
MAR/18/09…II..Source Release NW 7.0 only: Handling DI_CMS and DI Usage
MAR/18/09….V..Source Release based on 6.40 Java only: Shut down IGS
MAR/12/09….V..Increased Space Requirements in the Database
MAR/09/09….V..HA on Windows only: Apply Note 828432 Before the Upgrade
FEB/11/09…II..Upgrade Path SAP NW 7.0 EHP1 to NW PI 7.1- Not Supported
FEB/11/09….V..Cleaning Up the Profile Directory
FEB/03/09..III..Limited Length of the DDIC Password
JAN/28/09….V..Required JVM for Starting the Upgrade GUI
JAN/28/09..VII..Source Release Tables with Prefix “OLD_” Can be Dropped
JAN/16/09….V..Downloading Kernel DVDs for the Upgrade
JAN/14/09…VI..Resetting the Upgrade During the Preprocessing Step
JAN/09/09..III..Upgrade – Step by Step
NOV/25/08..VII..Large XSLT Stylesheets Cannot be Compiled to Java Method
NOV/17/08….V..Downloading Logically-Split Volumes
NOV/05/08….V..Apply the Latest Patches for ESR 7.10 and J2EEFRMW 7.10
AUG/06/08..III..Parameter Input Module – mount directories paths length
JUL/15/08….V..Prevent Calculation of Incorrect Stack XML
JUL/08/08..III..Upgrade – Step by Step
JUL/08/08..III..PI: Changing the User Type
JUN/20/08….V..Source Release NW 7.0 only: Check SCS Instance Profile
JUN/20/08….V..Check the Password for User DDIC
MAY/29/08….V..Upgrade of SEEBURGER Components
MAY/16/08….V..Check Availability of Equivalence Support Package
APR/29/08…VI..ERROR: AIX 5.0 C++ runtime is not installed
APR/24/08…II..Upgrade Source System must be a Dedicated PI System
APR/22/08..III..PI: Rescheduling PI-Specific Background Jobs
APR/18/08..III..Windows only: Restarting the Upgrade Program
APR/08/08…VI..Error in Phase RUN_APPLICATION_MIGRATION
APR/03/08…VI..Setting the Parameter fixdirectory in the STARTUP Script
APR/03/08…VI..AIX 6.x: Error in the STARTUP script
APR/02/08…II..Information for High Availability Environments
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
FEB/19/08..VII..PCK: Checking the aii properties file
FEB/07/08…II..BPE Integration Processes – Upgrade Information
JAN/29/08…II..AIX only: Check the C++ runtime level
JAN/24/08…VI..Phase: UPG_POSTP/REQSTARTSRV – sapstartsrv
JAN/23/08…VI..Resetting the Upgrade During the Preprocessing Step
JAN/14/08…VI..Java only: Reentering Passwords
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
DEC/04/07..VII..Components not registered in SLD
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/23/05..VII..SAP XI: Delete three empty tables
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/29/05..VII..SHORT DUMPS: XI: RFC_NO_AUTHORITY (XILDUSER)
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/09/02…VI..SDM Timout in DEPLOY_ONLINE Phase
FEB/02/05…II..LSMW now part of SAP_BASIS
DEC/02/05…II..Copying Commands From the Upgrade Guide
NOV/16/05…II..Include Equivalent Support Package Level in the Upgrade
OCT/19/05…VI..SAPJup Hangs in a J2EE Engine 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
———————————————————————-