Landscape data in SAP Solution Manager LMDB are the basis for business processes and ALM processes alike. Landscape data are gathered by the System Landscape Directory (SLD) and retrieved by the Landscape Management Database (LMDB) as a basis of the landscape descriptions in the SAP Solution Manager 7.1.

Dual-Stack Systems contain both an AS ABAP and an AS Java with the same SID. Dual-Stack Systems can be split into separate technical systems (with the exception of mandatory dual-stacks such as versions of SAP NetWeaver PI and SAP Solution Manager). The data representing a Dual-Stack System are changed by the split – for example, the SID of the Java part changes. In SLD and LMDB, as you might know, data is not deleted automatically. So you need to correct the data of the former Dual Stack System after a split.

More info on Dual-Stack-Split is available at the SCN…

Handling Technical System Data in SLD and LMDB after a Dual-Stack-Split

Figure 1 shows a technical system of type Dual-Stack and the tools involved in handling its data before and after a split:


Figure 1: Before the dual-stack split technical system ABC of type Dual-Stack is registered in the SLD (index “AJ” indicates, that the SID will turn up in the SLD twice, one as AS ABAP, one as AS Java). The SLD hands its data over to LMDB in SAP Solution Manager. After the split, which includes a rename of the AS Java, 2 technical systems (still) register, but with different SIDs (ABC is only showing up in the AS ABAP section). The duplicates that may occur in the SLD if not avoided need to be addressed in the SLD by deleting the old SID of AS Java. Changes in the SLD are synced into LMDB, provided that no manual changes have been done in ABCAJ. If you hacve done manual changes in the LMDB, some house-keeping is needed in LMDB, too.
In case of errors in the technical systems’ meta data sent by their data-supplier, you can correct them using Correction of Installed Software Information (CISI) process in LMDB and SUM
to correct them in the technical system (an example are product instances assigned to the wrong stack after the split).


These are your steps to deal with technical system data after the split:

However, some data remains in the SLD, which might indicate, that there still is a Dual-Stack, which can result in problems during update or upgrade of the system. How to avoid this is described in Note 1873543 – Postprocessing of SLD data after a Dual-Stack Split.

Trouble Shooting

In case of errors, caused by wrong data registered by the data suppliers after the split, use Correction of Installed Software Information (CISI) and the process in combination with LMDB, where data is corrected, handed over to CISI and applied to the technical system using Software Update Manager (SUM).

Use cases – example:

  • Dual-Stack Split: Java product instance on ABAP technical system (or vice versa)
  • Add-On: Missing data on installed add-ons installation is written or erroneously entered add-on information is deleted
  • CISI – AS ABAP product instances of the AS Java assigned & vice versa

Additional Information and Tools

Also see related information on:




To report this post you need to login first.


You must be Logged on to comment or reply to a post.

  1. Charles Koekemoer


    I know this is an old post but I am facing a problem with SLD after dual stack splitting of my solution manager 7.2 SP03. The Abap stack is registering OK but the JAVA (target) is failing to register to itself’s SLD. This situation is according to my understanding prohibiting the SLD sync with LMDB when doing the solman_setup. The error when tryiong to auto register on SLD_Data_supplier is the following
    http://host:5<##>00/sld/ds, Status: 403, Message: Forbidden

    Please guys any idea…

    1. Wolf Hengevoss Post author

      Dear Charles,

      sorry for the late reply – this question, I cannot answer directly. Please open an incident under BC-CCM-SLD.

      Best Regards,

      Wolf Hengevoss
      SAP SE


Leave a Reply