My Oracle Support Banner

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

Last updated on JULY 30, 2017

Applies to:

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


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 '' (111)")

Additional observations:

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




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

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