Error "SRM has not finished starting" and several innodb table errors appear after installing Spectrum 9.2.1.H07

Document ID : KB000049549
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

After installing hotfix H07 for Spectrum 9.2 the following errors seen may be seen:

When trying to access SRM applications:

"SRM has not finished starting"

In the $SPECROOT/mysql/data /<hostname>.err file:

120523 2:00:00 [ERROR] Cannot find or open table reporting/alarmactivity from the internal data dictionary of InnoDB though the .frm file for the table exists. Maybe you have deleted and recreated InnoDB data files but have forgotten to delete the corresponding .frm files of InnoDB tables, or you have moved .frm files to another database? or, the table contains indexes that this version of the engine doesn't support.

See http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting.html
how you can resolve the problem.

In the $SPECROOT/Install-Tools/LOGS/9.2.1.7.38_DATE/mysql.log:

reporting.alarminfo

Error : Unknown table engine 'InnoDB'

error : Corrupt

In both files these errors are seen for each of the innodb tables.

Solution:

Because of the way MySQL is upgraded during a Spectrum install like H07, the MySQL transaction log files can be moved around incorrectly which causes this condition. These logs are DB transactions that have already been made, therefore the clean up steps below are of no harm to actual MySQL data files and new transactions logs will be regenerated.

  • Stop tomcat and MySQL
  • Remove the $SPECROOT/mysql/data/ib* files
  • Restart MySQL and then restart tomcat.

The issue should now be resolved. If the issue continues to happen, please contact CA Spectrum support.