Kernel Upgrade Process

Step 1) Checks to be done before kernel upgrade
a) Find the current version of the  kernel
         ==> execute the command disp+work -v to get the present kernel version
         ==> use the R/3 SYSTEM->STATUS to get the present kernel level
b) Note the Compilation mode from disp+work -v (here UNICODE)
c) The Operating system BIT length.
     ==>This can be found using "winmsd" (in windows) and "isainfo -v" or "uname -a" on unix servers.
             Also "tp -v" will give the OS bit length.

Step 2) Download the latest kernel patch from SMP

http://service.sap.com/swdc 

 --->Support Packages and Patches --->SAP NetWeaver ---> SAP NETWEAVER---> SAP NETWEAVER 7.0 (2004S) ---> Entry by Component---> Application Server Java--->SAP Kernel 7.00 32 bit UNICODE
There are 2 files to be downloaded from SMP:

a) Database Independent Files
This is of the nomenclature SAPEXE_<Patch level>-<release date>.SAR

b) Database Dependent files
This is of the nomenclature SAPEXEDB_<Patch level>-<release date>.SAR

Step 3) Uncar the .SAR files
Uncar the files using the SAPCAR utility and store it in a directory. Use the command:
SAPCAR -xvf <filename.SAR>

Step 4) Stop the Application Server and the SAP OS Collector

               In windows, stop the SAPOSCOL service (Start-> run-> services.msc)
               In Unix servers, use the command:   saposcol –k

Step 5) Take Backup of the present Kernel directory 

==> Copy the present kernel folder safely. This is important because the activity is completely reversible and 

switching over to the old kernel will be possible. 

Step 6) Copy the new kernel files to the RUN folder location 

 ==>Copy the files in such a manner that the RUN folder is overwritten by the new files. 

Step 7) Check the permissions of the files in the kernel directory 

The Database independent files such as "brtools", "brbackup", "R3load" etc. will usually have <DB>SID as 

the owner. In such cases, the owner of the files needs to be changed using the "CHOWN" command to the 

appropriate user. 

                      chown [-R] newowner filenames 

                      chmod <1>permissions filename 

Step 8) Start the Application server and the SAP OS Collector 

Now the kernel patching activity is complete. 

In windows, start the SAPOSCOL service (Start-> run-> services.msc) 

In Unix servers, use the command:  saposcol –l 

Step 9) Check the latest Kernel level 

==> Execute the command disp+work -v to get the new kernel level 

==> Also run the command R3Trans -d to check if database connection too is fine.

==> use the R/3 SYSTEM->STATUS to get the updated kernel level