mysql server innodb_Windows环境 MYSQL SERVER 8.0 innodb 表损坏

最新推荐文章于 2024-07-09 19:20:44 发布

bgwsoye

最新推荐文章于 2024-07-09 19:20:44 发布

阅读量454

点赞数

文章标签： mysql server innodb

本文链接：https://blog.csdn.net/weixin_30152861/article/details/114759014

版权

2018-11-09T01:13:42.292194Z 0 [Note] Basedir set to C:\Program Files\MySQL\MySQL Server 8.0\

2018-11-09T01:13:42.294152Z 0 [Warning] option ‘read_buffer_size’: unsigned value 0 adjusted to 8192

2018-11-09T01:13:42.294171Z 0 [Warning] option ‘read_rnd_buffer_size’: unsigned value 0 adjusted to 1

2018-11-09T01:13:42.294230Z 0 [Warning] ‘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-11-09T01:13:42.297405Z 0 [Note] C:\Program Files\MySQL\MySQL Server 8.0\bin\mysqld.exe (mysqld 8.0.3-rc-log) starting as process 4012 …

2018-11-09T01:13:42.304207Z 0 [Warning] No argument was provided to –log-bin, and –log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use ‘–log-bin=iZ3i6uvp3vi7lkZ-bin’ to avoid this problem.

2018-11-09T01:13:42.309109Z 0 [Note] InnoDB: Adjusting innodb_buffer_pool_instances from 8 to 1 since innodb_buffer_pool_size is less than 1024 MiB

2018-11-09T01:13:42.310065Z 0 [Note] Plugin ‘FEDERATED’ is disabled.

2018-11-09T01:13:42.314009Z 1 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions

2018-11-09T01:13:42.314741Z 1 [Note] InnoDB: Uses event mutexes

2018-11-09T01:13:42.315210Z 1 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier

2018-11-09T01:13:42.315953Z 1 [Note] InnoDB: Compressed tables use zlib 1.2.11

2018-11-09T01:13:42.317048Z 1 [Note] InnoDB: Number of pools: 1

2018-11-09T01:13:42.317670Z 1 [Note] InnoDB: Using CPU crc32 instructions

2018-11-09T01:13:42.319948Z 1 [Note] InnoDB: Initializing buffer pool, total size = 8M, instances = 1, chunk size = 8M

2018-11-09T01:13:42.321384Z 1 [Note] InnoDB: Completed initialization of buffer pool

2018-11-09T01:13:42.366023Z 1 [Note] InnoDB: The log sequence number 64852319 in the system tablespace does not match the log sequence number 64921699 in the ib_logfiles!

2018-11-09T01:13:42.366957Z 1 [Note] InnoDB: Database was not shutdown normally!

2018-11-09T01:13:42.367365Z 1 [Note] InnoDB: Starting crash recovery.

2018-11-09T01:13:42.368054Z 1 [Note] InnoDB: Using ‘tablespaces.open.2’ max LSN: 64893612

2018-11-09T01:13:42.380013Z 1 [Note] InnoDB: Doing recovery: scanned up to log sequence number 64921699

2018-11-09T01:13:42.387705Z 1 [Note] InnoDB: Applying a batch of 0 redo log records …

2018-11-09T01:13:42.388176Z 1 [Note] InnoDB: Apply batch completed!

2018-11-09T01:13:42.389490Z 1 [Note] InnoDB: Last MySQL binlog file position 0 15870, file name iZ3i6uvp3vi7lkZ-bin.000006

2018-11-09T01:13:42.510964Z 1 [Note] InnoDB: Opened 2 existing undo tablespaces.

2018-11-09T01:13:43.355928Z 1 [Note] InnoDB: Removed temporary tablespace data file: “ibtmp1″

2018-11-09T01:13:43.356446Z 1 [Note] InnoDB: Creating shared tablespace for temporary tables

2018-11-09T01:13:43.357168Z 1 [Note] InnoDB: Setting file ‘.\ibtmp1’ size to 12 MB. Physically writing the file full; Please wait …

2018-11-09T01:13:43.467700Z 1 [Note] InnoDB: File ‘.\ibtmp1’ size is now 12 MB.

2018-11-09T01:13:43.473044Z 1 [Note] InnoDB: Created 128 and tracked 128 new rollback segment(s) in the temporary tablespace. 128 are now active.

2018-11-09T01:13:43.475558Z 1 [Note] InnoDB: 8.0.3 started; log sequence number 64921699

2018-11-09T01:13:43.746800Z 0 [Note] InnoDB: Loading buffer pool(s) from C:\ProgramData\MySQL\MySQL Server 8.0\Data\ib_buffer_pool

2018-11-09T01:13:43.747862Z 0 [Note] InnoDB: Buffer pool(s) load completed at 181109 9:13:43

2018-11-09T01:13:43.779606Z 1 [Note] Found data dictionary with version 1

2018-11-09T01:13:43.829080Z 0 [Note] Recovering after a crash using iZ3i6uvp3vi7lkZ-bin

2018-11-09T01:13:43.829574Z 0 [Note] Starting crash recovery…

2018-11-09T01:13:43.829975Z 0 [Note] Crash recovery finished.

2018-11-09T01:13:43.831694Z 0 [Note] InnoDB: DDL log recovery : begin

2018-11-09T01:13:43.833149Z 0 [Note] InnoDB: DDL log recovery : end

2018-11-09T01:13:43.852590Z 0 [Warning] Failed to set up SSL because of the following SSL library error: SSL context is not usable without certificate and private key

2018-11-09T01:13:43.853485Z 0 [Note] RSA private key file not found: C:\ProgramData\MySQL\MySQL Server 8.0\Data\\private_key.pem. Some authentication plugins will not work.

2018-11-09T01:13:43.854383Z 0 [Note] RSA public key file not found: C:\ProgramData\MySQL\MySQL Server 8.0\Data\\public_key.pem. Some authentication plugins will not work.

2018-11-09T01:13:43.855385Z 0 [Note] Server hostname (bind-address): ‘*’; port: 3306

2018-11-09T01:13:43.856119Z 0 [Note] IPv6 is available.

2018-11-09T01:13:43.856434Z 0 [Note] – ‘::’ resolves to ‘::’;

2018-11-09T01:13:43.856797Z 0 [Note] Server socket created on IP: ‘::’.

2018-11-09T01:13:43.926226Z 4 [Note] Event Scheduler: scheduler thread started with id 4

2018-11-09T01:13:43.926520Z 0 [Note] C:\Program Files\MySQL\MySQL Server 8.0\bin\mysqld.exe: ready for connections. Version: ‘8.0.3-rc-log’ socket: ” port: 3306 MySQL Community Server (GPL)

2018-11-09T01:13:44.861562Z 0 [ERROR] Invalid (old?) table or database name ‘dbs-gold_report’

2018-11-09T01:13:44.862085Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.

2018-11-09T01:13:44.862514Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.

2018-11-09T01:13:44.862942Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ‘.\dbs-gold_report\mt4_trades.ibd’ OS error: 103

2018-11-09T01:13:44.863625Z 0 [ERROR] Invalid (old?) table or database name ‘dbs-gold_report’

2018-11-09T01:13:44.864266Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.

2018-11-09T01:13:44.864866Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.

2018-11-09T01:13:44.865483Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ‘.\dbs-gold_report\mt4_users.ibd’ OS error: 103

2018-11-09T01:13:44.866346Z 0 [ERROR] Invalid (old?) table or database name ‘dbs-gold_report’

2018-11-09T01:13:44.866364Z 0 [ERROR] Invalid (old?) table or database name ‘dbs-gold_report’

2018-11-09T01:13:44.866398Z 0 [ERROR] Invalid (old?) table or database name ‘dbs-gold_report’

2018-11-09T01:13:44.866957Z 0 [ERROR] Invalid (old?) table or database name ‘dbs-gold_report’

2018-11-09T01:13:44.867540Z 0 [ERROR] Invalid (old?) table or database name ‘dbs-gold_report’

2018-11-09T01:13:44.867991Z 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.

2018-11-09T01:13:44.869500Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.

2018-11-09T01:13:44.870031Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: ‘.\dbs-gold_report\mt4_trades_copy.ibd’ OS error: 103

2018-11-09T01:13:44.870817Z 0 [ERROR] Invalid (old?) table or database name ‘dbs-gold_report’

2018-11-09T01:13:44.871338Z 0 [ERROR] Invalid (old?) table or database name ‘dbs-gold_report’

2018-11-09T01:13:44.871834Z 0 [ERROR] Invalid (old?) table or database name ‘dbs-gold_report’

2018-11-09T01:13:44.871342Z 0 [ERROR] Invalid (old?) table or database name ‘dbs-gold_report’

2018-11-09T01:13:44.872736Z 0 [ERROR] Invalid (old?) table or database name ‘dbs-gold_report’

2018-11-09T01:13:44.873149Z 0 [ERROR] Invalid (old?) table or database name ‘dbs-gold_report’

2018-11-09T01:13:44.873656Z 0 [ERROR] Invalid (old?) table or database name ‘dbs-gold_report’

2018-11-09T01:13:44.874165Z 0 [ERROR] Invalid (old?) table or database name ‘dbs-gold_report’

2018-11-09T01:13:44.874686Z 0 [ERROR] Invalid (old?) table or database name ‘dbs-gold_report’

2018-11-09T01:13:44.875264Z 0 [ERROR] Invalid (old?) table or database name ‘dbs-gold_report’

2018-11-09T01:14:06.944772Z 8 [ERROR] InnoDB: Assertion failure: dict0dict.cc:1331:table2 == NULL

InnoDB: thread 2928

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.

my.ini 中增加配置项innodb_force_recovery = 1

警告

innodb_force_recovery 在紧急情况下仅设置为大于0的值，以便您可以启动InnoDB和转储表。在此之前，请确保您拥有数据库的备份副本，以备需要重新创建时使用。值为4或更大可能会永久损坏数据文件。innodb_force_recovery在成功测试数据库的单独物理副本上的设置后，仅在生产服务器实例上使用 4或更高的设置。强制InnoDB恢复时，您应该始终使用 innodb_force_recovery=1并且只在必要时以递增方式增加值。

http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html

1 (SRV_FORCE_IGNORE_CORRUPT)

即使检测到损坏的页面，也允许服务器运行。尝试跳过损坏的索引记录和页面，这有助于转储表。 SELECT * FROM tbl_name

2 (SRV_FORCE_NO_BACKGROUND)

防止主线程和任何清除线程运行。如果在清除操作期间发生崩溃，则此恢复值会阻止它。

3 (SRV_FORCE_NO_TRX_UNDO)

崩溃恢复后不运行事务回滚。

4 (SRV_FORCE_NO_IBUF_MERGE)

阻止插入缓冲区合并操作。如果它们会导致崩溃，则不会这样做。不计算表统计信息。此值可能会永久损坏数据文件。使用此值后，请准备删除并重新创建所有二级索引。设置 InnoDB为只读。

5 (SRV_FORCE_NO_UNDO_LOG_SCAN)

启动数据库时不查看撤消日志： InnoDB将未完成的事务视为已提交。此值可能会永久损坏数据文件。设置InnoDB为只读。

6 (SRV_FORCE_NO_LOG_REDO)