系统升级后数据库打开报错

对偶句3w

5.2.7版本的数据库去做升级的，升级到5.3.8
升级后 数据库命令框报错如下  而且还弹出停止工作框如图
请问怎么解决？
也有到网上查找是否有相关的解决方案，据说是my.ini 文件配置问题，请问这个需要配置哪些呢，怎么配置


正在启动MySQL...
.
...小提示..................................................................
.                                                                         .
. MySQL默认参数                                                           .
. 主机名/IP：127.0.0.1                                                    .
. 用户名：root                                                            .
. 密码：x5                                                                .
. 端口：3306                                                              .
.                                                                         .
...........................................................................
2018-07-11 17:08:10 0 [Warning] TIMESTAMP with implicit DEFAULT value is depreca
ted. Please use --explicit_defaults_for_timestamp server option (see documentati
on for more details).
2018-07-11 17:08:10 0 [Note] mysqld (mysqld 5.6.26) starting as process 9908 ...

2018-07-11 17:08:10 9908 [Note] Plugin 'FEDERATED' is disabled.
2018-07-11 17:08:10 9908 [Note] InnoDB: Using atomics to ref count buffer pool p
ages
2018-07-11 17:08:10 9908 [Note] InnoDB: The InnoDB memory heap is disabled
2018-07-11 17:08:10 9908 [Note] InnoDB: Mutexes and rw_locks use Windows interlo
cked functions
2018-07-11 17:08:10 9908 [Note] InnoDB: Memory barrier is not used
2018-07-11 17:08:10 9908 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-07-11 17:08:10 9908 [Note] InnoDB: Not using CPU crc32 instructions
2018-07-11 17:08:10 9908 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2018-07-11 17:08:10 9908 [Note] InnoDB: Completed initialization of buffer pool
2018-07-11 17:08:10 9908 [Note] InnoDB: Highest supported file format is Barracu
da.
2018-07-11 17:08:10 9908 [Note] InnoDB: Log scan progressed past the checkpoint
lsn 4353776438
2018-07-11 17:08:10 9908 [Note] InnoDB: Database was not shutdown normally!
2018-07-11 17:08:10 9908 [Note] InnoDB: Starting crash recovery.
2018-07-11 17:08:10 9908 [Note] InnoDB: Reading tablespace information from the
.ibd files...
2018-07-11 17:08:12 9908 [Note] InnoDB: Restoring possible half-written data pag
es
2018-07-11 17:08:12 9908 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 4353776468
InnoDB: Last MySQL binlog file position 0 11466, file name .\mysql-bin.000427
2018-07-11 17:08:14 9908 [Note] InnoDB: 1 rollback segment(s) are active.
2018-07-11 17:08:14 9908 [Note] InnoDB: Waiting for purge to start
2018-07-11 17:08:14 9908 [Note] InnoDB: 5.6.26 started; log sequence number 4353
776468
2018-07-11 17:08:14 9908 [Note] Server hostname (bind-address): '*'; port: 3306
2018-07-11 17:08:14 9908 [Note] IPv6 is available.
2018-07-11 17:08:14 9908 [Note]   - '::' resolves to '::';
2018-07-11 17:08:14 9908 [Note] Server socket created on IP: '::'.
09:08:15 UTC - mysqld got exception 0xc0000005 ;
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.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 67460 K  b
ytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0xe528d08
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...
137fa73    mysqld.exe!?get_field@@YAPADPAUst_mem_root@@PAVField@@@Z()
132bd09    mysqld.exe!?init@ACL_PROXY_USER@@QAEXPAUTABLE@@PAUst_mem_root@@@Z()
132c9ea    mysqld.exe!?acl_reload@@YADPAVTHD@@@Z()
13303ef    mysqld.exe!?acl_init@@YAD_N@Z()
128290a    mysqld.exe!?win_main@@YAHHPAPAD@Z()
1282c67    mysqld.exe!?mysql_service@@YAHPAX@Z()
171751a    mysqld.exe!my_mb_ctype_mb()
76aa343d    kernel32.dll!BaseThreadInitThunk()
77d89832    ntdll.dll!RtlInitializeExceptionChain()
77d89805    ntdll.dll!RtlInitializeExceptionChain()

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): 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.

jishuang

mysqld (mysqld 5.6.26)

平台的5.2.7版本不是用这个版本的数据库
这个是5.3版本才升级到这个数据库的

不同版本的mysql数据库data下的数据文件是否可以兼容公用，这需要到网上查找mysql数据库是否执行
https://blog.csdn.net/cug_jiang126com/article/details/79193682

对偶句3w

jishuang 发表于 2018-7-11 17:28
mysqld (mysqld 5.6.26)

平台的5.2.7版本不是用这个版本的数据库

这个是按照教程做的，难道平台不能兼容mysql数据库下data？那怎样才能兼容，平台没有解决方法吗

jishuang

这个是什么地方看到的？

不要复制，就直接用5.2.7版本的mysql，直接用这个数据库执行升级程序

或者到网上查找mysql跨版本怎么还原数据