Information of news
  • Views: 0
  • Author: adm
  • Date: 7-03-2013, 05:31
7-03-2013, 05:31

Note 1713986 - Installation of kernel 721 (EXT)

Category: SAP Notes

Symptom

You want to use the kernel 7.21 or 7.21 EXT as a downward-compatible kernel in one of the following NetWeaver releases and products based on these NetWeaver releases:
SAP NetWeaver 7.0 ("7.00")
SAP EhP1 for SAP NetWeaver 7.0 ("7.01")
SAP EhP2 for SAP NetWeaver 7.0 ("7.02")
SAP EhP3 for SAP NetWeaver 7.0 ("7.03")
SAP NetWeaver 7.1 ("7.10")
SAP EhP1 for SAP NetWeaver 7.1 ("7.11")
SAP NetWeaver 7.2 ("7.20")
SAP NetWeaver 7.3 ("7.30")
SAP EhP1 forNetWeaver 7.3 ("7.31")

or SAP products based on these, such as:
SAP ECC 6.0
SAP CRM 5.0, 2007, 7.0
SAP SRM 5.0, 6.0, 7.0
SAP NetWeaver PI 7.1
SAP NetWeaver Mobile 7.1
SAP NetWeaver Composition Environment (CE) 7.1
SAP EhP1 for NW CE 7.1
SAP NetWeaver CE 7.2

Other terms

kernel, dck, akk, 721, 721 EXT, 721_EXT, downward compatible kernel, installation

Reason and Prerequisites


There are two use cases for the downward compatible kernel 721 (EXT):

    1. Kernel 721 (EXT) may be used as alternative to the downward compatible kernel 720 (EXT) for systems with NetWeaver Releases 7.00/7.01 (7.0 EhP 1)/7.1/7.11 (7.1 EhP 1) that still run with the originally delivered kernel 700, 701, 710 or 711.
    2. Kernel 721 (EXT) as downward-compatible kernel to the kernel 720 (EXT) can be installed on:
      a) Systems originally delivered with the kernel 720 (EXT)

OR

      b) Systems listed in the point 1 above where the original kernel 700/701/710/711 was earlier upgraded to the 720 (EXT) version.


Please make sure that all platform-, database-specific and other system requirements for the kernel 721 (EXT) are met. Please refer to the note 1716826, the section "Reason and Prerequisites".

Solution

The kernel 721 (EXT) is downward-compatible to the kernels for SAP NetWeaver releases 7.00 to 7.31 listed in the section "Symptom". Therefore, you can eliminate errors and make use of the new features by replacing the kernel with the kernel 721 so that you do not have to perform an SAP upgrade.

Important:

  • You must exchange the kernels on all servers of the affected system.
  • You can upgrade to the kernel 721 without having to install a new GUI version on the front-end PCs.
  • The general SAP recommendation to keep up to date with the upgrades/updates remains unaffected by this downward-compatible kernel because it does not correct application errors. After you have installed the kernel 721 (EXT), you must:
    • continue to import the Support Packages available for your installed SAP release.
    • In future, when correcting the kernel, use 721 (EXT) kernel patches only.


Definition of terms

Here, 'kernel' means all executable programs,libraries and other files 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 installation archives of the kernel 721 (EXT) can be regularly downloaded from the SAP Service Marketplace under "Additional Components -> SAP Kernel".
Further a differentiation is made between the character Unicode or non-Unicode kernels. At this level you find the list of platforms and, for each platform, subfolders for database-independent archives and (for each database supported in the platform) database-dependent archives.
The name of each 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).

Besides the kernel itself, there are also additional components required to install and run the kernel. These components are not available in the 721 version, the 720 (EXT) version should be used instead.
Please download and copy the following archives into the same directory <newkernel>:

        a)
SAPCAR
        : Due to the digital signature of the archives (see Note 1598550), you require the latest SAPCAR, currently it is the release
720
      . 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. The SAPCAR 720 can be found here: http://service.sap.com/patches -> "Browse Our Download Catalog" -> Additional Components -> SAPCAR -> SAPCAR 7.20 -> <your platform>.
        b) 721 stack kernel: The stack kernel consists of the database-independent archive
SAPEXE.SAR
        and the database-dependent archive
SAPEXEDB.SAR
      . If you use different platforms (for example, Windows Application Server with database DB2 on IBM i), you can immediately download the kernel for all of the required platforms.
        c) If you use the Internet Graphics Server (IGS): the kernel 721 (EXT) runs with the 720 (EXT) version of the IGS. So you will have to download the archives
igsexe.sar
        and, optionally,
igshelper.sar
      .
    • The archive igshelper.sar contains an optional component (see SAP note 1028690) that was introduced 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 the kernel 721 or 721 EXT. The igshelper.sar is operating-system independent and can be used with all 7.* SAP IGS releases. 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".
        d) If you use
SAPCRYPTOLIB
      , you must also download the corresponding 720 or 720_EXT version in accordance with SAP Notes 397175 and 1375378.
      e) For the Oracle database:
    • you also need the archive DBATOOLS.SAR in the 720 version: http://service.sap.com/patches -> "Browse Our Download Catalog" -> Additional Components -> SAP Kernel -> SAP KERNEL 64-BIT (UNICODE) -> SAP KERNEL 7.20 (EXT) 64-BIT (UNICODE) -> <your platform> -> ORACLE. For more detailed information see the note 12741.
    • 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.
    • For all other operating systems download the Oracle 11g Instant Client on all application servers and the database server as described in SAP Notes 819829 (UNIX) or 998004 (Windows). 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.
      f) For IBM i only:
    • Download the package ILE (ILE_<plevel>-<uid>.SAR) with the highest available patch level and rename it to ILE.SAR.
    • If you have already changed your SAP system to SAPJVM, you must also download one of the archives SAPJVM4, SAPJVM5 or SAPJVM6 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 kernel 721 (EXT) does not contain UNICODE parts in the ASCII Packages. Therefore you have to download the UNICODE SAPEXE package in addition.
      g) There is no new SAPHOSTAGENT package for the kernel 721 (EXT), the SAP Host Agent release 720 is used. So, for systems with the 720 (EXT) kernel (7.02, 7.03, 7.20, 7.30, 7.31) this component is already installed. Please note:
    • If using SYBASE ASE, the SAPHOSTAGENT 720 should have at least PL 115.

For systems with kernel releases <720 please check the below requirements:

    • If upgrading from kernel releases 700/701 you must install the package SAPHOSTAGENT.SAR in the 720 version in accordance with Note 1031096.
    • On IBM i platform the SAP HostAgent 720 version should be installed over kernel releases 700, 701, 710 and 711.
    • For NetWeaver 7.00, 7.01, 7.10 and 7.11 you must not use the 720 EXT version of SAP Host Agent even if using the 721 EXT kernel, use the 720 (non-EXT) version of the Agent instead.

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

After the installation you must delete the call of the program SAPOSCOL from all the start profiles (not Windows).

      h) 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. Importing the kernel 721 (EXT) on top of the kernel 720 (EXT)

If installing the kernel 721 (EXT) on top of the kernel 720 (EXT), either originally delivered or previously installed as DCK (i.e. in systems listed in the section "Reason and Prerequisites", 2A and B), the procedure is similar to an installation of a regular kernel patch:

  • On UNIX and Windows:
    • We strongly recommend to back up your old kernel directory before the kernel exchange.
    • Stop the SAP system and copy downloaded kernel archives into your kernel directory as per note 19466.
  • On IBM i:
    • Log on as <SAPSID>ADM and execute the following commands for importing the new kernel:
    • Apply all archives in <newkernel> simultaneously to the system:
      APYSIDKRN SID(<SAPSID>) ARCHIVES('<newkernel>/*') MODE(*FULLY) CHGENV(*NO) UPDAPAR(*NO)
    • Remove the SQL packages left over from using the old kernel:
      DLTR3PKG SID(<SAPSID>)
  • Skip the sections 3 and 4 and check the relevant points in the sections 5 and 6.


3. Preparations for the installation of kernel 721 (EXT) on top of 700/701/710/711 kernel versions

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 (NW release 7.0 and 7.01):
    cd /usr/sap/<SAPSID>/SYS/exe/run
    ./saposcol -k
  • On UNIX (NW release 7.10 and higher):
    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



4. Installation of the kernel 721 (EXT) on top of 700/701/710/711 kernel versions

Import the kernel 721 (EXT) from the directory <newkernel> onto 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) For Java or Dual-Stack systems: the directory jvm or sapjvm* (e.g. sapjvm, sapjvm_4, sapjvm_5, sapjvm_6).
      b) the file protect.lst if it exists (exists only in Java or Dual-Stack systems)
      c) the files rfcexec, rfcexec.sec if they exist
      d) the icu libraries (libicu*30.<a sh, so> or libicu*34.<a sh, so> if they exist
    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.21 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>/DBATOOLS.SAR

Also unpack the Oracle instant client to the directory as explained in the 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) For ABAP-only and Dual-stack systems:

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

      b) For Java-only systems:
    • For all application server instances (primary application server/central instance, additional application server/dialog instance):

cd /usr/sap/<SAPSID>/<INSTANCE>/work

sapcpe pf=/usr/sap/<SAPSID>/SYS/profile/<instance profile> list:/usr/sap/<SAPSID>/SYS/exe/run/j2eeinst.lst

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

      c) For Java 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 server/dialog instance):

sapcpe pf=/usr/sap/<SAPSID>/SYS/profile/<instance profile> source:<sapjvm directory> list:<sapjvm directory>/sapjvm_<version>.lst

    • For SCS and ERS (exist only in cluster) instances:

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) For Java or Dual-Stack systems: the directory jvm or sapjvm* (e.g. sapjvm, sapjvm_4, sapjvm_5, sapjvm_6).
      b) the file protect.lst (Java and Dual-Stack installations only)
      c) the files rfcexec.exe, rfcexec.sec
      d) icu*30.dll or icu*34.dll if they exist
      5. Oracle only:

      Unpack the DBATools to the <platform> directory:


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


    Also unpack the Oracle instant client to the <platform> directory as explained in the 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\<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 ABAP and Dual-stack systems:

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

      b) For Java-only systems:
    • For all application server instances (primary application server/central instance, additional application server/dialog instance):

< 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

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

      c) For Java and Dual-Stack systems:
    • If your system is running with the SAPJVM, copy it on all application server instances (primary application server, additional application server):

sapcpe pf=<drive>:\usr\sap\<SAPSID>\sys\profile\<instance profile> source:<sapjvm directory> list:<sapjvm directory>\sapjvm_<version>.lst

    • For SCS and ERS (exist only in cluster) instances:

< 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 4a 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.
      2. 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 =). 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.
    3. Also see SAP Note 1596496 on how to update the SAP Resource Type DLL.
    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:
    • 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:

    1. Log on as a QSECOFR-type user and execute the following commands or actions:
      2. Point the current directory explicitly to the downloaded archives:

    CHGCURDIR '<newkernel>'
      3. Cleanup the library SAP_TOOLS if it exists, otherwise you need not care

    CLRLIB SAP_TOOLS
      4. 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')
    5. 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.
      6. Set the authorities of the objects in SAP_TOOLS by these commands:

      ADDENVVAR ENVVAR(CLASSICUSERCONCEPT) VALUE('Y')

      ADDLIBLE SAP_TOOLS

    FIXSAPOWN *NONE SAP_TOOLS
    7. For 7.00/7.01 NetWeaver releases, 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, run command

    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. For 7.00/7.01/7.10/7.11 releases only:

Please remove any DLTOLDPKG call from all start profiles, because with the kernel 721 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 721 environment with the kernel library SAP<sapsid>IND.
(Caution: The name of the kernel library is predefined after you import the kernel 721 (EXT) and can no longer be freely selected.)

If you change a system with a 710 or 711 kernel to the kernel 721 (EXT) 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 before starting the system with the new kernel

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 (releases 7.00/7.01)

  • Only necessary for a dual-stack system: you must set the following parameter in the default system profile DEFAULT.PFL:
    system/type = DS
  • For dual-Stack and Java-only systems: 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 the SAPCRYPTOLIB for the 721 (EXT) version according to the 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 when upgrading from 700/701/710/711 kernel versions as these programs were deleted during the kernel exchange. If upgrading from the 720 kernel version, you also may want to reinstall these programs with a newest patch level.

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 For NetWeaver 7.0/7.1/7.10/7.11:
Copying executable file from NetWeaver RFC SDK 720.

The 720 and 721 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 1025361 for detailed instructions and further information.

5.5 Special features for the syslog (if upgrading from 700/701/710/711 kernel versions)

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 (Only for 7.00/7.01 NW releases)

The 720 and 721 kernel versions support 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 you upgraded your monitored system from and 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 the 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 on 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 for the Release 7.00/7.01

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

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

6.1 Java or Dual-Stack systems 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 outlined in the note 1716826, the section "Prerequisites" -> "Attention".
  • 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 (for 7.00/7.01/7.10/7.11 ABAP releases)

If you did not handle the DDIC_TYPELENG_INCONSISTENT issue described in the note 1716826, the section "Prerequisites" -> "Attention" while the original kernel was still running, you should now install the note 1610716.

6.3 Load format of ABAP programs (for 7.00/7.01/7.10/7.11 ABAP releases)

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 format is automatically regenerated.

It is also possible to regenerate these ABAP load formats directly. For more information about this, see Notes 170039, 162991 and 155580.

6.4. CCMS Monitoring issues

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

Header Data

   
Release Status: Released for Customer
Released on: 25.02.2013 14:48:59
Master Language: English
Priority: Recommendations/additional info
Category: Upgrade information
Primary Component: BC-CST Client/Server Technology

Affected Releases

Software
Component
Release
From
Release
To
Release
And
subsequent
KRNL32NUC
7.21
7.21
7.21
 
KRNL32NUC
7.21EXT
7.21EXT
7.21EXT
 
KRNL32UC
7.21
7.21
7.21
 
KRNL32UC
7.21EXT
7.21EXT
7.21EXT
 
KRNL64NUC
7.21
7.21
7.21
 
KRNL64NUC
7.21EXT
7.21EXT
7.21EXT
 
KRNL64UC
7.21
7.21
7.21
 
KRNL64UC
7.21EXT
7.21EXT
7.21EXT
 
SAP_BASIS
70
700
702
 
SAP_BASIS
71
710
730
 
SAP_BASIS
731
731
731
 
KERNEL
72
7.21
7.21
 

Dear visitor, you went to website as unregistered user.
We encourage you to Register or Login to website to see all content.

Add comments

Name:*
E-Mail:*
Comments:
bold italic underline strike | align left centered align right | Ensert smilies Choice the color | hidden text insert quote Convert selected text from transliteration to Cyrillic alphabet Insert spoiler
Type the two words: *

Tags Cloud

Archives

^