cancel
Showing results for 
Search instead for 
Did you mean: 

Long hours taken by AI_LMDB_R_SYNC_RUNNER

shaji_narayanan
Active Participant
0 Kudos

Hello Solution Manager Experts!

How can we reduce the long running hours taken by program AI_LMDB_R_SYNC_RUNNER (Background job SAP_LMDB_LDB_<nnnnnnn> - especially after a CR content update?

We recently updated CR content on Solution Manager 7.1 SP8 SLD (which also performs as central SLD for Development Solution Manager).

Previous version = SAP_CR 9.10

Current version   = SAP_CR 9.14

Post CR content update, the next run of AI_LMDB_R_SYNC_RUNNER took a long time and eventually cancelled due to a planned outage.

We restarted the job after the outage; eventually it took almost 68 hours to finish the job!  (Post-completion of the initial run, next iterations finished much quickly, in less than 5 seconds).

While agreeing

  • this is a development system with less-than-perfect production resources, and
  • older SolMan version - to be patched to latest SPS11 in coming weeks.

are there any performance tuning available for program AI_LMDB_R_SYNC_RUNNER?

After reading few blog posts / notes I updated DB statistics of few tables (eg: LMDB_P_INSTANCE) during the job run, but that was not of much help.

I looked for options to schedule the job in parallel, but could not find any.  Surely it should be possible to run this job in parallel, whereby multiple parallel jobs update Solution Manager with mutually exclusive SLD contents?

Any other options?

Highly appreciate your recommendations / suggestions; would love to reduce the runtime for next iterations of CR content updates.

Thanks in advance,

Shaji Narayanan

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi

After CR content update, it goes for Full automatic sync, this is of course long time than the incremental sync.

But 64 hours of full sync is really not fair.

1. Have you checked your extended memory

follow here under the section performance issues due to exhanusted extended memory https://help.sap.com/saphelp_sm71_sp08/helpdata/en/71/611c8079df409097f67d797670bc81/content.htm

This page also given reason for why incremental sync finishes quickly.

2. Check the locks and other opitons as mentioned in the note

1839372 - Long running job SAP_LMDB_LDB_0000000001

if this doesnt help, you get back to SAP with SLD traces.

Thanks

Jansi

shaji_narayanan
Active Participant
0 Kudos

Thanks for the URL, Jansi.  A combination of recommendations mentioned in note  and URL might sort out my issue.

Best regards,

Shaji

Answers (1)

Answers (1)

VJain
Active Contributor
0 Kudos

Hi Shaji,

1555955 -please check this not and based on the 1582842 note you have to maintain the parameter in system. After that you will find some performance improvement.

1669645 - No progress during incremental LMDB synchronization

1555955 - SAP Solution Manager 7.1 - Performance Checks for LMDB

1582842 - Profile parameters for SAP Solution Manager 7.1

Thanks

Vikram

shaji_narayanan
Active Participant
0 Kudos

Thanks for the notes, Vikram.

I am in the process of upgrading system to latest SPS version, SPS11.

Hopefully the upgrade + post processing - including latest CCN - should bring in latest versions of notes mentioned by Jansi and you.

Thanks

Shaji