How to update the

ABAP Kernel

Attention: Customer has to define within the

ticket which new kernel patch and type is
needed. Also a timeframe should be specified
in the ticket.
Latest kernel patch from night make:

1. Customer request kernel update via CSN (DEV-PSS, DEV-PSS-

INT).
IT PSS DEV will move suitable tickets to corresponding TCS
components.

2. Check, if the requestor is equal to the system owner (regarding to

R3SYS system owner or SISM: overall person in charge (could also
be a SAPNet distribution list)).
a. True: go ahead
b. False: Get approval of system owner or somebody of the
distribution list within the corresponding CSN ticket by setting
the ticket to “Author action” (the author have to take care
getting the approval of system owner).

3. Check, if a timeframe for the kernel update is mentioned by the

system owner or author within the ticket. If not, set ticket to “Author
action” asking for a timeframe.

4. Logon to the server, where the system is located (according to

SISM or R3SYS) with the SIDadm for Windows and root for
Unix/Linux

5. Execute PSSTool for updating the kernel to the latest night make
(the location of the new kernel will be displayed on the screen and
in the log file of the PSSTool in the temp directory).

6. Check, if the system is a Prio1 system (according to SISM). If yes,

set the system in maintenance and the “working flag” in SYSMON
III to prevent an alert in ALC (TCS Procative Monitoring will work
immediately on this alert and will try to start the system again)

7. Activate kernel manually: Set a system message (System will be

restarted on <Date> at <Time> due to kernel update) and proceed
as following:
 a. Stop system
b. Rename old kernel directory (eg.: run ->
run.old_<Date>_<Time>, G -> G.old_<Date>_<Time>)
c. Rename new kernel directory to run (Windows) or G
(Unix/Linux)
d. Test connection to the database with the command R3trans –d
e. Start system. If the system wouldn’t come up due to kernel
problems, switch back to the old kernel

8. Activate kernel automatically: The PSSTool will check, if the system

is up and running and asking for restarting the system. If the restart
failed, please switch back the kernel manually and start system with
the old kernel.

9. Login to the system with a user not equal to SAP* or DDIC and
check if the central instance and also the application server running
with the same kernel patch level (transaction sm51 -> Release
information). Also call transaction sick to check if the initial system
checks were successfully.
Latest customer released kernel patch from SAP Service Marketplace:

1. Customer request kernel update via CSN (DEV-PSS, DEV-PSS-

INT).
IT PSS DEV will move suitable tickets to corresponding TCS
components.

2. Check, if the requestor is equal to the system owner (regarding to

R3SYS system owner or SISM: overall person in charge).
a. True: go ahead
b. False: Get approval of system owner or somebody of the
distribution list within the corresponding CSN ticket by setting
the ticket to “Author action” (the author have to take care
getting the approval of system owner).

3. Check, if a timeframe for the kernel update is mentioned by the

system owner or author within the ticket. If not, set ticket to “Author
action” asking for a timeframe.

4. Logon to the server, where the system is located (according to

SISM or R3SYS) with the SIDadm for Windows and root for
Unix/Linux

5. Check the current kernel patch (by executing “disp+work” on OS

level or calling transaction sm51 -> Release Information in the
system directly) and collect following information:
a. kernel release
b. kernel compilation (non-Unicode/Unicode)
c. kernel bits (32/64)
d. database type

6. Login to the SAP Service Marketplace (see also CSS note: 19466)
and check if newer patch level is available. If a newer patch level is
available, download following packages:
a. disp+work package
b. R3trans package
c. TP package
d. Database library package (if requested by the customer)
and transfer them to the server.
If there are no newer patch level available, return ticket with a short
note back to the author (status: “Author action”)

7. Go to the kernel directory and create a new directory

G.new_<Date>_<Time> (Unix/Linux) or run.new_<Date>_<Time>
(Windows) and copy the current kernel to the new directory.

8. Copy the downloaded packages also to the new directory and

extract the archives to get the patched kernel
9. Check, if the system is a Prio1 system (according to SISM). If yes,
set the system in maintenance and the “working flag” in SYSMON
III to prevent an alert in ALC (TCS Procative Monitoring will work
immediately on this alert and will try to start the system again)

10. Activate the new kernel as following:

a. Set a system message (System will be restarted on
<Date> at <Time> due to kernel update)
b. Stop system
c. Rename old kernel directory (run ->
run.old_<Date>_<Time>, G -> G.old_<Date>_<Time>)
d. Rename new kernel directory to run (Windows) or G
(Unix/Linux)
e. Test connection to the database with the command
R3trans –d
f. Start system. If the system wouldn’t come up due to
kernel problems, switch back to the old kernel

11. Login to the system with a user not equal to SAP* or DDIC and
check if the central instance and also the application server running
with the same kernel patch level (transaction sm51 -> Release
information). Also call transaction sick to check if the initial system
checks were successfully.