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

11

Symptom
1. You want to use the 7.20 or 7.20 EXT kernel as a downward-compatible kernel in one of the following
Net Weaver releases
 SAP Net Weaver 7.0 ("7.00")
 SAP EhP1 for SAP Net Weaver 7.0 ("7.01")
 SAP Net Weaver 7.10 ("7.10")
 SAP EhP1 for SAP Net Weaver 7.10 ("7.11")
 Or in
 SAP Net Weaver CE 7.1
 SAP EhP1 for NW CE 7.1

2. This note is valid for all systems with Net Weaver 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.

We have valid release 7.01

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

Prerequisite Fulfilled.
4. 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".

Platform-Specific Information

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

AIX Version:-5.3
TL: 12
Prerequisite Fulfilled.

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

We have valid release 10.2.0.5.0

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

 Make sure that Note 1222907 is active in the system. Correction delivered in Support Package
SAPKB70101

We have valid release SAP_BASIS 701 0010 SAPKB70110 SAP Basis

Component

 Implement Note 1610716 - Correcting runtime objects with incorrect alignment

As CHARM is implemented IN DTS system we request Wipro team to implement the same.

Now Run report RUT_NOTE_1610716

Execute the report RUT_NOTE_1610716 in test mode in the background. This means that the 'Check'
selection field (technical name PCHECK) should be selected during the first run (this is also the default
setting). The runtime of the report is a few minutes. There should usually be none or very few incorrect
types (it is not unusual to have approximately 20 errors). If the check run finds more than 1000 errors, you
should open a message under the component BC-DWB-DIC-AC. 5. The results of the check run are
displayed as a list. In addition, you can use the report RADPROTA to evaluate the log. To do this,
execute the report RADPROTA, enter the log name NOTE1610716* and press F8 to
execute. Select the most recent log from the overview list by double-clicking.
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.

Package Requirement

You should download the following archives into the same directory <newkernel>:For more
information about the download, see Note 19466.

1. Due to the digital signature of the archives (see Note 1598550), you require the latest SAPCAR.

SAPCAR_5-20002094.EXE

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

SAPEXE_300-20005242.SAR
SAPEXEDB_300-20005243.SAR

3. If you use the Internet Graphics Server (IGS), you must also download the archives igsexe.sar
and, optionally, igshelper.sar.

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

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

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

DBATL720O10_29-20005243.SAR

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 and DB. (Note:-You do not need to stop the database but we still do it.)
On UNIX or Windows:
Stop the SAP system as usual.

2. Stop saposcol.
On UNIX (Web AS release 7.0 and 7.01):
cd /usr/sap/<SAPSID>/SYS/exe/run
./saposcol –k
3. Stop sapstartsrv (this is required on UNIX and Windows only):
On UNIX:
kill -2 <pid of sapstartsrv>

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]

No Process is running.

5. Remove any IPC objects that still exist (this is required on UNIX only):
cleanipc <instance no> remove
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)

Passwd of sapadm is sapadm1

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.

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

 The directory jvm or sapjvm if it exists[NA]

 The file protect.lst if it exists[NA]
 The files rfcexec, rfcexec.sec if they exist

Note: The directory 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

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 and move it to exe.:

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

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

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

Not Required

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

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

Not Required

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.

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

Additional steps

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.

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

"Installing the SAP Cryptographic Library on the AS ABAP"

"Installing the SAP Cryptographic Library on the AS Java"

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

3. Copying executable file from NetWeaver RFC SDK 720.

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

Already Done Above

4. Special features for the syslog (AS ABAP 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. Dynamic work processes (AS ABAP and Dual-Stack systems) 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
rsdb/ntab/entrycount=200000 (1398802 - Various problems if name tab buffer is too small)

6. Start the SAP system with the new kernel

Start the SAP system.
Post Step:-

Run SGEN.

Note:-To speed up SGEN, Increase dialog work process, reduce background Processes.
Also, in RZ12 change Max. Number of WPs Used (%) to 95.Please revert the changes back to
original once done.
Trouble shootings

AS Java or Dual-Stack systems and release 7.00 or 7.01:

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

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

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

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

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

5. Configuration of the CCMS central monitoring

Depending on the SAP kernel release of the monitored system youup graded from and depending on
the release of the central monitoring system (CEN), it is needed 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.

CEN system is based on SAP_BASIS 7.0 EhP 1 (7.01):

Register the integrated CCMS agents from the central system to have the upgraded system
monitored.

You upgraded the central system:

No reconfiguration is necessary. SAP note 1667336 contains a detailed description for every
case.