SAP Basis Tech Supports

Symptom
You experience some problems with the upgrade procedure or the upgrade documentation contains errors.
You are preparing for an upgrade.
Other terms
Update, migration, release upgrade, upgrade, SAPup, SAPJup, AS400, OS400, i5/OS, iSeries, IBM i, System i

Solution
***********************************************************************
This Note contains IBM i-specific problems only.
***********************************************************************

The topics discussed here are:
=========================================
I/ Important general information
II/ Errors in the upgrade documentation
III/ Errors on the CD-ROM
IV/ Actions before the upgrade
V/ Problems with the preparation phases
VI/ Problems during the upgrade phases
VII/ Actions after the upgrade
VIII/ Problems after the upgrade

I/ Important general information
———————< updated I045711 MAY/11/09 >——————–
———————–< I045711 JUN/16/08 >————————–
This note refers to those special features associated with the upgrade to SAP Business Suite 7 and SAP Business Suite 7 SR1 on IBM i.
All remarks and corrections contained in following general Notes are also relevant for these upgrades:
For SAP Business Suite 7:
SAP NetWeaver 7.0 including EHP1 ABAP (IBM DB2 for i): 1168235SAP SAP ERP 6.0 including EHP4 ABAP: 1156968SAP CRM 7.0 ABAP: 1156969SAP SCM 7.0 ABAP: 1156970SAP SRM 7.0 ABAP: 1156844SAP NetWeaver 7.0 including EHP1 Java (IBM DB2 for i): 1172907SAP SAP ERP 6.0 including EHP4 Java: 1157236SAP CRM 7.0 Java: 1157237SAP SCM 7.0 Java: 1157238SAP SRM LAC 7.0: 1156843
For SAP Business Suite 7 Support Release 1:
SAP NetWeaver 7.0 including EHP1 ABAP (IBM DB2 for i): 1168235SAP SAP ERP 6.0 including EHP4 SR1 ABAP: 1292069SAP CRM 7.0 SR1 ABAP: 1292070SAP SCM 7.0 SR1 ABAP: 1292071SAP SRM 7.0 SR1 ABAP: 1293387SAP NetWeaver 7.0 including EHP1 Java (IBM DB2 for i): 1172907SAP SAP ERP 6.0 including EHP4 SR1 Java: 1297742SAP CRM 7.0 SR1 Java: 1297803SAP SCM 7.0 SR1 Java: 1297804SAP SRM LAC SR1 7.0: 1300205SAP CRM/SRM 7.0 SR1 based on SAP NetWeaver 7.0 Java: 1283395
———————< C5018355 SEP/14/07 >—————————-
Before you start the upgrade, check whether the parameter
DIR_EXECUTABLE = /usr/sap/<SID>/SYS/exe/run
is set in the start profile START_DVEBMGS<nn>_<host> and in the instance profile <sid>_DVEBMGS<nn>_<host> of your system. If it is not set, insert the parameter or correct it. This will prevent errors from occurring in the phases DBCHK_PRE and STOPSAP_IUPG.

II/ Errors in the upgrade documentation

III/ Errors on the CD-ROM

IV/ Actions before the upgrade
———————-< C5061069 10/Sep/08 >—————————
Required Deployment for XI Adapter Framework
The XI Adapter Framework contains an adapter component which is based onApache Axis. In case the JDK IBM 1.4.2 – 64 Bit OS/400 is used, make sure that the archive axisproviderlib.sda is deployed as described in SAP Note1028961. Otherwise, the registration of EarLoader for application sap.com/com.sap.aii.adapter.axis.appdeployment will fail during the upgrade.
———————-< C5061069 10/Aug/08 >—————————
Before you start the upgrade please check parameter DIR_PROFILE within the instance profile of the SAP system. The value should be:
/usr/sap/<sid>/SYS/profile
If it is not the upgrade will stop in phase PREP_INPUT/INITPUT_PRE with an error: Definition of paths of profiles is inconsistent.
————————-< D036390 03/Sept/07 >————————
Please check access rights of following directories before you start the upgrade:
/usr/sap/trans/upgrade,
/usr/sap/<SID> and all its subdirectories,
/usr/sap/tmp and all its subdirectories.
All those directories must have one of the following group profiles <SID>GROUP, <SID>OWNER, R3GROUP, R3OWNER with right *RWX assigned.

———————-< c5061069 20/August/08>———————–
In rare cases the following message will be shown during the upgrade: The following files were found to be still open after phase <current phase>:
/usr/sap/<sid>/upg/abap/log/SAPup.ECO
Please report it to the upgrade development!
In this case please exit SAPup and restart the upgrade by the STARTUP command.

V/ Problems with the preparation phases
—————–< C5061069 MAY/15/09 >—————————-
Symptom:
In case you perform an upgrade to SAP Business Suite 2008 SR1 it may happen that SDT Gui seems to hang, eg. you are not able to klick button Next or Back to jump between modules.
Reason:
If you enter command DSPMSG QSYSOPR you see the message
Maximum number of records reached for file QPRINT.
Workaround:
Answer NOMAX and continue the upgrade.
—————–< C5018355 OCT/24/08 >—————————-
Java phaseFIX_PACK_REMINDER
Symptom:The following error message can be found in log file SAPJUP.trc (which can be found in subdirectory ‘trc’ of the Java upgrade part):
java.lang.NoClassDefFoundError: com/sap/sdt/util/parse/ValueHolder
Reason:This is a loader error of the Java Classic VM 1.4.2 and still under investigation by IBM. During this phase, fixes are applied to the Java upgrade directory but the Java VM does not recognize all the fixes immediately due to internal dependencies.
Workaround:Restart the Java upgrade using the commandJUMPas described in the upgrade guide in chapter “Restarting PREPARE”.

———————-< C5061069 20/August/08>————————
Phase INITPUT_PRE
Symptom:
Phase INITPUT_PRE stops with error
#Error message set: ‘Inconsistent definition of profile path in profile:’/usr/sap/<sid>/SYS/profile’ != ‘/sapmnt/<sid>/profile’!!
Reason:
Parameter DIR_PROFILE of instance profile have value /sapmnt/<sid>/profile assigned.
Workaround:
1. Please change the value of DIR_PROFILE within the instance profile of the SAP system to /usr/sap/<sid>/SYS/profile.
2. Restart the SAP system.
3. Repeat the phase.

VI/ Problems during the upgrade phases
—————–< D027190 OCT/21/05 >—————————-
SAP ECC
PhasePARMVNT_SHD
Symptom:The phase terminates. The <DIR_PUT>/log/MVNTSHD.ELG log file contains the following entries for each of the objects UGMD0001, UGMD0002 and UGMD0010:
MVNTABS ERRORS: ddlntabs and RETURN CODE in PD000905.EC1 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2EETP345 18:41:48: Retcode 1024: SQL-error “-601-UGMD0001 in R3EC1DATA type *FILE already exist
2EETP345 s. MSGID= Job=530511/EC1OFR/TP” in DDL statement for “UGMD0001″
2EETP334 18:41:48: error in DDL, nametab for “UGMD0001″ not activated
Reason:This is a database error. The database already assigned the names of the new tables to be created to the short names of the existing indexes.
Solution:Follow the instructions given in SAP Note696249
If possible, use the following new names when renaming the indexes:
RENAME INDEX R3<sid>DATA/UGMD0001 TO SYSTEM NAME UGMD9001
RENAME INDEX R3<sid>DATA/UGMD0002 TO SYSTEM NAME UGMD9002
RENAME INDEX R3<sid>DATA/UGMD0010 TO SYSTEM NAME UGMD9010
———————–< C5061069 August/20/08 >———————–
Phase START_SHDI_FIRST
Symptom:
Start of shaddow instance fails. Logfile DEVTRACE.LOG shows:
*** ERROR => not allowed to connect to message server via port sapmsSHDS<sid>
Reason:
Within file <DIR_PUT>/<sid>/SYS/global/ms_acl_info the host, on that the upgrade is running, is not defined with its full qualified domain name. Therefor message server connect fails. Damit ist es diesemnicht gestattet sich an den Message Server zu verbinden.
Workaround:
1.Add the definition to the file <DIR_PUT>/<sid>/SYS/global/ms_acl_info eg.
HOST=as0045.wdf.sap.corp
meaning
HOST=<host>.<…>.<2nd-level-domain>.<top-level-domain>
2. Repeat phase.

———————-< C5061069 10/Sep/08 >—————————
Java or Dual-Stack Upgrade
Upgrade phaseSTART_J2EE_INITIAL:
Symptom:SAPJup can’t start the instance. Log file SYSTEM_START_<number>_TJI_<number>.ERR shows
StartInstance: Program STRSBSJOB does not exist (ILE).
Reason:SAPJup tries to start the instances with its old library list.
Solution:Log on as user <SID>OFR (a new session is required) and start the instance manually as described in the upgrade guide. Repeat this phase.
Upgrade phaseDEPLOY_ONLINE:
Symptom:The phase stops with an error and the log directory contains a file DEPLOY_SLOT_<number>_DON_<number>.ERR with the error message:
Error: Aborted: software component ‘SAP_JTECHS’/’sap.com’/'SAP AG’/'1000.7.01.0.0.20080709115000”/’0′
Solution:Repeat this phase.
Symptom:The phase stops with an error and the log directory contains a file DEPLOY_SLOT_<number>_DON_<number>.ERR with the error message:
ERROR: Not deployed. Deploy Service returned ERROR: java.rmi.RemoteException: Cannot register EarLoader for application sap.com/com.sap.aii.adapter.axis.app..
Reason: null; nested exception is: java.lang.NullPointerException
Reason:The XI Adapter Framework contains an adapter component which is based on Apache Axis.
Solution:Make sure that the archive axisproviderlib.sda is deployed as described in SAP Note1028961. Otherwise, the registration of EarLoader for application sap.com/com.sap.aii.adapter.axis.appdeployment will fail during the upgrade.
—————–< C5018355 Mar/14/08 >—————————-
Java Upgrade Only
PhaseUNDEPLOY_LIST
Symptom:This phase might fail if the Java instance does not start fast enough. Right before this phase, the J2EE Engine is started. If not all services are started, connect and/or logon problems might occur.
Solution:Make sure that the Java instance is in state ‘running’ before you can choose the option “Repeat”. Check the state in file /usr/sap/<sid>/<inst>/work/dev_server0.

VII/ Actions after the upgrade

VIII/ Problems after the upgrade
———————-< C5061069 27/April/2009 >———————– Due to generic changes, program saposcol is not delivered via upgrade anymore. Therefore, you need to install it manually as described in SAP Note19227if it is a requirement for your daily business.
Repairs in the Code

Attention: Do not enter source code here! Enter source code under
“Corrections” -> “Correction instructions”.
Lines entered here are deleted automatically when saving!