Note 1636252 - Installing a 7.20 kernel in SAP Web AS 7.007.017.107.11

Symptom

You want to use the 7.20 or 7.20 EXT kernel as a downward-compatible kernel in one of the following NetWeaver releases

• SAP NetWeaver 7.0 ("7.00")

• SAP EhP1 for SAP NetWeaver 7.0 ("7.01")

• SAP NetWeaver 7.10 ("7.10")

• SAP EhP1 for SAP NetWeaver 7.10 ("7.11")

or in

• SAP NetWeaver CE 7.1

• SAP EhP1 for NW CE 7.1

Other terms

7.20, 7.20 EXT, 720_EXT, AKK, DCK, Downward-Compatible Kernel

Reason and Prerequisites

Attention

• This note is valid for all systems with NetWeaver Release 7.00, 7.01 (7.0 Enhancement Package 1), 7.10 and 7.11 (7.1 Enhancement Package 1) as well as CE 7.10 and 7.11 that still run with the 7.00, 7.01, 7.10 or 7.11 kernel that was originally delivered.

• You can also use the 7.20 EXT kernel as a downward-compatible kernel for the NetWeaver releases mentioned above. If you want to use the 7.20 EXT kernel, you have to download all kernel archives from the link of the corresponding EXT branch on the SAP Service Marketplace (e.g., from link "SAP Kernel 7.20 EXT 64-BIT UC" if you look for 64-bit UC kernel ). Please notice that it is very important not to mix executables from kernel 7.20 and 7.20 EXT. It is explicitly mentioned in the text if the handling of the 7.20 EXT kernel differs from the handling of the 7.20 standard kernel.
  For the handling of SAP HostAgent, please refer to section 3 "Installing SAPHOSTAGENT".

• You may have to perform an operating system upgrade before you upgrade the kernel, or you may have to ensure additional database-specific prerequisites before the kernel upgrade (for example, the 7.20 kernel may be supported for certain operating system releases or database releases only). In particular, this applies to SAP kernel 7.20 EXT.
  Release information is available at: http://service.sap.com/pam

• The 7.20 kernel checks complex DDIC structures in more detail than the previous kernels. Short dumps of the type DDIC_TYPELENG_INCONSISTENT may occur, for example, when calling transaction SM66. For more detailed information about correcting these inconsistencies, see Note 1610716.
  The actions described in this note can be performed anytime, but we recommend to implement it before the kernel switch.

• If you want to use DCK for CE Developer Workplace systems, then check note 1709911.

• Release 7.00 or 7.01: Follow SAP note 1119735 regarding the relocation of the contents of the CCMS agents' working directories. This is described under "Preface" in section "Solution".

The following four bullet points apply only to Dual-Stack or Java only systems:

• Release 7.00 or 7.01: There was an incompatibility regarding jmon (SAP note 1652660). This has been eliminated with the following versions of the SAP Tech S Offline component:

This implies that at least support-package stack 14 or 3, respectively, must be installed in your system.
Note 1652660 also lists the required patch levels for the higher support packages.

• Release 7.00 or 7.01: The tool JSPM must have at least SP 24 or 9, respectively.

• Release 7.10 or 7.11: When using the SAPJVM 5.1, you have to install the latest patch collection, at least PC 58 (Build 5.1.074).

• SAP Kernel 7.20 (EXT) should have at least Patch Level 201.

Platform-Specific Information

The downward compatible SAP Kernel 7.20 is designed for maximum coverage. As a result the SAP Kernel 7.20 can basically be used as DCK without additional platform requirements. Please verify for your SAP product release which database and operating system releases are supported with the 7.20 kernel. The PAM for your SAP product release can be accessed via the SAP Service Marketplace http://service.sap.com/pam. However, if you intend to use the SAP Kernel 7.20 as DCK you have to consider the following platform specific information:

• IBM AIX
  Please see SAP Note 1780629 for the minimal OS release and C/C++ runtime requirements.

• IBM DB2 LUW
  IBM DB2/UDB 8 is not supported with the SAP Kernel 7.20.

• IBM z/OS
  IBM z/OS 1.6, 1.7 and 1.8 are not supported with the SAP Kernel 7.20.

• SAP MaxDB
  The SAP Kernel 7.20 requires at least version 7.7.04.09 of the MaxDB Client software (SQLBC). For more details refer to SAP Note 1487269.

• Microsoft SQL Server

• Oracle Database
  Oracle 10.1 is not supported with the SAP Kernel 7.20. You have to use at least Oracle 10.2.

The downward compatible SAP Kernel 7.20 EXT is designed for maximum supportability. As a result you may need to update your database and operating system version to use the SAP Kernel 7.20 EXT as DCK. Please verify for your SAP product release which database and operating system releases are supported with the 7.20 EXT kernel. The PAM for your SAP product release can be accessed via the SAP Service Marketplace http://service.sap.com/pam. However, if you intend to use the SAP Kernel 7.20 EXT as DCK you have to consider the following platform specific information:

• AIX
  Please see SAP Note 1780629 for the minimal OS release and C/C++ runtime requirements.

• IBM i
  The SAP Kernel 7.20 EXT (but only non-Unicode) requires the locales of all languages you use within your SAP system to be installed on within PASE. For details refer to SAP Note 1423600.

• Linux
  For details on Linux requirements refer to SAP Note 1563102.

• Microsoft Windows
  The SAP Kernel 7.20 EXT requires a specific Microsoft Windows C Runtime environment. For details refer to SAP Note 1553465.

• Oracle Database
  On all operating system platforms, except IBM Power Linux, Windows IA64 and Linux IA64 (Intel Itanium), only Oracle 11g is supported. On IBM Power Linux, Windows IA64 and on Linux IA64 (Intel Itanium), only Oracle 10g is supported.

If you use a DB/OS platform combination in your system environment where both the DB release and the OS release are supported by the 7.20 EXT kernel, we recommend to use the 7.20 EXT kernel instead of the 7.20 standard kernel.

Solution

The 7.20 kernel, which is delivered by SAP for Release 7.02 (7.0 Enhancement Package 2), is downward-compatible to the kernels for releases 7.00, 7.01, 7.10, and 7.11. Therefore, you can eliminate errors by replacing the kernel with a 7.20 kernel so that you do not have to perform an SAP upgrade.

Important

• You must exchange the kernels on all servers of the affected system.

• The general SAP recommendation to keep up to date with the upgrades or updates remains unaffected by this downward-compatible kernel because it does not correct application errors.

• For compatibility reasons, the 7.20 kernel is still available for certain 32-bit platforms (Windows, Linux); however, we strongly recommend that you use the 64-bit variant. The 32-bit variant is not suitable for production operation.
  The 7.20 EXT kernel is not available in a 32-bit variant.

• You can upgrade to the 7.20 kernel without having to install the new GUI version on the front-end PCs.

• After you have installed a 7.20 (EXT) kernel, you must:

Definition of terms

Here, 'kernel' means all executable programs located in /usr/sap//SYS/exe/run (UNIX, IBM i) or \\$(SAPGLOBALHOST)\sapmnt\\sys\exe\\ (Windows), not just the executable disp+work.

1. Obtaining the Archives

The elements that are required for importing the kernel are available as an SAR archive on SAP Service Marketplace under "SAP Kernel". There a differentiation is made between 32-bit and 64-bit kernels and also between the character width (Unicode or non-Unicode). As a further sub-option, a differentiation is made between the platform and under this, a differentiation is made between database-independent archives and (for each database supported in the platform) database-dependent archives. The name of the archive is made from a template of type _-.SAR. Here, is the actual name of the archive, followed by the patch level and a unique ID in which the bit value, the character width, the platform and the database type of the relevant archive are included again. In general, only the short form .SAR is used in this note (for example, SAPEXE.SAR). For more information about the download, see Note 19466.
You should download the following archives into the same directory :

• Due to the digital signature of the archives (see Note 1598550), you require the latest SAPCAR. Therefore, download the archive SAPCAR_-.EXE from SAP Service Marketplace under the name SAPCAR (UNIX, IBM i) or sapcar.exe (Windows) into your local directory.

• Download the latest 7.20 stack kernel from SAP Service Marketplace. The stack kernel consists of the database-independent archive SAPEXE.SAR and the database-dependent archive SAPEXEDB.SAR.
  On Oracle on Windows, you also still require the current Oracle Instant Client (see Note 998004).
  If you use different platforms (for example, Windows Application Server with database DB2 on IBM i), you can immediately download the stack kernel for all of the required platforms.

• If the Internet Graphics Server (IGS) is installed, you must also download the archives igsexe.sar and, optionally, igshelper.sar. When upgrading to kernel 7.20 or kernel 7.20 EXT you also need to upgrade the IGS installation accordingly:

• The archive igshelper.sar contains an optional component (see SAP note 1028690), which is only available as of SAP IGS 7.20. We recommend to apply the igshelper.sar to your installation as described in SAP note 1028690 when you are upgrading to kernel 7.20 or 7.20 EXT. The igshelper.sar is operating-system independent and release independent regarding SAP IGS releases newer than or equal to 7.20.
  You can download igshelper.sar from http://service.sap.com/patches -> "Browse Our Download Catalog" -> "SAP Frontend Components" -> "SAP IGS HELPER APPLICATIONS" -> "SAP IGS HELPER" -> "SAP IGS HELPER".

• If you use SAPCRYPTOLIB, you must also download the corresponding archive in accordance with SAP Note 397175.

• For Oracle only:
  Download the package DBATL720O10_-.SAR from http://service.sap.com/patches -> "Browse Our Download Catalog" -> "Additional Components" -> "SAP Kernel" -> SAP KERNEL (32|64)-BIT (UNICODE) -> SAP KERNEL 7.20 (EXT) ... -> -> ORACLE.
  For detailed information see note 12741.

• For IBM i only:

• For UNIX/Windows only:
  Download any additional programs (such as the RFCSDK) if you still want to install such programs after the kernel installation.

2. Preparations

After you have downloaded the required kernel components, you must stop all of the relevant processes on all instances for the system to be processed and release or delete the kernel-specific resources. To do this, carry out the following actions as the user adm on all instances:

• On UNIX or Windows:
  Stop the SAP system as usual.

• On IBM i:
  Stop the SAP system together with sapstartsrv:
  STOPSAP INSTANCE(*ALL) STARTUPSRV(*ALL) XDNLISTEN(*YES) WAIT(*YES) ENDSBS(*YES)

• On UNIX (Web AS release 7.0 and 7.01):
  cd /usr/sap//SYS/exe/run
  ./saposcol -k

• On UNIX (Web AS release 7.10 and 7.11):
  cd /usr/sap/hostctrl/exe
  ./saposcol -k

• On Windows:
  If it exists, stop the Windows service SAPOsCol and delete it using the following commands:
  net stop saposcol
  sc delete saposcol

• On IBM i:
  CALL PGM(SAPOSCOL) PARM('-k')

• On UNIX:
  kill -2

• On Windows:
  Stop and deactivate (Startup Type = Disabled) the services SAP_.

• sapccm4x -u pf=
  sapccmsr -u pf= [-j2ee]

• cleanipc remove

3. Installing SAPHOSTAGENT

For releases 7.00 and 7.01 (7.0 Enhancement Package 1), you must also install the package SAPHOSTAGENT.SAR in the latest 7.20 version available (in accordance with Note 1031096). On IBM i, you must also update SAP HostAgent to the latest 7.20 version, when you use SAP systems based on NetWeaver 7.10 or 7.11 (7.10 Enhancement Package 1). SYBASE ASE: minimum PL is 115.
Afterwards, you must delete the call of the program SAPOSCOL from all the start profiles. (not Windows)
SAP HostAgent is available on the SAP Service Marketplace (http://service.sap.com/swdc) under following menu path: "Support Packages and Patches" -> "Browse our Download Catalog" -> "SAP Technology Components" -> "SAP HOST AGENT".
For NetWeaver 7.00, 7.01, 7.10 and 7.11 you must not use the 7.20 EXT version of SAP HostAgent.

4. Importing the new kernel

Import the 7.20 kernel from the directory on the host of the central instance and then on all of the application servers with local executables.

4.1 On UNIX

SAPCAR -cvf ../sapexe.tar ./*

The directories jvm or sapjvm* and the file protect.lst only exist in the case of a Java or Dual-Stack implementation.

su - root
chown adm /usr/sap/ /SYS/exe/run/*
exit

Important: On the operating system OS/390, you must use the command "su " instead of "su - root", where must have the UID 0.

rm -rf *

/SAPCAR -xvf /SAPEXE.SAR
/SAPCAR -xvf /SAPEXEDB.SAR

/SAPCAR -xvf /DBATL720O10. SAR

Install the Oracle instant client as described in note 819829.

/SAPCAR -xvf /igsexe. sar

/SAPCAR -xvf /IGSHELPER. SAR

su - root (or su on OS/390)
cd /usr/sap//SYS/exe/run
./saproot.sh
exit

rm -rf *

• For ABAP-only and Dual-Stack systems:

cd /usr/sap///work
sapcpe pf=/usr/sap//SYS/profile/

• For Java-only systems:

NB: The arguments ("pf", "list") are separated by a white space, not by a line break.

• For Java-only and Dual-Stack systems:

If your system is running with the SAPJVM, please copy it on all application server instances (primary application server/central instance, additional application servers/dialog instances):

sapcpe pf=/usr/sap//SYS/profile/ source: list:/sapjvm_.lst

NB: The arguments ("pf", "list", "source") are separated by a white space, not by a new-line character. means the location of the saved SAPJVM, see step 9 above.

4.2 On Windows

The directories jvm or sapjvm* and the file protect.lst only exist in the case of a Java or Dual-Stack implementation

and execute the command

< newkernel>\SAPCAR.EXE -xvf \IGSHELPER.SAR

• For ABAP-only and Dual-Stack systems:
  
  :
  cd \usr\sap\\\work
  sapcpe pf=:\usr\sap\\sys\profile\

• For Java-only systems:

NB: The arguments ("pf", "list") are separated by a white space, not by a line break.

• For Java-only and Dual-Stack systems:

If your system is running with the SAPJVM, copy it on all application server instances (primary application server, additional application servers):

sapcpe pf=:\usr\sap\\sys\profile\ source: list:\sapjvm_.lst

NB: The arguments ("pf", "list", "source") are separated by a white space, not by a line break. means the location of the saved SAPJVM, see step 4 above.

MSCS only:

4.3 On IBM i:

Log on as a QSECOFR-type user and execute the following commands or actions:

Log on as ADM and execute the following commands for importing the new kernel:

Log off and then log on again with ADM. You are now in the new 7.20 environment with the kernel library SAPIND.
(Caution: The name of the kernel library is predefined after you import the 7.20 kernel and can no longer be freely selected.)

If you change a system with a 7.10 or 7.11(7.1 Enhancement Package 1) kernel to the 7.20 kernel and have not yet changed the user concept, use the opportunity and change it now in accordance with Note 1149318 because future upgrade or update paths require the new user concept and they can only use the faster storage management with SHM_SEGS after the changeover (see Note 808607).

5. Additional steps

5.1 CAUTION: Retroactive kernel patches

In some executables (in particular, disp+work), errors were corrected at a later date. You must apply these kernel patches in any case. These are available in SAP Support Portal (http://service.sap.com/swdc).

Read Note 19466 (Downloading SAP kernel patches) or Note 1097751 for IBM i.

5.2 Additional manual changes in Dual-Stack and Java-only systems

This step applies only to releases 7.00 and 7.01.

• Only necessary in case of a Dual-Stack system: you must set the following parameter in the default system profile DEFAULT.PFL:
  system/type = DS

• In all (Dnn, DVEBMGSnn, Jnn, JCnn, etc.) instance profiles, you must set the following parameter:
  FN_JSTART = jcontrol$(FT_EXE)

5.3 Reinstalling SAPCRYPTOLIB

If you use SAPCRYPTOLIB, reinstall it according to SAP Note 510007, step 1.
The installation procedure is also described in the SAP Help Portal, http://help.sap.com, Search Documentation for

• "Installing the SAP Cryptographic Library on the AS ABAP"

• "Installing the SAP Cryptographic Library on the AS Java"

(enter the search string with quotation marks), Product Type "SAP NetWeaver", Release "7.0 EHP2".

5.4 Reinstalling additional programs

If you had installed additional programs such as the RFC Library, you have to install them again. To do this, proceed as follows:

On UNIX:
Execute the following commands as user adm:

On Windows:
Execute the following commands as user ADM:

On IBM i:
On IBM i, you do not have to install any further programs.

5.4.1 Copying executable files from NetWeaver RFC SDK 720.

The 720 versions of the kernel do not contain the program rfcexec (UNIX and IBM i) or rfcexec.exe (Windows) any longer. As this might break some application scenarios, by following the steps described above for UNIX or Windows, the old versions of these programs are kept (for IBM i these steps are ignored). For various reasons, it is highly recommended - and for IBM i it is mandatory - to move to a new version of these files, contained in the NW RFC SDK 720. Please refer to SAP Notes 1581595 and 1025361for detailed instructions and further information.

5.5 Special features for the syslog (ABAP-only and Dual-Stack systems)

Due to the situation described in note 1517379, you have to set the profile parameter
rslg/new_layout = 9.

If a syslog file already exists in the new format because this parameter has not been set from the very beginning, the syslog will still be written in the new format even if the parameter has been set in the meantime. In that case, the existing syslog files have to be deleted.

5.6 Dynamic work processes (NW 7.00 and NW 7.01 systems only)

The 7.20 kernel supports the dynamic increase of the number of work processes at runtime. However, this function is not fully compatible with NW 7.00 and NW 7.01. To prevent errors from occurring, deactivate it by setting the following parameters:
rdisp/wp_no_restricted = 0

rdisp/configurable_wp_no = 0

rdisp/dynamic_wp_check = FALSE

5.7 Configuration of the CCMS central monitoring

Depending on the SAP kernel release of the monitored system you upgraded from and depending on the release of the central monitoring system (CEN), it is necessary to check the following scenarios:

• You upgraded the monitored system:

• You upgraded the central system:
  No reconfiguration is necessary.

SAP note 1667336 contains a detailed description for every case.

6 System Start

Start the SAP system with the new kernel and check the poins below if relevant.

6.1 AS Java or Dual-Stack systems with release 7.00 or 7.01

If the Java instance or even the complete system does not start, check the following points:

• The minimum support packages and patch levels have been installed as described in section "Attention" under "Reason and Prerequisites".

• sapjvm: The directory jvm or sapjvm or the file protect.lst have been saved and restored as described in

6.2 DDIC_TYPELENG_INCONSISTENT short dumps

If you did not handle the DDIC_TYPELENG_INCONSISTENT issue, which is described in chapter "Reason and Prerequisites", section "Attention", while the original kernel was still running, you should now install Note 1610716.

6.3 Load format of ABAP programs

After you start the SAP system with the new kernel, the following message is displayed in the system log: 'Load format of PROGRAM not valid.'
You can ignore this message because the load is automatically regenerated.
It is also possible to regenerate these ABAP loads directly using transaction SGEN. For more information see Note 185745.

6.4 CCMS Monitoring issues

In case of any issues with the CCMS monitoring after the kernel upgrade, check note 1667336, in particular the section "Local monitoring in the upgraded double-stack system".