You may have to restore technical system descriptions from the System Landscape Directory (SLD), for the following reasons:
The system description was changed or created manually in the Landscape Management Database (LMDB), and you now want to reset it with the information from the SLD. For more information, see Registering Technical Systems Automatically by Data Suppliers.
Incorrect system information was migrated from transaction SMSY
during the LMDB setup. For more information, see Migrating System Information from SMSY to LMDB.
Different SLDs created inconsistent system descriptions in the LMDB. If the data in the SLDs differs (for example, because one SLD receives information from a data supplier and one by manual data import), LMDB data can be inconsistent. For more information, see Integration of System Landscape Management.
You deleted the system in the LMDB by mistake. For more information, see Deleting Technical System Information.
Note
Deleting the system information in the LMDB and waiting for the next automatic synchronization with the SLD does not re-create the system description consistently. It only updates the information that has changed since the last system registration, and a fragmentary system description will appear in the LMDB.
There are two ways of restoring system descriptions from the SLD:
Resynchronization from SLD, in the technical system editor:
Does not delete or overwrite assignments and information created manually in the LMDB, for example information about installed products that was not reported automatically by a data supplier.
Resynchronization by report:
Can overwrite all values in LMDB with SLD values, even if the corresponding fields are not filled in the SLD, so any values in the LMDB are cleared if there is no value in the SLD.
Can delete all technical system information in the LMDB, including assignments and manually-created information.
See Completing Technical System Information Manually.
If data is inconsistent in the SLD, for example because the same system is described differently in two SLDs attached to your LMDB, remove the incorrect information from the SLD first.
You can restore the complete technical system description from the SLD directly, in the technical system editor:
Start SAP Solution Manager: Work Centers (transaction SM_WORKCENTER
) and choose .
Select the technical system and choose
(You can also access the LMDB directly with transaction LMDB
.)
Choose
.If there is more than one SLD connected, select the one with the correct system description, and choose OK
.
Review the changes made by resynchronization.
Choose Save
to persist the changes.
Only data from automatic SLD data suppliers is synchronized. Data that was created manually in the LMDB is not deleted. Data that was created manually in the SLD is ignored. All manual assignments, for example product assignments, remain in the LMDB. To delete manually created data and assignments, refer to the next section.
If installed product information is updated by the resynchronization, the related product systems are automatically updated asynchronously. When you have saved, wait at least 5 minutes before you change a related product system.
There are reports to restore SLD data completely, including deleting assignments and data that was created manually in the LMDB.
Caution
Be sure that you really want to delete all manually created system information and assignments, such as product assignments. You may not be able to recover configurations that you delete, such as diagnostics-relevant indicators.
Start transaction SA38
and run one of the following reports:
RLMDB_SYNC_TECHNICAL_SYSTEM
(for a selected technical system)
RLMDB_SYNC_ALL_TECH_SYSTEMS
(for all technical systems in the LMDB). This report is available as of SP12. For more information, see SAP Note 1949792.
Choose the info button and read the help text for the report.
Make your selection.
Run the report in simulation mode first.
When you are sure that the report will achieve the desired result, deselect the Simulate
indicator and execute the report.
The synchronization can take a few minutes, depending on the number of CIM instances.