SAP Basis Tech Supports

Symptom
There are problems with the upgrade documentation or the upgrade procedure. This note outlines the preparatory steps for the upgrade and it also provides additional information about the upgrade.
Other terms
Update, migration, upgrade, release, maintenance level, SAPup, upgrade program, AS400, OS400, i5/OS, iSeries, IBM i, System i
Solution
***********************************************************************
This note describes only notes and problems in relation to IBM DB2 for i.
***********************************************************************
IMPORTANT:
This note is updated on a regular basis. You should therefore read it again directly before the upgrade.
What can I expect from this note?
This note contains additional information about the upgrade documentation. It describes problems that may occur during the system upgrade and it delivers information about how you can eliminate these problems. In general, references are made to other notes. Above all, this note should ensure that you do not lose data, the upgrade does not fail, and you do not experience long runtimes.
Which additional notes do I require in preparation for the upgrade?
This depends on the functions that you are using. You definitely require the following notes:
Short Text……………………………………..Note Number
______________________________________________________________________
Central Note: Upgrade to Systems on SAP NetWeaver 7.0 EHP 1 (ABAP)………1146578
Add. info.: Upgrade to SAP NetWeaver 7.0 EHP 1 (ABAP)………1146580
If you use additional applications on SAP NetWeaver 7.0 Enhancement Package 1, you also require the following note:
Upgrade to SAP Business Suite 7: IBM DB2 for i……..1179413
(not yet available)
Contents
===============
I/ …… Important general information
II/ ….. Errors in the upgrade documentation
III/ …. Errors on the CD
IV/ ….. Preparing for the upgrade
V/ …… Problems during the preparation and upgrade phases
VI/ ….. Problems after the upgrade
VII/ …. Chronological summary

———————————————————————-
I/ Important general information
———————-< D036390 SEP/03/2007 >———————-
This note relates to special features of the upgrade to SAP NetWeaver 7.0 with Enhancement Package 1 for SAP NetWeaver 7.0 on IBM DB2 for i. This note is also valid for the upgrade to NW 7.0 with Enhancement Package 1 SR1. All information and corrections contained in the general SAP Notes 1146578 and 1146580 are also relevant for this upgrade.
———————-< D024156 JUN/16/2008 >—————————
If you have to enter paths (for example, mount directories) during the upgrade, always enter these in UNIX format and not in Windows format.
———————-< C5061069 AUG/20/2008 >————————
———————-< D036390 SEP/03/2007 >———————-
The upgrade to SAP NetWeaver 7.0 Application Server ABAP with Enhancement Package 1 is allowed on operating system version V5R4M0 and higher once this has been generally certified by SAP. For more information, see Note 410783.
———————-< D036390 SEP/03/2007 >———————-
The upgrade was fully revised for SAP NetWeaver 7.1. As a result, there is no longer a strict distinction between the prepare phase and upgrade phase. Instead, the upgrade takes place in one continuous process that is subdivided into eight execution units. Therefore, in this note, you no longer need to use the PREPARE tool separately.
The start activity for the upgrade has also been changed (see also the paragraph in the upgrade documentation entitled “Starting the Upgrade Program” ). To start the upgrade, use only the command STARTUP. In this way, the actual upgrade program is also executed in batch operation. Here, the job queue QUSRNOMAX and, therefore, the subsystem QSYSWRK are used by default.
Since processes that require a lot of memory also run during the upgrade, a sufficiently large shared pool (for example, *BASE) must be assigned to the subsystem in which the upgrade program is to be executed. You avoid extremely long runtimes as a result. If necessary, choose another job queue (parameter JOBQ in the command STARTUP), so that a suitable subsystem is selected.
——————–< D036390 JUL/30/2007 >————————-
Due to the new general interface for the 710 upgrade, the PTF level is no longer checked when you start the upgrade. Therefore, you should manually check the PTF level before you start the upgrade. Refer to the IBM Information APAR for your OS/400 release as described in Note 83292.
If your Info APAR is obsolete, load the current version onto your machine in accordance with Note 144149.
After you load the upgrade tool (also refer to the upgrade documentation – loaduplib), you can use the command CHKR3PTF from the upgrade library to check the PTF level.
———————-< C5061069 AUG/20/2008 >————————
————————< C5018355 MAY/25/2007 >————————
For the upgrade to SAP NetWeaver 7.0 with Enhancement Package 1 and higher, the directory structure for the upgrade directory has changed and is now within the directory of the relevant SAP system by default. The following subdirectories are available:
/usr/sap/<SID>/upg/abap only for AS ABAP or double-stack systems
…/jvm contains SAP JVM (Java runtime)
…/sdt contains tools for the upgrade GUI
As a result, the directory /usr/sap/SID/upg/abap now corresponds to the put directory DIR_PUT.
———————-< C5061069 AUG/20/2008 >————————
————————< D036390 MAY/25/2007 >————————–
Applying patches:
Note that the tools for importing corrections change from release to release. Therefore, depending on the situation, you must proceed according to the instructions in the source or target release. The target release tools are always available in the upgrade library. A number of problematic issues and errors that occur frequently when you patch the upgrade tool are collected in the following points:
During the upgrade, you should not apply any patches to the target kernel. It does not make sense to implement corrections unless concrete errors that affect the upgrade occur. If they occur, adhere to the procedure described here.You must implement corrections for the upgrade in advance. That is, you must implement the corrections before you use loaduplib to install the upgrade tools. Proceed as follows:1. Download the latest version of SAPup7104 (see:http://service.sap.com: ->”Entry by Application Group -> Additional Components ->Upgrade Tools ->SAPup Unicode ->SAPup7.10 -> Os/400″) and of ILE.SAR (see: http://service.sap.com: ->”Entry by Application Group ->Additional Components ->SAP Kernel ->SAP Kernel 64 Bit (UNICODE) ->SAP Kernel 7.01_64 Bit ->Os/400 ->DB2/400″) from SAP Service Marketplace.2. Copy the upgrade master CD/DVD to an IFS directory on your upgrade server. The root directory of the copy should subsequently be identified by /<UM_copy_root>.3. Replace SAPup.SAR on the upgrade master CD/DVD copy in the directory /<UM_copy_root>/DATA_UNITS/SAPUP_710_4_OS400_PPC64.4. Replace ILE.SAR on the upgrade master CD/DVD copy in the directory /<UM_copy_root>/DATA_UNITS/UM_SAPCAR_OS400_PPC64.5. You can now begin to load the upgrade tools as described in the upgrade documentation.
——————–< C5061069 AUG/20/2008 >————————–
———————-< D035492 JAN/05/2007 >—————————-
Previously, the system i upgrade to target release NetWeaver 7.0 with Enhancement Package 1 did not support an incremental table conversion (ICNV). However, the fields that result from this conversion are only displayed when you initialize the tables or when data is transferred. Therefore, when you use the ICNV function in later phases of the upgrade (MODPROF_TRANS), some errors or inconsistencies may occur that require you to restart the upgrade (for more information, see Note 904120). Therefore, never use ICNV. As soon as ICNV is supported, we will update this section of the note.
———————-< D027190 SEP/06/2002 >—————————
Note that, depending on the upgrade strategy that you have selected and the archiving mode, the size of the journal receiver may increase considerably during the upgrade. This may cause space problems, in particular during the EU_IMPORT phases if you do not save and delete the fully-run journal receiver in time.
———————-< D027190 FEB/28/2002 >————————
If a point-in-time recovery is required during the SAP system upgrade (this is unlikely), you must use the command APYJRNCHGX instead of the usual APYJRNCHG. This is because a large number of DDL statements are executed during the upgrade, and DB2 UDB for iSeries does not automatically support the recovery of DDL statements. For more information, refer to the IBM documentation and the F1 help for APYJRNCHGX.
As a result of validation by SAP, IBM was able to find and repair a substantial number of errors that occur when using APYJRNCHGX. Therefore, before you start the upgrade, it is absolutely essential that you install the current PTF version in accordance with the APAR information for your release. For more information, see Note 83292.
———————< D021890 FEB/05/1999>————————–
New procedures and technologies are in use as of Basis Release 6.40. For more information, see the following note: 766913.

II/ Errors in the upgrade documentation

III/ Errors on the CD-ROM

IV/ Preparing for the upgrade
———————< C5061069 AUG/20/2008 >————————-
Before the upgrade, check the entry DIR_PROFILE in the instance profile of your SAP system. The value of the parameter must be as follows:
/usr/sap/<sid>/SYS/profile
Otherwise, the upgrade will display an error message in the phase PREP_INPUT/INITPUT_PRE stating that the definition of the profile path in the profiles is inconsistent.
————————-< D036390 SEP/03/2007 >————————
Before the upgrade, check the access rights on the following directories: /usr/sap/trans/upgrade, /usr/sap/<SID> and all of the subdirectories, and /usr/sap/tmp and all of the subdirectories. For all of these directories and subdirectories, one of the group profiles (SID>GROUP, <SID>OWNER, R3GROUP or R3OWNER) must have the *RWX authorizations.
———————–< D036390 JUL/31/2007>———————-
Before you start the upgrade, proceed as follows: In the start profile of your system START_DVEBMGS_<host>, check whether the parameter DIR_EXECUTABLE is set with the value /usr/sap/<SID>/SYS/exe/run. If it is not set, insert the parameter or correct it. Doing this prevents an error in the DBCHK_PRE phase.
———————-< D036390 JUN/28/2002 >———————
Support Packages in the source release:
Implement a kernel correction.
Irrespective of the source release, implement the latest corrections for DLTOLDPKGS into your source system.
For 46D – The kernel must have at least patch level 1041. In addition, the tp program must have at least patch level 1305.
For 6.40 (this is also DCK for systems on 6.10/6.20 Basis) – The kernel must have at least patch level 62.
For 7.00 – The kernel must have at least patch level 75.
Application corrections (Support Packages)
For systems with Basis 6.10 or Basis 6.20, you must import at least the following Support Packages before the upgrade:
SAP_BASIS 6.10: SAPKB61031
SAP_BASIS 6.20: SAPKB62041
General information
Note that the APYR3KRN command also replaces the program R3INLPGM in the R3<sid>400 library. If the target release kernel has already been loaded by the upgrade (always after the phase EXTRACTKRN_PRE), you must execute the following commands as user QSECOFR immediately after APYR3KRN:
ADDLIBLE LIB(SAP_TOOLS)
CRTDUPOBJ OBJ(R3INLPGM) FROMLIB(SAP_TOOLS) OBJTYPE(*PGM) TOLIB(R3<sid>400) NEWOBJ(*OBJ)
FIXSAPOWN SID(*NONE) LIB(R3<sid>400)
The SAP_TOOLS library contains all of the primary tools required to start the upgrade. The loaduplib script loads this library.
————————-< D027190 JUN/13/2006 >————————
Before you start the upgrade, make sure that the name of the instance profile for the central instance corresponds to SAP conventions, that is, ensure that it has the form <SID>_DVEBMGS_<host>. The referencing in the start profile must also be modified to include any changes that have been made. Any differences mean that it will not be possible to convert the name of the instance profile in the copy of the start profile for the shadow instance. Accordingly, the shadow instance cannot start in the phase START_SHDI_FIRST.
After you execute the preprocessing unit, check whether the entries in the start profile of the shadow instance are consistent with the name of the associated instance profile. Both profiles are available in the <DIR_PUT>/<SID>/SYS/profile directory.
————————-< C5018355 JUN/13/2006 >———————–
If your SAP system was already upgraded in the past, the IND_NTACT help index may remain in rare cases. You can use transaction DB02 to determine whether or not the help index exists. In the consistency check, call the comparison between the database and the ABAP dictionary. If the index exists, it is listed as an index that is unknown to the dictionary. Delete this index before you start the upgrade.
———————< D027190 OCT/04/2005 >———————-
The tables DBSTATHDB4 and DBSTAIHDB4, and also (as of 6.40) the tables DB4TABLE_HIST (short name: DB4TA00001) and DB4INDEX_HIST (short name: DB4IN00001) may have become very large. As of Release 7.00, the system automatically cleans up these tables. If you obtain this function in your system as a result of the upgrade, the first cleanup run can take a very long time and this may lead to an overrun in the journal in the system ASP. To avoid problems, you should check the size of the tables before the upgrade, for example, using the operating system command DSPOBJD. If the tables are larger than 1 GB, you should carry out a cleanup before the upgrade using CLRPFM, as described in Note 93774. You can also carry out this cleanup if the problems described above occur after the upgrade.
———————-< D027190 MAR/01/2002 >———————-
Check the journal settings of the database for the size of the journal receiver (command WRKJRNA). Recommended values:
Receiver size options:
*RMVINTENT (recommended)
*MAXOPT2 (mandatory)
Without these settings, an error will occur in the the upgrade in the EU_IMPORT phase.
————————< D019267 DEC/07/2001 >——————–
Before the upgrade, check the page size of tables. Otherwise, considerable performance problems will occur after the upgrade. Proceed as described in SAP Note 457209.
———————-< D030451 FEB/16/2001 >———————–
Before you begin the upgrade, check the table types as described in Note 380968.
———————< D021890 FEB/05/1999>————————–
Check if the problem with the SQL catalog described in SAP Note 66985 exists.
Make sure that the language and code page settings are implemented in your system so that you can fully import the English language, which is imported by default during the upgrade. For more information, see Note 42305.
V/ Problems during the preparation and upgrade phases
———————-< C5061069 AUG/20/2008 >————————
In rare cases, the system displays the following error message during the upgrade:
The following files were found to be still open after phase <current phase>:
/usr/sap/ALF/upg/abap/log/SAPup.ECO
Please report it to the upgrade development!
If this file or other files are listed, you must end the upgrade and restart it using STARTUP.
———————-< D036390 SEP/04/2007 >———————-
Phase KEY_CHK
In this phase, the system asks for a path to a (new) upgrade program in order to exchange the program. This option is not yet supported on iSeries.
———————-< C5061069 AUG/20/2008 >———————-
Phase INITPUT_PRE
Symptom:
The phase INITPUT_PRE terminates with the following error message:
#Error message set: ‘Inconsistent definition of profile path in profile:’/usr/sap/<sid>/SYS/profile’ != ‘/sapmnt/<sid>/profile’!!
Reason:
The entry DIR_PROFILE in the instance profile of your SAP system has the value /sapmnt/<sid>/profile.
Solution:
1. Change the value of the parameter DIR_PROFILE in the instance profile of your SAP system to the value /usr/sap/<sid>/SYS/profile.
2. Restart you SAP system.
3. Repeat the phase.
———————–< D027190 FEB/28/2002 >————————
LANG_SELECT phase
Symptom:
The LANG_SELECT phase terminates with the following error message:
Please mount another Language Disk for these language(s). You need at least CDs which satisfy the vector “DE” (standard languages) for all components. It is not allowed to omit this update.
Reason:
An error occurred in the kernel of the SAP system that is running. For more information, refer Note 454083
Solution:
For an SAP system with Basis Release 4.6D, use a kernel with at least patch level 1041.
——————-< D027190 OCT/26/2004 >————————–
EU_IMPORT phases
Symptom:
When you restart after a termination, R3load terminates again with an error during the import. Error message CPF7032 appears in the job log of the R3load and in the corresponding log file: Command ENDJRNPF or ENDJRNAP failed.
Reason:
After tables are created, the journal recording for the “Resource minimized” upgrade strategy is deactivated during the import to improve performance. If an error occurs during this time, R3load will probably not be able to restart the journal recording. When you restart, the deactivation fails.
Solution:
Start the journal recording for the table in question explicitly using the STRJRNPF command. You can catch a large number of the possible scenarios that would result in this error by using the most recent R3load (at least Version 13) in the kernel of the target release.
———————–< C5061069 AUG/20/2008 >———————– Phase START_SHDI_FIRST
Symptom: Attempts to start the shadow system fail. The following error is logged in the file DEVTRACE.LOG:
*** ERROR => not allowed to connect to message server via port sapmsSHDS<sid>
Reason:
In the file <DIR_PUT>/<sid>/SYS/global/ms_acl_info, the host is not defined with its fully qualified domain name, which contains the SAP system to be upgraded. As a result, the host is not allowed to connect to the message server.
Solution:
1. Add the fully qualified domain name to the host definition in the file <DIR_PUT>/<sid>/SYS/global/ms_acl_info,
for example, as follows: HOST=as0045.wdf.sap.corp
that is
HOST=<host>.<…>.<2nd-level-domain>.<top-level-domain>
2. Repeat the phase.
——————-< D021890 APR/20/1997 >————————
DDL statements during the upgrade
During the upgrade, problems may occur that relate to a DDL statement and cause a termination. If this occurs, check whether this relates to the problem of inconsistencies in the system’s cross-reference files as described in Note 71258. This could affect the PARCONV_UPG phase, for example.
VI/ Problems after the upgrade
———————-< C5061069 APR/27/2009 >———————– Due to general changes in the upgrade, the program saposcol is no longer delivered with the upgrade and, after executing it, you should install it (if required) in accordance with SAP Note 19227.
——————-< D030451 JAN/02/2001 >———————–
After the upgrade of production systems, increase the value of the profile parameter em/initialsize_MB in the instance profile to 8192 as described in SAP Note 371029. Otherwise, if many users log on, all the work processes may have the PRIV mode.
———————-< D027190 JUL/06/2004 >——————
During the upgrade, the program creates the IND_NTACT index, which is not known to the Data Dictionary, and which is therefore displayed when you call transaction DB02. Use SQL tools to delete this index after you complete the upgrade.

VII/ Chronological summary