Guide to Patching your SAP System

I need to upgrade our internal demo systems every once in a while. Now, as I don’t unleash my Basis skills on customers everyday I tend to forget how its done. I decided to record the steps here to save me a bit of time next time around. Please treat any advice given here with care(I’m no expert at this) and read the official guides and help files.
Applying patches to an SAP system is not as simple as, say updating your Windows PC. There is no auto update or one click upgrade process. I will be surprised if there ever will be. The thing is, SAP actually allows you a lot of freedom and flexibility in changing the way it works(Windows doesn’t). The price you pay is a slightly complex upgrade process.
Doing a full Support Pack update of an SAP system broadly involves the following:
1. Log in to the Service Market Place and select the packages to be downloaded. Admittedly, this is a bit easier now with SP Stacks.
2. Log on to your Solution Manager System(Maintenance Optimizer) to confirm your download basket. If you don’t do this you can’t download your Patches. I must still figure out what the benefit of this is.
3. Download the files using the SAP Download Manager.
4. Use sapcar to extract the patches. You can use the command sapcar -xvf from command line to do this. An easy way to extract these files in Windows is to register the extensions .CAR or .SAR to open automatically in Explorer.
You can do this by opening Windows Explorer and going to Tools->Folder Options and clicking on the File Types Tab.
Create a new type for the .CAR/.SAR file types and create a default action as shown in the screen shot below( Copy SAPCAR.EXE to your C:Windows directory first).

SAPCAR Image

You can now “mass extract” all your patches at once by selecting all 50+ files in Windows Explorer and hitting enter on them. If you do this on a laptop now would be a good time for a coffee break.
5. Now the real upgrade can start. Always update your kernel to the latest release first. This involves the following:
• Determine your global kernel directory. Goto transaction AL11 and look for directory mapped to DIR_CT_RUN. In my case(on Linux) this is /usr/sap//SYS/exe/run.
• Log in with your adm user. This will ensure you preserve the correct rights to your files.
• Backup this directory by copying it to somewhere safe.
• Overwrite the files in your DIR_CT_RUN directory with the new kernel files extracted in step 4. These files aren’t used by the SAP System, so you can safely overwrite them while the system is still running.
• On Windows I would recommend rebooting the box, on Unix environments you only need to stop and start the instance.
• During the startup of the instance a program called sapcpe will copy the new kernel files in DIR_CT_RUN to DIR_EXE_ROOT(usr/sap//exe).
6. Now, do a full off line database backup and keep in a safe place.
7. Copy the ABAP Support Pack files extracted in Step 4 to the following location on the SAP Server: /usr/sap/trans/EPS/in.
8. Log on to the SAP System in client 000 with your own user(not SAP* or DDIC).
9. Execute transaction SPAM(what a name…).
10. Load the Support Packages. On the SPAM main menu goto Support Package->Load Packages->From Application Server.
11. Now we hit the stage where P.P.P.P.P.P. You have to read all the notes on all the patches for all the components you want to upgrade. There are many dependencies here and it is easy to stuff up. But a few points:
• Make sure TMS is configured properly and actually working(i.e. test with a transport). This is important on new installs and has burned me in the past.
• Always upgrade SPAM to the latest version first. Always!
• Read the notes on optimal queue definitions, make them as long as possible, but keep the next point in mind…
• Don’t overshoot(see note 70228 for explanation). This is critical if you have add-ons such as XRPM, WFM or even CRM 2007(which now requires a CRT(Conflict Resolution Transport) after every ABAP support pack).
• Write down all the steps you took and queues you used as this will help in the upgrade of downstream systems.
12. If you read the plethora of notes before hand and manage to follow them correctly everything should go fine.
13. If you do it Cowboy style(and ignore point 12 like I do ), SPAM failure is likely. You could try the following, in order:
• Restart the Process. Always do this 2 or 3 times before proceeding, especially with BASIS/ABAP support packs.
• Search for notes on the Service Market Place. You are probably not the first one to mess up. Also, sometimes the support packs contain errors.
• Try to reset the queue and process again.
• If you absolutely have to back out and SPAM does not allow you to reset the queue, you can do the following if you are brave. Run Function Module OCS_RESET_QUEUE in SE37 with the parameters IV_TOOL=SPAM and IV_FORCE=X. Just realize that this will leave your system in an inconsistent state. You may need to do some significant manual fixing.
• Log it with SAP.
• Restore your backup and try again.
Eventually you should have an up-to-date, everything recompiling, SAP System.

Source : johanvanzijl.com

Leave a Reply

Your email address will not be published. Required fields are marked *

seventeen + 12 =

Time limit is exhausted. Please reload CAPTCHA.