Last updated on MARCH 08, 2017
Applies to:MySQL Cluster - Version 7.3 and later
Information in this document applies to any platform.
On : 7.3 version, Crashes
When attempting to have a running cluster,
the following error occurs.
2013-10-16 07:37:31 32754 [ERROR] Invalid (old?) table or database name 'mysql-cluster'
02:07:31 UTC - mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail.
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68218 K bytes of memory Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x24330a0 Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went terribly wrong...
stack_bottom = 7f74645eee18 thread_stack 0x40000
The issue can be reproduced at will with the following steps:
1. Create UNDO/TABLESPACES using static paths.
2. Each data node identifying the same static path i.e. sharing the file
3. Run the Cluster until crash
The issue has the following business impact:
Due to this issue, users cannot guarantee the cluster will remain working.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms