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!

For detailed LMDB information, see the
Documentation for System Landscape Management - LMDB

Not found what you are looking for?
Check out the SAP xSearch at http://service.sap.com/notes

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 ...?

Where can I find landscape descriptions?

The system landscape consists of all the systems in the landscape. These systems' data is collected by the System Landscape Directory (SLD). While the SLD only knows about single technical systems, the landscape description is created in the LMDB of SAP Solution Manager, describing the dependencies between technical systems for maintenance and monitoring purposes. The LMDB provides landscape descriptions to other tools, such as Maintenance Optimizer and Landscape Planner.
For more information, see Landscape Descriptions.

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?

What's better with the LMDB?

For information on the advantages of the LMDB with regards to the previous SMSY storage, see the SCN blog Evolution of landscape data management - What's better with LMDB?

SAP Note 1679673 explains the most important differences between LMDB and SMSY.

For further improvements of the LMDB with SAP Solution Manager 7.1 SP10, see the following documents:

How does data get into the LMDB?

The most important data source for the LMDB is the SLD – every LMDB needs to be connected to an SLD. All data contained in the SLD is retrieved by the LMDB via full, automatic synchronization. Some data is created in the LMDB, manually.#

CIM model and CR content (SAP software catalog) are synchronized from the SLD.
All technical systems with a data supplier are supposed to forward their system identity to an SLD. For 3rd-Party systems, this can be done by 'sldreg' data suppliers; details under System Landscape Directory -> Registering Third-Part Systems in the SLD.
From the SLD, all data changes are forwarded to the LMDB.
If a technical system type doesn't have a data supplier (yet), its data can be created in the LMDB manually.
Systems that were manually created in transaction SMSY (because they once didn't have a data supplier, for example) can be migrated to the LMDB when you are updating to SAP Solution Manager 7.1. For more information, see SAP Help Portal: Migrating System Information from SMSY to LMDB.
Product system descriptions always must be created in the LMDB manually (as of SP5, previously in TA SMSY), based on the technical information provided by the SLD.

SAP Help Portal: Integration of System Landscape Management
SCN: More on System Landscape Directory-> Demo: The Full Automatic Sync Feature in the SLD of SAP NetWeaver 7.1.
Planning Guide — System Landscape Directoryat http://scn.sap.com/docs/DOC-8042
SAP Note 1669649

Can all LMDB data be updated automatically?

There is an increasing automation in creating and updating LMDB data. For example, as of SAP Solution Manager 7.1 SP08, product system information is aut. updated, when the technical system information is updated. For more information, e.g. on repairing system duplicates, deleting uninstalled application servers and technical systems, and SAP Solution Manager application changes due to system landscape changes.
For more information, see SAP Note 1916052.

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 is the significance of SMSY as of SAP Solution Manager 7.1 SP9/10?

Several SAP Solution Manager applications still receive system information from transaction SMSY, though the data in SMSY is only replicated from the new repositories. For more information, see SAP Note 1905236.

What to do with data of systems that do not exist any longer?

First of all: Do not simply delete technical system information in the LMDB. If a system becomes obsolete, delete it from the SLD, first, and deactivate the data supplier. The deletion is aut. synchronized with the LMDB and SMSY.

To consistently delete information for a managed system, see the guided procedure in SAP Solution Manager 7.1:
- SP11: Guided Procedure Management> Selection> select system > Guided Procedure Browser > Start Embedded > Start All Guided Procedures > Decommissioning
- SP12: Managed Systems Configuration> Technical Systems> select the system to remove > Advanced Options> Decommissioning
If, for some good reason, a technical system information was manually created in the LMDB, you also have to delete it manually. For more information, see the SAP Help Portal: Delete Technical System Information and SAP Note 1714786.
If a system was moved to a different server, this move can be handled in the SLD so that depending data (e.g. business systems) does not get lost but is updated.

What to do if there are duplicate system entries in the LMDB?

For different reasons, it can happen that the same system is registered more than once in the LMDB, with the same SID (e.g. ABC) but with different extended SIDs (e.g. ABC00001 and ABC00002) and maybe different hosts or installation numbers.

To find out how to clean up this situation, see SAP Note 1694004.

How can I deal with duplicate host names in VAR scenarios?

In a value-added reseller (VAR) scenario, systems from different customers are managed. When these systems share the same system IDs (e.g. C00) and the same host names (e.g. SAPPRD), you end up with several systems named "C00 on sapprd". The issue is described in the following discussions, for example: http://scn.sap.com/thread/3451267 and http://scn.sap.com/thread/3538016.If independent landscape are managed by a VAR in one SLD and SAP Solution Manager/LMDB, you must ensure a seperation of host names, for example by customer individual prefixes.For more information, see How-To Handle Landscape Data as a Value-Added Reseller Using LMDB -> Uniqueness of Landscape Data.

How can VARs manage landscape data of several customers?

Value-added resellers (VARs) provide services for several SAP customers and have to deal with a more complex landscape. For more information, see the blog How-To Handle Landscape Data as a Value-Added Reseller Using LMDB.

How do I connect the right SLD, can I change SLDs in between?

The SLD connection in SAP Solution Manager is set up in TA SOLMAN_SETUP -> System Preparation -> Prepare Landscape Description -> Select SLD and Set Up LMDB.

Connecting several SLDs to one SAP Solution Manager LMDB is not recommended. If you need to do so, you MUST make sure that any piece of information gets to the LMDB only via one SLD. Data on two or more SLDs must not overlap.

To ensure consistent CR content, you can only select one SLD as a CR source. For all other data (SIDs of tech. systems, business systems, host names, servers, etc.) you MUST install processes to fully separate the names (by naming conventions) and the data flow (by complete separation of SLD systems) to keep the unique-path-principle for data.

SLD-LMDB Topology – Connections, Valid, and Invalid Data Exchange Between SLD and LMDB of SAP Solution Manager
SLD and LMDB Topology: Replacing the Source SLD for the LMDB
To keep SLD content available for SAP Solution Manager during SLD maintenance, you can switch between different SLDs that are in sync. For more information, see Switching between 2 SLD Systems in Sync with an LMDB or a 3rd SLD.

How can I update outdated CR Content in the LMDB?

CIM model and CR Content are identical in System Landscape Directory (SLD) and LMDB. Every LMDB needs to be connected to an SLD system via full automatic synchronization. Together with all other data CIM model and CR Content are retrieved and updated from the SLD.

For details on CIM model and CR Content, see:

SAP Note 669669
SAP Note 1701770

More on System Landscape Directory -> How-to Handle Data in the SAP NetWeaver System Landscape Directory

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. See Software Catalog Data aka CR CONTENT in SLD and LMDB for more information.

If data supplier information is forwarded from a PI-SLD to the Solution Manager SLD, where must the latest CR content be installed?

Ideally, the CR content is up-to-date in all SLDs. If you cannot make changes to your PI production system, you must at least update the SAP Solution Manager SLD. For the synchronization between SLD and LMDB it is important to have the latest CR content in the SLD that is used as CR source for the content synch (here, the Solution Manager SLD). The supplier data sent to the PI-SLD is forwarded in its original state and processed in the SAP Solution Manager SLD, hence, it does not matter for the LMDB if the CR content is outdated in the PI-SLD.

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 (transaction solman_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 check the data suppliers for a technical system?

In SAP Solution Manager, you can check the completeness of data suppliers in the editor for technical systems. In transaction LMDB, display technical system information and choose the More... link on the Overview screen. Here you see, which data suppliers are required, which are actually found and working, and if there are problems. For more information, read the help text in the new window that opens.
You can also run a report on data supplier completeness for several technical systems: On the start screen of transaction LMDB, choose Landscape Reporting. Under Report ID, choose SAP: Technical System: Data Supplier Completeness.

How can I regularly monitor all my data suppliers?

As mentioned in the previous FAQ, there is a report for data supplier completeness checks in the LMDB: transaction LMDB → Landscape Reporting → report SAP: Technical System – Data Supplier Completeness.

To check the activity of your data suppliers on a daily basis, for example, you can schedule regular exports of report results to spread sheets (see also the help tray in the report UI).

Define a report variant:
1. In transaction SA38 of your SAP Solution Manager system, enter the program AI_LMDB_EXEC_REPORTING and choose Variants.
2. Enter a name for your variant and choose Create.
3. Select the namespace (normally ‘active’) and the report SAP: Technical System – Data Supplier Completeness.
  Select a system type.
  Under Export Option, we recommend that you choose Export to Server (Excel).
  To setup the path, see the report help text with key words transaction FILE and AL11.
4. Choose Variant Attributes. Make the required settings and save.
5. Choose Save, again, then choose Back.
Schedule a job for the report:
1. In SA38, enter the program AI_LMDB_EXEC_REPORTING and choose System→ Services→ Jobs→ Define Job (SM36).
2. Enter the job name, choose Step to apply the predefined variant.
  Save and go back to Define Job (SM36).
3. Choose Start condition.
  Choose Date/Time: Define a start date and check Periodic job.
  Choose Period values, select Daily and save.
  Save the start conditions.

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 Notes 1717846 (sapstartsrv SLD registration), 1824302 (Caption property of the SCS instance is incorrect in SLD), and 1715334 (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.

Where do I report problems with the LMDB?

The component to create incidents is SV-SMG-LDB.

NEW Table rlmdb_clear_changelog keeps growing - how can I regularly delete old entries?

From SAP Solution Manager 7.1 SP13, you can schedule regular jobs to run the delete report rlmdb_clear_changelog. For example, you can define that the job should run daily and delete all changelog entries that are older than 6 month. For details, start the report rlmdb_clear_changelog in SA38 and read the help text.

How is LMDB data synchronized with the SAP Support Portal?

See SAP Help Portal: Synchronize System Information with the SAP Support Portal.

Which background jobs are running for the LMDB?

Job	What it does
SAP_LMDB_LDB_*	Synchronization with SLD: In the SAP Solution Manager system, the name of the sync jobs between SLD and LMDB start with SAP_LMDB_LDB_* (e.g. SAP_LMDB_LDB_0000000001) and run under the SOLMAN_BTC system user. More at Connect LMDB to SLD.
SAP_LMDB_SMSY_SYNC SAP_LMDB_LCACHE_* DIAG_NOTIF_GUIDS_*	Jobs that initially fill the data stores in SAP Solution Manager: SAP_LMDB_SMSY_SYNC for consumer CL_LMDBS_NOTIFICATION (SMSY) SAP_LMDB_LCACHE_<domain id>_<namespace id> for consumer CL_LAPI_NOTIFICATION_CONSUMER (L-API cache) DIAG_NOTIF_GUIDS__<domain id>_<namespace id> for consumer CL_DIAGLS_LMDB_NOTIF_MANAGER (diagnostics) Valid until 7.1 SP7. See SAP Note 1592461.
SAP_LMDB_NOTIFY_LDB_*	Synchronization with SMSY and others: Between SMSY and SLD, there is no direct connection anymore. But all data in LMDB is automatically forwarded to SMSY by this notification job and by downstream sync jobs of individual consumers. Furthermore, this job updates other notification consumers, e.g. the Landscape API (L-API), diagnostics, and dual-stacks.
REFRESH_ADMIN_DATA_FROM_SUPPORT	Download SAP Support Portal information to SAP Solution Manager: Basic license data is regularly downloaded from the SAP Support Portal (aka 'OSS system') to SAP Solution Manager with this batch job. Parts of the downloaded information is stored in the LMDB. More in SAP Note 1490774.
LANDSCAPE FETCH job (daily) triggers report RSGET_SMSY (During solman_setup, is directly executed, once.)	Synchronization of LMDB and SAP Support Portal: LMDB data for all technical systems that are configured as 'active' is synchronized with the SAP Support Portal. For more information, see Synchronize System Information with the SAP Support Portal, which also explains how to trigger the job manually. See also SAP Note 993775. RFC Synchronization with ABAP systems: The job gets data, directly by RFC, from ABAP systems where there READ RFC is available or maintained. For more information, see Manage RFC Connections for ABAP Technical Systems. In SAP Solution Manager, this data is stored in transaction SMSY. with Transport Management System (TMS): If the system is a domain controller for the Transport Management System (TMS), also transport landscape information is synchronized, which includes system names, clients, software components, and TMS-specific information for systems in the transport domain.This is required for Change Request Management (ChaRM). In SAP Solution Manager 7.1, this data is stored in transaction SMSY. You can find the LANDSCAPE FETCH job in transaction solman_setup under Basic Configuration -> Configure Automatically -> Schedule Solution ManagerBackground Jobs.
RLMDB_OSS_SYNC_CONF_AUTO_MIG	Synchronization from LMDB to SAP Support Portal: This report uploads LMDB system information to the SAP Support Portal. More in SAP Note 993775.
LMDB_VERIFICATION	LMDB Verification Checks for Product Systems: The job is run when you trigger verification checks in the LMDB product system editor. For more information, see Execute Verification.

SAP Note 894279 (Background processing in SAP Solution Manager) provides you with an overview of all jobs running in the background for SAP Solution Manager.

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.

How can I get support to plan a company-wide SLD landscape?

For complex system landscapes an SLD planning workshop is recommended to define what the system landscape should look like. It can be followed-up by other services like a detailed migration plan, best practice recommendations for naming conventions, failover strategies, and maintenance or execution of the recommendations.

German-speaking customers still find the workshop as Strategischer SLD-Planungsworkshop in the ITTS Catalog.
In the future, SLD planning is part of a global SPM Service.

Where do I assign product instances to the product system?

When you maintain a product system, assign technical system + product instances to the product system - do NOT change the instances marked as installed on the technical system! Technical system information should always be sent by data supplier - do not change it manually.

How can I familiarize myself with logical components?

for a general introduction: White Paper: SAP Solution Landscape
SAP Help Portal: Logical Components
Live demo in SAP Solution Manager RKT Material under https://service.sap.com/rkt -> SAP Solution Manager -> SAP Solution Manager 7.1 -> Solution Roles - SP10 -> Setup and Operations -> Configuration of SAP Solution Manager -> Logical Component Creation
UI help text in SAP Solution Manager, transaction LMDB -> Logical Components -> expand help tray

Are there reports to extract landscape data from the LMDB?

There are several options. See System Landscape Reporting in SAP Solution Manager.