1.

KERNAL UPGRADE :

Upgrading the SAP Basis kernel is a crucial task in maintaining the health, security, and
performance of your SAP environment. Here's a detailed explanation of the process:

What is the SAP Kernel?

The SAP kernel is a set of executables and shared libraries used to run SAP applications. It
includes essential components such as the SAP dispatcher, message server, and gateway.

Why Upgrade the Kernel?

1. Security: New kernel versions often include important security patches.

2. Performance: Upgraded kernels can offer performance enhancements.
3. Bug Fixes: Resolves known issues and bugs.
4. Compatibility: Ensures compatibility with the latest SAP applications and databases.

Preparation

1. Check Current Version: Use transaction code SM51 to check the current kernel
version.
2. Backup: Take a full system backup, including database and application server.
3. Plan Downtime: Kernel upgrade requires system downtime. Schedule it during non-
peak hours.
4. Download Latest Kernel: From the SAP Service Marketplace or SAP ONE Support
Launchpad, download the appropriate kernel files for your OS and SAP version.

Steps to Upgrade the Kernel

1. Stop SAP System:

o Use sapcontrol or stopsap command to stop the SAP system.
o Ensure all SAP processes are stopped using ps -ef | grep sap.
2. Backup Existing Kernel:
o Navigate to the directory where the current kernel is installed, usually
/usr/sap/<SID>/SYS/exe/run.
o Copy the entire directory to a backup location.
3. Extract New Kernel Files:
o Extract the downloaded kernel files using a tool like unzip or tar.
o Ensure the extracted files match the structure of the existing kernel directory.
4. Replace Kernel Files:
o Copy the extracted files to the kernel directory, replacing the existing files.
o Ensure correct file permissions and ownership.
5. Update Database Library (if required):
o If your database requires a specific library, update the dbclient directory.
o Ensure the correct version of the database client is in place.
6. Start SAP System:
o Start the SAP system using startsap or sapcontrol command.
o Monitor the startup process to ensure there are no issues.
7. Post-Upgrade Steps:
 o Check logs: dev_disp, dev_w0, and dev_ms for any errors.
o Run transaction SM51 to verify the new kernel version.
o Conduct functional testing to ensure the system operates correctly.

Common Issues and Troubleshooting

1. Kernel Not Starting: Check for missing or incorrect files.

2. Permission Errors: Ensure the correct file permissions and ownership.
3. Compatibility Issues: Ensure the kernel version is compatible with your SAP and
database versions.

Best Practices

 Always read the release notes and upgrade guides provided by SAP.
 Test the kernel upgrade in a sandbox or development environment before applying it
to production.
 Maintain a detailed log of all steps performed during the upgrade process.

Tools and Transactions

 Transaction Codes: SM51, SM50, SM21

 Commands: sapcontrol, stopsap, startsap
 SAP Notes: Refer to specific SAP Notes related to your kernel version and operating
system for additional guidance and troubleshooting.

Upgrading the SAP Basis kernel is a meticulous process that requires careful planning and
execution. Following these steps will help ensure a smooth and successful upgrade.
 2. PATCH MANAGEMENT :

The SAP BASIS Patch Manager, primarily known as the Software Update Manager (SUM),
is a critical tool within the SAP landscape. It is used for managing and applying updates,
enhancements, and patches to SAP systems. This tool ensures that your SAP environment
stays up-to-date with the latest functionalities, performance improvements, and security
patches.

Key Definitions

1. SUM (Software Update Manager): A tool provided by SAP for system maintenance,
including updates, upgrades, and migrations.
2. Support Packages: Collections of corrections, performance improvements, and legal changes
provided by SAP.
3. Enhancement Packages (EHP): Optional packages that provide new or improved
functionality for existing SAP applications.
4. Kernel: The core part of the SAP system, consisting of executables and libraries, which are
responsible for running the SAP applications.
5. Transaction Codes: Shortcuts in the SAP GUI that allow users to quickly navigate to specific
tasks or functions.

Key Functions of SAP BASIS Patch Manager

1. Applying Support Packages: Ensures the SAP system is up-to-date with the latest corrections
and performance improvements.
2. Installing Enhancement Packages: Adds new functionalities and features without needing a
full system upgrade.
3. Upgrading SAP Systems: Facilitates major version upgrades to the SAP software.
4. Database Migrations: Assists in moving the SAP system to a different database platform.
5. Updating Kernel: Updates the core components of the SAP system to the latest version.

Detailed Steps for Using SAP BASIS Patch Manager (SUM)

1. Preparation

 Download SUM Tool: Obtain the latest version of SUM from the SAP Service Marketplace or
SAP ONE Support Launchpad.
 Check Prerequisites: Ensure your system meets the necessary requirements for the update
or upgrade, including hardware, software, and authorization prerequisites.
 Backup System: Perform a full system backup to ensure you can restore your system in case
of any issues during the update.

2. Execution Phases

1. Setup Phase
o Extract SUM: Unzip the SUM tool and place it in the appropriate directory on your
server.
o Start SUM: Execute the SUM tool using the command line or SAP GUI.
o Define Parameters: Specify the parameters required for the update, such as the
target system, update type, and package locations.
 2. Initialization Phase
o System Check: SUM performs a system check to verify that all prerequisites are met.
o Configuration: Configure the tool according to the specifics of the update or
upgrade.
3. Execution Phase
o Download and Unpack Files: SUM downloads and unpacks the necessary files for
the update.
o Pre-processing: Executes preparatory steps, such as creating a shadow instance for
updates to avoid downtime.
o Main Processing: Applies the updates or upgrades. This includes database changes,
code modifications, and other necessary updates.
4. Post-processing Phase
o Verification: SUM verifies the updates to ensure they have been applied correctly.
o System Checks: Conducts system checks to confirm system stability and
performance.
o Finalization: Cleans up any temporary files and finalizes the update process.

3. Completion

 Review Logs: Check the log files generated by SUM for any errors or warnings that occurred
during the update process.
 Functional Testing: Conduct thorough testing of the SAP system to ensure that all
functionalities are working as expected.
 Backup Updated System: Perform another full system backup after the successful
completion of the update.

Best Practices

1. Test in Non-Production: Always perform updates or upgrades in a sandbox or development

environment before applying them to the production system.
2. Read SAP Notes: Review relevant SAP Notes for known issues, prerequisites, and additional
instructions.
3. Documentation: Maintain detailed documentation of the update process, including steps
taken and any issues encountered.
4. Monitor System: Closely monitor the system during and after the update to quickly address
any issues that arise.

By following these steps and best practices, you can effectively use the SAP BASIS Patch
Manager (SUM) to keep your SAP system current, secure, and performant.

4o