SAP Basis Tech Supports

Symptom
Errors in the upgrade procedure or in the upgrade guide; preparations for the upgrade
Other terms
Update, migration, upgrade, release upgrade, maintenance level, SAPJup, PREPARE, upgrade program
Reason and Prerequisites
*
Solution

CAUTION:
This Note is updated regularly!
Therefore, you should read it again immediately before starting the upgrade.
CAUTION: This Note only applies when upgrading SAP Business Suite applications based on SAP NetWeaver 7.0 Java using SAPJup (Easy Adoption approach)

What information can I expect from this note?
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.
Which additional notes do I require in preparation for the upgrade?
This depends on the functions that you are using.
In addition to the central upgrade Note, you need to refer to the relevant database-specific Note below:
Database ………………………………………….. Note number
_______________________________________________________________________
SAP MaxDB ………………………………………………851229
IBM DB2 for i ………………………………………….1179413
IBM DB2 for Linux, UNIX and Windows ……………………….819876
IBM DB2 for z/OS ………………………………………..815202
MS SQL Server …………………………………………..825146
Oracle …………………………………………………885167

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

I/ SAPJup Keyword

———————————————————————-
The SAPJup keyword is: 11142341
This must be entered the first time you call SAPJup.
———————————————————————-

II/ Important General Information

——————–< I045711 JUN/19/09 >——————————
Correction Package for the Upgrade Program
Before the upgrade, it is ESSENTIAL that you check whether there are corrections for the Java upgrade program for your specific upgrade. The correction package includes the latest corrections for the upgrade program and is provided as SAR archive on SAP Service Marketplace.
Make sure that you have downloaded the latest version of the correction package at: 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.00-> #OS independent.
Correction Package Name: FIX_J_BS7EA.UPG
The SAR archive on SAP Service Marketplace has a slightly different naming convention: JBS7EA_<extension>.SAR, where <extension> represents the patch level and an 8 digit number. This extension varies with each patch level of the archive.
Detailed information on including the correction package in the upgrade program, is provided in the upgrade guide (section “Making Entries for the Initialization and Extraction Modules”).
——————–< I036200 JUN/17/08 >——————————
Enabling Upgrade to Usage Type EP Core (EPC)
You are only able to upgrade your portal system to usage type EPC if
you do not use PDK for .NET in the source release system. For more information, see SAP Note1179872.
——————–< I026023 FEB/22/08 >——————————
Upgrade of a standalone RTC Application Sharing Server only
If you want to upgrade a standalone Real-Time Collaboration Application Sharing Server, follow the instructions given in SAP Note1143013.
——————–< C5050823 APR/19/05 >—————————–
AIX only: JDK Version
Use the JDK version that is specified in SAP Note716927.

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

III/ Corrections to the Guides

——————–< C5034989 JUN/19/09 >—————————–
Upgrading or Installing Dialog Instances
To upgrade your dialog instance(s), you do not need to uninstall the old dialog instance(s) and then install new one(s) on the target SP level.
You must proceed with the option that is applicable:
If the dialog instance shares the kernel of the central instance (that is, the kernel directories DIR_CT_RUN effectively reside on the host indicated by the profile parameter SAPGLOBALHOST), then the dialog instance is already up-to-date after the upgrade of the central instance. Restart the dialog instance after performing all follow-up activities described in the upgrade guide.If the dialog instance uses a local kernel (when you are running a heterogeneous cluster), update the kernel binaries of the instance manually to the same SP level as on the central instance:Log on as user <sapsid>adm to the host of the instance to be updated.Back up the kernel directory that is specified by the profile parameter DIR_CT_RUN.Extract the SAR files of the kernel Support Packages (that is, the Support Packages for components SAP kernel and SAP IGS) to a temporary directory with SAPCAR.Stop the instance being updated.
NOTE: If the system is running in a high availability environment, make sure that the high availability software does not restart the instance automatically during the update.Copy or move the extracted programs from the temporary directory to the local kernel directory.Restart the instance after performing all follow-up activities described in the upgrade guide.

———————————————————————
IV/ Errors on the CD-ROM

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

V/ Preparing the Upgrade

———————–< D039661 JUL/15/08 >—————————
Dual-Stack Upgrade Only: 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.
———————–< I035253 JUL/26/07 >—————————
UNIX only: Deactivate enhanced sapstartsrv functions
Applies to the source release level SAP Basis 7.00 Kernel patch 96 or SP 12 or higher:
Make sure that you deactivate the enhanced sapstartsrv functionality before the upgrade. Otherwise, you will experience problems when exchanging the SAP kernel.
For more information, see Note995116.
———————–< I036200 JAN/15/07 >—————————
Usage Type Enterprise Portal: Preventing BI Java Deployment
If the BI Java usage type is not installed on your source release system and you do not want that the upgrade program deploys it during the upgrade, prepare your system as described inSAP Note 1015214.
——————–< I030669 changed MAR/16/06 > ———————
———————< I030669 DEC/22/05 >—————————-
Checking Java VM Setting Before the Upgrade
Before the upgrade, check that the following Java VM setting is configured correctly in your system. This prevents an error in the START_J2EE_INITIAL phase of the upgrade.
1. Open file \usr\sap\ <SID>\JCxx\j2ee\configtool\configtool.bat on Windows
or /usr/sap/<SID>/JCxx/j2ee/configtool/configtool.sh on Unix.2. Go to the Cluster Data node.3. Go to the Instance_IDxxxxxxx node.4. Go to the Dispatcher_IDxxxxxx node.5. On the General tab check the Java parameters.6. If there is a “-” missing in front of the -Xmsxxx parameter, add “-”
(xxx is the value of the parameter).7. Save your change.8. Restart the system.
———————–< D031901 OCT/05/05 >—————————
Free Space Requirements in the Database
Oracle
Usage Type Application Server
PSAP< SID>DB:…..1000 MB
SYSAUX:…………50 MB
SYSTEM:………….1 MB
Archiving logs:..1500 MBUsage Type Business Intelligence
PSAP< SID>DB:……2000 MB
SYSAUX:…………200 MB
SYSTEM:…………500 MB
Archiving logs:..10000 MBUsage Type Enterprise Portal
PSAP< SID>DB:……2000 MB
SYSAUX:…………200 MB
SYSTEM:…………500 MB
Archiving logs:..10000 MBUsage Type Development Infrastructure
PSAP< SID>DB:…..1500 MB
SYSAUX:…………20 MB
SYSTEM:………….5 MB
Archiving logs:…1500 MB
SAP MaxDB
Usage Type Application Server: 1000 MB; Archiving log: 1000 MBUsage Type Enterprise Portal: 1000 MBUsage Type Business Intelligence: 3000 MB
IBM DB2 for Linux, UNIX and Windows
Usage Type Application Server
< SID>#DBD:……………1500 MB
<SID>#DBI + SYSCATSPACE:..100 MBUsage Type Enterprise Portal:
< SID>#DBD:……………2000 MB
<SID>#DBI + SYSCATSPACE:..100 MBUsage Type Business Intelligence:
< SID>#DBD:……………2500 MB
<SID>#DBI + SYSCATSPACE:..100 MBUsage Type Development Infrastructure:
< SID>#DBD:…………….2000 MB
<SID>#DBI + SYSCATSPACE:…150 MB
MS SQL Server
Usage Type Application Server: 1500 MB; Archiving log: 500 MB
Usage Type Enterprise Portal: 2000 MB; Archiving log: 100 MB
Usage Type Business Intelligence: 2000 MB; Archiving log: 100 MB
Usage Type Development Infrastructure: 2000 MB;

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

VI/ Problems During the PREPARE and Upgrade Phases

This section addresses known problems that cannot be avoided using preventive measures. These problems will only occur under very specific circumstances.

Problems During the PREPARE Phases

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

Problems During the Upgrade Phases

———————-< D039661 NOV/03/08 >—————————
Usage Type EP: START_J2EE_EP Phase Fails
If you are upgrading an SAP system with usage type EP, the START_J2EE_EP phase may fail due to an error with the portal content deployment. The error message in the phase log file shows information about the found *.err files.
In this case, proceed as described in SAP Note1130469.
———————-< I024101 OCT/21/08 >—————————
Error in START_J2EE_EP Phase
The bootstrap process fails in this phase because its heap size is too small. You need to increase the heap size by using the J2EE Engine ConfigTool.
Proceed as described in SAP Note891510.
———————-< I024101 MAY/21/07 >—————————
Login error during upgrade
Inconsistencies of the SAP* user password in the different storage locations for the password lead to a failure of the phases UNDEPLOY_APPLICATIONS, DEPLOY_ONLINE or SET_PRODUCT_VERSION. You can find the following error in the SDM log file:
com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [p63734] with user name: [SAP*]
Check your login information.
Exception is:
com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Access Denied.
For information about the solution, seeSAP Note 865424.

————————–< I024140 JAN/21/08 >————————
Deployment of SP binaries fails
If deployment of SP binaries fails, this can be due to connectivity problems between the SDM and SAP J2EE Engine. For more information and troubleshooting, see SAP Notes609603and756084.

————————–< I805316 MAR/15/06 >————————
Deployment Errors
The upgrade may fail due to a deployment problem during the upgrade phase. Known issues are resolved in SAP Notes that can be found in the “Related Notes” section of this note or by searching the keyword SAPJUP.
——————< changed I035760, OCT/07/08 >———————–
———————–< I036707 FEB/09/06 >—————————
SDM Timeout in DEPLOY_ONLINE Phase
The upgrade may abort in the DEPLOY_ONLINE phase due to an SDM timeout.
The following error message can be found in the log file DEPLOY_SLOT_1__DON_xx.LOG:
Error: An error occured in JStartup Framework:
The instance with instance name ‘<instance name>’ did not respond within 300 s. Throwable:
com.sap.bc.proj.jstartup.impl.JStartupClusterControlExceptionImpl
Throwable message: The instance with instance name ‘<instance name>’ did not respond within 300 s.
In this case, proceed as described in SAP Note739190.

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.

———————-< I031877 29/AUG/08 >—————————-
Follow-up Activities for Groupware Connectivity
For information about follow-up activities for Groupware connectivity,
see SAP Note788151.
———————-< I030662 DEC/01/06 >—————————-
Error Messages in UNDEPLOY_LIST Phase Log
After the upgrade, you may find one or several of the following error messages in the UNDEPLOY_LIST_<xxx>_.LOG file:
Error: No deployed SDA with the specified component attributes <…> found.
You can ignore these messages.
————————< I036707 JUL/03/06 >————————-
Components Missing in Transport Directory
After the upgrade of DEV system under NWDI control, components used for compilation only are missing in the transport directory.
You must manually copy the new versions of components you need for compilation.
For more information, see Note960817.

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

VIII/ Chronological Summary

Date……Topic..Short description
———————————————————————–
JUN/19/09..III…Upgrading or Installing Dialog Instances
JUN/19/09…II…Correction Package for the Upgrade Program
NOV/03/08…VI…Usage Type EP: START_J2EE_EP Phase Fails
OCT/21/08…VI…Error in START_J2EE_EP Phase
AUG/29/08..VII…Follow-up Activities for Groupware Connectivity
JUL/15/08….V…Dual-Stack Upgrade Only: Prevent Incorrect Stack XML
JUN/17/08…II…Enabling Upgrade to Usage Type EP Core (EPC)
FEB/22/08…II…Upgrade of a standalone RTC Application Sharing Server
JAN/21/08…VI…Deployment of SP binaries fails
JUL/26/07….V…UNIX only: Deactivate enhanced sapstartsrv functions
MAY/21/07…VI…Login Error During Upgrade
JAN/15/07….V…EP: Preventing BI Java Deployment
DEC/01/06..VII…Error Messages in UNDEPLOY_LIST Phase Log
JUL/03/06..VII…Components Missing in Transport Directory
MAR/15/06…VI…Deployment Errors
FEB/09/06…VI…SDM Timout in DEPLOY_ONLINE Phase
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”
APR/19/05…II…AIX only: JDK Version

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