This document will guide you through resolving a situation where you have duplicate entries for the same system in the SLD and LMDB of Solution Manager 7.1. You will know that you have duplicate entries when you have the original SID BD1 and the duplicate entry BD100001. The duplicate entry issue will cause the original system entry to not be updated with the new software components when the system is upgraded or changed. Which will cause issues with the Solution Manager Applications that are configured for the system. This guide is designed to allow you to update a system entry in the LMDB that has already had Managed system Configuration Completed and multiple Solution Manager Applications configured for it. Allowing you to update the original entry without breaking the Applications configured for that system and causing considerable work. When you complete these steps the new entry in the SLD will be configured to update the original entry in the LMDB.

This guide is critical when ChaRM is in place. With ChaRM configured, if you delete the original entry in the LMDB; ChaRM will stop functioning for the managed system. In this case the system was upgraded from Netweaver 7.0 to 7.4 and it was migrated from a Oracle Database to HANA. This resulted in a change in the hostname, causing duplicate entries in the LMDB and SLD. In addition to ChaRM we also have Technical Monitoring configured. Now that the software components have been upgraded, new extractors and alerts need to be activated within Solution Manager. We cannot activate the new extractors and alerts until we get the Original LMDB entry updated with the software component versions. Since the current extractors and alerts are designed for the old software components the monitoring of the software components is not functioning. This operation is the only way to resolving this issue with Technical Monitoring without having to break ChaRM and completing Managed system configuration on the new entry.

The most common reasons for duplicate entries in the LMDB are:

  1. The Host Name of the system has changed
  2. The installation Number has changed

Before you begin review the information below:

  1. Ensure that No configuration activities have been completed on the duplicate entry.
  2. Ensure they are truly duplicate systems entries for the same system.
    1. Compare the 2 entries in the LMDB to ensure they are truly the same system.
  3. Validate that you have a recent backup of Solution Manager before you begin.
  4. Stop the jobs in RZ70 in the managed system to ensure that the SLD is not updated while you are making changes.
  5. Lastly refer to the notes below for additional Information:
      1. 1747926 – Dealing with duplicate technical system names (old SLD)
      2. 1694004 – Dealing with duplicate technical system names (SIDs)
  6. To ensure this doesn’t happen again in the future. Upgrade you SLD to the version in Note Note 1727294 – AS Java/ABAP System move functionality, then turn on the automatic move functionality in the SLD by adjusting the parameter “AutomaticSystemMove” to 1.

Operation

1. Execute Transaction SLDHTMLGUI in Solution Manager

2. Select Administration

blog 1.png

 

3. Select Content Maintenance

blog 2.png

4. Select Application Server JAVA or ABAP.

       a. Filter by the SID*

       b. Write down the Duplicate and original System Names

  blog 3.png

5. Complete the next steps for both the new and old systems. Writing down the Unique “KeyElementFingerprint” for both the original and duplicate entries

          a. Select a system

blog 4.png

          b. Select Associated Instances

blog 5.png

          c. Scroll to the bottom of the page and select the link to the Supplied Elements

blog 6.png

          d. Write down the “KeyElementFingerprint”

  blog 7.png

blog 8.png

          e.In this case the data I recorded is below

              Original

                    1. BD1.SystemNumber.##########.SystemHome.cinbd00

                    2. a3d4307f-6c5a-fd1f-3119-08fa9b531a3b

              Duplicate

                    1. BD1.SystemNumber.##########.SystemHome.cinl08p134

                    2. 5baf714c-59a4-6ac9-7216-c1e2f6221c64

6. Execute Transaction LMDB in Solution Manager

7. Open the new duplicate System Entry in Edit mode (make sure you are selecting the duplicate system entry!!)

blog 9.png

8. Select Advanced

9. Select Delete Technical System from LMDB

blog 10.jpg

10.  Select Ok to delete the duplicate system entry

blog 11.png

11.  Open the original system entry in the LMDB in edit mode

blog 12.png

12.  Select Details

blog 13.png

13.  Select Actions and select Rename Instance

blog 14.png

14.  Enter in the name from the new duplicate entry that you wrote down earlier.

15.  Select Calculate Reference String

16.  Select Execute Renaming

blog 15.png

17.  Select Associated Instances

18.  Select Filter

blog 16.png

19.  Enter *Elem* under the Associated Class column and hit the enter key to filter

20.  Select the BCSystem.SID.on.Hostname – DSC

blog 17.png

21.  Select the Properties tan, you will see this is where the KeyElementFingerprint is associated to the system.

22.  Select Actions and select Rename Instance

blog 18.png

23.  Remove the old and Enter the new KeyElementFingerprint number that you wrote down earlier

24.  Select Calculate Reference String

25.  Select Execute Renaming

blog 19.png

26.  Select Save to save the renaming changes you just made

blog 20.png

27.  Select Advanced

28.  Select Re-synchronize Technical System from SLD

  blog 21.png

29.  Validate that the system is updated with the new software components.

30.  Delete the Original entry in the SLD. The new/duplicate entry in the SLD is now the entry that needs to exist.

To report this post you need to login first.

Be the first to leave a comment

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

Leave a Reply