1   2   3   4   5   6   7   8   9   10   11   12  13  14  15 …

In order to apply new support packages and kernel patches to a SAP system, several preparation steps are required:

 

·         Checking for new SPAM updates, support packages and kernel patches

·         Downloading the new SPAM updates, support packages, and kernel patches

·         Preparing the new SPAM updates, support packages, and kernel patches for application

·         Applying the new SPAM updates, support packages, and kernel patches

·         Mass recompiling all programs used in patched components

 

Be aware that SPAM/SAINT update and support package application occurs within the SAP system using the SPAM transaction. These corrections are changes to ABAP program code and must be handled in a special way by SAP.  Kernel patches, on the other hand, are fixes to SAP executables found on the SAP server.  Kernel patches must be applied when the SAP instance is down.

 

Please refer to the Check for New SPAM Updates, Support Packages and Kernel

Patches.

 

To check if SAP has released any new software fixes for your release of SAP, you need to know your current support package and kernel release levels.

 

The patching process consists of:

 

-        finding you current patch levels

-        finding what patches you should be applying

-        downloading the patches

-        unCARing the patches

-        loading the patches into the patching EPS queue

-        applying the patches

 

Read More…

Steps for SAP System Copy.

1. Take offline backup of both the server (source and target servers)

2. Verify the backup is successfully done.

3. Run the following command on source system.

       a. Login as adm

       b. svrmgrl

       c. connect internal

       d. alter database backup controlfile to trace;

       e. exit;

       f. Above command will generate a .trc file in  /oracle/P01/saptrance/usertrace directory.

       g. Copy the text from CREATE CONTROLFILE until the (;) and paste it in to any new .sql or controlfile.sql file.

       h. Copy the controlfile.sql to target system..

       i. Edit the file and replace the entire source SID to target SID.

       j.. Edit the reuse database command with the set database command

Read More…