SAPTechno

Note 1636252 - Installing a 7.20 kernel in SAP Web AS 7.00/7.01/7.10/7.11

Version : 71 / 2014-03-14


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 Java Technology S Offline component (SAPTECHF.SCA)
    • Release 7.00: SAP TECH S 7.00 OFFLINE, SP 14, PL 24
    • Release 7.01: SAP TECH S OFFLINE 7.01, SP 3, PL 13

           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.
           Please note: As described in note 1652660, you have to install the corresponding SAPJTECHS.SCA ("SAP Java Technology Services") as well if you need to install a suitable SAPJTECHF.SCA (cf. also KBA 1738769).

  • 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.07.41 of the MaxDB Client software (SQLBC). For more details refer to SAP Notes 822239 and 1487269.
  • Microsoft SQL Server
    • The SAP Kernel 7.20 is intended for Microsoft SQL Server 2005 and higher. If you are still using Microsoft SQL Server 2000 refer to SAP Note 1341097.
    • For additional information about the usage of the SAP Kernel 7.20 as DCK with Microsoft SQL Server refer to SAP Note 1467086.
  • 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.
    • Oracle dababase server
      The Oracle database server has to be Oracle 11.2.0.2 or higher.
      The latest SAP Bundle Patch needs to be applied on top of the existing patch set release.
    • Oracle database client
      Install the Oracle 11g Instant Client on all application servers and the database server as described in SAP Note 1431794. The Oracle client software can be downloaded from the SAP Service Marketplace at: https://service.sap.com/oracle-download
      Please note: After the installation of the Oracle 11g Instant Client, make sure that the library path for the <sid>adm user (LIBPATH, SHLIB_PATH, LD_LIBRARY_PATH) no longer contains any references to the old Oracle 10g Instant Client location.
    • On IBM Power Linux, Windows IA64 and on Linux IA64 (Intel Itanium), only Oracle 10g is supported. For these three platforms you do not have to make any changes to your database client.


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:
    • Continue to import the Support Packages available for your original SAP release when you use Support Packages to implement corrections of repository objects.
    • In future, when correcting the kernel using kernel patches, use 7.20 (EXT) patches only.

Definition of terms


Here, 'kernel' means all executable programs located in /usr/sap/<SAPSID>/SYS/exe/run (UNIX, IBM i) or \\$(SAPGLOBALHOST)\sapmnt\<SAPSID>\sys\exe\<nuc|uc>\<platform> (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 <name>_<plevel>-<uid>.SAR. Here, <name> is the actual name of the archive, followed by the patch level <plevel> and a unique ID <uid> 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 <name>.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 <newkernel>:

  • Due to the digital signature of the archives (see Note 1598550), you require the latest SAPCAR. Therefore, download the archive SAPCAR_<plevel>-<uid>.EXE from SAP Service Marketplace under the name SAPCAR (UNIX, IBM i) or sapcar.exe (Windows) into your local <newkernel> 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:
    • SAP IGS 7.20 needs kernel 7.20
    • SAP IGS 7.20 EXT needs kernel 7.20 EXT
  • 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: from the PL 513 on it is replaced by the new CommonCryptoLib, please refer to the section 5.3.
  • For Oracle only:
    Download the package DBATL720O10_<plevel>-<uid>.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) ... -> <your platform> -> ORACLE.
    For detailed information see note 12741.
  • For IBM i only:
    • Download the package ILE_<plevel>-<uid>.SAR with at least patch level 109 as ILE.SAR.
    • If you have already changed your SAP system to SAPJVM, you must also download one of the archives SAPJVM4 or SAPJVM5, depending on which one you currently use.
    • If you know that there are already patches on SAP Service Marketplace for the SAPEXE.SAR that is used (for example, DW), download these into the directory. So they are automatically applied with the kernel.
    • For a 7.00/7.01 ASCII based dual stack system you used to download only ASCII Packages. The ASCII package contained the UNICODE part for the SCS Instance, too. The 7.20 Kernel does not contain UNICODE parts in the ASCII Packages. Therefore you have to download the UNICODE SAPEXE package in addition.
  • 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 <sapsid>adm on all instances:

    1. Stop the SAP system. (You do not need to stop the database.)
  • 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)
    2. Stop saposcol.
  • On UNIX (Web AS release 7.0 and 7.01):
    cd /usr/sap/<SAPSID>/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')
    3. Stop sapstartsrv (this is required on UNIX and Windows only):
  • On UNIX:
    kill -2 <pid of sapstartsrv>
  • On Windows:
    Stop and deactivate (Startup Type = Disabled) the services SAP<SID>_<INSTANCE no.>.
    4. If present, unregister all standalone CCMS agents (sapccmsr [-j2ee], sapccm4x). On Unix you can see corresponding processes, on Windows you can see them running as services <agent name>.<instance number>:
  • sapccm4x -u pf=<profile the agent started with>
    sapccmsr -u pf=<profile the agent started with> [-j2ee]
    5. Remove any IPC objects that still exist (this is required on UNIX only):
  • cleanipc <instance no> 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".
Please note that a 7.20 EXT version of SAP HostAgent does not exist. You have to install the 7.20 version of SAP HostAgent even if you install SAP Kernel 7.20 EXT.

4. Importing the new kernel


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

4.1 On UNIX

    1. Log on as user <sapsid>adm and switch to the directory /usr/sap/<SAPSID>/SYS/exe/run.
      2. We recommend saving the old kernel before deploying the new kernel.
    Save the old kernel by creating a tar archive of the complete kernel directory using the following command:

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

    3. Save the following files and directories
      a) the directory jvm or sapjvm* (e.g., sapjvm, sapjvm_4, sapjvm_5) if it exists
      b) the file protect.lst if it exists
        c) the files rfcexec, rfcexec.sec if exists
        d) the icu libraries (libicu*30.<a sh, so> or libicu*34.<a sh, so> if they exist

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

      4. Switch to the user root and change the owner of all files to <SAPSID>adm using the following commands:

               su - root
    chown <sapsid>adm /usr/sap/<SAPSID> /SYS/exe/run/*
    exit
                  Important: On the operating system OS/390, you must use the command "su <user>" instead of "su - root", where <user> must have the UID 0.

      5. Delete all of the files from the kernel directory, including the subdirectories. This ensures that there are no remaining files from the earlier release, which have a different name in Release 7.20 or are in a different place in a subdirectory.

               rm -rf *

      6. Unpack the new kernel with the following commands:

               <newkernel>/SAPCAR -xvf <newkernel>/SAPEXE.SAR
    <newkernel>/SAPCAR -xvf <newkernel>/SAPEXEDB.SAR

    7. Oracle only:

      Unpack the DBATools with the following command:

               <newkernel>/SAPCAR -xvf <newkernel>/DBATL720O10. SAR
                  Install the Oracle instant client as described in note 819829.

        8. If you use IGS, you must unpack the IGS archive using the following
      command:

               <newkernel>/SAPCAR -xvf <newkernel>/igsexe. sar

      9. If there are files or directories that were saved in step 3, restore them into the current directory
      10. To deploy the optional IGSHELPER archive switch to the relevant local directory /usr/sap/<SAPSID>/<INSTANCE> on every instance and execute the command:

               <newkernel>/SAPCAR -xvf <newkernel>/IGSHELPER. SAR

      11. Switch to the user root and run the shell script saproot.sh, which is available in the kernel directory.

               su - root (or su <user with UID 0> on OS/390)
    cd /usr/sap/<SAPSID>/SYS/exe/run
    ./saproot.sh <SAPSID>
    exit

      12. Delete all of the local executables on the individual instances. To do this, switch to the relevant local executable directory /usr/sap/<SAPSID>/<INSTANCE>/exe and execute

               rm -rf *

      13. Since executables from the local executable directories may already be executed for the start before sapcpe runs, start an initial copy of the executables.
        a) All application server instances (primary application server/central instance, additional application servers/dialog instances):
      • For ABAP-only systems:

                        cd /usr/sap/<SAPSID>/<INSTANCE>/work
    sapcpe pf=/usr/sap/<SAPSID>/SYS/profile/<instance profile>

      • For Dual-Stack systems:

                        cd /usr/sap/<SAPSID>/<INSTANCE>/work
    sapcpe pf=/usr/sap/<SAPSID>/SYS/profile/<instance profile>
                        If your system is running with the SAPJVM:
                        sapcpe pf=/usr/sap/<SAPSID>/SYS/profile/<instance profile> source:<sapjvm directory> list:<sapjvm directory>/sapjvm_<version>.lst

      • For Java-only systems:

                        cd /usr/sap/<SAPSID>/<INSTANCE>/work
    sapcpe pf=/usr/sap/<SAPSID>/SYS/profile/<instance profile> list:/usr/sap/<SAPSID>/SYS/exe/run/j2eeinst.lst
                        If your system is running with the SAPJVM:
                        sapcpe pf=/usr/sap/<SAPSID>/SYS/profile/<instance profile> source:<sapjvm directory> list:<sapjvm directory>/sapjvm_<version>.lst

        b) For additional instances such as ASCS, SCS and ERS (exist only in a cluster):

                        cd /usr/sap/<SAPSID>/<INSTANCE>/work
    sapcpe pf=/usr/sap/<SAPSID>/SYS/profile/<instance profile> list:/usr/sap/<SAPSID>/SYS/exe/run/scs.lst
               NB: the arguments ("pf", "list", "source") are separated by a white space, not by a newline character. <sapjvm directory> means the location of the saved SAPJVM, see the step 9 above.
               
               
    4.2 On Windows

      1. Log on as user <sapsid>adm and switch to the global host in your kernel directory, for example: <drive>:\usr\sap\<SAPSID>\sys\exe\<uc|nuc>
      2. Rename the <platform> directory, for example <platform>.save.
        3. Create a new directory <platform> and switch to this directory.
        Unpack the new kernel from the directory <newkernel> of the downloaded archive in the specified sequence.



        Important: Do not call SAPCAR.EXE directly without specifying a path; instead, use the specified directory structure.



        <newkernel>\SAPCAR.EXE -xvf <newkernel>\SAPEXE.SAR
      <newkernel>\SAPCAR.EXE -xvf <newkernel>\SAPEXEDB.SAR
      4. Restore the following directories and files into the newly created directory if they exist in the <platform>.save directory
        a) the directory jvm or sapjvm* (e.g., sapjvm, sapjvm_4)
        b) the file protect.lst
          c) the files rfcexec.exe, rfcexec.sec
          d) the icu libraries icu*30.dll or icu*34.dll if they exist

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

            5.

      Oracle only:

          Unpack the DBATools to the <platform> directory:



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



        Install the Oracle instant client as described in note 998004.
          6. If you use IGS, unpack the new IGS using the following command:



        <newkernel>\SAPCAR.EXE -xvf <newkernel>\igsexe.sar
        7. To deploy the optional IGSHELPER archive, still logged in as <sapsid>adm, switch to the relevant local directory on every instance. For example:
        • primary application server instance:
          <drive>:\usr\sap\<SAPSID>\DVEBMGS<No>
        • additional application server instance:
          <drive>:\usr\sap\<SAPSID>\D<No>

                    and execute the command

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

        8. On all instances in the directories <drive>:\usr\sap\<SAPSID>\<INSTANCE>\exe, delete all of the files (including the subdirectories).
        9. Install the current C runtime library as per note 1553465 by executing vcredist_<platform>.msi in the command box (or by double-clicking this file in the Windows Explorer). Before you start the system for the first time, and if you have a distributed system environment, perform this step manually on each node where a component of the system is configured to run.
        10. Since executables from the local executable directories may already be executed for the start before sapcpe runs, start an initial copy of the executables.
          a) For all application server instances (primary application server/central instance, additional application servers/dialog instances):
        • For ABAP-only systems:

                          < drive>:
      cd \usr\sap\<SAPSID>\<INSTANCE>\work
      sapcpe pf=<drive>:\usr\sap\<SAPSID>\sys\profile\<instance profile>

        • For Dual-Stack systems:

                          < drive>:
      cd \usr\sap\<SAPSID>\<INSTANCE>\work
      sapcpe pf=<drive>:\usr\sap\<SAPSID>\sys\profile\<instance profile>
                          If your system is running with the SAPJVM:
                          sapcpe pf=<drive>:\usr\sap\<SAPSID>\sys\profile\<instance profile> source:<sapjvm directory> list:<sapjvm directory>\sapjvm_<version>.lst

        • For Java-only systems:

                          < drive>:
      cd \usr\sap\<SAPSID>\<INSTANCE>\work
      sapcpe pf=<drive>:\usr\sap\<SAPSID>\sys\profile\<instance profile> list:<drive>:\usr\sap\<SAPSID>\sys\exe\<uc|nuc>\<platform>\j2eeinst.lst
                          If your system is running with the SAPJVM:
                          sapcpe pf=<drive>:\usr\sap\<SAPSID>\sys\profile\<instance profile> source:<sapjvm directory> list:<sapjvm directory>\sapjvm_<version>.lst

          b) For additional instances such as ASCS, SCS and ERS (exist only in a cluster):

                          < drive>:
      cd \usr\sap\<SAPSID>\<INSTANCE>\work
      sapcpe pf=<drive>:\usr\sap\<SAPSID>\sys\profile\<instance profile> list:<drive>:\usr\sap\<SAPSID>\sys\exe\<uc|nuc>\<platform>\scs.lst
                 NB: the arguments ("pf", "list", "source") are separated by a white space, not by a line break. <sapjvm directory> means the location of the saved SAPJVM, see the step 4 above.

        11. Activate (Startup Type = Automatic) and start the Windows Services SAP<SID>_<INSTANCE no.> of primary application server instance and of every additional application server instance to active the new version of sapstartsrv.exe.



      MSCS only:

        1. Start and Stop the clustered (A)SCS instances and the appropriate SAP services using the cluster admin tool or the Powershell.
        2. Also see SAP Note 1596496 on how to update the SAP Resource Type DLL.
          3. You have to follow step 6-10 also for the ERS instances on your cluster nodes.
          Search for REPSRV.lst in all Start Profile of the ERS instances (line Start_Program_00 =)and if it exists replace it with SCS.lst.
        Be sure to check if your Enqueue Replication Service is replicating again after starting the ERS instances
        4. If you have standalone gateway instances installed on cluster nodes, these also need to be updated with the corresponding files from the kernel staging directory \\$(SAPGLOBALHOST)\sapmnt\<SAPSID>\sys\exe\<nuc|uc>\<platform>.
        • On Windows Server 2003 (see Note 657999) the standalone gateway is installed in the <Windows>\SAPCLUSTER directory.
        • On Windows Server 2008 and higher (see Note 1764650 - How to install a standalone gateway in a Microsoft Failover Cluster for Oracle) it is <oracle shared disk>:\sap\<DB-SID>\dbtools.



      4.3 On IBM i:


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

          1. Point the current directory explicitly to the downloaded archives:
        CHGCURDIR '<newkernel>'
          2. Cleanup the library SAP_TOOLS if it exists, otherwise you need not care
        CLRLIB SAP_TOOLS
          3. Extract the required tools from *SAVF file ILE_TOOLS in ILE.SAR by program iletools into SAP_TOOLS (*LIB) - use 'Copy & Paste' to transfer the following command to your session and execute it:
        CALL QP2SHELL PARM('/QOpenSys/usr/bin/csh' '-c' 'SAPCAR -xvf ILE.SAR iletools ILE_TOOLS;iletools')
        4. Since this call to QP2SHELL does not produce any output, check whether library SAP_TOOLS exists now and has some objects in it. If not, check with the WRKSPLF command for spool files with error messages.
          5. Set the authorities of the objects in SAP_TOOLS by these commands:
          If your starting kernel is already running with the 'newuserconcept' set:
            ADDENVVAR ENVVAR(CLASSICUSERCONCEPT) VALUE('N')
            ADDLIBLE  SAP_TOOLS
            FIXSAPOWN *NONE SAP_TOOLS
          If your starting kernel is still running with the 'classicuserconcept' set:
            ADDENVVAR ENVVAR(CLASSICUSERCONCEPT) VALUE('Y')
            ADDLIBLE  SAP_TOOLS
            FIXSAPOWN *NONE SAP_TOOLS



      note:

        If you are not sure which userconcept your current system is using please check for the file /sapmnt/<SID>/profile/.newuserconcept The existence of this file says that the newuserconcept is active. You can also check who is the owner/primary-group of the executable files underneath /sapmnt/<SID>/exe. <SID>ADM/R3GROUP is an indicator for the newuserconcept, while R3OWNER/<SID>GROUP is an indicator for the classicuserconcept.
        6. For SAP systems with a release lower than 7.10, check the contents of the file /usr/sap/sapservices. If sapstartsrv is started under the name sapstartsrvu (/usr/sap/<sapsid>/SYS/exe/run/sapstartsrvu ...), you must change the entry so that sapstartsrv is started from the subdirectory .../uc of the previous directory in future (/usr/sap/<sapsid>/SYS/exe/run/uc/sapstartsrv ...)


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

        1. ADDLIBLE SAP_TOOLS
          2. Check whether the environment variable CLASSICUSERCONCEPT is set by the login process (use WRKENVVAR); if it is not set, set it in the following way:
          If your starting kernel is already running with the 'newuserconcept' set:
            ADDENVVAR ENVVAR(CLASSICUSERCONCEPT) VALUE('N')
          If your starting kernel is still running with the 'classicuserconcept' set:
          ADDENVVAR ENVVAR(CLASSICUSERCONCEPT) VALUE('Y')
        3. Check that all instance- and start-profiles of the system contain the parameter DIR_CT_RUN. If missing in a 7.00/7.01 environment set it to: DIR_CT_RUN = $(DIR_EXE_ROOT)/run (for Windows instances: DIR_CT_RUN = $(DIR_EXE_ROOT)\run ); For 7.10/7.11 set it to: DIR_CT_RUN = $(DIR_EXE_ROOT)/$(OS_UNICODE)/as400_pase_64 (for Windows: DIR_CT_RUN = $(DIR_EXE_ROOT)\$(OS_UNICODE)\ntamd64 )
        4. Please remove any DLTOLDPKG call from all start profiles, because with the 7.20 Kernel DLTOLDPKG will be started by STARTSAP automatically. For further information please refer to note 1657890.
          5. Apply all archives in <newkernel> simultaneously to the system:
        APYSIDKRN SID(<SAPSID>) ARCHIVES('<newkernel>/*') SAVSAR(*NONE) MODE(*FULLY) CHGENV(*NO) UPDAPAR(*NO)
          6. Remove the SQL packages left over from using the old kernel:
        DLTR3PKG SID(<SAPSID>)


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

      If not done yet, it is highly recommended to switch to the SAPCPE process for kernel maintenance now (see SAP note 1632754 for details) in order to minimize the system downtime for kernel maintenance.

      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.The faster storage management with SHM_SEGS can only be used 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

      Starting with the patch level 513, also in SP stack kernels 720 PL >=600, a new CommonCryptoLib is delivered with the SAP Kernel. This library is fully compatible to the SAPCRYPTOLIB and replaces it, so the reinstallation of SAPCRYPTOLIB is no longer necessary. See the Note 1848999 for more detail.


      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 <sapsid>adm:

        1. cd /usr/sap/<SAPSID>/SYS/exe/run
        2. <newkernel>/SAPCAR -xvf <newkernel>/<additional package>.SAR


      On Windows:
      Execute the following commands as user <SAPSID>ADM:

        1. CD \USR\SAP\<SAPSID>\SYS\EXE\RUN
        2. <newkernel>\SAPCAR.EXE -xvf <newkernel>\<additional package>.SAR


      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.


      Due to security reasons the program rfcexec (UNIX and IBM i) or rfcexec.exe (Windows) is no longer shipped together with SAP kernel 720. For various reasons, 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.

      Remark: The new version of rfcexec might break some of your application scenarios. Therefore please use the old version, which was saved in the previous preparation step (Unix, step 3 c, Windows 4 c).

      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
                 rdisp/wp_max_no = Sum of
      ( rdisp/wp_no_dia + rdisp/wp_no_btc + rdisp/wp_no_vb + rdisp/wp_no_vb2 + rdisp/wp_no_spo +rdisp/wp_no_enq )
                 Mind that rdisp/wp_max_no has the default value DEFAULT, which will add two unwanted dynamic processes if not set to the number of configured classical wp types.

      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:
        • CEN system is based on SAP_BASIS 7.0 (7.00) and lower:
          You have to disable the integrated CCMS agents in sapstartsrv of the upgraded system and use standalone CCMS agents instead. sapccm4x for the central monitoring of pure ABAP and Dual-Stack systems, sapccmsr -j2ee for the central monitoring of pure Java systems. Please proceed as outlined in note 1368389, section "Solution".
        • CEN system is based on SAP_BASIS 7.0 EhP 1 (7.01):
          The registration of the integrated CCMS agents from the central system needs to be repeated. Please follow the instructions given in SAP Help (http://help.sap.com/saphelp_nwpi71/helpdata/EN/44/893e933dc912d3e10000000a422035/content.htm).
      • You upgraded the central system:
        No reconfiguration is necessary.


      SAP note 1667336 contains a detailed description for every case.

      5.8. Check your environment on Linux and UNIX platforms

      On all UNIX/Linux platforms with deactivated interactive user logon for <sidadm> user - check Note 1825259.

      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
        • Section 4.1, "On Unix", steps 3 and 9
        • Section 4.2, "On Windows", step 4

      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".



      Header Data

      Released On 14.03.2014 08:51:34
      Release Status Released for Customer
      Component BC-CST Client/Server Technology
      Priority Recommendations / Additional Info
      Category Upgrade information

      Validity

      Software Component
      From Rel.
      To Rel.
      And Subsequent
      KRNL32NUC
      7.20
      7.20
       
      7.20EXT
      7.20EXT
       
      KRNL32UC
      7.20
      7.20
       
      7.20EXT
      7.20EXT
       
      KRNL64NUC
      7.20
      7.20
       
      7.20EXT
      7.20EXT
       
      KRNL64UC
      7.20
      7.20
       
      7.20EXT
      7.20EXT
       
      SAP_BASIS
      700
      701
       
      710
      711
       
      KERNEL
      7.20
      7.20
       

      References

      This document refers to:

      SAP Knowledge Base Articles
      1738769   java.lang.NoClassDefFoundError: com/sap/tc/webdynpro/services/sal/core/AbstractManager
      SAP Notes
      1825259   UNIX sapstartsrv: the system does not start with 720 kernel
      1785100   Internet Explorer 10 Release Notes
      1781218   Spontaneous code page conversion error after DB recoonect
      1780629   AIX: Minimal OS Requirements for SAP Kernel
      1760861   Collecting DSR data in double stack with SAP_BASIS 7.00
      1744209   SAP Kernel 720 and 721: Versions and Kernel Patch Levels
      1737262   Message server: crash during URL handler load
      1728283   SAP Kernel 721: General Information
      1722035   Islamic calendars: Initial dates not handled correctly
      1716826   Usage of the downward compatible kernel 721 (EXT)
      1713986   Installation of kernel 721 (EXT)
      1709911   Maintenance tools on request
      1707141   Diagnostics Agent - How to upgrade SAP Kernel
      1707012   IBM i: Prepare Installation Kits for Usage with DCK Kernel
      1702912   IBM i: collectSystemInfo: sid DLT ... does not match sid DLT
      1687173   IBM i: Collection of notes about the 7.20 kernel
      1669684   SAP on Oracle Solaris 11
      1667336   CCMS Monitoring with Kernel 7.20 (DCK)
      1657890   IBM i: STARTSAP calling DLTOLDPKG via instance profile
      1652660   UnsatisfiedLinkError or InvocationTargetException in JMonAPI
      1633731   Usage of the 7.20 Downward-Compatible Kernel
      1629598   SAP Kernel 720 will replace older kernel versions
      1610716   Correcting runtime objects with incorrect alignment
      1598550   SAPCAR: Signed archive
      1597627   SAP HANA connection
      1581595   rfcexec or startrfc fail after upgrade
      1563102   Linux Requirements for 7.20 EXT and higher kernel
      1553465   Prerequisites for 720/721 EXT and higher kernels on Windows
      1553301   7.20 EXT Kernel - Usage
      1553300   7.20 EXT Kernel - Extended Kernel Maintenance
      1517379   Which system log format does the 720 kernel write?
      1487269   Installation of 720 kernel on SAP MaxDB-based SAP systems
      1467086   SAP 7.20 Kernel (DCK) on MS SQL Server
      1454536   Deadlock on table REPOSRC when importing into running system
      1431794   Oracle 11.2.0: Instant Client
      1423600   iSeries: Note in work process trace: "locale is missing"
      1341097   MSSQL: 720 DCK, 7.0* on SQL 2000, dbmssslib_oledb.dll
      1163719   CCMS: Incorrect version of the JMON library
      1149318   User concept conversion using the tool CONVUSRCPT
      1119735   CCMS agents: Upgrade of monitored systems from 7.0 to 7.1
      1097751   iSeries: Info & recommendations for kernel libraries
      1031096   Installing Package SAPHOSTAGENT
      1028690   True Type Fonts delivered with IGS
      998004   Update the Oracle Instant Client on Windows
      808607   iSeries: Memory management in a system based on PASE
      684106   Microsoft runtime DLLs
      510007   Setting up SSL on Web Application Server ABAP
      447519   Kernel patches for code pages, languages and locales
      397175   SAP Cryptographic Software - Export control
      185745   Mass generation due to incorrect load format
      19466   Downloading SAP kernel patches
      SAP Notes (unidirectional)
      1848999   Central Note for CommonCryptoLib 8 (replacing SAPCRYPTOLIB)

      This document is referenced by:

      SAP Notes (27)
      1643916   igshelper.sar not updated when upgrading from 720 to 720_EXT
      1652660   UnsatisfiedLinkError or InvocationTargetException in JMonAPI
      1780629   AIX: Minimal OS Requirements for SAP Kernel
      1781218   Spontaneous code page conversion error after DB recoonect
      1785100   Internet Explorer 10 Release Notes
      1669684   SAP on Oracle Solaris 11
      1553300   7.20 EXT Kernel - Extended Kernel Maintenance
      1553301   7.20 EXT Kernel - Usage
      1687173   IBM i: Collection of notes about the 7.20 kernel
      1972803   SAP on AIX: Recommendations
      1728283   SAP Kernel 721: General Information
      1825259   UNIX sapstartsrv: the system does not start with 720 kernel
      1737262   Message server: crash during URL handler load
      1744209   SAP Kernel 720 and 721: Versions and Kernel Patch Levels
      1667336   CCMS Monitoring with Kernel 7.20 (DCK)
      1707012   IBM i: Prepare Installation Kits for Usage with DCK Kernel
      1707141   Diagnostics Agent - How to upgrade SAP Kernel
      1702912   IBM i: collectSystemInfo: sid DLT ... does not match sid DLT
      1713986   Installation of kernel 721 (EXT)
      1716826   Usage of the downward compatible kernel 721 (EXT)
      1722035   Islamic calendars: Initial dates not handled correctly
      1454536   Deadlock on table REPOSRC when importing into running system
      447519   Kernel patches for code pages, languages and locales
      1629598   SAP Kernel 720 will replace older kernel versions
      1477428   Downport (SAP_BASIS 7.01): Security Session Management
      1633731   Usage of the 7.20 Downward-Compatible Kernel
      1760861   Collecting DSR data in double stack with SAP_BASIS 7.00