I was becoming crazy since I couldn’t find the reason. The scope of this search was from performance issues in the SAP GUI to problems with the rendering of the SAPGUI or even incompatibilities between VPN clients with the SAP GUI. Checked for SAP Notes in the Support Portal for almost two months.I took a look at the loaded DLLs in the SAP GUI before and after using it.Checked on the Performance Monitor the performance of the disk, CPU, RAM, etc.I know it sounds crazy but the problems started when I updated Firefox to the new Quantum version. Stopped using Firefox Quantum and use Google Chrome.This seems to help a bit but after some minutes the performance is the same as before. Closed processes running on the task manager.
Patched to the latest patch available for both SAP GUI 7.40 and 7.50.Installed the version 7.40 of the SAP GUI, including the SAP GUI for S4HANA.Reinstalled completely the SAP GUI, even in a different disk.I tried a lot of different things to fix this: When I restart my computer everything works correctly but after a couple of days working the SAP GUI becomes unusable. Read the DMO introduction PDF document.Since a two months ago I’ve noticed that the performance on SAP GUI 7.50 is getting worse.Go to the Support Portal DMO page for an introduction and links to detailed SAP Community Blog Posts.The technical unicode conversion can be part of the DMO procedure if the target software level is lower than SAP BASIS 7.50. In addition, it is possible to change not only the database (host), but also the Application Server: DMO with System Move. Now, DMO allows for migration to other database types than SAP HANA database (see respective SAP note for details and restrictions) and DMO can be used for a pure migration, without changing the SAP software level: DMO without System Change. At this time, only the combination of upgrade and migration was possible, since typically the source system was not yet on a software level that is supported by SAP HANA database. The Software Update Manager offers the Database Migration Option (DMO), which is the combination of the SAP software update with the database migration.ĭMO was initially a procedure to migrate to an SAP HANA database only. Reason is that Oracle and SAP HANA clients require EXT kernel (not relevant for SUM 1.1, as SUM 1.1 is only provided for EXT-kernel anyhow)Ī database migration transfers the SAP system from one database type to another. You need the archive with HDB in the name whenever an SAP HANA or an Oracle database is part of your scenario: either your system is running on Oracle or SAP HANA database, or you intend to migrate your system to SAP HANA database (using DMO of SUM). SUM10HDBSP26 versus SUM10SP26, depending on the involved database:.SUM 1.0 SP 26 archive is only available on request:Ĭreate a case on component XX-SER-SWFL-SHIP with reference to SAP Note 2882395, and request to forward the case to component BC-UPG-TLS-TLA.for source releases based on SAP BASIS 4.6C, 6.20 or 6.40.for source releases based on SAP BASIS 7.00 and higher (SUM 1.1 archive is available in the download area).SUM 1.1 SP 00 (and higher) is the successor of SUM 1.0 SP 28.SUM 1 versions, depending on the source release: SUM 1 is used if the source system is either a dual-stack system, or a Java stack, or for ABAP stack if target is based on BASIS 7.40 or lower.SUM 2.0 is used for System Conversions, for ABAP single stacks targeting systems based on BASIS 7.50 and higher, and for ZDO.SUM 1 versus SUM 2.0: each scenario is covered by only one of the SUM versions, depending on the target release: