Table reporting․event doesn't exist in Spectrum
search cancel

Table reporting․event doesn't exist in Spectrum

book

Article ID: 430985

calendar_today

Updated On:

Products

Network Observability Spectrum

Issue/Introduction

The Report Manager page fails to load in the OneClick Administration interface, and CABI reports show incorrect availability data․​​​​‌​‍

ERROR MESSAGE: "ERROR 1146 (42S02) at line 21 in file: '/opt/CA/spectrum/Install-Tools/rpmgr/sql/srmdbapi/ddl/create_v_fact_event․sql': Table 'reporting․event' doesn't exist"

SYMPTOMS:

  • Report Manager page fails to load

  • CABI generates reports with inaccurate metrics

  • Tomcat catalina․out log displays FatalSchemaChangeException

CONTEXT: This occurs when accessing the Report Manager or generating network availability reports

IMPACT: Administrators cannot generate accurate network performance reports or manage configurations

Environment

DX NetOps Spectrum: Any version

Cause

Due to a lack of disk space, the active MySQL event database file was manually compressed․ This prevented the database server from accessing the reporting table, causing the schema change exception and interface failure․

Resolution

PREREQUISITES:

  • Administrator access to the Linux database server

  • Sufficient disk space for file extraction

 

STEPS:

1․ VERIFY COMPRESSED DATABASE FILES

Path: $SPECROOT/mysql/data/reporting/

Command: ls -lart event#p#event_p*

EXPECTED: The output shows the event database file ends with a gz extension NOTE: Ensure sufficient disk space is available before proceeding

2․ STOP TOMCAT SERVICE

Path: $SPECROOT/tomcat/bin/

Command: ․/stopTomcat․sh

EXPECTED: The Tomcat service stops completely

3․ STOP MYSQL SERVICE

Path: $SPECROOT/bin/

Command: ․/cmdC․exe localhost 2 MYSQL

EXPECTED: The MySQL database service shuts down safely

4․ EXTRACT COMPRESSED DATABASE FILE

Path: $SPECROOT/mysql/data/reporting/

Command: gunzip event#p#event_p123․idb․gz

EXPECTED: The archive extracts successfully and restores the original idb file

5․ START MYSQL SERVICE

Path: $SPECROOT/bin/

Command: ․/launchinstdbapp․exe localhost MYSQL y MYSQL․OUT

EXPECTED: The MySQL service starts successfully

6․ START TOMCAT SERVICE

Path: $SPECROOT/tomcat/bin/

Command: ․/startTomcat․sh

EXPECTED: The service starts and SRM synchronizes the reporting database over the next few days

 

VERIFY SUCCESS:

  • Navigate to the OneClick Administration page and open Report Manager successfully

  • Confirm newly generated CABI reports display accurate availability metrics