Blog Series: Solution Manager 7.2 SP 08 Upgrade+Migration Using SUM-DMO Approach
Solution Manager 7.2 SP 08 Upgrade and Migration to Hana using SUM DMO Approach
This blog series is all about recent update on Solution Manager Support Pack 08 will be the minimum Support Pack required by Jan 2020
In this blog I would like to share my experience How I performed Upgrade of Solution Manager 7.2 SP 04 To SP 08 and migration from Oracle to Hana database using SUM DMO approach.
->Upgrade your SAP Solution Manager system to version 7.2 and migrate your AS ABAP system to SAP HANA or SAP ASE in one step with the Software Update Manager (SUM).
Here in my scenario ABAP and JAVA system are independent , it is not dual stack .
Please find the series of Solution Manager 7.2 SP 08 Upgrade and Migration to Hana using SUM DMO Approach blog links at the end of this blog page.
->You can find out more about DMO, the blog post Database Migration Option (DMO) of SUM – Introduction is a good introduction to start .
Why we need to Upgrade Solution Manager 7.2 SP 08 ?
SAP Solution Manager 7.2 SP 08
Support Pack 08 will be the minimum Support Pack required by Jan 2020 (Connectivity to SAP’s Support Backbone)
Key new features are:
- Mass Change for documents and Mass downloads
- New Cloud Monitoring templates for Ariba, S/4 HANA Cloud, Concur, Field glass
- Custom E-mail Notifications
- Backbone HTTPS connectivity
See Solution Manager SP08 for full details.
SAP’s Support Backbone
SAP’s support backbone is the central infrastructure located at SAP to provide technical support to our customers.The support backbone consists of several different systems for different purposes – for example, it provides the SAP Support Portal infrastructure, the Maintenance Planner, SAP Early Watch Alert Reports, and many more.
SAP’s support backbone has been updated. The legacy infrastructure remains in place to allow a safe transition for customers. Customers need to switch to the new infrastructure before January 2020 to ensure continuous connectivity
SAP Solution Manager: Affected capabilities
- Landscape synchronization with SAP (automatic update of customer system data, used for Maintenance Planner)
- Remote Service Connection Management from SAP Solution Manager
- System Recommendations
- Automatic distribution of licenses and maintenance certificates
- Scope and Effort Analyzer
IT Service Management
- Exchange of messages with SAP
SAP Engagement and Service Delivery
- Service Delivery
- SAP Early Watch Alert from SAP Solution Manager to SAP
- Service Content Update
Existing RFC connections to SAP
New connections to SAP
After January 1st, 2020:
- SAP Solution Manager 7.2 systems on SPS 06 and earlier support package stack levels cannot communicate with SAP Support Backbone.
- SAP Solution Manager 7.0 and 7.1 releases cannot communicate with SAP Support Backbone after January 1st 2020 and need to be upgraded to SAP Solman 7.2 SPS 08
Areas “outside” SAP Solution Manager and Focused Run are affected by the update of the Support Backbone. Please refer to the overall landing page for more information.
How the SAP Support Backbone update affects SAP Solution Manager and Focused Run
Synchronization of system data with SAP Support Portal in Solution Manager 7.2 has changed.
If you are using Solution Manager 7.2 Support Package 5 and higher and want to upload data to the Sap Support Backbone, upload functionality has been changed.It still uploads system data into the SAP Support Backbone but it uses a different format and mechanism to select the relevant data.
As described in note 2177157:The existing jobs will be replaced that have uploaded system data up to now.
- LANDSCAPE_FETCH (obsolete already since ST 720)
- SM:UPLOAD SYSTEM DATA
For the time being, SM:UPLOAD SYSTEM DATA and SM:LMDB GENERIC UPLOAD will run in parallel. The data upload within that jobs can be switched centrally by SAP, so no further customer action will be required for retirement of the old upload.
Report RLMDB_UPLOAD_FEATURE_STATUS shows which upload mechanism is active in your system.
Upload Job cycles
Job SM:LMDB GENERIC UPLOAD runs hourly. In every run, the LMDB generic upload receives data from and puts data into the so-called postbox of the Support Hub Connectivity. Support Hub Connectivity collects data packages once every hour from the postbox. Thus, it may take two hours at maximum until a requested system data change in LMDB is sent to the SAP Service Backbone.
Support Hub Collection in SAP Service Backbone allows postbox access also on an hourly base. So in the most unfavorable case, it takes another hour until the requested system data change can be processed in the Service Backbone.
If it is really urgent, you can still force the immediate upload for a selected system in the technical system editor (transaction LMDB). On the “SAP Support Portal” tab, choose the “Upload to SAP Support Portal” button. However, due to the reduced delay of uploading changes automatically and the book-keeping of data supplier registrations without changes, a manual upload should not be needed in most situations.
As a prerequisite, you have to make sure that the Support Hub Connectivity is working properly via SOLMAN_SETUP –> Mandatory Configuration –> System Preparation –> Set Up Connections to SAP –> Support Hub Connectivity. This will automatically schedule the job SM:AGS_SISE_SUPHUB_OUTBOX_PROCESS.
Cross Check Of Uploading Data
Report RLMDB_UPLOAD_FEATURE_STATUS shows whether the new upload mechanism is active already in your system. Use SM37 to check both requried jobs, SM:UPLOAD SYSTEM DATA and SM:LMDB GENERIC UPLOAD and their logs. The log of SM:LMDB GENERIC UPLOAD should reflect the following three phases:
- Retrieve data requests and settings from SAP Support Backbone.
- Collect payload according to the data requests and send it.
- Prepare metadata about data changes and send it.
Please also find more detailed logs via report RLMDB_UPLOAD_DISPLAY_LOG.
seamless use of Solution Manager 7.2 :After upgrading to SP 08, the number of SAP Notes to be applied have been significantly reduced.
Eight is Great. Watch this video for details: https://www.msgp.pl/vmoTRow
How To Prevent Know Issues
->The job SM:UPLOAD SYSTEM DATA failed with ABAP dump CX_LMDB_SERVCON_NO_SUCH_SYSTEM after upgrading to Solution Manager 7.2 SP 08. Ensure that the following note is implemented- 2751217
->Facing issue in step 2.1 “Define HTTP Connectivity” under scenario “Infrastructure Preparation” in SOLMAN_SETUP? Check the guided answer link below https://www.wbca.st/c5AM8Cw
->If you’re facing error in Activity ‘Check Java Software Prerequisites’ in Step 2.2 ‘Enable Connectivity’ under Infrastructure Preparation in Solution Manager 7.2 SP 08, implement this correction-2739682
->Scope Selection does not work in several applications after upgrading to Solution Manager 7.2 SP 07-SP 08, to resolve please refer note 2652988
->IMPORTANT If you are upgrading SAP Solution Manager 7.2 to SP 08, you need to follow the steps in this KBA to avoid dumps when accessing Solution Documentation. https://www.wbca.st/YxFY04w
For Solution Manager 7.2 SP 08 following knowledge article has been updated with important notes,Implement the recommended notes to prevent known issues-https://www.wbca.st/Bt9lEcw
To get all the latest information about SAP Solution Manager right in your mobile device? Watch this video for more information.
Now lets start with the actual process of Solution Manager 7.2 SPS 08 Upgrade and Migration to Hana using SUM DMO Approach for ABAP system and SWPM heterogeneous export import procedure for Java system in the following blog series:
This series of blog posts will cover the following topics in sequential order:
Solution Manager 7.2 SP 08 Upgrade and Migration Using SUM DMO Approach – I – Generate Stack File – ABAP Stack
Solution Manager 7.2 SP 08 Upgrade and Migration Using SUM DMO Approach – II – Preparations – ABAP Stack
Solution Manager 7.2 SP 08 Upgrade and Migration Using SUM DMO Approach – III -A– Upgrade+Migration – ABAP Stack
Solution Manager 7.2 SP 08 Upgrade and Migration Using SUM DMO Approach – III -B– Upgrade+Migration – ABAP Stack
Solution Manager 7.2 SP 08 Upgrade and Migration Using SUM DMO Approach – IV – Post Steps – ABAP Stack
Solution Manager 7.2 SP 08 Upgrade – Enterprise Search Configuration from TREX to SAP HANA – V – ABAP Stack
Solution Manager 7.2 SP 08,NW 7.4 Upgrade – Generate Stack File – VI– Java Stack
Solution Manager 7.2 SP 08,NW 7.4 Upgrade – VII– Java Stack
Solution Manager 7.2 SP 08,NW 7.4 Migration Using SWPM – VIII – Export Java Stack
Solution Manager 7.2 SP 08,NW 7.4 Migration Using SWPM – IX– Import Java Stack
Solution Manager 7.2 SP 08,NW 7.4 Migration Post Steps – X– Java Stack
I hope this sequential blogs series of post would give you profound information and it has extreme practical value to get engaged, you can find step-by-step description on how to perform Solution Manager 7.2 SP 08 Upgrade and Migration to Hana using SUM DMO Approach for ABAP system and for Java system using SWPM heterogeneous export import method.However any doubt, you can leave it in the comment section.
Thanks Sumit for describing each and every step of SAP Solman Upgrade
thanks sumit for sharing this blog
Hello Sumit Patel,
Thanks for this informative blog. It is very useful indeed.
I have a query and it would be great if you can share your insight on this.
Above mentioned scenarios are only feasible when OS of source Solman is Unix/Linux. Is that right?
I'm asking it because in my case, Source Solman System is set up on Windows and Sql DB and I'm afraid that DMO will not work in that case.
Kindly correct if my understanding is wrong here.
In my case , OS is Red Hat Linux and I have migrated from Oracle Db to Hana using DMO approach.
DMO is useful only when you want to migrate from any DB to Hana.
If you also want to perform OS migration then in that case you need to follow different approach.
Hope it is clear, please revert back in case of any issues and for more clarification.
Thanks, Sumit for the response. Your answer is crisp and clear. Appreciate it.
I'd further like to know about the timelines for this project. I've also got a similar assignment and in the planning phase right and tentative timelines could help me to plan better.
Procedure will be the same which I have mentioned in the blog, just the OS and DB changes.
If you have any doubts you can ping me on gmail.