Skip to Content
Technical Articles

SAP SLD And LMDB CR Content Repair

Hello Friends,

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 http://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

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 URLhttp://<host>:<port>/sld/admin/CRRepair.jsp.

Start repair

Lets repair process to finish

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:

SAP CR Content Version 11.14 27aae44d-ac7d-37e1-1f18-47de18fecf2f
SAP CR Content Version 11.13 65fc7855-ab5d-2487-7af0-57f3620b32e6
SAP CR Content Version 11.12 b8a9b16f-ea96-259f-655e-e6796ea1c651
SAP CR Content Version 11.11 4fd7045f-d357-a9a1-dc6e-64288b34c404
SAP CR Content Version 11.10 ca250a10-3d77-ef97-758f-821b6fb8cc00
SAP CR Content Version 11.9 390d77eb-ea22-e461-58e9-e24dcbedfe20
SAP CR Content Version 11.8 9bb890d9-195d-686b-ff3e-de4fe542a198
SAP CR Content Version 11.7 cebb3392-521e-77f9-01b7-e6762fbefdfc
SAP CR Content Version 11.6 3249529a-f384-a263-93de-a7c658820068
SAP CR Content Version 11.5 1e5c1e6a-442b-316d-8c46-8caa6494b3d8
SAP CR Content Version 11.4 645b514b-db84-0d20-1e52-8dd6d50350b8
SAP CR Content Version 11.3 64e57b8d-baea-dbf6-3707-1693d9ea038a
SAP CR Content Version 11.2 7a8567f1-eab4-dc9f-4350-3f99f4d74e6c
SAP CR Content Version 11.1 026da763-a588-b16f-68a1-d5ea4bbfb562
SAP CR Content Version 11.0 123cb9c8-5886-4cf3-f01f-7ab9239981ec
SAP CR Content Version 10.12 6ed9e867-81fb-050c-988f-c6afdac17916
SAP CR Content Version 10.11 b9481f5d-b410-85f6-b943-643c2ceed655
SAP CR Content Version 10.10 f4ecae34-7a83-431d-403b-39fc88cf6f46
SAP CR Content Version 10.9 437026e9-6f77-ceca-2672-8fc2f5a4ce74
SAP CR Content Version 10.8 11e60a49-cc65-0789-87b8-082412042575
SAP CR Content Version 10.7 e6595d59-ec3d-5543-0e93-65cfd463180e
SAP CR Content Version 10.6 71742950-39be-d58f-127c-0515cc572bf7

These expected hashes are valid for report version 2.0:

SAP CR Content Version 12.1 eafe50c3-d8ea-eb1f-60a9-cb812ed6f7fb
SAP CR Content Version 12.0 6b80a3aa-ef37-8505-4994-3a242622afa9
SAP CR Content Version 11.13 36e7b696-8651-51e6-c896-0c7f76e733ef
SAP CR Content Version 11.12 592562b9-51f1-cfe5-9c51-5d11cbea6ee4
SAP CR Content Version 11.11 8cc46d70-c2f3-3a30-9c09-45c880467186
SAP CR Content Version 11.10 f21f213e-0554-b7c7-cd91-cb4c4e2f9248
SAP CR Content Version 11.9 38bb0da1-e2bf-521f-fcab-11214821af1a
SAP CR Content Version 11.8 30951165-565a-706a-366a-a5d1c13a8c19

Update

Expected hashes:

SAP CR Content Version Hashes valid for report version 3 Hashes valid for report version 2
15.7 01ab1439-fe45-3134-f78f-ec52f9b995b8 —  not supported any more  —
15.6 d7211ed0-8ba1-adc3-c327-1c42db311b37 —  not supported any more  —
15.5 93f7727a-9235-01af-9cd7-78ba4ed6e628 —  not supported any more  —
15.4 0d29197b-a0a4-ad10-72cf-e95685f0895d —  not supported any more  —
15.3 08b2ad8d-2e56-3c68-9001-23d367dd75bd —  not supported any more  —
15.2 f3ed868d-18ef-e3b3-dfa3-cb40a4020d32 —  not supported any more  —
15.1 9fce66c5-5ceb-b4a7-a2d4-b50e36e87377 —  not supported any more  —
15.0 11483123-5d9e-c744-674d-ee08e0f8a545 —  not supported any more  —
14.12 e49b8c70-12eb-7546-2910-f7aeb261ff03 —  not supported any more  —
14.11 58380c75-9806-5cb3-b9e6-93dc51e9b6bb —  not supported any more  —
14.10 11c5046e-5e24-20a5-f8b0-25bc62d3106a —  not supported any more  —
14.9 de372d6b-a64e-3280-e58b-e20cb26307fe 8e42e1d0-06fe-b39c-0aef-0da0757bfb92
14.8 8660443d-8deb-bc3a-dbe5-7c4b4f2e6431 48422f4a-b465-20f8-cc04-990da2b8664c
14.7 92858c3c-bf8a-b021-ab15-7e97b75c6ebb a0eabb26-071a-a0e9-551a-5034e3dc4569
14.6 6b070c6b-e72e-9260-0aa4-243a462107ec cf2874b1-ee88-be59-c55b-4b0757bfbf99
14.5 982ddaf3-fe5e-1418-a0bf-bd26e1b8a7d1 2474e423-9de3-c001-0acc-09f686c2e8fe
14.4 35fd0db0-c965-2d95-c782-869539f7bdca e95a6848-3d74-54d6-b2f0-470abf9a5b73
14.3 359dc7c2-08d2-44d1-0f20-e5e8f2767e53 20b105f4-df5c-5a1a-fe4b-9472185e25e0
14.2 3b29a1d1-4189-2d92-4ccf-6635baac1d63 6899ae59-da5c-ebef-f165-cb2eeba6596e
14.1 b2b6abaa-b72e-c173-43b6-0682c4049a3c 85ec396f-d141-8cb3-750e-2e5983c7127b
14.0 30547cda-c11f-6528-126c-5aa566e77986 74af0872-9d63-db5b-dc00-17ab4da4df57
13.4 1284d485-3ce1-265c-eff2-ff4ea5811c4b cb3bcff3-4347-10ff-b947-15612a8368c6
13.3 235a1c63-68ca-a9ce-455c-e19737741d94 cc990e9c-611e-60fb-6274-fb322dc19552
13.2 e1e2564c-de3b-b7db-387e-31b400c763ce 67410319-5ff8-b94b-cf8e-cfdb7c699323
13.1 5ec4a8da-89de-95fe-21bc-798e55186720 c7cb56b0-e8bd-6afc-6fbd-827d69706e15
13.0 d77bfb71-5a3d-2b9c-1417-768aa5616256 412c5df8-cbc6-2e92-3780-251232648a1d

 

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

Yogesh Patel

3 Comments
You must be Logged on to comment or reply to a post.