Skip to Content
Author's profile photo Wolf Hengevoss

SLD and LMDB Topology: Replacing the Source SLD for the LMDB

Switching the Source SLD of an LMDB


It is recommended to use just one System Landscape Directory (SLD) system as the source of CIM model, CR Content, and Technical Systems’ data for the Landscape Management Database (LMDB) – see figure 1:

Topology - Source SLD for an LMDB

Figure 1: Recommended SLD/LMDB Topology in a default landscape, with the source SLD in the PRD area.


However, the necessity may arise to change the SLD system you use as the source SLD for the LMDB – usually the central SLD in your landscape, getting the Data Supplier data. The switch may be necessary because you restructure the SLD Topology: How-To Gather and Distribute SLD-Data in Your IT-Landscape?, replace the central SLD with a completely new one, etc.

Here are the points to consider in case of a switch to another SLD and some hints how to prepare the switch. Data retrieved from the SLD by Demo: The Full Automatic Sync Feature in the SLD of SAP NetWeaver 7.1 is an important part of the LMDB content and the basis for all other data. Also, it is forbidden to have the same data retrieved from more than one SLD system, because this will lead to a violation of the unique-path-principle. Therefore, the switch of the source SLD by replacing the central SLD system needs to be planned thoroughly to avoid inconsistencies and gaps in the availability of SLD data.



In any scenario, where you want to switch to a new source SLD, the following is needed:

  1. Decide on the new source SLD.
    Install a new SLD or prepare an existing one. If you newly install the SLD, using the most recent version is recommended. At least an SLD based on SAP NetWeaver 7.11 should be used.
  2. Prepare the new source SLD.
    Import the CIM model; the CR Content version of the current source SLD will be synced into the new SLD by the full automatic synchronization.Note: During the phase when both SLD systems are used, do not update CIM model and CR Content. In case an update is needed, do so in the preparation phase or after the LMDB Source SLD switch is done.

Switch Procedure for the Replacement of the Central SLD

Figure 2: Synchronization between current and new source SLD by bidirectional sync. One Data Supplier is already pointing to the new source SLD:

State during replacement of the Source SLD

  1. Make the content of the current source SLD available in the new one. 

    Preferably, create and activate a bidirectional Full Automatic Synchronization connection. (This is done to distribute Data Supplier data during the phase when both SLD systems get Data Supplier data.)
    All available data will be synched into the new source SLD, while the new Source SLD is prepared but not yet acting as a source SLD for the LMDB.Note: Depending on the amount of data in SLD and LMDB, the first phase of synchronization (full synchronization) will take several hours

    – You can also use manual backup and import – also prepare the CR Content in this case. In that case, additionally create bridge forwarding from the new source SLD to the current, to keep Data Supplier data up-to-date until the actual switch

  2. Prepare the Data Suppliers of the Technical Systems.
    Re-configure the SLD Data Suppliers of all Technical Systems to point to the new source SLD.Note: If you are using a virtual IP address – or a virtual host name – as recommended to address the current source SLD, no action is required on the Technical Systems. (Remember, one prerequisite is that both SLD systems are using the same port or gateway – for further details, read How to Ensure that SLD Data is Available during Maintenance.)
    One more hint: You can also switch to the virtual address over time, while keeping the real and the virtual address of the initial SLD until all connections are pointing to the virtual address.
  3. Prepare the Bridge Forwarding of the new central SLD to all other SLD systems:
    Setup Bridge forwarding to supply all Data Supplier data delivered by the technical systems to all SLD system in landscape areas DEV and QA.
  4. In the SAP Solution Manager hosting the LMDB, reconfigure the LMDB Synchronization Connection to the SLD
    (Note that preconditions for that are that data in both SLDs is the same at this point – with no pending changes -, especially CR content and technical system descriptions, as described above):
    In transaction SOLMAN_SETUP go to System Preparation -> Prepare Landscape ->  Setup LMDB (see figure 3):Sync Connection between SLD and LMDB

    Figure 3: Deleting and adding synchronization connection between SLD and LMDB in Setup LMDB.

    – In the edit mode delete the old synchronization connection.

    – Then add the new connection to the new source SLD.

  5. After the switch, the old SLD can be shut down or be running in a new role.


Other Switch Scenarios

Switch Procedure to a Back-Up SLD (in full-synchronization with the central SLD)

This is quite simple. All the prerequisites are fulfilled already, changes in Data Suppliers or forwarding of Data Supplier data is taken care of already, so you only need to follow step 4 in the “Switch Procedure for the Replacement of the Central SLD”.

Switch Procedure to another SLD already Available in the Landscape but not the Central SLD

This is generally not recommended. Some exceptions of this rule may exist. In any case, the prerequisites must be fulfilled.


Occurrence and Handling of Sync Conflicts Regarding the SLD Data Supplier Time Stamp

If you do not use the full, automatic sync for the SLD contents during the change, sync conflict concerning the SLD Data Supplier time stamps will occur. Steps and correction to handle sync-conflicts related to time stamps of SAP Data Suppliers are described in SAP Note 1949792 – Report to resynchronize technical systems and data supplier timestamps from SLD to LMDB.

Additional Information

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Former Member
      Former Member

      Hi Wolf, very interesting blog!

      This adress exactly my problem: Started initially to sync Solution Managers own SLD with LMDB to get started. Now the SLD topology are in place and I want to switch to the central SLD. However, as Solution Managers SLD is version 702 I'm not able to do the full automatic uni-sync as of NW 7.1. Instead, as You wrote, I have to do import/export of the CR content to the new central SLD.

      Here comes the tricky part; I'm not really interested of doing that as the SLD data content on the Solution Manager SLD is not up to date, and I dont want to mix that with the new central SLD.

      My question is then: what would happen if I just make sure that both SLDs are on same CIM/CR version, but don't do the full sync between those? Am I able to clean up in LMDB afterwards. I haven't runned "System Managed setup" yet?

      Best regards

      When trying to switch component repository source from Solution Managers SLD to the new central SLD, it says that

      "new CR source based on SAP_CR 7.8 produced on 06.02.2012 with 843211 pending changes" , and
      "old CR source: CR_SAP_CR 7.8 produced on 06.02.2012 with 3591641 pending changes".

      But looking at configuration details for both SLDs, it says: "Number of Source changes pending: 0"

      When setting "New CR_Source" to the new central SLD the above info occur, and its very clearly stated that: "The two synchronization connections must not have changes pending in LMDB. It may be necessary to set the SLD sources to read-only mode to achieve this"

      So: which of the above statement to believe in; a lot of pending changes from both SLDs to LMDB or none?

      And how do I set SLD sources to read-only mode to achieve this?

      This is somehow confusing, and there's really no documentation on this issue except for this fine blog.


      Author's profile photo Wolf Hengevoss
      Wolf Hengevoss
      Blog Post Author

      Dear Kurt,

      The import of CIM / CR Content refers to the process as described in SAP Note 669669, where the download from SAP Service Marketplace is described. Of course the blog assumes that all the other info on technical systems, business systems and so on is valid.

      A full-sync is possible for a source SLD being on verison 7.0x, since it'as a pull mechanism.

      Regarding your update: Because of the pending changes, this looks like you should open a message for SLD (BC-CCM-SLD) or LMDB (SV-SMG-LDB).

      Best Regards,

      Wolf Hengevoss

      Author's profile photo Former Member
      Former Member

      Which type of SLD content data needs to be available in the new central SLD to make the LMDB source SLD switch possible?

      Is it only the data which has been delivered by data suppliers or is it required that data

      written by the SAP Solution Manager 7.1

      application is available as well (if any)?