...
To enable the RKS procedure, the Enqueue server and message server must be located in separate instances.
This instance host must not contain any application server (ABAP SAP Central Services, ASCS )As of 7.4x version, the RKS procedure does not support any DUAL stack or JAVA stack systems.
Avoid long-running background jobs when RKS is scheduled.
Use a logical spool server instead of an application server which can be defined in SPAD to avoid any print failure during this activity.
Use local IGS services as this service might get stopped/restarted.
If we are using update server groups, we should check if each group is RKS compatible.
We can verify this by checking if the UPD work process exists for all/ at least 2 application servers in the group.VMC must be active in at least two AS ABAP instances or in none.
RFC’s must be configured with load balancing, if the single host is used, chances are to get they will fail.
Backup DIR_CT_RUN in which we want to import a new kernel patch.
Download relevant SAPEXE.SAR and SAPEXE<DB>.SAR archives and extract them in DIR_CT_RUN (central executable directory) using SAPCAR. (Refer SNOTE:19466).
Source and target version kernels must be RKS compatible.
...
10.0.1.132 oz2ascs - ASCS00 (ASCS)
10.0.1.133 oz2ha01 (Node A)
10.0.1.134 oz2ha02 (Node B)
10.0.1.135 oz2ers - ERS10 (ERS)
10.0.1.136 oz2appdb - D01,D02 (Node C)
/usr/sap/OZ2/SYS/exe/uc link to /sapmnt/OZ2/exe/uc
...
Before the RKS procedure is started, the system administrator must manually check the RKS prerequisites in the system configuration.
Download relevant SAPEXE.SAR and SAPEXE<DB>.SAR archives and extract them in DIR_CT_RUN (central executable directory) using SAPCAR.
You can start the RKS procedure with various tools:
...
If the operation terminates with a warning, you can force the RKS procedure. Enter the following command: sapcontrol -nr <NR> -function UpdateSystem <waittimeout sec> <softtimeout sec> 1
...
Monitoring the RKS Procedure
...
You can call up the same information with the following command:
sapcontrol -nr <NR> -function GetSystemUpdateList
/sapmnt/OZ2/exe/uc/linuxx86_64/sapcontrol -nr 01 -function GetSystemUpdateList
...
sapcontrol -nr <NR> -function GetVersionInfo
sapcontrol -nr <NR> -function UpdateSystem
Demo Scenario
Show the original version of the Kernel and IGS (Problem: In ITC there is only the Kernel version without a patch number, there is no IGS version)
...
Сheck in the SAP system
Kernel:
...
IGS:
...
The file resources are mounted to the server via NFS.
...
The following is the directory for SAPEXE and SAPEXEDB:
...
The following is the directory for SAPIGS:
...
Start Kernel Update
...
