How to remove a Global Collection in Jasper that no longer exist in Spectrum

Products

• Network Observability
• Spectrum

Issue/Introduction

I have compared the contents of the Spectrum Global Collections with the drop-down menu in Jasper and found one remaining discrepancy. The 'DT_GC_test' Global Collection was removed/deleted from Spectrum on 13.10.2025, but is still visible in Jasper. How can we remove it from Jasper?

Environment

DX NetOps Spectrum: Any version

Resolution

a) Take note of the model_key of the problematic GC name:

mysql> select * from model where model_name like 'GC_test'\G
*************************** 1. row ***************************
       model_key: 346
         model_h: 16777797
      model_name: GC_test
         mtype_h: 66676
     model_class: 0
 network_address: 0.0.0.0
first_event_time: 2025-11-06 08:38:48
     landscape_h: 16777216
    destroy_time: NULL
 security_string:
 isClusterEntity: 0
       tenant_id: -1
SDM_Host_Address: 0.0.0.0

1 row in set (0.00 sec)

 

b) Take note of the gc_rec_ID of the problematic GC name:

mysql> select * from globalcollection where gc_name like 'GC_test';
+-----------+---------+--------------------------------------+
| gc_rec_ID | gc_name | gc_unique_key                        |
+-----------+---------+--------------------------------------+
|       222 | GC_test | 690ca4e8-0224-1000-0d01-0afd81e10000 |
+-----------+---------+--------------------------------------+

1 row in set (0.00 sec)

 

c) Take note of the entity_group_ID of the problematic GC name:

mysql> select * from entitygroup where entity_group_name like 'GC_test';
+-----------------+-------------------+-------------------+--------------------------------------+
| entity_group_ID | entity_group_name | entity_group_type | gc_unique_key                        |
+-----------------+-------------------+-------------------+--------------------------------------+
|              18 | GC_test           |              1000 | 690ca4e8-0224-1000-0d01-0afd81e10000 |
+-----------------+-------------------+-------------------+--------------------------------------+

1 row in set (0.01 sec)

 

d) Take note of the entity_IDs to use in the next MySQL query:

mysql> select * from entitygroupentity where entity_group_ID=18;
+-----------------+-----------+
| entity_group_ID | entity_ID |
+-----------------+-----------+
|              18 |         3 |
|              18 |        28 |
+-----------------+-----------+

2 rows in set (0.00 sec)

e) To find what models belong to the problem GC name:

mysql> select * from entity where entity_id in (3,28);
+-----------+------------------+-------------+-------------------+----------------------+---------------------+--------------+
| entity_id | legacy_entity_id | landscape_h | current_model_key | entity_name          | create_time         | destroy_time |
+-----------+------------------+-------------+-------------------+----------------------+---------------------+--------------+
|         3 |                0 |    16777216 |                 4 | Sim38896:Device XYZ  | 2025-08-08 15:50:32 | NULL         |
|        28 |                0 |    16777216 |               316 | Sim39283:UPS Agent   | 2025-10-16 14:09:45 | NULL         |
+-----------+------------------+-------------+-------------------+----------------------+---------------------+--------------+

2 rows in set (0.00 sec)

================================

 

How to manually clean up the problematic GC in the reporting db:

1) Set the destroy_time in the model table for the problematic GC name (model_key from step a):

update model set destroy_time=NOW() where model_key=346;

2) Delete the problematic GC name from the globalcollection table (gc_rec_ID from step b):

delete from globalcollection where gc_rec_ID=222;

3) Delete the problematic GC name from the entitygroup table (entity_group_ID from step c):

delete from entitygroup where entity_group_ID=18;

4) Delete the entity membership from the entitygroupentity table (entity_group_ID from step c):

delete from entitygroupentity where entity_group_ID=18;