9-Bonus

Download as pdf or txt
Download as pdf or txt
You are on page 1of 4

Contents

Kernel Backup ............................................................................................................................................... 1


Unpack a New Kernel .................................................................................................................................... 1
Stop the SAP System ..................................................................................................................................... 2
Replacing Kernel Files ................................................................................................................................... 3
Start the SAP System and Check the logs ..................................................................................................... 4

Kernel Backup

Begin by making a backup of the old kernel tiles, by copying the entire kernel directory at the operating
system level. This can be done while the SAP system is running.
1. Use the user "<SID>adm" to log on to your SAP server.
2. Create a backup directory, for example:
• <drive>:\saptemp\kernel_701_69\bak (Windows)
• /usr/sap/<SID>/<instance>/temp/kernel_701_69/bak (Unix)
If you want to save the update data permanently, give your directory a name that is as meaningful as
possible. You also need to ensure that there is sufficient memory available on your drives.
3. Copy the entire kernel directory, <drive>:\usr\sap\<SID>\<instance>\exe or /
usr/sap/<SID>/<instance>/exe, including all subdirectories, into your backup directory.

This completes the kernel backup. If necessary, save your backup directory on a separate server on your
local PC or on tape. Ensure that you comply with all security measures so that your directory can't be
deleted by another user while you're busy with the kernel update.

Unpack a New Kernel

The kernel files you downloaded from the SAP Support Portal exist in a compressed
format in your system. You need to transfer them to the server and unpack them
with the SAPCAR program.
1. Use the user "<SID>adm" to log on to your SAP server.
2. Create a directory for the new kernel files, for example:
• <drive>:\saptcmp\kernel_701_69\new
• /usr/sap/<SID>/<instance>/temp/kernel_701_69/new
The size of the SAP kernel is several hundred megabytes, even when compressed.
Ensure that a sufficient amount of memory is available to store the packed files,
and make a sufficient number of hard disk reserves available for decompression
of the files.
3. Copy all new kernel tiles to your server:
• SAPEXE_ <patch level>-<identifier>.SAR
• SAPEXEDB_ <patch level>-<identifier>.SAR
• igsexe_ <patch level>-<identifier>.sar
4. Create a directory in which to unpack the files, for example:
•<drive>:\saptemp\kernel_701_69\new\unpacked
• / usr/sap/<SID>/<instance>/temp/kernel_701_69/new/ unpacked
5. Open a shell session, and switch to the/usr/sap/<SID>/<instance>/exe or <drive>:\
usr\sap\<SID>\<instance>\exe directory.
6. Unpack the kernel files with SAPCAR, for example:
•SAPCAR -xvf SAPEXE_<patch level> - <identifier>. SAR -R <drive> : \saptemp\ kernel_701_69\new
• SAPCAR -xvf SAPEXE_<patch level>-<identifier>.SAR -R /usr/
sap/<SID>/<instance>/temp/kerne1_701_69/new
The sequence in which you unpack the tiles is irrelevant. When you've finished,
the decompressed kernel is saved in the directory you selected for unpacking.
SAPCAR lists the unpacked files in the shell. If the SAPCAR: NOT ALL FILES COULD BE EXTRACTED
message is displayed, check first whether the syntax in your SAPCAR command was correct. Enter
SAPCAR to display the Help. Errors may also occur if case sensitivity is not taken into account, in
particular in the Unix/Linux environment. In rare cases, an archive may be damaged during the
download, for example. If this occurs, download it a second time and try again.

Stop the SAP System

During the kernel update, you replace the files at the operating system level. To do
this, you must stop the SAP system and the database.
You also need to ensure that files in use by running programs are not deleted or
overwritten. You therefore need to end all running SAP services.
1. Open a shell session, and log on to the SAP server with user <SID>adm.
2. Switch to the directory: /usr/sap/<SID>/<instance>/exe or <drive>:\usr\
sap\<SID>\<instance>\exe.
3. Stop the SAP system and database first with the stopsap -all command or by
using the SAP Management Console.
4. Stop all SAP services that are currently running. Your system's release and the
scope of its installation will determine how many services are still running and
which services these are. Therefore, the following list may not be complete in
all cases:
• saposcol: sapos col - k
• CCMS agents: sapccm4x -stop / sapccmsr –stop
• SAProuter: saprouter - s
5. Depending on your operating system, you may also need to clean the kernel
libraries in the buffer with the following command under Unix, for example:
/usr/sbin/slibclean.
You can also stop all services that are currently running with the task manager or
a similar operating system tool.
When you've finished, you should be able to overwrite all old files when you copy
the new kernel version. It you are unable to replace all files due to programs that are
currently running, errors are very likely to occur during SAP system operation.

Replacing Kernel Files

After you've made a backup copy of the old kernel, unpacked the new files on the server, and
completely stopped the SAP system, you can begin to replace the old kernel files with the new version.
Follow these steps:

1.Use the user "<SID>adm" to log on to your SAP server.


2. Copy all files and subdirectories from your unpacked directory into the kernel directory
<drive>:\usr\sap\<SID>\<instance> \exe or /usr/sap/<SID>/<instance>/exe.
3. Overwrite the existing files if the operating system prompts you to do so.

Pay particular attention to messages indicating that certain files could not be overwritten because they
are in use by a program. This means that you have not stopped all SAP services.

If this occurs, find the applications that are still running and stop them. Then copy the files again.

The authorizations on your server for the old kernel files may be configured differently before and after
the update in certain cases. This may result in errors when functions are executed in the SAP system.

Compare the authorizations in your kernel backup with the new version, and make adjustments so that
they are identical. If necessary, ask an operating system administrator for help.

Start the SAP System and Check the logs

When the kernel files have been copied successfully, start the SAP system again:

1. Open a shell session, and log on to the SAP server as user <SID>adm.

2. Start the database and SAP system with the command startsap or by using the SAP Management
Console.

3. Check the operating system log, database log, and SAP system log for error messages. If problems
occur, pay particular attention to the trace files of the work processes, and especially the dev_w0 file in
<drive>:\usr\sap\<SID>\<instance>\work or /usr/sap/<SID>/<instance>/work.

4. Try to log on to the system with the SAP GUI. If a logon screen is displayed, this
indicates that the SAP system is running.

5. Log on, and check the kernel version under SYSTEM -> STATUS.
If the new kernel version is displayed in the status view, you know that you have performed the kernel
update successfully.

You might also like