SAP Basis Tech Supports

Symptom

This note provides information about problems in the installation documentation or in the installation procedure, preparations for the installation and additional information about the installation.

Other terms

Installation, installation program, i5/OS, iSeries, AS400, OS400, System i, IBM i, EHPI

Solution

***********************************************************************
This note describes only notes and problems in relation to IBM DB2 for i.
***********************************************************************
CAUTION:
This note is updated on a regular basis. You should therefore read it again directly before the installation.
What can I expect from this note?
This note contains additional information about the installation documentation. It describes problems that may occur during the Enhancement Package installation and it provides information that may help you to solve these problems. In general, references are made to other notes. Above all, this note should ensure that you do not lose data, the installation does not fail, and you do not experience long runtimes.
Which additional notes do I require in preparation for the Enhancement Package installation?
This depends on the functions that you are using. You definitely require the following notes:
Short Text……………………………………..Note Number
______________________________________________________________________
Installing Enhancement Package 1 for SAP NetWeaver 7.0 (general)……..1175848

Contents
===============
I/ …… Important general information
II/ ….. Errors in the Installation Documentation
III/ …. Errors on the CD
IV/ ….. Preparing for the installation
V/ …… Problems during the preparation and installation phases
VI/ ….. Problems after the Installation
VII/ …. Chronological Summary

———————————————————————-
I/ Important general information
———————< C5018355 JUN/09/2009 >—————————-
The SAP EHP Installer 7.00 currently indicates a problem, whereby the kernel switch cannot be successfully performed on kernel Release 701 for dual-stack systems. For this reason, the installer terminates the processing if the ABAP part is in the phase PARCONV_UPG and the Java part is in the phase DEPLOY_ONLINE_DEPL. Both phases usually run in parallel at this point. After this termination, several complex repairs are required to be able to continue with the EHP Installer. To do so, contact Development Support (component BC-INS-AS4) to allow them to perform the repairs. Ideally, you should postpone the installation of Enhancement Package 1 for NetWeaver 7.0 or Enhancement Package 4 for ERP 6.0 until the next patch is available. The EHP Installer for single-stack systems does not indicate this problem and can be performed. As a precautionary measure, however, we removed the package SAPehpi.SAR for the installer from the download area. If you operate a single-stack SAP system and require the EHP Installer package, also contact Development Support to obtain the file for the short term.
If you cannot postpone your schedule, the synchronization that is missing between the ABAP part and Java part must be provided manually. To do so, you are required to define a phase breakpoint in the phase PARCONV_UPG in the ABAP part and a phase breakpoint in the Java phase DEPLOY_ONLINE_DEPL. Then perform the EHP installation in accordance with the documentation until both EHP Installer parts have reached their breakpoints. Then stop only the ABAP part by choosing the option “Exit”. Then check whether there are still locks for the library SAP70U. This library is created during the kernel switch in the ABAP part and is used by it as of the phase KX_SWITCH. If there are no locks for this library, change the JSPM timeout in the file
/usr/sap//DVEBMGS/j2ee/JSPM/param/jspm-srv_config.txt
You must increase the value for “/dialog/SDTServerConnection/timeout” from 10000 to 50000. You then just let the Java part continue to run. In some cases, the online deployment terminates again at the start when you restart the SDM. You can recognize this because the first deployment log file was written in the current log directory of the JSPM (file name: OPERATESDM_nn…). One of these log files contains the messages
Could not shutdown server: The SDM Server is not running.(1)
Details: Could not establish connection to server ‘localhost/5nn18′:
Connection refused
Check whether the SDM server runs again in the meantime (with the command NETSTAT, check whether the aforementioned port has been reactivated). In this case, choose the option “Repeat” and repeat the deployment. If you cannot find any SDM log files, also contact Development Support. If the deployment is active (can be identified from the progress bars “xx items of yy deployed” in the Java tab page of the SDT GUI), also restart the ABAP part by choosing “Next” in the GUI and then choosing the option “Repeat” of the ABAP dialog. The EHP Installer should then continue to run as usual.
———————< D038245 08/MAY/08 >—————————-
This note refers to the special features of the SAP Enhancement Package installer on IBM DB2 for i. All comments and corrections contained in general Note 1175848 are also relevant for this installation.
———————-< c5018355 20/AUG/08 >———————-
You can use the SAP Enhancement Package installer for installations on the operating system version V5R4M0 and above as long as this has been generally certified by SAP. Note 410783 contains more detailed information about this. To start the installer, you must only use the command STARTEHPI. When you do this, the actual installation program is executed in the batch operation. Here, the job queue QUSRNOMAX and, therefore, the subsystem QSYSWRK are used.
Since processes that require a lot of memory also run during the update, a sufficiently large shared pool (for example, *BASE) must be assigned to the subsystem in which the program is to be executed. You avoid extremely long runtimes as a result. If necessary, choose another job queue (the parameter JOBQ in the command STARTEHPI), so that a suitable subsystem is selected.
——————–< D036390 JUL/30/07 >————————-
The system does not perform a separate check of the PTF level. 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.
———————–< C5018355 MAY/25/2007 >————————
For the SAP Enhancement Package installer, there is a predefined directory structure for the EHPI directory. The following subdirectories are available:
/usr/sap//upg/abap only for AS ABAP or double-stack systems
…/java only for AS Java or double-stack systems
…/jvm contains SAP JVM (Java runtime)
…/sdt contains tools for the front end (SDT GUI)
———————-< D027190 February 28, 2002 >——————
If a point-in-time recovery is required when installing an SAP Enhancement Package (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. 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.

II/ Error in the installation documentation
————————< C5018355 18/SEP/08 >————————-
Chapter 5.1 Starting the Installation Program
In the current version, the script ‘loadepilib’ also requires a mandatory parameter. During the call, you must enter the system ID of your SAP system. In this chapter, the calls that are described in the documentation change as follows:
QSH CMD(’//EHPI/loadepilib ‘)
or if you want to use different library names:
QSH CMD(’//EHPI/loadepilib
epilib= srvlib=‘)
You can view an overview of all of the available parameters by calling
QSH CMD(’//EHPI/loadepilib -help’)
————————< C5018355 20/Oct/08 >————————-
Chapter 5.3 Restarting the Installation Program
The EHP installer now analyzes the relevant data in the EHPI directory during the restart. For this reason, we removed the parameter RESTART for the command STARTEHPI.

ABAP:
=====
Java:
=====

III/ Errors in the delivery
ABAP:
=====
Java:
=====

IV/. Preparing for the installation
————————< C5018355 20/AUG/08 >————————-
Important!
When you install an SAP Enhancement Package, a new kernel with release 701 or above is also imported while the previously used version of the IGS is retained. Older versions of the IGS are not compatible with kernel release 701 or above and cause problems that may cause the machine to shut down. Before the installation, you must therefore install a new 700 version of the IGS (from September 3, 2008 or later). Proceed as described in Note 937000. In addition, this new IGS version requires at least DW patch 177 in your current kernel. To do this, proceed as described in Note 49365.
————————-< C5018355 17/Oct/08 >————————
When the first JSPM patch for NW701is released, you can also import a new IGS version using the EhP installer if your SAP system contains a Java stack. Before the installation, check whether the EhP stack contains at least the following versions:
Java Support Package Manager (JSPM): JSPM02_0-.SCA
IGS: igsexe_13-.sar
You are no longer required to import the IGS manually into the original kernel.

ABAP:
=====
————————-< D036390 04/Nov/08 >————————
Check the access authorizations of the directory /usr/sap/sap/trans/ehpi
if it exists. Set the authorizations so that a general access is
possible (for example, assign *PUBLIC *ALL/RWX authorizations)
———————–< D036390 JUL/31/2007>——————
Before you start the installer, check whether the parameter DIR_EXECUTABLE is set with the value /usr/sap//SYS/exe/run in the start profile of your system START_DVEBMGS_. 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:

1. Implement a kernel correction.
Irrespective of the source release, implement the latest corrections for DLTOLDPKGS into your source system.
- the 700 kernel must have at least patch level 75.
- patch R3INLPGM (patch level 26 or higher)
- patch LODSAPKRN (patch level 11 or higher)

2. General information
Note that the APYSAP command also replaces the program R3INLPGM in the R3400 library. If the target release kernel has already been loaded by the installer (always after the phase EXTRACTKRN_PRE), you must execute the following commands as user QSECOFR immediately after APYSAP:
ADDLIBLE LIB(SAP_TOOLS)
CRTDUPOBJ OBJ(R3INLPGM) FROMLIB(SAP_TOOLS) OBJTYPE(*PGM)
TOLIB(R3400) NEWOBJ(*OBJ)
FIXSAPOWN SID(*NONE) LIB(R3400)
The SAP_TOOLS library contains all of the primary tools required to start the installer library. The loaduplib script creates this library.
————————< D027190 JUN/13/2006 >——————–
Before you start the installation, 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 _DVEBMGS_. 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 //SYS/profile directory.
———————-< D019267 December 07, 2001 >——————-
Before the installation, check the page size of the tables. Otherwise, considerable performance problems will occur after the installation. Proceed as described in SAP Note 457209.
——————–< D030451 FEB/16/2001 >——————–
Before you begin the installation, 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 installation. For more information, see Note 42305.
Java:
=====
————————< C5018355 26/AUG/08 >————————-
Ensure that no further open deployments exist for the Java part (particularly for the JSPM itself). If you are in doubt, manually start the JSPM once before the installation in accordance with Note 885063 (section 1 – Installing and Starting JSPM). Follow the dialog boxes until the JSPM requests the “Package Type”. You can then choose “Cancel” and end the JSPM again.
————————< C5018355 27/AUG/08 >————————-
You require a newer version of the JSPM for double stack systems. Ensure that your EhP stack contains the file JSPM00_1-.SCA (in other words, it has patch level 1 or above, is a number for internal use). If your stack does contain the file JSPM00_0-.SCA, you cannot start the installation. If you start the installation, problems will occur in the the Java phase DEPLOY_ONLINE_DEPL that lead to the installation being reset.

V/ Problems during the preparation and installation phases
ABAP:
=====

——————–< D036390 24/SEP/08 >——————–
Resetting the roadmap step EXTRACTION
Before you reset the “Roadmap Step” EXTRACTION (using the
option “Back”, for example, if an error occurs) you must check the
directories //EHPI/abap/exe or
//EHPI/abap/exenew. If these directories are references
(links) to another directory, you must manually delete them using
the command RMVLNK.
By resetting, the directory //EHPI/abap
and all of its subdirectories are deleted. This means that in the case of
links, unwanted side effects and data loss may occur.
————————-< D036390 04/Nov/08 >————————
In the phase START_SHDI_FIRST
This phase may terminate under certain circumstances if the shadow system does not start
completely. The logfile of the message server (shadow system, path:
/usr/sap//EHPI/abap//DVEBMGSnn/work/dev_ms) contains the following :
load acl file = /usr/sap/BR2/EHPI/abap/BR2/SYS/global/ms_acl_info
*** I listen to port 3661 (3661) ***
*** ERROR => MsSLoginClient: client as0050_BR2_61 (127.0.0.1) is
not in acl List acess denied.
Your host has not been entered correctly in the authorization list ms_acl_info
(= hosts that are allowed to access the message server).
Check the entry in the file:
/usr/sap/BR2/EHPI/abap/BR2/SYS/global/ms_acl_info
and correct the entry. If required, enter
HOST=* (= any host permitted).
Before you repeat the phase, stop all active jobs of the shadow system manually.

——————-< D021890 APR/20/1997 >————————
DDL statements during the update
During the update, 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 cross-reference files of the system as described in Note 71258. This could affect the PARCONV_UPG phase, for example.
Java:
=====

VI/ Problems after the installation
ABAP:
=====
———————-< C5061069 APR/27/2009 >———————– EHP1:
=====
Due to general changes in Enhancement Package I, the program saposcol is no longer delivered with the Enhancement Package and, after executing it, you should install it (if required) in accordance with SAP Note 19227.
Enhancement Package 2:
=====
The program saposcol was replaced with saphostagent. saphostagent is not delivered with the Enhancement Package and, after performing, it should be installed (if required) in accordance with SAP Note 1031096.
——————-< 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.
Java:
=====

VII/ Chronological summary