7/4/2014 #sapadmin:: EHP Technical Checklist & Best ... | SCN

http://scn.sap.com/community/enhancement-packages/blog/2012/03/28/sapadmin-ehp-technical-checklist-best-practice-catalyst-to-a-successful-upgrade--part-i 1/2

Getting Started Newsletters Store

Products Services & Support About SCN Downloads

Industries Training & Education Partnership Developer Center

Lines of Business University Alliances Events & Webinars Innovation

Log On Join UsHi, Guest Search the Community

Activity Communications Actions

Browse

SAP Enhancement Packages

Previous

post

Next

post

Tweet

To ensure a successful EHP upgrade, technically (this blog is focus on the technical aspect, which doesn't coverfunctional) , it is important and critical to have a proper planning, preparation, understand what's happening behind foreach critical process (especially during DBCLONE, DDIC_UPG, ACT_UPG, SHADOW_IMPORT_INC andTABIM_UPG and etc); which log file, program to investigate in case of error. Sometimes, we are in an awkwardsituation when there's no status indication for long running job, no update to the log, and you see no wps, TP, R3transis running, you start getting worry and unsure is your upgrade hung or still running.In this blog, I've summarized the catalyst to a successful EHP upgrade which comprise of general planning +preparation, critical & long running EHP upgrade processes. MOPZ is not cover here. I'll focus more on EHPI,nevertheless, it can be used as a reference for SAPup, since most of the steps, processes are identical.

SAPehpi Tool:SAPehpi is used when upgrade SAP ERP 6 to EHP*, SAP EHP4 for ERP to EHP5, SAP NW 7 to SAP NW EHP* andSAP EHP1 for NW 7 to SAP EHP2 for NW7.

General Planning + Preparation:

EHP Installation/ Upgrade Guide ::Download all the related EHP upgrade guide from SMP and read thruevery section, ensure you understanding what you are reading.

Mandatory guide ­ How to install Enhancement Package 4/5 for SAP ERP 6.0 or How to install Enhancement Package2 for SAP NW 7.0, Installation Guide ­ SAP EHPI, using SAP Enhancement Package Installer (SAPehpi) 7.00 , Masterguide.* Most of the preparation task which covered in upgrade guide such as ensure no canceled update in SM13, noinbound/ outbound queue in SMQ1/SMQ2, invalidate temp object in SE14, etc are not covered here.

EHP Upgrade Notes :: SAP Notes highlighted in the installation guide, sub­notes that mentioned in each andevery note are important. Go thru every note to identify is this relevant to your application.

Mandatory SAP Notes ­Note 822379 ­ Known problems with Support Packages in SAP NW 7.0x AS ABAP ­ Check all notes that are relatedand relevant to your System.Note 1302772 ­ Central Note ­ SAP Enhancement Package Installer 7.00 ­ Carefully go thru and implement therecommendation, for example:­­­­­­­­­­­­­­­­­­­­­< D030559 MAY/06/05 >­­­­­­­­­­­­­­­­­­­­­­­­­­­­Increase Parameter em/initial_size_MBTo avoid a runtime error in the RUN_RSAIMMERGE_UPG phase, increase parameter "em/initial_size_MB = 1024" to"em/initial_size_MB = 4096" in the instance profile of your target system. ­­> this mean that at least 4096 MB set forem/initial_size_MB.SAP Notes for product, OS and DB specific mentioned in Central Note are critical. It is important to follow andimplement the recommendation to mitigate all possible errors during upgrade.For example, if your DB platform is Oracle, you need update statistic, increase open_cursors, processes & sessionsparameter before upgrade by following Note 1161052 ­ Add. Info: SAPehpi/SUM for Systems on Oracle

SAPehpi version :: Always download the latest SAPehpi tool available in SMP. This is critical as the latestSAPehpi will avoid expected & unexpected bugs.

Use the latest SAP binary:: Ensure MOPZ is generated accordingly and correctly. All download SPs, Kerneland Stack.XML are copied into download directory. Besides Kernel downloaded during MOPZ generation,please check any updated SAP Kernel (SAPEXE, SAPDBEXE and DW package), lib_dbsl, TP, R3trans andR3load (for SAPup) available in SMP. If yes, please download and copy them to the download directory. Errorsand bugs can be avoided by using the latest binary.

SAPehpi will extract dw, TP and R3trans to the exe and exenew automatically. At the end of "Configuration" phase:

#sapadmin:: EHP Technical Checklist & Best Practice,catalyst to a successful Upgrade ­ Part IPosted by Nicholas Chang in SAP Enhancement Packages on Mar 28, 2012 10:59:22 AM

7/4/2014 #sapadmin:: EHP Technical Checklist & Best ... | SCN

http://scn.sap.com/community/enhancement-packages/blog/2012/03/28/sapadmin-ehp-technical-checklist-best-practice-catalyst-to-a-successful-upgrade--part-i 2/2

Follow SCNSite Index Contact Us SAP Help PortalPrivacy Terms of Use Legal Disclosure Copyright

Average User Rating

(3 ratings)

Tweet

Space :: Ensure sufficient space is allocated before start the upgrade. Example of approximate spaceneeded:

EHPI Directory ­ 30 ­> 50GB (depends on how many SPs you downloading & upgrading)Download Directory ­ 20 ­> 40GB (depends on how many SPs you downloading)DIR_TRANS ­ 30 ­> 50GBDatabase free space ­ approximate 20 ­> 40% of your current Database size. Again, this is highly depends on howmany level of Software Component s you are deploying. Large space is needed to build and store shadow repositoryin your current database. However, there's < 10% increase of your current DB size after upgrade as the old DDIC,nametab, and etc will be deleted and replaced.*EHPI will alert if insufficient DB free space at the end of "Check" phase. For Oracle, you need to create tablespacePSAPSR370X manually.Take my recent upgrade for example:DB size before upgrade ­> 348GBDB size after shadow repository created (end of "Pre­Processing") ­> 420GBDB size after upgraded to EHP5 (downtime completed, before SGEN) ­> 350GB (sometimes you'll notice your DBsize is slightly smaller or same with size before upgrade due to the DB­Platform specific compression feature, eg:MSSQL 2008)

SPAM :: Update your SPAM to latest level available in SMP

Source Kernel :: Update your source kernel to latest level as well. Again, this action can avoid time‐consuming error investigation.

To make this useful to every #sapadmin, valuable and kind input is mostly welcome. Let's make this a brainstormingsection ;­)I'll talk more on the long running upgrade process in Part II, and thing to look into for each critical process, whatprocess is running and what log to check in case of error.

11427 Views Topics: technical_operations Tasks: upgrade Tags: ehp

1 Comment

Like (0)

Jose Carlos Valiente Chunga Jul 25, 2012 8:09 PM

Hello Nicolas, I just finished implementing ERP 6.0 EHP4 during the process,searching information in SCN your comments help me as well as the friend Sunny Pahuja.Thanks for sharing, Jose Carlos Valiente.