LMDB synchronization error

[Former Member]

Hi SAP Gurus,

During our Solution Manager Setup we were struck at the Setup LMDB step. The LMDB / SLD synchronization job is getting failed with the below error message.

Error in processing of HTTP request: (402)ICM_HTTP_TIMEOUT

Full synchronization failed for class SAP_SupportPackage

Correct the error and repeat full synchronization

Because of this error we are unable to proceed further and does anyone know the fix to this issue?

Thanks,

Chekri.

[Former Member]

What does report RLMDB_SHM_READ_TEST say? Maybe the shared memory segment can't be read.

And did you install latest CR content?

[sumit_goel553]

run report for the synchronisation RLMDB_SYNC_TECHNICAL_SYSTEM report in SE38 and increase the timeout parameter

[former_member477084]

Hi,

I had same problem and I did troubleshooting with this links. Please check it will help

https://help.sap.com/saphelp_sm71_sp08/helpdata/en/71/611c8079df409097f67d797670bc81/content.htmhttps://help.sap.com/saphelp_sm71_sp08/helpdata/en/71/611c8079df409097f67d797670bc81/content.htmhttps://help.sap.com/saphelp_sm71_sp08/helpdata/en/71/611c8079df409097f67d797670bc81/content.htm

[former_member183107]

Hi,

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.

Regards,

Himanshu

[Former Member]

Hi,

Please look below parameters.

icm/server_port_<>

icm/keep_alive_timeout

icm/conn_timeout

[Former Member]

Hi Subhash,

Thanks for your reply.

I have checked these three parameters

icm/server_port_<> is maintained in instance profile

icm/keep_alive_tomeout and icm/conn_timeout are not maintained in instance profile.

But i have checked at RZ11 these two parameters are maintained.

those values are 60 and  5000.

[Former Member]

Hi Purna ,

Refer the Sap note 824554  for increasing the ICM timeout paramters.

Increase proctimeout to 600 ,if the issues still exist change it to 1800

Thanks

ASim

[sunny_pahuja2]

Hello,

Please refer to SAP Note 1753601 - Timeout during synchronization from SLD to LMDB

Thanks,

Sunny