Ready a kernel patch for application in SAP

Prepare a SPAM/SAINT Update or Support Package for Application

Once you have downloaded your SPAM/SAINT Update and/or support package(s), they must be moved to the appropriate transport directory and uncompressed.

1.               For a SAP instance, move the downloaded K*.?AR file to the /usr/sap/trans/tmp directory on the SAP Transport Domain Server which is normally the DEV server of a SAP “Flavor”.

2.               Log on to the appropriate server as <sid>adm.

3.               Type the following:

cd /usr/sap/trans ¬

SAPCAR.EXE -xvf “tmp\*.?AR” ¬

This will unCAR all CAR and SAR files in the \usr\sap\trans\tmp directory to the /usr/sap/trans/EPS/in.

4.               Log off the server.

5.               Log on client 000 of the appropriate SAP system.

6.               Go to transaction SPAM.

7.               From the menu bar of the Support Package Manager screen, click Support Package → Load Packages → From application server.

8.               On the SPAM: Confirm upload popup, click the green √ picture-icon.  The progress of the support package loads will show in the status bar at the bottom of the screen.

9.               Scroll down the SPAM: Uploading Packages from the file system screen to make sure your SPAM/SAINT update is listed.  Use the Go Back icon to return to the previous screen.

10.           You may now leave the SPAM transaction.

Check for New SPAM Updates, Support Packages and Kernel Patches in SAP

Apply support packages in SAP

Apply other SAP binary patches in SAP

Apply kernel patches in SAP

Application of SAP Kernel Patches

*** It is recommended that the /usr/sap/<SID>/SYS/exe/run directory be copied to /usr/sap/<SID>/SYS/exe/backup_run before replacing the kernel ***

1.               Log on to the appropriate server as <sid>adm.

2.               Double check that the SAP instance, SAPOSCOL, and SAP<SID>_00 services are stopped.

3.               To apply the new kernel patch to a R/3 instance, copy the new files into usr\sap\<SID>\SYS\exe\run directory.  If prompted for overwrites, say yes to all.

4.               After the new kernel has been copied make sure that the following file ownerships are correct:

All files in /usr/sap/<SID>/SYS/exe/run   <sid>adm

/usr/sap/<SID>/SYS/exe/run/saposcol       root

/usr/sap/<SID>/SYS/exe/run/br*            ora<sid>

/usr/sap/<SID>/SYS/exe/run/sapdba         ora<sid>

5.               After the successful completion of the kernel patch, you may bring the instance back up and log off the server.

Apply a SPAM\SAINT update in SAP

Application of SPAM/SAINT Updates

Before you apply the most current SPAM/SAINT, please pull the OSS Note 484219 - Known problems with transaction SAINT in Basis Release 6.20 or for whatever version you are using and review any problems you may have adding the SPAM/SAINT patch.

Once you have loaded the latest SPAM/SAINT update into your support Package manager buffer, you need to apply the update to your SAP system.

1.               Log on client 000 of the appropriate SAP system.

2.               Go to the SPAM transaction.

3.               From the menu bar of the Support Package Manager screen, click Support Package → Import SPAM/SAINT update.  Click the green √ picture-icon to continue.

4.               The progress of the SPAM/SAINT update application will be displayed in the status bar at the bottom of the screen.  These messages look very similar to the messages generated during a change request transport.

5.               When the Restart SPAM popup appears, click the green √ picture-icon to leave the SPAM transaction.

6.               Go to the SPAM transaction.  You may notice programs compiling in the status bar at the bottom of the screen.  This is normal.

7.               Once you are again on the Support Package Manager screen, verify that the SPAM status in the Status section of the screen contains a green light.

8.               You may now leave the SPAM transaction.