The purpose of this upgrade, is to take advantage of BI export library 2.0 which is provided particularly in Netweaver 7.01 release for BEx broadcaster printing since ADS is not supported on AS/400.
Source system SPs and kernel patch
Source system database is 100GB, locates in a LPAR which has 0.8 physical CPU allocated. The entire upgrade process took about 8 hours, detailed phases below:
Preliminary tasks (load new kernel, prepare upgrade directory): 1hour;
Preprocessing: 5hours, in this case it might have some lock wait situation and
performance conflict with backup process;
Downtime upgrade: 1.5hours
Post processing: 20mins, not include another 2-4hours system compiling.
Afterwards, data growth is less than 5GB.
Upgrade steps:
1. Turn off MIMIX IFS replication, clear library MIMIX_A (if applicable)
2. Download EHPi from SWDC: Support Packages and Patches - Entry by Application
Group Additional Components Upgrade Tools SAP EHP INSTALLER SAP EHP INSTALLER 7.00 Patch level 17
Note: version 17 requires TP version 372.04.81 or higher, make sure you have it ready before preprocessing. Additionally, 701 kernel is compatible for 700 instances but for upgrade process only (refer to note 1284805), so it's safe and convenient to <br />apply latest 701 kernel library before starting the actual upgrade.) TYPE(ABAP) EPIPATH('/<installation directory>/ehpi') <br />SAPEPILIB(SAPEPI) SAPEPISRV(SAPEPISRV) <br />OPTIONS('jce_policy_zip=/<directory>/ehpi/SAPJCE.ZIP' '-srvarg=/RoleService/off')<br /><br /><br />9. Call SDTgui: http://<host>:4239</p><p>!https://weblogs.sdn.sap.com/weblogs/images/252007537/4239.JPG|height=437|alt=sdt|width=498|src=https...!</p><p> </p><p>10. Click next, EhpI recognizes this is an ABAP-only instance by loading its start <br />profile. If this is a dual stack instance, then you'll see another Java tag shows up.</p><p>!https://weblogs.sdn.sap.com/weblogs/images/252007537/01.JPG|height=492|alt=01|width=447|src=https://...! </p><p> </p><p> </p><p> </p><p> </p><p> </p><p> </p><p> </p><p> </p><p> </p><p> </p><p> </p><p> </p><p> </p><p> </p><p> </p><p> </p><p> </p><p> </p><p> </p><p> </p><p> </p><p> </p><p> </p><p>Note: For Java-only instance, using JSPM to patch directly to 701 support packages is a more effcient solution.</p><p> </p><p>11. Input keyword and download directory </p><p>!https://weblogs.sdn.sap.com/weblogs/images/252007537/02.JPG|height=377|alt=02|width=491|src=https://...!</p><p>12. Extraction step started, takes 30-45 mins.</p><p>13. At the beginning of step, configuration, you need to define resource mode of <br />this upgrade, apply the best in your case. !https://weblogs.sdn.sap.com/weblogs/images/252007537/03.JPG|height=296|alt=03|width=486|src=https://...!</p><p> </p><p>14. I recommend that not to choose system compiling here, because if enabled it'll <br />start SGEN as the first action in postprocessing phase. !https://weblogs.sdn.sap.com/weblogs/images/252007537/04.JPG|height=135|alt=04|width=385|src=https://...!</p><p> </p><p>Other features like memory optimized activator, TP parallel processing, there's no <br />negative impact to enable them as default.<br /><br />15. EhpI checks stack file for the target support package level, and other <br />components installed in this instance as well.<br /><br />16. Define instance number for shadow instance, profiles as well if you want it be <br />different from source instance. Phase configuration ends here.<br /><br />17. Phase check and preprocessing doesn't require manual input, at last asks you <br />whether to lock development.<br /><br />Note: one error of failed to start shadow instance could occur here:<br /><br />Check note 1291388:<br />Check the entry in the file: /usr/sap/BR2/EHPI/abap/BR2/SYS/global/ms_acl_info and <br />correct the entry. If required, enter HOST=
18. Preprocessing finished, now has reached downtime phase, backup all journal
receivers and delete them
19. In phase postprocessing, it reminds you to re-enable scheduled batch jobs which
are suspended by upgrade process by report BTCTRNS2.
20. Bravo!
Target system SPs and kernel patch!https://weblogs.sdn.sap.com/weblogs/images/252007537/07.JPG|height=442|alt=07|width=439|src=https://...!</body>
