SAP Basis Upgrade Kernel Patching

Step by step how to upgrade and patch SAP Kernel.

Kernel is an executable program that exists between SAP Applications and Operating System. It consists of executable program under the path — "/sapmnt/<SID>/exe" for UNIX and \usr\sap\SID\SYS\exe\run Windows. It starts and stops application services such as message server, dispatcher, etc.

In Kernel upgrade, new .exec files replace old executable files in SAP system. To check the current version, use transaction code — SM51 > Go to Release Notes.

To check the status, go to System → Status tab → Other Kernel info

In UNIX, use disp+work − version to see information on the current Kernel version.

Follow these steps to download Kernel from SAP Market Place −

Step 1 − Open URL — https:\\service.sap.com and login with SID and password.

Step 2 − Go to SAP Support Portal from dropdown → Software Downloads.

Step 3 − Go to Support Packages and patches under software downloads. Go to Software Downloads.

All Kernel Versions are available in 64-bit −

Step 4 − Select the Kernel version and download the files as per the Operating System – Windows, Linux, Solaris, AIX, and HP-UX.

Upgrade Kernel Version

Let us now follow these steps to upgrade the Kernel version −

Step 1 − Create a directory with enough disk space and enter the name of directory.

Step 2 − Copy the upgrade files SAPEXEDB.SAR & SAPEXE.SAR files to the new directory at OS level.

Step 3 − To check directory, use 'pwd' to ensure you are in the same directory.

STep 4 − Now, uncompress .SAR files by sapcar exe.

SAPCAR –xvf sapexe.SAR

SAPCAR –xvf sapexedb.SAR

Step 5 − To take backup of existing Kernel, you have to create one more directory with the name "exe_old<ddmmyy>" and take backup of existing Kernel file.

Step 6 − To perform upgrade, stop the SAP application. You don’t need to shut down the database for Kernel upgrade but you need to stop the SAP application using this command — stopsap r3.

Step 7 − Copy the files from the new kernel directory exe_new<ddmmyy → to the existing kernel directory exe.

Step 8 − Use this command to copy — cp -rp /sapmnt/<SID>/exe_new<ddmmyy>/* /sapmnt/<SID>/exe/

Step 9 − Now if you check the current Kernel version using disp+work, then check the kernel version from OS level by the command disp+work − versions and new patch version should be displayed.

Step 10 − Login to the operating system as root specific to UNIX. Execute the script in Kernel directory — ./saproot.sh <SID>

You use this to assign correct permissions to all the executable programs in the kernel such as br* file etc.

Step 11 − Start SAP Applications using this command — startsap r3.

Step 12 − If you run Transaction SM52, you can see current kernel version level.

See also  SAP Basis Patch Management 

Uninstallation of SAP SMD Agent Using SWPM SP04

1. SAP Solution Manager Setup
2.   Diagnostics Agent

Переход к началу метаданных
In Installation of SMD Agent With SWPM SP04  we have seen how to carry out Installation of SMD Agent . Here we will see how to uninstall that using SWPM. You must delete a Diagnostics Agent instance only using SAPINST comes with SWPM  otherwise you might have problems with further installations on this host.  Before you go ahead with the removal of SMD Agent please make sure you have refre to the Section 4 of this SAP Note : 1833501  and Rule no # 6 of the attached document Agent Installation Strategy from SAP Note : 1365123


Rule No: 6 of SAP Note attached document 1365123

To remove a Diagnostics Agent instance installed for a specific hostname you must remove the JVM parameters described in the Introscope Setup Guide, which is available at service.sap.com/instguides.
Finally restart the Java Managed system to no longer run the Introscope Byte Code Agent
– The Managed System JVM parameters (to be removed) show that the Introscope Byte Code Adapter
executed inside the Managed System uses files from Diagnostics Agent directory structure:
Xbootclasspath/p:D:/usr/sap/DAA/SMDA77/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.3.5-2011-01-
14/wily/connectors/AutoProbeConnector.jar;D:/usr/sap/DAA/SMDA77/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.
3.5-2011-01-14/wily/Agent.jar
Section 4 of SAP Note : 1833501
Make sure to respect the section(s) dealing with "Uninstalling Introscope Agents" here [http://wiki.sdn.sap.com/wiki/x/kgELE].
SAP Note 1259982 documents "Deleting a Diagnostics Agent Manually" for UNIX Operating Systems.


following above instruction here below is the test case with steps, how would uninstall SMD Agent.















Note: If you have registered this agent to any SLD then it is also advisable to remove the agent detail from SLD using remove button on this below SLD screen.


1. 
   See also : Installation of SAP SMD diagnostics agent 
   SAP Solution Manager Diagnostics Agents

Installation of SAP SMD diagnostics agent

1. SAP Solution Manager Setup Diagnostics Agents

Перейти к концу метаданных

• Installation of SMD diagnostics  Agent With SWPM SP04

In the Diagnostics Agents page, we have seen Diagnostic Agent installation related Information and all key SAP Notes having all required detail. To summarize that info I would like to introduce some steps on how to install the latest Diagnostic Agent (includes SAP Host Agent). This Diagnostic Agent is compatible with any SP level of SAP Solution manager 7.1. Also, you don't have to do a separate SAP Host Agent installation, if you have followed these steps.You can also activate the Agents On-the-fly feature with this Diagnostic Agent.

Note:  When carrying out the below steps, make sure you have read and understood the Diagnostics Agent Installation Strategy PDF file attached with SAP Notes: 1365123  
            And sap note 1833501 for diagnostic agent installer version that is mentioned in the General Information section here: Diagnostics Agents. They explain the 
            strategy, download procedure, and installation details.

Note: These steps have been performed on MS Windows server 2003 Enterprise Edition X64 bit encoding, so in your case, the file name could be different.

Download and extract Installer media file.

To start the installation you need to first download the  Software Provisioning Manager 1.0 and their relevant kernel file. Once the correct files are downloaded have you need to unpack those.

Following these steps below you can download Kernal media file.







Once download is finished then you have to unpack these 2 files



Once you unpack those files then you have something like below ,  Once you see these files available then you are ready to launch the installation.



After launching SAPINST.EXE  you will have to select this option below to go ahead.

Here you need to select the path of Kernal file been extracted in the same folder D:\download_basket\SWPM_SP04\Krnl_7.20_WIN__IA32__IA64__x64__SP04_








Note : here on this step 2 user get created on OS level , you need to make sure on this server these users have admin level or rights also they should have full Read + Write + Execute access to any folder and subfolder available on this server.







Note : This part below registering to the SLD is not advisable with the newer Solution Manager system so this step could be ignored and direct do to the next step Connection of diagnostic agent with Solution Manager. 

On this step, if the user credential of target SLD system is correct then this agent get to register to the SLD. Here target SLD Could be any in your landscape usually you should connect this agent to the same SLD where your Managed system is reporting to using RZ70 or JAVA data supplier. This is an optional step but it is strongly advised to connect the agent with some SLD.

If you have SAP MMC Installed on the same server then you can see a new Instance of SMD Agent is available, should appear something like this below, from here you can start or stop agent.

 

To make sure in if the SMD Agent is connected to the SLD detail you have provided before, just logon to SLD and navigate to this below screen here you will see an agent instance is available under Diagnostic Agent Class.

See also: Uninstallation of SAP SMD Agent

SAP Solution Manager  Diagnostics Agents