|Release Status||Released for Customer|
|Released on||02.12.2011 11:51:18|
You want to use the 7.20 or 7.20 EXT kernel as a downward-compatible kernel in one of the following NetWeaver releases
7.20, 7.20 EXT, 720_EXT, AKK, DCK, Downward-Compatible KernelReason and Prerequisites
The installation of the 7.20 or 7.20 EXT kernel as a downward-compatible kernel is, until further notice, only released
Read the following platform-specific SAP notes:
If you are using the 7.20 kernel as a DCK the following platform limitations are in place:
If you are using the 7.20 EXT kernel as a DCK the following platform specific limitations are in place (check the PAM for general information about the supported DB and OS releases):
The 7.20 kernel that 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
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.
After you have installed a 7.20 kernel, you must
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, 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>:
The archive igshelper. sar contains an optional component (see SAP note 1028690) that 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".
After you have centrally compiled the required kernel components, you must stop all of the relevant processes 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:
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 this to the latest version for Releases 7.10 and 7.11 (7.10 Enhancement Package 1).
Afterwards, you must delete the call of the program SAPOSCOL from all of the start profiles. (not Windows)
The SAPHOSTAGENT 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".
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.
Save the old kernel by creating a tar archive of the complete kernel directory using the following command:
tar -cvf ../sapexe.tar
su - root
chown <sapsid>adm /usr/sap/<SAPSID> /SYS/exe/run/*
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.
rm -rf *
<newkernel>/SAPCAR -xvf <newkernel>/SAPEXE.SAR
<newkernel>/SAPCAR -xvf <newkernel>/SAPEXEDB.SAR
Unpack the DBATools with the following command:
<newkernel>/SAPCAR -xvf <newkernel>/DBATOOLS.SAR
Also unpack the Oracle instant client to the directory.
<newkernel>/SAPCAR -xvf <newkernel>/igsexe. sar
<newkernel>/SAPCAR -xvf <newkernel>/IGSHELPER. SAR
su - root (or su <user with UID 0> on OS/390)
rm -rf *
sapcpe pf=/usr/sap/<SAPSID>/SYS/profile/<instance profile>
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
Unpack the DBATools to the <platform> directory:
<newkernel>\SAPCAR.EXE -xvf <newkernel>\DBATOOLS.SAR
Also unpack the Oracle instant client to the <platform> directory.
<newkernel>\SAPCAR.EXE -xvf <newkernel>\igsexe.sar
For the primary application server instance and every application server instance proceed as follows:
sapcar.exe -xvf <TEMPDIR>\IGSHELPER.SAR
sapcpe <drive>:\usr\sap\<SAPSID>\sys\profile\<instance profile>
Search for REPSRV.lst in all Start Profile of the ERS instances (line Start_Program_00 =)and if exists replace it with SCS.lst.
Be sure to check if your Enqueue Replication Service is replicating again after starting the ERS instances.
Log on as a QSECOFR-type user and execute the following commands or actions:
CALL QP2SHELL PARM('/QOpenSys/usr/bin/csh' '-c' 'SAPCAR -xvf ILE.SAR iletools ILE_TOOLS;iletools')
ADDENVVAR ENVVAR(CLASSICUSERCONCEPT) VALUE('Y')
FIXSAPOWN *NONE SAP_TOOLS
Log on as <SAPSID>ADM and execute the following commands for importing the new kernel:
ADDENVVAR ENVVAR(CLASSICUSERCONCEPT) VALUE('Y')
APYSIDKRN SID(<SAPSID>) ARCHIVES('<newkernel>/*') SAVSAR(*NONE) MODE(*FULLY) CHGENV(*NO) UPDAPAR(*NO)
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 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).
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.
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
(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 RFC Library, CPIC Library, and so on, you must install them again. To do this, proceed as follows:
Execute the following commands as user <sapsid>adm:
Execute the following commands as user <SAPSID>ADM:
On IBM i:
On IBM i, you do not have to install any further programs.
We recommend that you set the profile parameter
rslg/new_layout = 9.
If no old system log file exists, this parameter must be set. See Note 1517379 for further information.
The 7.20 kernel supports the dynamic increase of the number of
work processes at runtime. However, this function is not fully compatible with lower ABAP versions. 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
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. You can also implement this note before changing the kernel.
AS Java or Dual-Stack systems:
If the Java instance doesn't start, check if SAP note 1163719 applies.
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.
|Software Component||Release||From Release||To Release||And subsequent|
|1632755||IBM i: Description of command APYSIDKRN|
|1632754||IBM i: Umstellung auf ein Instanz-spezifisches Verzeichnis|
|1629598||SAP Kernel 720 will replace older kernel versions|
|1610716||Correcting runtime objects with incorrect alignment|
|1598550||SAPCAR: Signed archive|
|1563102||Linux Requirements for 7.20 EXT kernel|
|1553465||Prerequisites for running the 720_EXT kernel 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?|
|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 tool CONVUSRCPT|
|1078134||IBM i: Distribution of ILE and PASE system components|
|1031096||Installing Package SAPHOSTAGENT|
|1028690||True Type Fonts delivered with IGS|
|808607||iSeries: Memory management in a system based on PASE|
|684106||Microsoft runtime DLLs|
|510007||Setting up SSL on Web Application Server ABAP|
|397175||SAP Cryptographic Software - Export control|
|170039||Kernel upgrade 4.5A/4.5B: -> Mass generation|
|162991||Generation tools for ABAP programs|
|155580||Creating report loads after transport|
|19466||Downloading SAP kernel patches|