Showing results for 
Search instead for 
Did you mean: 

SLD to LMDB sync

Former Member
0 Kudos


I recently upgraded our solution manager from 7.0 to 7.1. AS a part of solman_setup I am trying to sync local sld with LMDB. Ideally full sync shouldn't take more than few hours but it's been 3 days and my sync shows just 5%. I cancelled the job and started again but its still same. I see follwoing in the job log:

10/06/2015 10:48:15 Skipped class SAP_CIMData (already processed before abort)

10/06/2015 10:48:15 Skipped class SAP_InstalledSoftwareFeature (already processed before abort)

10/06/2015 10:48:15 Skipped class SAP_Supplier (already processed before abort)

10/06/2015 10:48:15 Skipped class SAP_SoftwareComponent (already processed before abort)

10/06/2015 10:48:15 Starting full synchronization of class SAP_SupportPackage...

10/06/2015 10:53:39 Data fetched: 76,246 source instances in 197,067 ms, 29,084 target instances in 126,470 ms

Content synchronization from SLD to LMDB is not finished (progress 5%)



Accepted Solutions (0)

Answers (4)

Answers (4)

0 Kudos

The problem was surely already solved, but maybe this tip helps other users.

I've observed the same issue on a SolMan system after upgrade from 7.0 to 7.1 (SP12). It was solved by stopping the sync job, recreating the Oracle database statistics (schedule by periodic job in DB13), and afterwards restarting the sync job.

Runtime before: 3 days (~40%)

Runtime after: 4-5 hours (complete)

Former Member
0 Kudos


Initial Sync for LMDB usually takes more than 3 days in Oracle .. i have seen that this happens faster if your DB is Sybase or MaxDB . But in oracle you have to wait for sync to complete ..

This is normal.



Former Member
0 Kudos

Hi ,

You can  monitor  the  procedure with standard transactions.

Transaction SM37 monitors jobs. The job log tells you,  for  example,  the  progress of a complete

synchronization, or any problems. The name  of  the synchronization job  for  the target namespace

is SAP_LMDB_LDB_<namespace ID>,  for  example: SAP_LMDB_LDB_0000000001.

Transaction SLG1 (Display Logs) for the object AI_LMDB, shows synchronization errors by

default.  You  can extend the analysis, and  for  example, also show warnings. Extending can impair

performance, so only do so if necessary.

Last, search for hanging LMDB locks in transaction SM12.

Table name: LMDB*

User: *

If the time of the lock is more than one day, you can safely delete this lock.


Former Member
0 Kudos

Hello Bobby

I am doing initial sync between SLD and LMDB and every 1% finish takes 2-3 hours. I am using SolMam 7.1 SP14 with local SLD. I have updated CIM Model and CR Content to the latest values.

In SM37 job log (SAP_LMDB_LDB_0000000001), i see below value even after 3.5 hours. There is no progress shown here:


  1. 27.11.2015 11:23:48 Starting synchronization from destination: LMDB_SyncDest1 (SLM SLD)
  2. 27.11.2015 11:23:48 Source URL: http://DWSSOL:8000/sld/cimom, source namespace: sld/active
  3. 27.11.2015 11:23:49 Starting full synchronization phase...


  1. 27.11.2015 11:23:54 Starting full synchronization of class SAP_SupportPackage...
  2. 27.11.2015 11:26:30 Data fetched: 74.394 source instances in 156.172 ms, 256 target instances in 656 ms


TCode SLG1 does not show any meaningful data.

There are no hanging locks in SM12 against table LMDB*.

Background JOB is running for passt 3.5 hrs and shows below information:


The value for Sequential Read is increasing by 3 per sec. Insert value is updating randomly. Can you please suggest if this progress is normal? I have updated table stastics in DB using BRTOOLS but it did not bring any benefit. Can you please suggest what else can i do to improve the sync performance?



Former Member
0 Kudos

Did you import the latest CR CONTENT into your upgraded SLD?