JasperReports return "No Records Found" due to missing Global Collection associations - Spectrum

Products

• Network Observability
• Spectrum

Issue/Introduction

Scheduled or on-demand JasperReports (such as Availability, Asset, or Group reports) in DX NetOps Spectrum Report Manager (SRM) return a "No Records Found" message. This occurs when the reporting database does not contain a record of devices associated with a specific Global Collection, even though the collection appears populated in the OneClick console.

Symptoms

• CABI JasperReports (e.g., Monthly Availability Reports) return "No Records Found."
• The Spectrum Status for Report Manager shows "Up to date," but reports for specific Global Collections remain empty.
• Running the following MySQL queries against the reporting database returns zero results for the affected Global Collection:

sql

SELECT model.model_name, model.network_address, globalcollection.gc_name FROM reporting.model model INNER JOIN reporting.gcmodel gcmodel ON model.model_key = gcmodel.model_key INNER JOIN reporting.globalcollection globalcollection ON gcmodel.gc_rec_ID = globalcollection.gc_rec_ID WHERE globalcollection.gc_name = '####_Collection_Name';

SELECT entity.entity_name, entity.create_time, entity.destroy_time, model.network_address FROM entity, entitygroup, entitygroupentity, model WHERE entity.entity_ID=entitygroupentity.entity_ID AND entitygroupentity.entity_group_ID=entitygroup.entity_group_ID AND entity.current_model_key=model.model_key AND entitygroup.entity_group_name='####_Collection_Name';

Environment

• DX NetOps Spectrum 24.3.13 and earlier
• Report Manager (SRM) / CABI JasperReports 7.9.2.x

Cause

The Archive Manager (ArchMgr) may stop processing events if it becomes hung or encounters database connection failures. Because Global Collection synchronization relies on events stored in the DDM database, a failure in the Archive Manager prevents new model associations from being synchronized to the Report Manager (SRM) reporting database.

Resolution

Workaround to address Global Collection association issue in reporting database:

1. Restart the Archive Manager on the SpectroSERVER host (temporary workaround) or apply the patch (KB410531).
2. Once the Archive Manager is stable, recreate the impacted Global Collections (with new names).

Additional Information

• Running the following MySQL query against the reporting database returns the number of models associated with Global Collections:

sql

SELECT globalcollection.gc_name,COUNT(gcmodel.model_key) AS model_count FROM reporting.globalcollection globalcollection INNER JOIN reporting.gcmodel gcmodel ON globalcollection.gc_rec_ID = gcmodel.gc_rec_ID GROUP BY globalcollection.gc_name ORDER BY globalcollection.gc_name;