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