ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Deleting EventModel models is causing SpectroSERVER CPU to spike


Article ID: 6900


Updated On:


CA Spectrum


Inside an EventAdmin container model, if there are many (10,000 +) EventModel models located within the EventAdmin model, deleting even a few of these EventModel models may cause the SpectroSERVER CPU to spike and the delete process to take up to several hours to complete.


The more EventModel models contained inside an EventAdmin model, the larger the VIB data for the EventAdmin model for these EventModel models. When deleting an EventModel model, this VIB data needs to be updated. It is the updating of this information that is causing the CPU to spike and the delete process to take so long.


Release: SDBSFO99000-10.2-Spectrum-Device Based Suite-Server FOC


The resolution is to install the Spectrum_10.02.00.D174. The Spectrum_10.02.00.D174 patch contains intelligence to disable the storing of this VIB data by the EventAdmin model for the EventModel models. It basically removes the Topology view for the EventAdmin model. Access to the EventModel models would be through the List tab when the EventAdmin model is selected.

After installing the Spectrum_10.02.00.D174 and before starting the SpectroSERVER process, in order to activate this intelligence, you will need to add the following entry to the $SPECROOT/SS/.vnmrc file and restart the SpectroSERVER process for the change to take affect:


Please open a case with Spectrum support if you feel you are experiencing this issue.

This functionality is scheduled to be included in Spectrum 10.03.00.