SAP SLD And LMDB CR Content Repair

Hello Friends,

SAP SLD And LMDB CR Content Repair: As you know SAP Solution manager is mostly depending on SAP SLD and LMDB Database. Sometimes chances are corruption of SLD CR Content and LMDB CR Content.

This document will help to solve inconsistency in CR Content.

Reference SAP Notes are as below

1939864 – Check if SAP CR Content is corrupt in LMDB or SLD

1093168 – Repair of SLD CR content

1891566 – Repair of LMDB CR Content

Checking for corruption

As of first step please make sure you have checked CR Content is corrupt or not.

Background job RLMDB_CR_CONTENT_HASH will show log as below

Example log for  SAP_CR 11.13

Note: If your CR Content corrupt make sure you have repair CR content in SLD first and after run report to fix it in LMDB as per SAP note: 1891566

Repair SLD CR Content

 

Login to SAP SLD https://host:5XX00/sld

 

Go to Administration and create new namespace as below

 

 

 

Now go back to Home and you will see that new created namespace

 

You can see that namespace is empty as below

 

 

 

Now Import BASE version of CIM Model

 

 

Go to Detail to verify

 

Import BASE CR Content

 

 

Now you can verify

 

Now match Model Version and SAP_CR Content performing import as per SAP note :  669669 – Update of SAP System Component Repository in SLD

Download can be found at : Support Packages and Patches – C” SAP CR CONTENT” SAP CR CONTENT UP TO 20XX

Note: In my case I was not able to download SAP CR Content 9.11 from SAP so I updated my Productive SLD CR Content to new available version in order to match my new CR Content

 

Now you can see below my production and temp namespace have same version of Model and Content

 

Repair Process

Navigate to “Administration” -> “Maintenance” -> “Repair Software Catalog” to do this.

 

Note: For lower releases, call the repair function at the URLhttps://:/sld/admin/CRRepair.jsp.

Start repair

 

Lets repair process to finish

Log of SLD CR Content repair

 

Remove sld/temp Namespace

Go to Administration >> Namespaces

 

 

You have successfully repair CR Content in SLD

Repair LMDB CR Content

Login to SAP Solution Manager and run transaction SA38

Run program  RLMDB_SAP_CR_REPAIR_LMDB in background

 

Log for job

 

Note: Make sure you have not schedule this jog frequently

Verification

Make sure you check your LMDB and SLD Content through RLMDB_CR_CONTENT_HASHER program and both hash must be same and match to SAP note : 1939864 – Check if SAP CR Content is corrupt in LMDB or SLD

 

These expected hashes are currently known:

These expected hashes are valid for report version 2.0:

Thank you for reading. Any comment and suggestions are welcome.

Yogesh Patel