Show TOC

Procedure documentationTroubleshooting for the LMDB Locate this document in the navigation structure


This section provides solutions for common problems with the Landscape Management Database (LMDB).

Damaged Technical System Description in LMDB

Example: In a second SLD, there is an old system description with a removed ABAP client and an old Support Package level. This data has been created in the LMDB via content synchronization, and mixed with the correct description from the first SLD connected to SAP Solution Manager. The result is an overlap: Different system descriptions in different source SLDs and duplicate entries for the system clients and installed Support Packages are created in the LMDB.

Solution: Remove the outdated, overlapping data in the SLD and run a resynchronization from the SLD for the current data.

For more information, see Resynchronize Technical System Information from SLD.

Restore a Deleted Technical System Description

If a technical system has been deleted from LMDB, its extended system identifier (extended SID) and any key information is no longer known in LMDB. Neither the resynchronization function in the technical system editor, nor the report RLMDB_SYNC_TECHNICAL_SYSTEM can recover data from SLD without the extended SID. (For more information, see Resynchronize Technical System Information from SLD.)

To load all data of a deleted system into LMDB again, perform the following steps:

  1. Log on to the source SLD.

  2. Go to CIM Instances (in NetWeaver 7.0: Content Maintenance).

  3. Choose the CIM class of the key instance for your system type.

    Technical System Type — Caption

    Technical System Type — Technical Name

    CIM Class

    .NET System



    Apache Tomcat Server



    Application Server ABAP



    Application Server Java



    SAP BusinessObjects Cluster



    Database System



    Diagnostics Agent



    External Service



    SAP HANA Database



    IBM WebSphere Application Server



    Wily Introscope Enterprise Manager (Cluster)



    Wily Introscope Enterprise Manager (Standalone)



    SAP liveCache



    SAP NetWeaver Master Data Management Server



    Microsoft Internet Information Services



    SAP Web Dispatcher



    Sybase Unwired Platform



    TREX System



    Unspecific 3-Tier System



    Unspecific Cluster System



    Unspecific Standalone Application System



  4. Filter to find your system, for example by SID or host name.

  5. Make a pseudo-change to the key instance of your system, for example:

    1. Add an X to the description.

    2. Save the change.

    3. Reverse the change.

    4. Save again.

  6. Wait until the changes are replicated into the LMDB. The key instance and the extended SID, but no detailed system information, are written to the LMDB.

  7. To transfer the rest of the system information to the LMDB, use the Resynchronization from SLD function, as described under Resynchronize Technical System Information from SLD.

Synchronization Jobs Complete too Quickly

If you notice that one or more jobs for incremental synchronization are completed very quickly (within seconds) with status OK, there are two possible reasons:

  • There are no pending changes to be synchronized.

    Solution: No action required.

  • A predecessor job is processing a large number of pending changes and has not finished yet. In this case, following jobs are immediately set to complete while the preceding synchronization job continues processing. When this processing has finished, subsequent jobs will run productively again.

    Solution: Wait until the running job has finished.

In both cases, the reason for the job completion is documented in the job log.

SLD Synchronization Ends in a Timeout

If the job SAP_LMDB_LDB_0000000001 fails with the error ICM_HTTP_TIMEOUT', the reason is difficult to find if there are no ICM traces. You can investigate the following:

  1. Is the URL of the source SLD using the HTTP port of the AS Java system itself? Or is it pointing to the HTTP port of the ABAP ICM which redirects SLD requests to the Java stack? In the latter case, change the destination in SM59 to use the AS Java HTTP port directly.

  2. Assuming that the SLD response takes too much time, you can increase the read timeout in the LMDB:

    1. Start transaction SM34 and access the view cluster VC_LMDB_SETT_C.

    2. Choose Maintain.

    3. When you are asked for the CIM domain, enter LDB.

    4. Add a new entry and select ContentSync.ReadTimeoutSec from the value help.

    5. Choose Save. Select a transport request because this change will be transported from the development system to the test and system, for example.

    6. The default is 600 seconds, which is usually sufficient, but you can try to increase this value to 1200 seconds, for example.

    If this does not solve the issue, you can reset the default value by removing the entry ContentSync.ReadTimeoutSec.

    For more information, see SAP Note 1753601.

  3. If steps 1 and 2 did not solve the problem, SAP support can try find out what happens in the SLD while the synchronization job in the LMDB is running. For this purpose, use the SLD request trace as described in SAP Note 1354154.

Cannot Create RFC Connection Because of Wrong Host FQDN

Problem: You cannot create an RFC connection because the fully qualified domain name (FQDN) of the host is incorrect.

Solution for host information coming from Outside Discovery: Change the FQDN in the SMD agent as described in SAP Note 1626853.

For host information from an SLD: Access the technical system editor, choose Resync from SLD, and select the SLD containing the correct FQDN.

To find out which data supplier provided the host information, check the Details in the System Overview of the technical system editor.

If Outside Discovery has provided the host information, you can see all available alternative FQDNs and IP addresses under Alternative Hostnames in the host editor. Select the correct one from this list.

Performance Issues During Synchronization

For information on how to check the progress of synchronization, see Monitoring the Synchronization under Connect LMDB to System Landscape Directory (SLD).

Performance Issues Because of Exhausted Shared Memory

The LMDB in SAP Solution Manager 7.1 relies on ABAP shared objects in the shared memory of the application server. If the shared memory of the server is exhausted, or if the shared memory segment for the LMDB cannot be created for other reasons, LMDB processes will access the database instead of shared memory. This causes long response times. This behavior is visible in the work process overview (transactions SM50 and SM66), in which a lot of work processes are accessing the LMDB_P_CLASS table.

To see whether the shared memory area is used, start transaction LMDB_ADM (support tool for LMDB administration). Check the shared memory status under Content Synchronization Status on the Overview tab.

Administration of ABAP Shared Memory Areas for LMDB

Shared memory objects are ABAP object instances in the shared memory of the application server, which share data in various user sessions. This is quicker than individual database accesses. At runtime, LMDB uses ABAP shared objects to buffer CIM class information in shared memory.

The Shared Objects Monitor (transaction SHMM) provides an overview of the area instances in shared objects memory of the current application server.

The area relevant for LMDB is CL_LMDB_MODEL_SHM_AREA. As of SP5, the shared memory has a size of about 100 MB, of which about 13 MB are used by the LMDB.

The maximum size of all SAP Solution Manager objects in shared memory is specified by the abap/shared_objects_size_MB profile parameter.

On the Shared Objects Memory tab in SHMM, you can see how much shared memory is currently in use, and how much free space remains.

Use of Shared Memory

When LMDB processes are running, class information is read from shared memory. You can get the number of read accesses from the Accumulated Read Locks field in transaction SHMM.

Performance Issues Because of Swapping

The LMDB is regularly accessed by several SAP Solution Manager applications. The memory consumption of each LMDB access is relatively high, which can be an issue when the operating system is heavily swapping and the used virtual memory is exceeding the physical memory by far.

Use transaction SM50 or SM66 to check if there are many processes accessing the LMDB tables (search for LMDB*); this would indicate a swapping operating system. Do not consider table LMDB_P_CLASS, which is an exception described in the previous section.

No Progress in Incremental Synchronization

If the incremental synchronization between SLD and LMDB does not finish after a long time, proceed as follows:

  1. Check whether the synchronization is still active in transaction SOLMAN_SETUP under   System Preparation   Setup LMDB  .

    If it is active, choose Details. If the number of Pending Source Changes is much larger than 0 for a longer period of time, and if the Date of Source Change Log ID is in the past, the changes are not going through and the connection between source and target is probably corrupt. Reasons can be, for example, that shared memory is exhausted, database statistics are outdated, or SLD is down.

  2. For a job overview, start transaction SM37, enter SAP_LMDB_LDB* under Job Name and an asterisk (*) under User. Extend the date range if you do not find a job that successfully processed SLD changes.

    Check the job logs and look for the error messages.

Error Because of Changed Object Server Name

The synchronization job log can provide the following error: Object server name of source system changed from &2 to &1. This means that someone has changed the name of the object server in the SLD or the configured URL points to a different SLD now. The LMDB can no longer identify the source objects, so pending changes from the SLD are not transferred to the LMDB.

There are two possibilities:

  • If the name change of the object server was intended in SLD, proceed as follows:

    1. Rename the object server name to its previous name under   SLD   Administration   Profile   Object Server  .

    2. Wait for about ten minutes and return to SAP Solution Manager Configuration (transaction SOLMAN_SETUP) and go to   System Preparation   Setup LMDB   to check whether all pending changes are being processed completely. The job log in SM37 must not show any more errors.

    3. To temporarily avoid further synchronization, proceed as follows:

      1. Set the SLD to read-only. You can do this under   Administration   Settings   Server Configuration  .

      2. Wait until there are no more pending changes in the SAP Solution Manager system.

      3. Delete the SLD synchronization connection in the SAP Solution Manager Configuration (transaction SOLMAN_SETUP).

    4. Repeat the change of the object server name in SLD.

    5. Recreate the SLD synchronization connection.

    6. Wait until the full synchronization has started. Then, switch off read-only mode in the SLD.

  • If the name change in SLD was not intended, only carry out step 1 and 2.

Out-of-Date Oracle Database Statistics

If the SAP Solution Manager system is installed with an Oracle database, statistics can be out-of-date. After the installation or upgrade of the SAP Solution Manager 7.1 system, most LMDB tables are empty. If statistics are calculated at this time, the Cost Based Optimizer (CBO) will probably run a full table scan during all subsequent database accesses. If the LMDB tables are continually filled, for example because of full automatic synchronization of SLD and LMDB, the real costs for the full table scan increase, without the CBO realizing this.

After you start the content synchronization between SLD and LMDB, ensure that the Oracle database statistics are updated. To do so, start transaction DB20 with parameter LMDB_P_INSTANCE (table for CIM Instances) and check the optimizer statistics. If the statistics are out-of-date, use the Update Statistics with BRCONNECT function.

For best performance, update the statistics repeatedly while the content synchronization job is running. This will force the CBO to realize the increasing fill level of the LMDB tables.

You should update statistics for the following tables:

  • LMDB_P_ASSOC (Associations)

  • LMDB_P_CHANGELOG (Change Log)

  • LMDB_P_CLASS (Classes)

  • LMDB_P_GUID (GUIDs of Instance References)

  • LMDB_P_INSTANCE (CIM Instances)

  • LMDB_P_LONG_VAL (Long Value Storage)

  • LMDB_P_NAMESPACE (CIM Namespaces)

  • LMDB_P_PQ_NAMES (Hash Values for Names)

  • LMDB_P_QUALIFIER (CIM Qualifier Declarations)

You can update the statistics with the Update Statistics with BRCONNECT function while the content synchronization job is running. Do not stop the synchronization job for a statistics update. The performance improvement will become effective automatically, whereas a new synchronization job will take some time to check and process data up to the point where it was interrupted.

For more information, see SAP Note 1555955.

Unicode Characters Are Not Displayed

On a non-Unicode SAP Solution Manager system, Unicode characters included in system descriptions from the SLD are replaced by hash marks (#) in the LMDB. Avoid Unicode characters in SLD.

Errors During Verification in the Product System Editor

The product system verification of the Landscape Management Database (LMDB) in SAP Solution Manager 7.1 SP5 can display warnings or error messages that can be difficult to solve.

For detailed recommendations, see SAP Note 1721112.

System Duplicates

There can be two systems with the same system name (for example ABC) and with different extended system IDs (for example ABC00001 and ABC00002). This looks like two different systems, but actually both can mean the same technical system. This can happen, for example, because of a change of the host name or installation number or because of incorrect manual creation in the LMDB.

For information on how to clean up system duplicates, see SAP Note 1694004.