Description:
When update a table, the mysql server crashed, and the server cann't start now, always report the same error
the operating sql is:
update wos_17.wos_all set ur_char = replace(UT, 'WOS:',‘’);
the error information of restarting is as follows:
2018-12-31T02:59:36.6NZ mysqld_safe Logging to '/Volumes/LaCie/MySQL_data/data/Zhuss-Mac-Pro.local.err'.
2018-12-31T02:59:36.6NZ mysqld_safe Starting mysqld daemon with databases from /Volumes/LaCie/MySQL_data/data
2018-12-31T02:59:37.064087Z 0 [Warning] [MY-011071] [Server] option 'max_allowed_packet': unsigned value 2147483648 adjusted to 1073741824
2018-12-31T02:59:37.066596Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
2018-12-31T02:59:37.067065Z 0 [Warning] [MY-010097] [Server] Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.
2018-12-31T02:59:37.067456Z 0 [System] [MY-010116] [Server] /usr/local/Cellar/mysql/8.0.12/bin/mysqld (mysqld 8.0.12) starting as process 33510
2018-12-31T02:59:37.141435Z 0 [Warning] [MY-010159] [Server] Setting lower_case_table_names=2 because file system for /Volumes/LaCie/MySQL_data/data/ is case insensitive
2018-12-31T02:59:37.149014Z 0 [Warning] [MY-011071] [Server] option 'innodb-purge-threads': unsigned value 0 adjusted to 1
2018-12-31T02:59:49.843630Z 1 [Warning] [MY-012351] [InnoDB] InnoDB: Tablespace 93, name 'testdb/bowen_all_citation', file './testdb/bowen_all_citation.ibd' is missing!
2018-12-31T02:59:49.859366Z 1 [Warning] [MY-012351] [InnoDB] InnoDB: Tablespace 94, name 'testdb/bowen_alt', file './testdb/bowen_alt.ibd' is missing!
......
2018-12-31T02:59:51.024416Z 1 [Warning] [MY-012351] [InnoDB] InnoDB: Tablespace 1470, name 'testdb/vicky_inst_countrynew', file './testdb/vicky_inst_countrynew.ibd' is missing!
2018-12-31T02:59:51.024536Z 1 [Warning] [MY-012351] [InnoDB] InnoDB: Tablespace 1471, name 'testdb/vicky_inst_countrynew_notchn', file './testdb/vicky_inst_countrynew_notchn.ibd' is missing!
InnoDB: Progress in percents: 12018-12-31T02:59:51.246122Z 0 [ERROR] [MY-000000] [InnoDB] InnoDB: Assertion failure: row0umod.cc:151:!dummy_big_rec
InnoDB: thread 123145404334080
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
02:59:51 UTC - mysqld got signal 6 ;
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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.
key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=1
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 67870 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x7fe647058a00
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 = 70000614be70 thread_stack 0x46000
0 mysqld 0x000000010b8589f4 my_print_stacktrace(unsigned char*, unsigned long) + 60
1 mysqld 0x000000010aef3c2a handle_fatal_signal + 690
2 libsystem_platform.dylib 0x00007fff7d82cf5a _sigtramp + 26
3 ??? 0x000000010f5ad314 0x0 + 4552577812
4 libsystem_c.dylib 0x00007fff7d5ca1ae abort + 127
5 mysqld 0x000000010bb400f6 ut_dbg_assertion_failed(char const*, char const*, unsigned long) + 226
6 mysqld 0x000000010baf7646 row_undo_mod_clust_low(undo_node_t*, unsigned long**, mem_block_info_t**, mem_block_info_t*, dtuple_t const**, unsigned char*, que_thr_t*, mtr_t*, unsigned long) + 256
7 mysqld 0x000000010baf5ef2 row_undo_mod(undo_node_t*, que_thr_t*) + 3347
8 mysqld 0x000000010baf83ec row_undo_step(que_thr_t*) + 690
9 mysqld 0x000000010bab0d94 que_run_threads(que_thr_t*) + 600
10 mysqld 0x000000010bb2e706 trx_rollback_or_clean_recovered(unsigned long) + 992
11 mysqld 0x000000010bb2ea10 trx_recovery_rollback_thread() + 50
12 mysqld 0x000000010bb1635d void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, Runnable, void (*)()> >(void*) + 52
13 libsystem_pthread.dylib 0x00007fff7d836661 _pthread_body + 340
14 libsystem_pthread.dylib 0x00007fff7d83650d _pthread_body + 0
15 libsystem_pthread.dylib 0x00007fff7d835bf9 thread_start + 13
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): is an invalid pointer
Connection ID (thread ID): 0
Status: NOT_KILLED
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
2018-12-31T02:59:51.6NZ mysqld_safe mysqld from pid file /Volumes/LaCie/MySQL_data/data//Zhuss-Mac-Pro.local.pid ended
How to repeat:
I don't know how the mysql crashed by the update operating,
but everytime I restart the mysql server, the error occured and the server restarted failed
