My Oracle Support Banner

MySQL Fails to Start with mysqld_error.log Reporting "[ERROR] InnoDB: Tablespace <ID> was not found at ./activity_monitor/CMON_ATT_LMV_<TIMESTAMP>.ibd." (Doc ID 2291847.1)

Last updated on JANUARY 21, 2021

Applies to:

Big Data Appliance Integrated Software - Version 4.8.0 and later
Linux x86-64

Symptoms

NOTE: In the examples that follow, user details, cluster names, hostnames, directory paths, filenames, etc. represent a fictitious sample (and are used to provide an illustrative example only). Any similarity to actual persons, or entities, living or dead, is purely coincidental and not intended in any manner. 

MySQL does not start on Node 3 of the cluster (or node with Node 3 role). Since MySQL will not start, Cloudera Manager is down. The logging for cluster services, for example hue, report errors like:

OperationalError: (2003, "Can't connect to MySQL server on 'bdanode03.example.com' (111)")

Additional observations:

1. On Node 3 (or node with Node 3 role) the mysqld service will not start.

Running:

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.