Highlighted
Respected Contributor.. Respected Contributor..
Respected Contributor..
390 views

Handling Duplicated CI's in ucmdb-HPSM

Jump to solution

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!

Tags (4)
0 Likes
1 Solution

Accepted Solutions
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: Handling Duplicated CI's in ucmdb-HPSM

Jump to solution

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

 

 

If you find that this or any other post resolves your issue, please remember to click "Accept as Solution". If you are satisfied with anyone’s response, please remember to give them KUDOS by clicking on the "thumbs up" at the bottom left of the post to show your appreciation.

View solution in original post

2 Replies
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: Handling Duplicated CI's in ucmdb-HPSM

Jump to solution

Hello Lucy,

hope you are doing fine.

I would suggest you to read the following guide, it explains about duplicate CI's

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

 

Carlos Villalobos R
Customer Support Engineer
If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a KUDOS by clicking on the STAR at the bottom left of the post and show your appreciation.
0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: Handling Duplicated CI's in ucmdb-HPSM

Jump to solution

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

 

 

If you find that this or any other post resolves your issue, please remember to click "Accept as Solution". If you are satisfied with anyone’s response, please remember to give them KUDOS by clicking on the "thumbs up" at the bottom left of the post to show your appreciation.

View solution in original post

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.