Bucket files in the $SPECROOT/mysql/data/reporting directory on the Spectrum OneClick system not getting processed

Products

• Spectrum
• Network Observability

Issue/Introduction

Bucket files in the $SPECROOT/mysql/data/reporting directory on the Spectrum OneClick system not getting processed

Environment

Release : Any
Component : Spectrum Report Manager (SRM)

Cause

Possible root cause is a corrupt bucketactivitylog table

Resolution

NOTE: In the following MySql commands, replace <PASSWD> with the root password for your DX NetOps Spectrum version.

Recreated the bucketactivitylog table on the OneClick SRM system.

You can recreate the bucketactivitylog table by doing the following:

1. Log into the OneClick SRM system as the user that owns the Spectrum installation

2. Shutdown tomcat

3. If on Windows, start a bash shell by running "bash -login"

4. cd to the $SPECROOT/mysql/bin directory and enter the following command to log into mysql:

./mysql --defaults-file=../my-spectrum.cnf -u<PASSWD> -p reporting

5. At the mysql prompt, enter the following command to find out how the bucketactivitylog table was created:

show create table bucketactivitylog;

NOTE: The following is an example of the output from the above command run from a 10.4.2 install on Linux

| bucketactivitylog | CREATE TABLE `bucketactivitylog` (
  `log_id` int(10) unsigned NOT NULL AUTO_INCREMENT,
  `bucket_table_name` varchar(255) NOT NULL,
  `landscape_h` int(10) unsigned NOT NULL,
  `handler_name` varchar(255) NOT NULL,
  `finished_inserting_events` tinyint(1) NOT NULL DEFAULT '0',
  `creation_time` datetime DEFAULT NULL,
  `destroy_time` datetime DEFAULT NULL,
  `event_log_id` int(10) unsigned NOT NULL,
  PRIMARY KEY (`log_id`),
  KEY `bucket_table_name` (`bucket_table_name`),
  KEY `landscape_h` (`landscape_h`),
  KEY `handler_name` (`handler_name`),
  KEY `finished_inserting_events` (`finished_inserting_events`),
  KEY `creation_time` (`creation_time`),
  KEY `event_log_id` (`event_log_id`)
) ENGINE=InnoDB AUTO_INCREMENT=19123 DEFAULT CHARSET=utf8 |


6. Enter the following command at the mysql prompt to drop the bucketactivitylog table:

drop table bucketactivitylog;

7. Enter the "CREATE TABLE" command at the mysql prompt. Use the output from the command entered in step 5 above to recreate the bucketactivitylog table.

NOTE: The following is an example using the example output from step 5 above. DO NOT forget the semi colon at the end of the command.

CREATE TABLE `bucketactivitylog` (
  `log_id` int(10) unsigned NOT NULL AUTO_INCREMENT,
  `bucket_table_name` varchar(255) NOT NULL,
  `landscape_h` int(10) unsigned NOT NULL,
  `handler_name` varchar(255) NOT NULL,
  `finished_inserting_events` tinyint(1) NOT NULL DEFAULT '0',
  `creation_time` datetime DEFAULT NULL,
  `destroy_time` datetime DEFAULT NULL,
  `event_log_id` int(10) unsigned NOT NULL,
  PRIMARY KEY (`log_id`),
  KEY `bucket_table_name` (`bucket_table_name`),
  KEY `landscape_h` (`landscape_h`),
  KEY `handler_name` (`handler_name`),
  KEY `finished_inserting_events` (`finished_inserting_events`),
  KEY `creation_time` (`creation_time`),
  KEY `event_log_id` (`event_log_id`)
) ENGINE=InnoDB AUTO_INCREMENT=19123 DEFAULT CHARSET=utf8;

8. Start tomcat and check to verify the bucket files are now getting processed