How to Ensure Your Landscape Data is Up-to-Date – House-Keeping in the LMDB
Introduction
Landscape Management Database (LMDB) is the single source of truth for landscape data as of SAP Solution Manager 7.1 SPS05. Data is provided for many processes in SAP Solution Manager: Maintenance, monitoring, Early Watch Alert, and Change Request Management depend on the data quality in the LMDB. It is therefore highly recommended to put some effort into the house-keeping in the LMDB.
Also see teh Wiki on de-commissioning of systems:
http://wiki.scn.sap.com/wiki/display/SMSETUP/Delete_Managed_Systems
.
Scenarios
This section describes how you can improve data quality in the LMDB. LMDB cannot be used without a System Landscape Directory (SLD): LMDB CIM Model, CR Content and all automatically registered data on technical system are read from the SLD by the LMDB via full automatic synchronization. Therefore, to get a valid landscape description, SLD and LMDB need to be administered together. Figure 1 shows the most important actions:
Figure 1: Actions in maintaining an up-to-date landscape description.
.
Prerequisite Steps
To ensure a good quality of your landscape description you need to do the following actions on:
.
- Technical systems:
- Configure SLD Data Suppliers: This is done in the technical system; technical system data is then regularly updated in the SLD by the data supplier. See Data Handling in the SLD – Step-By-Step
- Install Host Agents: Details on operation system and database are sent to the LMDB. See Agent Data in the LMDB
- SLD:
- Maintain CIM/CR_Content: Technical system are described following the CIM Model; technical system types and products are described in the
CR_Content (for Component Repository or software catalog) – both need to be up-to date to describe the latest state of SAP software. See Step-by-Step Description of Data Handling in the SAP NetWeaver System Landscape Directory > Part 2.
- Maintain CIM/CR_Content: Technical system are described following the CIM Model; technical system types and products are described in the
- LMDB:
- Configure the (full automatic) content sync with the SLD. See SLD-LMDB Topology – Connections, Valid, and Invalid Data Exchange Between SLD and LMDB of SAP Solution Manager
- Configure the hoot agents. See Agent Data in the LMDB
- Create and verify product systems. See Product System Editor in LMDB of SAP Solution Manager SP5
.
Avoiding Problems
Landscape data in the LMDB are based on data from the System Landscape Directory and read by full automatic synchronization:
- The majority of technical systems, which are most important here, are loaded from the SLD. Make sure all technical systems register in the SLD wherever possible. Only where no data supplier is available, technical systems should be created manually in the LMDB.
- Usually, automatically delivered data should not be changed manually.
.
.
Correcting Data
Rule of Thumb
- Do changes to data where they originally occur
- Change data that stem from the SLD in the SLD – by full automatic synchronization all changes will turn up in the LMDB automatically, including deletions.
- For a description of what you can do in the SLD, see How-to Manage House-Cleaning in the System Landscape Directory – Duplicate System Entries.
- SAP Note 1727294 describes how system duplicates can be handled automatically by SLD, requiring the documented minimal version of SLD.
- If you would change data read from the SLD in the LMDB you will probably run into conflicts. The situation is described for two SLD
systems, but the LMDB will work exactly like the higher-ranked SLD: SAP NetWeaver System Landscape Directory: Conflicts and Ranks in Full Automatic Content Synchronization
- Change data that you created in the LMDB in the LMDB. What should be done is:
- Delete outdated product systems that are no longer used in logical components or solutions (this is checked during deletion)
- Delete outdated technical scenarios
- Change data that stem from the SLD in the SLD – by full automatic synchronization all changes will turn up in the LMDB automatically, including deletions.
.
.
Consistent Deletion of Managed Systems — System Decommissioning
The SCN Wiki document Delete_Managed_Systems (http://wiki.scn.com/wiki/display/SMSETUP/Delete_Managed_System) describes the steps necessary for consistent handling of deletion of technical system data depending on your version of SAP Solution Manager.
.
.
Correcting Technical System Data that are Correct in the SLD but Wrong in LMDB
Technical systems’ data is read from the SLD and therefore will be identical in SLD and LMDB. However, if you have done manual changes to a technical system’s data in the LMDB, due to LMDB’s higher rank, updates from the SLD will not be accepted in many cases.
If you find such a case, you can re-synchronize the technical system’s data from the SLD in LMDB Technical System Editor.
.
.
Clean-Up of Data in SMSY
As of SAP Solution Manager 7.1 technical systems’ data are hosted in the LMDB. As of SP5, this is also true for product systems. In these cases, see the “rules of thumb” above about correcting data. In all other cases data should be kept up-to-date in SMSY.
.
Upgrading SAP Solution Manager 7.0 to 7.1
Product Systems
After an upgrade to SAP Solution Manger 7.1, you’ll find a migration option for product systems from SMSY to the LMDB. Those systems that can be migrated can be selected for a mass migration. Those product systems that cannot be migrated (indicated by a red traffic light), should be either
- created manually in the LMDB (see Product System Editor in LMDB of SAP Solution Manager SP5 )
- corrected – this could be done prior to the upgrade using Landscape Verification.
- … or deleted.
.
Technical Systems
Technical systems should be read from the SLD whenever possible. Therefore, a migration is not necessary. In the rare case that no SLD Data Supplier is available for that technical system, it is preferable, creating the technical system manually in LMDB.
.
Logical Components
Logical components are handled in SMSY also with SP08 of SAP Solution Manager 7.1 – migration does not apply here. Products systems assignment of migrated product systems is not affected (these are synced into SMSY, too).
.
.
Clean-Up of LMDB Data after a Data Center Move
You want to clean LMDB completely due to a data center move but without losing the other configurations in the system. This last part is the deciding factor.
It is important to note that cleaning up LMDB completely in general only makes sense in a newly installed SAP Solution Manager system that hasn’t been in productive use and no configurations depending on landscape data exist. Otherwise cleaning up LMDB will lead to inconsistent configurations in other areas/applications, for example:
- Monitoring configuration, extractors, etc.
- Incident Management, Service Desk, etc.(based on IObjects in iBase which correspond to LMDB entities)
- Logical components
The list goes on. It will mean high effort to correct these inconsistencies afterwards. It would also mean that other stores dependent on LMDB need to be cleaned up as well (e.g. SMSY, IObjects), which leads to further complications.
In a data center migration it is instead recommendable to treat this in the same way as any other system move. This means if the systems are using virtualized host names, you should try to ensure that the systems use the same configuration afterwards. With host names, SIDs and installation numbers of the systems remaining stable, the will just report to SLD as usual and update the system descriptions in SLD and LMDB automatically.
If the host names cannot be kept stable, system duplicates will occur, which can be treated. For details about this please refer to SAP Note 1694004.
Let me also point out here that the related SAP Note 1727294 describes how system duplicates can be handled automatically by SLD, requiring the documented minimal version of SLD.
.
.
Cleaning-Up of Change Log Data in the LMDB
SAP Note 1695927 – Cleaning up the change history in the LMDB describes report RLMDB_CLEAR_CHANGELOG, which (using background jobs) cleans up old LMDB change logs that are no longer needed. It is available with SAP Solution Manager 7.1 (SPS01). Read the SAP Note for detailed information.
.
.
Further Information
For more information on SAP’s product model, SLD, LMDB, verification of landscape data, etc., see Landscape Descriptions @ SCN.
.
.
.
is there any facility for mass clean up of systems in LMDB? With our constant landscape changes we have many systems that get stale and unused, cleaning them up one at a time is rather time consuming .
Thanks.
Bernie
Dear Bernie,
at the moment, you have read what we can offer - there are some thoughts, however, to improve here and I'll update things in teh SCN once this is more concrete - and your question reminds me of that topic...
Thanks and Best Regards,
Wolf Hengevoss
SAP SE
Hello.
I have a question about systems that exist only in LMDB, for example an MS IIS Server. In my knowledge, MS IIS only exists in LMDB.
When we do a manual change to add technical Instances for an MS IIS, these changes are overwritten by the Data Supplier every time it updates LMDB.
Is there a way to avoid this situation?
Thank you.
Foivos Gkourogiannis
Hi Wolf,
we have a problem in updating HANA DB in SLD. sldreg.xml created but it is not updating in Sld.
Is there any way in which we can import this sldreg.xml in SLD so that it can be synced to LMDB automatically to perform MSS setup.
Thanks,
Kiran