Note 664679 - Installing 6.40 kernel in SAP WEB AS 6.10/6.20

Version / Date 21 / 2006-03-08
Priority Recommendations/additional info
Category Upgrade information
Primary Component BC-CST Client/Server Technology
Secondary Components


There is an error in the SAP kernel of Release 6.10 or 6.20 that is solved with the 6.40 Kernel.

Other terms

Downward-compatible kernel DCK 640

Reason and Prerequisites
  • This note applies to all systems with Web AS Release 6.10 or 6.20 (SAP_BASIS component).
  • As of April 2004, the 6.40 kernel is being sent to customers.
  • You may need to perform an operating system upgrade before the kernel upgrade.
  • Caution: The 6.40 kernel is not yet available for all products on all platforms. You can find the up to date information on the combinations of SAP products, Operating System version and database versions that is allowed under:
    Use this information and the notes mentioned below to check whether the 6.40 kernel is released for your SAP product, DB and operating system platform.
  • You may need to perform a DB upgrade before the kernel upgrade. Use the following notes to check whether the 6.40 kernel still supports your current database release:
    • Note 407314 (Oracle)
    • Note 407317 (INFORMIX)
    • Note 727683 (MaxDB)
    • Note 407322 (DB2/UDB)
    • Note 407325 (DB2/390)
    • Note 407328 (MS SQL Server)
    • Note 410783 (DB2/400)


The SAP kernel of Release 6.10 or 6.20 contains an error that is corrected with the 6.40 kernel. You can therefore correct errors in the 6.10 or 6.20 kernel by replacing the kernel without implementing an SAP upgrade.

Caution: The kernels must be replaced on ALL application servers of the affected system.

Special feature on Windows:

    1. On Windows, the local kernel executables for the application server are usually updated automatically with the SAP copy program sapcpe.
    As of SAP Release 6.20, the executables of the central instance can be updated with sapcpe.
    Check whether sapcpe is configured for the central instance and all application servers. To do this, check whether there is an sapcpe entry in each start profile in the central instance and application server.
    Carry out the following steps, depending on whether or not sapcpe is configured:
    sapcpe is configured:
      a) Execute the RSPARAM report in your SAP system for the central instance and all application servers.
      b) Check which directory the DIR_CT_RUN parameter is referring to.
      c) Unpack the kernel executables into the directory specified in DIR_CT_RUN.

                       sapcpe is not configured:

      a) Execute the RSPARAM report in your SAP system for the central instance and all application servers.
      b) Check which directory the DIR_EXECUTABLE parameter is referring to. This is generally the <drive>:\usr\sap\<SAPSID>\sys\exe\run directory.
      c) Unpack the kernel executables into the directory specified in DIR_EXECUTABLE.
    2. Since SAP Release 6.20, there is a new kernel directory structure on Windows (64-bit), depending on whether you are using Unicode, non-Unicode or other platforms.

    Previous kernel directory structure on your global host: <drive>:/usr/sap\<SAPSID>\sys\exe\run

    New directory structure:
    Replace <characterset>  with "nuc" (non-Unicode) or "uc" (Unicode).
    Replace <platform> with NTI386, NTAMD64 or NTIA64
    Example: <drive>:\usr\sap\<SAPSID>\sys\exe\nuc\NTIA64 ************************************************************************

SAP's general recommendation to remain as up-to-date as possible with the upgrades is not affected by this downward-compatible kernel, since no application errors are corrected.

You can upgrade to the 6.40 kernel without installing a new GUI version on the front-end servers. The 6.10 or 6.20 GUI also works with the 6.40 kernel.

Definition of terms

'Kernels' here refers to all executable programs in
/usr/sap/<SAPSID>/SYS/exe/run (UNIX) or
\\$(SAPGLOBALHOST)\sapmnt\<SAPSID>\sys\exe\run (Windows), not just the
disp+work executable.

After you have installed a 6.40 kernel, you must:

  • Continue to import the Support Packages available for your installed SAP release when you use Support Packages to implement corrections to repository objects.
  • In future, only use 6.40 patches when you use kernel patches to implement corrections to the kernel.


Download the latest 6.40 stack kernel from the SAP Service Marketplace. The stack kernel consists of the database-independent SAPEXE.SAR and the database-dependent SAPEXEDB.SAR archive. You can also order the 6.40 downwardly compatible kernel CD from the SAP online shop. For further information about the download, see Note 19466.

Install the 6.40 kernel from this kernel CD by carrying out the following actions as the user <sapsid>adm (or <SID>OFR on OS/400) on the central instance computer and then on all application servers with local executables:

Preliminary tasks:
    1. Stop the SAP System (there is no need to stop the database).
    2. Stop saposcol.
    In Windows:
       Stop the SAP<SID>_<system no.> and SAPOsCol services
    In UNIX:    cd /usr/sap/<SAPSID>/SYS/exe/run
       ./saposcol -k
       rm saposcolIn OS/400:    CALL PGM(SAPOSCOL) PARM('-k')
    3. Terminate the SAProuter.
    4. Delete the statistics file (/usr/sap/<SID>/<DVEBMGS00>/data/stat).
    5. Insert the kernel CD and install it.
Importing the new kernel from CD/DVD:


    1. Switch to the /usr/sap/<SAPSID>/SYS/exe/run directory.
    2. Save the old kernel using the following commands:
      mkdir oldkernel
      cp -p * oldkernel
      su - root
      chown <sapsid>adm /usr/sap/<SAPSID>/SYS/exe/run/*

The oldkernel directory will be deleted during the next regular upgrade.
Caution: With the OS/390 operating system, you must use the "su <user>" command instead of "su - root", where <user> must have the UID 0.

    3. Unpack the new kernel using the following commands:   /<sapcd>/UNIX/< OS>/SAPCAR -xvf /<sapcd>/UNIX/< OS>/SAPEXE.SAR
      /<sapcd>/UNIX/< OS>/SAPCAR -xvf /<sapcd>/UNIX/< OS>/SAPEXEDB.SAR
    4. Logon as user <sapsid>adm and execute the following commands:

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

    • In DB2 Universal Database for UNIX, Windows:

  su root (not su - root)   cd /usr/sap/<SAPSID>/SYS/exe/run
  ./ <SAPSID>

    5. In ORACLE:
    CAUTION: The DBATOOLS only support Oracle 9.2.0. If required, upgrade your database to 9.2.0.
    You can download the latest version of dbatools.sar from the SAP Service Marketplace (DBATL640092_xx-xxxxxxx.SAR).
In Windows:
    1. On the global host, Switch to your kernel directory, for example: <drive>usr\<SAPSID>\sys\exe\run
    2. Unpack the new kernel from the kernel directory of the DVD in the specified sequence.
    IMPORTANT: Do not call SAPCAR.EXE directly without a path specification, instead use the specified directory structure for the kernel DVD.
    3. In Oracle:
    CAUTION: The DBATOOLS only support Oracle 9.2.0. If required, upgrade your database to 9.2.0.
    You can download the latest version of dbatools.sar from the SAP Service Marketplace.
    4. If you want to keep the old kernel executables, you must use the copy function and not the rename function (see SAP note 142100, point 18).
    5. This step is only valid for MSCS:
    Update the files on all cluster nodes in the Windows\SAPCLUSTER directory with the corresponding files in the central kernel directory, for example in <dir>:/usr/sap/<SAPSID>/sys/exe/run.
    6. Install the DLLs retrieved as an attachment in Note 684106.

In OS/400:

Before you can use the 6.40 kernel, the following Support Package must be installed in your SAP system:

  • SAP_BASIS 610: SAPKB61031
  • SAP_BASIS 620: SAPKB62041

To avoid the problems described in note 787328, the following Support Packages are also recommended:

  • SAP_BASIS 610: SAPKB61042
  • SAP_BASIS 620: SAPKB62047

You must have installed product option 33 - Portable App Solutions Environment (PASE) of the operating system.

If you want to use double byte language, such as Chinese, Japanese or Korean in your SAP system, you must install these explicitly on your IBM eServier. For detailed information about this, see Note 807912.

Logon as QSECOFR and load the latest tools from CD into the LODKRN library.
Logon as <SID>OFR.

Use the new tools to import the 6.40 kernel.

             KRNLIB(<kernel library>)

In the MNTPNT parameter, replace <VOLID> with the name of the CD.

Remove the old kernel
Change the library list (EDTLIBL) and replace the old kernel library with the new 6.40 kernel library.

Activate the 6.40 kernel

    APYR3KRN SID(<SID>) KRNLIB(<new kernel library>)
For a detailed description of the APYR3KRN command, see Note 751132.

Delete all SQL packages.


The following profile parameters must be added.

DEFAULT profile:
rdisp/sna_gateway=<iSeries Name>  (see SAPDBHOST)

Instance profile:

Start profile:
_CO = $(DIR_EXECUTABLE)/rslgcoll
Start_Program_04 = local $(_CO) -F pf=$(DIR_PROFILE)/<Instance profile>
_SE = $(DIR_EXECUTABLE)/rslgsend
Start_Program_05 = local $(_SE) -F pf=$(DIR_PROFILE)/<Instance profile>

Note 760162 describes how to exchange the executables of an SAP J2EE Engine.

For additional information about the 6.40 kernel on iSeries, see SAP Note 766913.


Further errors have been subsequently corrected in individual executables (in particular disp+work). These kernel patches MUST be imported. They are available from the SAP Service Marketplace Software Center (
See Note 19466 (downloading kernel patch from sapservX) or 751131 for OS/400.

Additional steps

    1. In DB2 Universal Database for UNIX, Windows:

    Proceed as follows to install the 6.40 SAP DB2admin tool:

              In UNIX:

    • Log onto the database server as the user <sapsid>adm.
    • Change to the root user with 'su root' (not su - root).
    • Change to the DBTOOLS directory on the CD.
    • Install the 6.40 tools with the following command:
        ./sddb6ins -i

              In Windows:

    • Log onto the database server as the user <sapsid>adm.
    • Change to the DBTOOLS directory on the CD:
        .\sddb6ins -i -db2dbnamepwd <password of the db2<dbsid> user>

      You will find detailed information about the admin tools in the SAP documentation "Database Administration Guide: SAP on IBM DB2 Universal Database for UNIX and Windows" and in Note 455506.
    2. In Windows for MS SQL server:

    You must delete the stored procedures that are automatically generated. To do this, execute the following SQL commands:
    If your installation is not a schema installation (check in the R/3 system: System->Status specifies dbo as the owner):        use <SAPSID>
          sap_droprocIf your installation is a schema installation (System->Status specifies <sid> as the owner (lower-case SAP system name)):        use <SAPSID>
           setuser '<sid>'
    3. In DB2 for OS/390 and z/OS:

    For the operating systems OS/390 and z/OS, see also  Note 318198 and for other operating systems for DB2/390z/OS, see Note 100189.
    4. In Oracle for UNIX:

    Also unpack the Oracle 9.2 client because the 640 kernel is built with Oracle 9.2. The Oracle 9.2 client is available on the kernel CD as OCL920<64/32>.SAR or on the SAP Service Marketplace (
    For details about installing the Oracle 9.2 client, see Note 539922.
    5. Reinstalling additional programs

    If you had installed additional programs such as the RFC library, CPIC library and so on in the executable directory, you must install these again from the presentation CD. To do this, proceed as follows:

              In UNIX:
Execute the following commands as user <sapsid>adm:
1. cd /usr/sap/<SAPSID>/SYS/exe/run
2. /<CD-Dir>/SDK/UNIX/< OS>/SAPCAR -xvf
   / /<CD-Dir>/SDK/UNIX/< OS>/<additional package>.SAR

              In Windows:
Execute the following commands as the user <SAPSID>ADM:
2. <CD drive>\SDK\NT\I386\SAPCAR.EXE -xvf
   <CD drive>\SDK\NT\I386\<additional package>.SAR

              In OS/400:
The additional programs are already in the kernel library, and therefore do not have to be installed again.

    6. Start the SAP System.
    7. Start the SAProuter.
    8. In Windows: Restart the SAP services.
    9. After you import the kernel, you will find the following message in the system log:
    'Load format of PROGRAM invalid.'
    You can ignore this message, since the load format is automatically regenerated.
    You can also recreate these ABAP load formats directly. For further information about this, see Notes 170039, 162991 and 155580.

Resetting to the old kernel

If the system behavior does not meet your expectations after you use the downward-compatible kernel, you can reactivate the old kernel.

    1. Stop the SAP System (see above).
    2. Copy back the old kernel.
    3. In OS/400:
    • Delete all SQL packages as described in Note 63037.
    • Remove the 6.40 kernel (RMVR3KRN).
    • Adjust your library list (EDTLIBL).
    • Activate the old kernel (APYR3KRN).
    • Undo the profile changes.
    4. Start the SAP System.

Affected Releases
Software Component Release From Release To Release And subsequent

Related Notes
1088922Improvement: Starting RFC servers
1084953Correct code page when receiving MDMP tables using RFC
1084757RFC Patch Collection 33 2007
1058988640_EX2 Kernels
982686Occasional WP crash with SNC-protected RFCs (CUA,ALE)
947809ZV-Meldeprogramm 2006: Datenträger Sortierung für VBL
945736Farsi (Persian) calendar support
931129Deactivating the command field during RFC debugging
929512Sporadic errors with SSO (MYSAPSSO2) from J2EE to ABAP
914486Installing J2EE Add-In for WAS 6.20