Handling Duplicated CI's in ucmdb-HPSM

Hi,

I am looking for a solution for duplicated CI's created in ucmdb&hpsm. The root cause of the duplication is known and being looked at. One solution is to remove the CI's from both ucmdb and SM and re-scan, however I am unable to delete any CI's as all history needs to be kept. Is there another way to handle those duplicates that are now in ucmdb and HPSM (as "XXXXX__RENAMED") other than deleting them and re-scanning, or is that the only way? Please advise

Thanks!

Parents
  • Verified Answer

    This may be related to the following UCMDB Enhancement Request:

    https://softwaresupport.hpe.com/group/softwaresupport/search-result/-/facetsearch/document/LID/QCCR1E74950

    The way that R&D has recommended handling this situation in the past depends on how your DEM rules are set up in SM. It sounds like you are using the first option, which means you are supposed to remove the duplicate.

    1. If duplication rule is set to "RENAME":

    Step 1: Go Configuration Managment -- > Resources -- > Search CIs

    Step 2: Click "Expert Search" display option

    Step 3: Type index("RENAME", logical.name) > 0 as query, and Search

    Step 4: Remove dirty (duplicated) item

     

    2. If duplication rule is set to "Return Error":

    Step 1: set uCMDB log to debug level and restart server.

    Step 2: Push CI

    Step 3: Find CIs which have error message "This record contains an invalid duplicate key" in uCMDB log.

    Step 4: For all CIs found in step3, set ucmdb.id to NULL in SM

    Step 5: Push CI again

     

     

Reply
  • Verified Answer

    This may be related to the following UCMDB Enhancement Request:

    https://softwaresupport.hpe.com/group/softwaresupport/search-result/-/facetsearch/document/LID/QCCR1E74950

    The way that R&D has recommended handling this situation in the past depends on how your DEM rules are set up in SM. It sounds like you are using the first option, which means you are supposed to remove the duplicate.

    1. If duplication rule is set to "RENAME":

    Step 1: Go Configuration Managment -- > Resources -- > Search CIs

    Step 2: Click "Expert Search" display option

    Step 3: Type index("RENAME", logical.name) > 0 as query, and Search

    Step 4: Remove dirty (duplicated) item

     

    2. If duplication rule is set to "Return Error":

    Step 1: set uCMDB log to debug level and restart server.

    Step 2: Push CI

    Step 3: Find CIs which have error message "This record contains an invalid duplicate key" in uCMDB log.

    Step 4: For all CIs found in step3, set ucmdb.id to NULL in SM

    Step 5: Push CI again

     

     

Children
No Data