This article shows us with detailed steps to upgrade SAP Kernel to 720 version.
It includes every step to be performed for the activity.
This procedure is for linux OS.
Stop the SAP system. (You do not need to stop the database.)
Login as adm
Stopsap r3 ( if it doesn’t work use hostname with stopsap command)
Ex: Stopsap r3 SAPSID
Stop SAPOSCOL
Saposcol –k (with sidadm user)
Stop sapstartsrv
Kill -2 (with sidadm user)
If exists, unregister all standalone CCMS agents (sapccmsr [-j2ee],
sapccm4x). On Unix you can see corresponding processes
sapccm4x -u pf=
sapccmsr -u pf= [-j2ee]
Remove any IPC objects that still exist
cleanipc remove
Save old kernel before deploying new Kernel
As per sapnote we'd like to execute like below command
SAPCAR -cvf ../sapexe.tar (it wasn’t worked for me. So I took tar backup of exe dir)
As sidadm change directory to /sapmnt/SID
Execute below command
tar –cvf exe.tar exe ( we can take it as SIDexe.tar).
Delete all of the files existing in the kernel directory, including the
Subdirectories. This ensures that there are not any remaining files from
the earlier release, which have a special name in Release 7.20 or
are in a different place in a subdirectory.
Log on as user adm and switch to the directory
/usr/sap//SYS/exe/run
(Check twice on which locaton you're executing rm -rf command)
rm –rf *
Unpack the new kernel with the following commands in the same dir.
/SAPCAR –xvf R3trans_221-10007264.SAR
/SAPCAR –xvf dw_utils_220-10007264.sar
/SAPCAR –xvf R3check_210-0007264.SAR
/SAPCAR –xvf R3ldctl_221-10007263.SAR
/SAPCAR –xvf R3load_221-10007263.SAR
/SAPCAR –xvf R3szchk_221-10007263.SAR
/SAPCAR –xvf sapcpe_218-10007264.sar
/SAPCAR –xvf SAPEXEDB_201-10007263.SAR
/SAPCAR –xvf SAPCAR_2-10007272.exe
/SAPCAR –xvf SAPEXE_201-10007264.SAR
/SAPCAR –xvf tp_340-20001346.sar
/SAPCAR –xvf saprouter_212-10007264.sar
/SAPCAR –xvf SAPSLDREG_210-10007264.SAR
/SAPCAR –xvf lib_dbsl_225-10007263.sar
/SAPCAR –xvf NWRFC_11-20004549.SAR
/SAPCAR –xvf DBATL720O10_25-10007263.SAR
Delete all of the local executables from all the individual instances.
To do this, switch to the local executable directory of each instance.
/usr/sap///exe and execute
(Check twice on which locaton you're executing this command)
rm -rf *
It includes every step to be performed for the activity.
This procedure is for linux OS.
Stop the SAP system. (You do not need to stop the database.)
Login as adm
Stopsap r3 ( if it doesn’t work use hostname with stopsap command)
Ex: Stopsap r3 SAPSID
Stop SAPOSCOL
Saposcol –k (with sidadm user)
Stop sapstartsrv
Kill -2 (with sidadm user)
If exists, unregister all standalone CCMS agents (sapccmsr [-j2ee],
sapccm4x). On Unix you can see corresponding processes
sapccm4x -u pf=
sapccmsr -u pf= [-j2ee]
Remove any IPC objects that still exist
cleanipc remove
Save old kernel before deploying new Kernel
As per sapnote we'd like to execute like below command
SAPCAR -cvf ../sapexe.tar (it wasn’t worked for me. So I took tar backup of exe dir)
As sidadm change directory to /sapmnt/SID
Execute below command
tar –cvf exe.tar exe ( we can take it as SIDexe.tar).
Delete all of the files existing in the kernel directory, including the
Subdirectories. This ensures that there are not any remaining files from
the earlier release, which have a special name in Release 7.20 or
are in a different place in a subdirectory.
Log on as user adm and switch to the directory
/usr/sap//SYS/exe/run
(Check twice on which locaton you're executing rm -rf command)
rm –rf *
Unpack the new kernel with the following commands in the same dir.
/SAPCAR –xvf R3trans_221-10007264.SAR
/SAPCAR –xvf dw_utils_220-10007264.sar
/SAPCAR –xvf R3check_210-0007264.SAR
/SAPCAR –xvf R3ldctl_221-10007263.SAR
/SAPCAR –xvf R3load_221-10007263.SAR
/SAPCAR –xvf R3szchk_221-10007263.SAR
/SAPCAR –xvf sapcpe_218-10007264.sar
/SAPCAR –xvf SAPEXEDB_201-10007263.SAR
/SAPCAR –xvf SAPCAR_2-10007272.exe
/SAPCAR –xvf SAPEXE_201-10007264.SAR
/SAPCAR –xvf tp_340-20001346.sar
/SAPCAR –xvf saprouter_212-10007264.sar
/SAPCAR –xvf SAPSLDREG_210-10007264.SAR
/SAPCAR –xvf lib_dbsl_225-10007263.sar
/SAPCAR –xvf NWRFC_11-20004549.SAR
/SAPCAR –xvf DBATL720O10_25-10007263.SAR
Delete all of the local executables from all the individual instances.
To do this, switch to the local executable directory of each instance.
/usr/sap///exe and execute
(Check twice on which locaton you're executing this command)
rm -rf *
Installing
SAPHOSTAGENT
For releases 7.00 and 7.01 (7.0 Enhancement Package 1), you need to also
install the package SAPHOSTAGENT.SAR within the latest 7.20 version available
(in accordance with Note 1031096).
Extract the SAPHOSTAGENT to a temporary folder. Here in this case we have already
Extract the HOST AGENT to temporary local folder.
cd /Common//Kernel_720/KERNEL_NEW/
mkdir SAPHOSTAGENT
cd SAPHOSTAGENT
/Common//Kernel_720/SAPCAR_5-20002089.EXE –xvf
/Common//Kernel_720/SAPHOSTAGENT111_111-20005731.SAR
Switch to root user
saphostexec –install
Run SAPROOT.SH
Switch to root
cd /sapmnt//exe
./saproot.sh
Run sapcpe
As executables from the local executable directories may already be
executed for the beginning before sapcpe runs, start an initial copy of the executables.
cd /usr/sap///work
sapcpe pf=/usr/sap//SYS/profile/
sapcpe pf=/usr/sap//SYS/profile/
install the package SAPHOSTAGENT.SAR within the latest 7.20 version available
(in accordance with Note 1031096).
Extract the SAPHOSTAGENT to a temporary folder. Here in this case we have already
Extract the HOST AGENT to temporary local folder.
cd /Common//Kernel_720/KERNEL_NEW/
mkdir SAPHOSTAGENT
cd SAPHOSTAGENT
/Common//Kernel_720/SAPCAR_5-20002089.EXE –xvf
/Common//Kernel_720/SAPHOSTAGENT111_111-20005731.SAR
Switch to root user
saphostexec –install
Run SAPROOT.SH
Switch to root
cd /sapmnt//exe
./saproot.sh
Run sapcpe
As executables from the local executable directories may already be
executed for the beginning before sapcpe runs, start an initial copy of the executables.
cd /usr/sap///work
sapcpe pf=/usr/sap//SYS/profile/
sapcpe pf=/usr/sap//SYS/profile/
Post Actions
Special functions for the syslog (AS ABAP and Dual-Stack systems)
Due to things described in note 1517379, you've got to line the profile
Parameter
rslg/new_layout = 9.
If a syslog file already exists within the new format because this parameter
has not been set from the very beginning, the syslog will still be written
in the new format albeit the parameter has been set within the meantime. In
that case, the existing syslog files have to be deleted.
Dynamic work processes (AS ABAP and Dual-Stack systems)
The 7.20 kernel supports the dynamic increase of the amount 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
Start SAP system with new Kernel
Startsap r3 (with sidadm user)
Run sgen in productive client .
Due to things described in note 1517379, you've got to line the profile
Parameter
rslg/new_layout = 9.
If a syslog file already exists within the new format because this parameter
has not been set from the very beginning, the syslog will still be written
in the new format albeit the parameter has been set within the meantime. In
that case, the existing syslog files have to be deleted.
Dynamic work processes (AS ABAP and Dual-Stack systems)
The 7.20 kernel supports the dynamic increase of the amount 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
Start SAP system with new Kernel
Startsap r3 (with sidadm user)
Run sgen in productive client .
