Ansicht
Dokumentation

SOLMAN_LMDB_PARAMS - Set Up Parameters

General Material Data   CPI1466 during Backup  
This documentation is copyright by SAP AG.

The Landscape Management Database (LMDB) serves as a directory for your landscape data. It is used by Root Cause Analysis and in the Technical Monitoring work center.

You set up LMDB in the transaction SOLMAN_SETUP or the SAP Solution Manager Configuration work center. You can set configuration parameters as well as perform the steps specified. All parameters have default values delivered. An adjustment is only necessary when problems occur, under special circumstances or when you are instructed to do so by SAP Support.

1. Choose the Maintain button.
2. As the CIM domain, choose Landscape Management Database (LDB).
3. In order to choose configuration parameters, choose the New Entries button and select the desired parameter in the input help of the CIM Setting column.
4. Choose the Continue button; the current value of the parameter is displayed. Change the parameter as you wish and save your changes.

Among the many parameters displayed, a selection of the parameters that you can adjust is shown below:

Note

The LMDB contains the data of your system landscape from the System Landscape Directory (SLD); a synchronization of the content is carried out on a regular basis. In principle, two phases exist in the synchronization:

• During a full synchronization, the entire contents of the SLD are transferred to the LMDB.

• During an incremental synchronization, only changes made to the SLD since the last synchronization are transferred to the LMDB. The system obtains this information from the change log of the SLD.

ContentSync.ConsistentReadTimeout

During a full synchronization, the system must check whether critical changes that could lead to inconsistencies in the dataset of the LMDB were made to the dataset of the SLD while this synchronization was being carried out (renaming of key fields, for example). In order to ensure that the change transactions have been completed, the system does not begin to check for these changes immediately after the synchronization has finished, but instead waits for a specified time period. This parameter specifies the time period in milliseconds.

Set this parameter in the target system of the synchronization. In the default installation, this is the system of the SAP Solution Manager on which the LMDB runs.

Change the value of this parameter only when instructed to do so by SAP Support.

ContentSync.FullSyncLimit

Changes to the dataset of the SLD are documented in the change log of this SLD. With the help of this log, a synchronization with another SLD or with an LMDB that is supplied with this landscape data is carried out.

If a certain number of changes are exceeded through another synchronization connection in the source system within the scope of a full synchronization, the individual changes are no longer documented in the change log. In this case, a full synchronization is required during the next synchronization of the LMDB. This parameter specifies the maximum number of changes.

Setting this parameter optimizes the performance of the synchronization, because it is possible that a full synchronization may generate less of a load than the individual synchronization of each change when there are a large number of changes. Conversely, it is more efficient to individually transport a small number of changes rather than trigger a full synchronization.

Set this parameter in the source system of the synchronization (in the context of the standard installation, this would be the system of the SLD that supplies the LMDB with landscape data).

Change the value of this parameter if performance problems that were triggered by a full synchronization in the source system exist during incremental synchronization.

ContentSync.FullSyncMaxLoops

If critical changes are made to the dataset of the SLD that could lead to inconsistencies in the dataset of the LMDB (renaming of key fields, for example) while a full synchronization is being carried out, this synchronization is repeated. In order to prevent an endless loop from occurring, use this parameter to set the maximum number of these full synchronizations that can be carried out in succession.

If a value less than two is set for this parameter, you deactivate the repetition of the full synchronization when simultaneous changes occur in the source SLD.

Set this parameter in the target system of the synchronization (in the context of the standard installation, this would be the system of the SAP Solution Manager on which the LMDB runs).

Change the value only when there are problems with the full synchronization.

ContentSync.PingReadTimeoutSec

Before a synchronization is carried out, the target system checks the availability of the source system using a test call (ping). This parameter allows you to set the maximum waiting time in seconds for this ping. During this time, the source system is considered available and the synchronization is carried out.

Set this parameter in the target system of the synchronization (in the context of the standard installation, this would be the system of the SAP Solution Manager on which the LMDB runs).

Increase this parameter if the time is exceeded even though the source system is available.

ContentSync.PollingIntervalMinutes

This interval specifies the time in minutes after which the target system triggers a synchronization of the landscape data if the source system has not sent a notification to the target system in regard to a change to the dataset during this time period.

If you set this parameter to 0 or a negative value, polling from the target system is deactivated.

Set this parameter in the target system of the synchronization (in the context of the standard installation, this would be the system of the SAP Solution Manager on which the LMDB runs).

ContentSync.ReadTimeoutSec

During a synchronization, there is a maximum time that the target system will wait for the source system to answer. You set the maximum waiting time in this parameter. When this waiting time is exceeded, the source system is considered to be not available. The synchronization is aborted and repeated at a later point in time (see the parameter ContentSync.PollingIntervalMinutes).

Set this parameter in the target system of the synchronization (in the context of the standard installation, this would be the system of the SAP Solution Manager on which the LMDB runs).

Increase this parameter if the time is exceeded even though the source system is available.

ObjectManager.StrictModifyClassChecks

If incompatible changes to CIM classes are found when the CIM model is changed, these changes are rejected if this parameter is set to its default value of TRUE. However, you no longer have a consistent model status at your disposal in this case.

If you set the parameter to FALSE, incompatible changes to CIM classes are allowed if no instances exist for these classes or if the existing instances can be converted to the new model. However, this also reduces performance during model import.

Only change this parameter if problems arise during import of a new model or if instructed to do so by SAP Support.

ObjectManager.StrictModifyQualifierChecks

If incompatible changes to CIM qualifier declarations are found when the CIM model is changed, these changes are rejected if this parameter is set to its default value of TRUE. However, you no longer have a consistent model status at your disposal in this case.

If you set the parameter to FALSE, incompatible changes to CIM qualifier declarations are allowed if they are not being used anywhere. However, this also reduces performance during model import.

Only change this parameter if problems arise during import of a new model or if instructed to do so by SAP Support.

ObjectServerExternal

This parameter is available to you for future enhancements. In this case, use the external name of the LMDB object server if you want to operate two LMDBs for continuous availability. These LMDB then have different internal names (parameter ObjectServerInternal), but the same external names.

See SAP Note 935245 for further information about the name of the object server.

ObjectServerInternal

Together with the CIM namespace, the name of the object server specifies an absolute prefix for all objects in the LMDB. The parameter should be identical to an ABAP namespace that you have reserved in the SAP Service Marketplace (without the framing slashes). A namespace reserved in this way ensures that all of your objects in all directories can be globally differentiated.

You set this parameter in the setup of the Solution Manager.

See SAP Note 935245 for further information about the name of the object server.

Persistence.NamespaceDeletionDays

Data of your system landscape is organized in the LMDB in namespaces. If there is incorrect data in a namespace, it can be easier to delete the namespace and reload the data instead of correcting it.

As an additional safeguard, namespaces are not immediately deleted, but instead just marked for deletion. You use this parameter to set the time period in days between the deletion command and the actual deletion of the namespace. The parameter value that is set at the point in time of the deletion command is decisive; subsequent changes made to the parameter do not have an effect on the deletions that have already occurred.

CL_GUI_FRONTEND_SERVICES - Frontend Services   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

Length: 10939 Date: 20240523 Time: 183032     sap01-206 ( 164 ms )