Cluster Does Not Start After it Crashes; DICT Table Creation Error
(Doc ID 2170201.1)
Last updated on MARCH 24, 2019
Applies to:MySQL Cluster - Version 7.3 and later
Information in this document applies to any platform.
Fixed in 7.3.15, 7.4.13, and 7.5.4 or higher.
On : 7.3 version, Crashes
When attempting to restart Cluster after a crash,
the following error occurs.
Time: Wednesday 30 March 2016 - 04:00:17
Status: Temporary error, restart node
Message: Internal program error (failed ndbrequire) (Internal error,
programming error or missing error message, please report a bug)
Error data: DbdihMain.cpp
Error object: DBDIH (Line: 7947) 0x00000002
Pid: 9400 thr: 0
Version: mysql-5.6.19 ndb-7.3.6
Trace: /ndb/mysql-cluster/ndb_13_trace.log.9 [t1..t15]
The issue can be reproduced at will with the following steps:
1. Create some tables + populate them
2. Take node X down
3. Perform multiple LCPs (ALL DUMP 7099) to remove old redo logs
4. [Drop some tables] + Create more tables, populate them (Generating some DDL action on node X recovery)
5. Take the cluster down
6. Start all nodes (SR)
The other nodes will start as normal, node X will wait, with takeover logs
Once the others have started, node X will start takeover...
The issue has the following business impact:
Due to this issue, users cannot bring up the Cluster completely.
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