Kernel Patch Upgrade in MSCS setup

Introduction:

This document is intended to outline the steps to upgrade SAP 7.20 kernel patch on MSCS set up. There may be confusion on the MSCS set up as to what exactly needs to be done and after successfully carrying out this activity recently I feel this document will benefit other fellow members. I will try to put the screens wherever necessary to explain the step.

Overview:

This document contains steps to upgrade SAP Kernel 7.20 from Patch level 105 to Patch level 201

Technical Information:

Kernel 7.20

Windows 2008 Enterprise Editon Service Pack 2

Oracle 11g

Pre-requistes:

a. Download the latest Kernel Patch from http: service.sap.com/swdc->Support Packages and Patches -> A - Z Index -> E -> SAP ERP -> SAP ERP ENHANCEMENT PACKAGE -> Choose your Version -> Entry by Component -> ABAP Technology for ERP EHP 5 -> SAP Kernel 7.20 64-Bit Unicode

you need to download the following files:

SAPEXE_201-10007272.SAR (this file is available under 'database independent' title)

ntclust_2-10007272.sar (this file is also available under 'database independent' title)

SAPEXEDB_201-10007270.SAR

b. Take backup of your existing Kernel directory: ie: \usr\sap\SID\SYS\exe\uc\<os platform>

you can also find this directory by checking in RZ11 the value of parameter DIR_CT_RUN

c. It will also be better if you take an image backup of your C: drive

d. Always perform the Kernel Upgrade first in your test system to check for any errors. Once its verfied only then Upgrade in Production.

Procedure::

1. Take backup of your existing kernel directory:  \usr\sap\SID\SYS\exe\uc\<os platform>

2. Take backup of C:\windows\sapcluster on all MSCS nodes

3. Take backup of C:\Windows\system32\SapClus.dll on all MSCS nodes

4. Unpack the latest kernel (201) using the following command

SAPCAR -xvf SAPEXE_201-10007272.SAR

SAPCAR -xvf SAPEXEDB_201-10007270.SAR

SAPCAR -xvf ntclust_2-10007272.sar

same way you need to extract SAPEXE & ntclust.sar

5. Shutdown SAP System

6. Take SAP Service offline (from Failover Cluster Management)

7. Shutdown database (from Oracle Failsafe Manager)

8. Now, start copying the latest kernel files(kernel 201) to your existing kernel directory

Select 'Copy and Replace' option

6. Now Update the files on all cluster nodes in the Windows\SAPCLUSTER directory with the corresponding files in the central kernel staging directory.

7. Next, we have to update SapClus.dll file

when you run SAPCAR on ntclust.sar file, following folders will be available

In the NTCLUSTER sub-folder, you will find 'SapClus.dll' file

We need to copy 'SapClus.dll' to C:\Windows\System32 on all MSCS nodes

NOTE: Although on some scn threads it is said to update 'Saprc.dll' & 'Saprcex.dll' also but we only copied 'SapClus.dll' and our Kernel Upgrade went fine. We performed both the switchover & failover test for our MSCS nodes and it was successful.

8. Now restart the database and bring the SAP services online

9. Next, Re-start SAP system

NOTE: The instance restart will take 5 - 10 mins and if you have one or more dialog instances then you do not need to update them separately.

10. Finally, Perform the MSCS Switchover/Failover test to confirm the successful upgrade of the kernel patch.

Result:

Your have upgraded your kernel patch on MSCS setup.

Upgrade SAP Kernel

(a) Login to the ABAP system
     (b) Execute transaction SE38
     (c) Specify Program GRAPHICS_IGS_ADMIN
     (d) Click Execute (The RFC destination for the IGS should automatically populate)
     (e) Click Execute
     (f) The version will be displayed (e.g. 7000.0.10.1)
1.stop the sap
2.kill oscol,
3. clean unused libraries from memorey
   sudo /usr/sbin/slibclean
4.Make a backup copy of the current kernel as follows:
     (a) cd /usr/sap/<SID>
     (b) rm -rf oldkernel (this command may error if the directory does not exist)
     (c) mkdir oldkernel
     (d) cd /sapmnt/SBX/exe
     (e) cp -rp * /usr/sap/SBX/oldkernel
      f) mkdir /usr/sap/<SID>/oldkernel/igs
     (g) cd /usr/sap/<SID>/DVEBMGS*/igs (cd /usr/sap/<SID>/JC*/igs for non-ABAP systems)
     (h) cp -rp * /usr/sap/<SID>/oldkernel/igs

5. Change the file ownerships as follows to minimize extraction errors as follows:
     (a) cd /sapmnt/SBX/exe
     (b) sudo chown sbxadm:sapsys *
     (c) sudo chown -R sbxadm:sapsys cfw
     (d) sudo chown -R sbxadm:sapsys jkit
     (e) sudo chown -R sbxadm:sapsys servicehttp
6.cd /sapmnt/SBX/exe
   cp -pfr /usr/sap/trans/newkernel/* /sapmnt/SBX/exe

 Extract the new kernel files as follows:
    Note: Steps (e) through (g) are only appropriate for SAP Basis release 7.00 or higher
     (a) cd /sapmnt/<SID>/exe
     (b) mv SAPCAR SAPCAR.old    
                (SAPCAR is delivered in the new files and needs to be renamed)
     (c) ./SAPCAR.old -xvf /usr/sap/trans/new_kernel/SAPEXE_201-20000978.SAR
                (If a file cannot be overwritten, rename the filename to filename.mmddyyyy and repeat)
     (d) ./SAPCAR.old -xvf /usr/sap/trans/new_kernel/SAPEXEDB_201-20000977.SAR
                (If a file cannot be overwritten, rename the filename to filename.mmddyyyy and repeat)
      (e) ./SAPCAR.old -xvf /usr/sap/trans/new_kernel/dw_218-20000978.sar
      (e) SAPCAR -xvf /usr/sap/trans/newkernel/igs<restoffilename>
                (If a file cannot be overwritten, rename the filename to filename.mmddyyyy and repeat)
     (f) cd /usr/sap/<SID>/DVEBMGS* (/usr/sap/<SID>/JC* for non-ABAP systems)
     (g) SAPCAR -xvf /usr/sap/trans/newkernel/igshelper<restoffilename>
                (If a file cannot be overwritten, rename the filename to filename.mmddyyyy and repeat)

7. Set the permissions of the kernel files and saposcol as follows:
     (a) cd /sapmnt/SBX/exe
     (b) sudo cp saproot.sh /usr/sap
     (c) sudo /usr/sap/saproot.sh SBX
     (d) sudo chown root saposcol
     (e) sudo chmod o+s saposcol

8. Start the SAP system as per the customer policies and procedures document

Installing the Database Shared Library (DBSL)

PurposeThe database-dependent part of the SAP database interface can be found in its own library that is dynamically linked to the SAP kernel. This database library contains the Database Shared Library (DBSL), as well as libraries belonging to the corresponding database manufacturer. These are either statically or dynamically linked to the database library.
When initiating an SAP system, the database-dependent database library is loaded before the DBSL is called up for the first time. The system searches for the library in the directory indicated by the environment variable DIR_LIBRARY (for example,. /usr/sap/<SAPSID>/SYS/exe/run). The environment variable dbms_type contains the name of the required database management system. When the system is initiated, an attempt is made to load the library belonging to the required database management system from the directory indicated by the environment variable DIR_LIBRARY.

You can find additional information about the database library in the SAP note 400818 - Information about the R/3 Database Library.One of the advantages of this architecture is that a work process can include connections for several different databases belonging to different manufacturers.
To be able to transfer DB Connect data into a BW, you need to have installed the SAP-specific part of the database interface – the DBSL for the corresponding source-database management system for each BW application server.ProcessThe database library is made available in the SAP Service Marketplace in the SAR archives LIB_DBSL.SAR, in the patch directories, which are independent of database manufacturer.

1. You can access the required directory via the Software Center of the SAP Service Marketplace in the Internet, via the following address: http://service.sap.com/swcenter-main ® SAP Web AS ® Relevant SAP Web AS Release ® Binary Patches ® Relevant SAP Kernel Release ® BW Application Server Operating System ® Source-Database Management System® LIB_DBSL.SAR.

2. Load the file into the directory indicated by the environment variable DIR_LIBRARY.

The file LIB_DBSL.SAR forms a complete SAP kernel patch together with the database-independent DW.SAR archive. (SAP Note 19466 - Downloading SAP Kernel Patches describes how kernel patches are imported).

3. Next, unpack the SAR archive with the SAPCAR tool. Before doing so, refer to note 212876- The New Archiving Tool SAPCAR

We recommend you also download the latest DBSL from the SAP Service Marketplace for SAP DB databases.ResultIn the directory defined in the environment variable of the BW Application server, you can find the library db<dbs>slib.<ext>, where <dbs> is the SAP-specific ID for the database management system and <ext> stands for the enhancement of the shared libraries in the respective operating system.

The database library for the Oracle database management system in Windows is called dboraslib.dll.After the database-specific DB Client has been installed, all installation prerequisites for using DB Connect are met. You get information about the database-specific DB client from the respective database manufacturer.