How to find duplicate robots in UIM

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)
• Unified Infrastructure Management for Mainframe
• CA Unified Infrastructure Management SaaS (Nimsoft / UIM)

Issue/Introduction

Managing Duplicate Robots in UIM with Large environments (e.g., those with 1,000+ duplicates) often encounter this issue due to robot cloning.

Environment

Release : All supported versions

Cause

The primary cause of duplicate robot entries is typically the practice of robot cloning

 

Resolution

Step 1: Identify Duplicate Robots
To find which robots are duplicated in your database, run the following SQL query against your UIM database:

SELECT name FROM cm_computer_system 
GROUP BY name 
HAVING COUNT(*) > 1;

select * from cm_computer_system where name like '%<robot or device name>%' order by name

Step 2: Retrieve CS Keys for Deletion
Once you have the names of the duplicates, you need their specific cs_key to target them for removal. Use this query, replacing the placeholder with your specific robot name:

SELECT origin, name, ip, dns_name, nimbus_type, cs_id, cs_key, dedicated, mac, os_name 
FROM cm_computer_system 
WHERE name LIKE ('%robot_name%') 
ORDER BY name;

Step 3: Remove Devices via Discovery Server
After gathering the cs_key values for the "bad" entries, use the Discovery Server's advanced configuration to delete them.   

Best Practices for Deletion:

Batching: Process 64 CS Keys at a time for stability. While the system can handle up to 128, smaller batches are safer.

Validation: If you accidentally input a duplicate cs_key during the process, the system will recognize it and provide a count of the unique keys queued for deletion.