Kernel Upgrades: A Survival Timeline
The SAP kernel is the executable layer that sits between the operating system and the ABAP or Java application. It handles work process management, memory allocation, database communication, and inter-process messaging. Upgrading it is one of the simpler maintenance tasks a BASIS admin performs — but it requires downtime, a rollback plan, and a methodical approach.
What the Kernel Is and What It Affects
The kernel is a set of executables stored in /usr/sap/SID/SYS/exe/. When you start an SAP instance, the kernel executables are what actually run. The ABAP repository, database, and profiles are separate — a kernel upgrade changes only the executables, not the application or data.
A kernel mismatch — running application code that requires capabilities from a newer kernel than what is installed — is a common cause of cryptic runtime errors after upgrades or support package applications. Conversely, upgrading the kernel to a version that introduces a regression can break previously working functionality. Neither situation is catastrophic as long as you have a rollback plan.
Kernel releases come in two variants: patch levels within a kernel release (e.g., 7.89 patch 4 to patch 6) and major kernel releases (e.g., 7.77 to 7.89). Patch-level upgrades are low-risk and routine. Major kernel upgrades require more testing and carry higher risk.
When to Upgrade
Upgrade the kernel when: a security patch requires it, SAP Support recommends it for a specific issue you are experiencing, you are applying a support package that requires a minimum kernel level, or your current kernel is approaching end of maintenance.
Do not upgrade the kernel speculatively during a business-critical period. Kernel upgrades require a system restart and cannot be applied to a running instance. Schedule them in a maintenance window.
Download and Verification
Download the kernel from the SAP Software Center on the SAP Support Portal. Select the correct combination of: operating system, database platform, kernel release (32-bit is not used in modern landscapes — 64-bit only), and architecture.
The SAP Support Portal provides checksums for each download. Verify them before proceeding. A corrupted kernel archive that passes silently will either fail during extraction or, worse, behave unpredictably after installation.
Download into a staging directory, not directly into the kernel directory. You need the existing kernel directory intact for rollback.
Pre-Upgrade Checks
Before the upgrade window, verify the following. First, check that all work processes are idle or can be cleanly stopped — review SM50 or SM66 for long-running processes that need to complete or be cancelled. Second, confirm that the database is healthy: no pending redo log issues, no space alerts. Third, take a backup of the current kernel directory. Copy /usr/sap/SID/SYS/exe/run to a backup location — this is your rollback.
Notify all users of the downtime window. Set system message in SM02 before shutdown.
The Upgrade Procedure
Stop all SAP instances cleanly using sapcontrol or the stopsap command. Verify that all processes are down before touching the kernel directory. Replacing kernel executables while the system is running will cause unpredictable behaviour.
Extract the downloaded kernel archive into the kernel directory, overwriting the existing executables. The typical extraction command on Linux is: unzip the archive and copy the contents to /usr/sap/SID/SYS/exe/run/. Ensure ownership and permissions are correct — files should be owned by the SID administration user.
For systems running on Windows, use the SAPHOSTAGENT-managed kernel update process or follow the Windows-specific procedure from SAP Note 19466.
Start the SAP instance. Review the system log in SM21 immediately after startup for any kernel-related errors. The kernel version is visible in transaction SM51 under the instance details.
Rollback Plan
Before starting, you have already backed up the old kernel directory. Rollback is: stop the system, restore the backup kernel directory, start the system. Document the backup location before starting the upgrade. A rollback that requires searching for where the backup was put is not a rollback plan.
If the system fails to start after the upgrade, do not attempt repeated restarts. Restore the backup immediately. Diagnose from the old kernel before attempting the upgrade again.
Post-Upgrade Validation
After a successful start, verify the kernel version in SM51. Check SM21 for any errors generated during startup or in the first few minutes of operation. Run a representative set of transactions to confirm basic functionality.
For patch-level upgrades, this validation can be lightweight. For major kernel version upgrades, run a broader smoke test covering the transactions your most critical business processes use — month-end posting, payroll, outbound delivery processing — before declaring the window complete.
Update your system documentation with the new kernel version and upgrade date. If you track kernel versions centrally (e.g., in SAP Solution Manager or a CMDB), update the record.
> Editorial note: Kernel upgrade procedures vary by operating system, database, and SAP release. Always consult the release-specific SAP Notes (primary reference: SAP Note 19466 for kernel installation) and verify the procedure applies to your landscape before executing in production.