SolMan ABAP system not available in LMDB

[former_member603657]

Hello Experts,

By mistake, SolMan 7.2 ABAP system is deleted from LMDB. So we deleted it in SLD and used RZ70 transaction to send again the system data to SLD (Java System). It is available in SLD but not im LMDB.

We used the following SAP procedures but not able to fix the issue:

https://help.sap.com/doc/saphelp_sm71_sp11/7.1.11/en-US/71/611c8079df409097f67d797670bc81/content.ht...

https://help.sap.com/doc/saphelp_sm72_sp03/7.2.03/en-US/a5/9619539e24c835e10000000a441590/content.ht...

Any ideas are appreciated.

Thanks

Sreenivas

[TomCenens]

Hi Sreenivas

Troubleshooting would go as follows:

Execute RZ70 to push the ABAP system details to the SLD connected to SAP Solution Manager which is configured to sync into SAP Solution Manager LMDB

(or use LMDB directly if you are on high enough version of 7.2 = alternative option)

Next step/check would then be: do you see the system in the SLD after using RZ70 again?

If no: there is an issue with your RZ70 push and you have to investigate there

If yes: there seems to be an issue with your synchronization between SLD and LMDB - check the current status via transaction solman_setup - infrastructure preparation - 1.2 LMDB synchronization

If your configuration is stated as green and the config looks fine then click on "advanced" above the line that contains your sync configuration

If you are fast enough after pushing RZ70: under status details, you should see a number of pending changes -> this number should become 0 after the background job SAP_LMDB_LDB_0000000001 runs

If this doesn't happen, check the log of background job SAP_LMDB_LDB_0000000001 to figure out what is going wrong. Continue troubleshooting from there.

You should be getting something as follows in that job log in terms of it spotting changes to apply and then applying them and stating everything is "ok".

Starting incremental synchronization phase... Current number of pending changes: 3 Incremental sync. summary: 3 changes, 0 filtered, runtime 0s Content synchronization finished successfully Job finished

Best regards

Tom