Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
(LMDB) FAQ
created by Stephanie Daum on Sep 6, 2012 1:59 PM, last modified by Stephanie Daum on May 4, 2015 4:25
PM
Version 154
inShare1
Tweet
With SAP Solution Manager 7.1, the Landscape Management Database (LMDB) has been introduced, changing the handling
of landscape data. In the following, we have collected answers to frequently asked questions.
Add new questions as comment!
What is a ...
Where can I find landscape descriptions?
Why are there several repositories for landscape data: SLD, SMSY, and LMDB?
What's better with the LMDB?
How does data get into the LMDB?
Can all LMDB data be updated automatically?
How does data get into SMSY when the LMDB replaces the local SLD in the SAP
Solution Manager 7.1?
What is the significance of SMSY as of SAP Solution Manager 7.1 SP9/10?
What to do with data of systems that do not exist any longer?
What to do if there are duplicate system entries in the LMDB?
How can I deal with duplicate host names in VAR scenarios?
How can VARs manage landscape data of several customers?
How do I connect the right SLD, can I change SLDs in between?
How can I update outdated CR Content in the LMDB?
What CR CONTENT (SAP Software Catalog) do I need and how can I update or
repair it?
If data supplier information is forwarded from a PI-SLD to the Solution Manager
SLD, where must the latest CR content be installed?
How do I set the rank for content synchronization between SLD and LMDB?
Which CIM model version does the LMDB need? Must the SLD have the same
version?
Why do I not see some properties of my technical system? Why is there outdated
data?
How can I check the data suppliers for a technical system?
How can I regularly monitor all my data suppliers?
How can I ensure that data suppliers send correct data to the SLD?
I deleted a technical system in the LMDB how can I get it back?
Where do I report problems with the LMDB?
***NEW*** Table rlmdb_clear_changelog keeps growing - how can I regularly
delete old entries?
How is LMDB data synchronized with the SAP Support Portal?
Which background jobs are running for the LMDB?
As long as NW7.31 PI SLD has all contents, can we simply swap LMDB sync from
NW PI 7.11 SLD? Is there any risk removing the target of NW PI 7.11 SLD and add
NW7.31 SLD?
How can I get support to plan a company-wide SLD landscape?
Where do I assign product instances to the product system?
How can I familiarize myself with logical components?
Are there reports to extract landscape data from the LMDB?
Under SCN blogs and docs on SLD and LMDB you may also more information.
What is a ...
technical system, product system, product instance, software component (version), logical component ...?
Why are there several repositories for landscape data: SLD, SMSY, and LMDB?
There is a clear separation of tasks in System Landscape Directory (SLD) and LMDB:
The SLD is the target for self-registration of technical systems in the IP landscape. This technical systems information is
provided for applications in non-productive and productive applications such as SAP NetWeaver Process Integration and
WebDynpro (Java) based applications that need this information. Because of the productive use of the data it provides, often
many SLD systems are used in customer landscapes (see SLD Topology: How-To Gather and Distribute SLD-Data in Your
IT-Landscape).
The LMDB retrieves technical system information from the SLD as a basis for landscape data, to manage technical systems
in monitoring and maintenance processes. It acts as a single source of truth in SAP Solution Manager. It provides a
centralized UI approach to landscape verification functions and transaction SMSY.
As of SAP Solution Manager 7.1 SP0-4, the LMDB manages information about technical systems, hosts.
As of SP5, the LMDB also manages product system information.
Transaction SMSY is the "old" system information storage, being replaced by the LMDB bit by bit.
Up to SAP Solution Manager 7.1 SP4, SMSY is still used to manage product system information, but gets all technical
systems information from the LMDB.
As of SP5, SMSY is only used to manage project-related data (logical components and solutions); the required data
(technical systems and product systems) ar edited and provided by the LMDB (see New in SP05: Product System Editor in
the Landscape Management Database of SAP Solution Manager 7.1).
The separation of roles is reflected in the architecture: Technical systems can register only in the SLD. All data changes in
the SLD are retrieved immediately by the LMDB, as well as the CIM model and the CR content (SAP software catalog).
Because both SLD and LMDB are needed in one landscape; without an SLD connected, LMDB cannot work AND data in
SLD and LMDB must be consistent and must not overlap.
More: How-to get an Overview of Your IT-Landscape?
How does data get into SMSY when the LMDB replaces the local SLD in the SAP
Solution Manager 7.1?
SMSY gets all technical (as of SAP Solution Manager 7.1 SP0) and product system information (as of SP5) from the LMDB.
For older technical systems, that were registered in SAP Solution Manager 7.0 in SMSY manually, a migration process from
SMSY to LMDB is available; for more information, see SAP Help Portal: Migrating System Information from SMSY to
LMDB.
Product systems (until SP4) and logical components are still created in SMSY.
What CR CONTENT (SAP Software Catalog) do I need and how can I update or
repair it?
Having consistent and up-to-date software catalog data (also known as CR CONTENT) in SLD and LMDB is a prerequisite
for correct description of the IT landscape. There are several SAP Notes describing how to install SAP CR CONTENT, how
to keep it up-to-date, and how to repair it if there are inconsistencies in the SLD and/or LMDB. SeeSoftware Catalog Data
aka CR CONTENT in SLD and LMDB for more information.
How do I set the rank for content synchronization between SLD and LMDB?
LMDB is acting as a single source of truth for landscape data in the SAP Solution Manager 7.1. It must always have a higher
rank than the connected SLDs. Thereby, you avoid overwriting of manually edited data in the LMDB. For more information,
see the SAP Help Portal: Connect LMDB to SLD.
Which CIM model version does the LMDB need? Must the SLD have the same
version?
As a general rule, CIM model and CR content should not be older than three months compared to the latest version available
in SAP Support Portal. The SLD content updates are published every four to six weeks. If more than one SLD is connected to
the LMDB, each connected SLD must contain at least the required CIM model version. But the model versions in multiple
SLDs don't need to be identical. For more information, see the SAP Help Portal: Connect LMDB to SLD and SAP
Note 1701770.
Why do I not see some properties of my technical system? Why is there outdated
data?
Check if the full, automatic content synchronization is running under SAP Solution Manager Configuration
(transactionsolman_setup) -> System Preparation -> Prepare Landscape Description -> Set Up LMDB.
Check if the affected technical system is available in the SLD if it is: Did you change the system information manually in
the LMDB (you can see this on the Overview under Last Manual Change for the technical system)? Manual changes in the
LMDB have a higher ranking than information from the SLD to avoid manual changes from being overwritten. But this also
means that you need to update manually what you changed manually. If there is updated information from the SLD, it won't
be written into the LMDB.
In such a case, when data is correct in the SLD, it can be helpful to use the SLD re-synchronization function in the LMDB.
For more information, see the SAP Help Portal: Resynchronize Technical System Information from SLD and SAP
Note 1714786.
How can I ensure that data suppliers send correct data to the SLD?
Check SAP Note 1842956 (Check Data Supplier Consistency for Technical System in LMDB).
If kernel or database data is missing, especially check if the SLD registration by sapstartsrv is active. See SAP
Notes1717846 (sapstartsrv SLD registration), 1824302 (Caption property of the SCS instance is incorrect in SLD),
and1715334 (SAPJVM version registered incorrectly in SLD).
I deleted a technical system in the LMDB how can I get it back?
If you deleted information for a technical system from the LMDB completely, see SAP Note 1714786.
As long as NW7.31 PI SLD has all contents, can we simply swap LMDB sync from
NW PI 7.11 SLD? Is there any risk removing the target of NW PI 7.11 SLD and add
NW7.31 SLD?
See SLD and LMDB Topology: Replacing the Source SLD for the LMDB.