1. 环境说明
RHEL 6.4 x86_64 + MySQL 5.5.37和MySQL 5.6.19
blog地址:http://blog.csdn.net/hw_libo/article/details/39215723
2. 案例:redo log文件(ib_logfile)大小参数被修改:innodb_log_file_size
innodb_log_file_size = 256M -- 修改为200M
版本是5.5的,启动失败,会出现如下错误:
InnoDB: Error: log file ./ib_logfile0 is of different size 0 268435456 bytes ## 原来redo log的大小 InnoDB: than specified in the .cnf file 0 209715200 bytes! ## redo log被修改的大小 140912 0:01:12 [ERROR] Plugin 'InnoDB' init function returned error. 140912 0:01:12 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 140912 0:01:12 [ERROR] Unknown/unsupported storage engine: InnoDB 140912 0:01:12 [ERROR] Aborting版本是5.6.16之后的,正常启动,会自动将原来的redo log删除,然后重新生成新的redo log(这个比较重要):
2014-09-11 21:57:05 1093 [Warning] InnoDB: Resizing redo log from 2*16384 to 2*12800 pages, LSN=71249171 2014-09-11 21:57:05 1093 [Warning] InnoDB: Starting to delete and rewrite log files. ## 删除原redo log 2014-09-11 21:57:05 1093 [Note] InnoDB: Setting log file ./ib_logfile101 size to 200 MB InnoDB: Progress in MB: 100 200 2014-09-11 21:57:06 1093 [Note] InnoDB: Setting log file ./ib_logfile1 size to 200 MB InnoDB: Progress in MB: 100 200 2014-09-11 21:57:07 1093 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0 2014-09-11 21:57:07 1093 [Warning] InnoDB: New log files created, LSN=71249171 ## 新redo log重建完毕原redo log大小:2*16384*8(page的大小为8k)/1024=256MB
新redo log大小:2*12800*8/1024=200MB
3. 案例:ibdata1文件大小参数被修改:innodb_data_file_path
(1)ibdata1从大改小
innodb_data_file_path = ibdata1:1G:autoextend -- 修改为:ibdata1:300M:autoextend
在版本是5.5和5.6中,启动正常,并且日志中没有任何异常。但是如果将autoextend去掉,就会报错,启动失败,如:[版本:5.5.37]
InnoDB: Error: data file ./ibdata1 is of a different size InnoDB: 65536 pages (rounded down to MB) InnoDB: than specified in the .cnf file 19200 pages! 140911 23:51:53 InnoDB: Could not open or create data files. 140911 23:51:53 InnoDB: If you tried to add new data files, and it failed here, 140911 23:51:53 InnoDB: you should now edit innodb_data_file_path in my.cnf back 140911 23:51:53 InnoDB: to what it was, and remove the new ibdata files InnoDB created 140911 23:51:53 InnoDB: in this failed attempt. InnoDB only wrote those files full of 140911 23:51:53 InnoDB: zeros, but did not yet use them in any way. But be careful: do not 140911 23:51:53 InnoDB: remove old data files which contain your precious data! 140911 23:51:53 [ERROR] Plugin 'InnoDB' init function returned error. 140911 23:51:53 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 140911 23:51:53 [ERROR] Unknown/unsupported storage engine: InnoDB 140911 23:51:53 [ERROR] Aborting 原来的ibdata1大小为:65536*8*2/1024=1024M=1G 当前ibdata1被修改为:19200*8*2/1024=300M(2)ibdata1值小改大
比如:
innodb_data_file_path = ibdata1:1G:autoextend -- 修改为:ibdata1:1200M:autoextend
那么会在启动时出现如下错误:
*****在5.5版本中:[版本:5.5.37]
InnoDB: Error: auto-extending data file ./ibdata1 is of a different size InnoDB: 65536 pages (rounded down to MB) than specified in the .cnf file: InnoDB: initial 76800 pages, max 0 (relevant if non-zero) pages! 140911 23:57:43 InnoDB: Could not open or create data files. 140911 23:57:43 InnoDB: If you tried to add new data files, and it failed here, 140911 23:57:43 InnoDB: you should now edit innodb_data_file_path in my.cnf back 140911 23:57:43 InnoDB: to what it was, and remove the new ibdata files InnoDB created 140911 23:57:43 InnoDB: in this failed attempt. InnoDB only wrote those files full of 140911 23:57:43 InnoDB: zeros, but did not yet use them in any way. But be careful: do not 140911 23:57:43 InnoDB: remove old data files which contain your precious data! 140911 23:57:43 [ERROR] Plugin 'InnoDB' init function returned error. 140911 23:57:43 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 140911 23:57:43 [ERROR] Unknown/unsupported storage engine: InnoDB 140911 23:57:43 [ERROR] Aborting*****在5.6版本中:[版本:5.6.19]
2014-09-11 22:20:01 1222 [ERROR] InnoDB: auto-extending data file ./ibdata1 is of a different size 65536 pages (rounded down to MB) than specified in the .cnf file: initial 76800 pages, max 0 (relevant if non-zero) pages! 2014-09-11 22:20:01 1222 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the syste m tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata fil es InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be caref ul: do not remove old data files which contain your precious data! 2014-09-11 22:20:01 1222 [ERROR] Plugin 'InnoDB' init function returned error. 2014-09-11 22:20:01 1222 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 2014-09-11 22:20:01 1222 [ERROR] Unknown/unsupported storage engine: InnoDB 2014-09-11 22:20:01 1222 [ERROR] Aborting原来的ibdata1大小为:65536*8*2/1024=1024M=1G
当前ibdata1被修改为:76800*8*2/1024=1200M
blog地址:http://blog.csdn.net/hw_libo/article/details/39215723
-- Bosco QQ:375612082
---- END ----
-------------------------------------------------------------------------------------------------------
版权所有,文章允许转载,但必须以链接方式注明源地址,否则追究法律责任!

掌握添加MySQL用户的方法对于数据库管理员和开发者至关重要,因为它确保数据库的安全性和访问控制。1)使用CREATEUSER命令创建新用户,2)通过GRANT命令分配权限,3)使用FLUSHPRIVILEGES确保权限生效,4)定期审计和清理用户账户以维护性能和安全。

chosecharforfixed-lengthdata,varcharforvariable-lengthdata,andtextforlargetextfield.1)chariseffity forconsistent-lengthdatalikecodes.2)varcharsuitsvariable-lengthdatalikenames,ballancingflexibilitibility andperformance.3)

在MySQL中处理字符串数据类型和索引的最佳实践包括:1)选择合适的字符串类型,如CHAR用于固定长度,VARCHAR用于可变长度,TEXT用于大文本;2)谨慎索引,避免过度索引,针对常用查询创建索引;3)使用前缀索引和全文索引优化长字符串搜索;4)定期监控和优化索引,保持索引小巧高效。通过这些方法,可以在读取和写入性能之间取得平衡,提升数据库效率。

ToaddauserremotelytoMySQL,followthesesteps:1)ConnecttoMySQLasroot,2)Createanewuserwithremoteaccess,3)Grantnecessaryprivileges,and4)Flushprivileges.BecautiousofsecurityrisksbylimitingprivilegesandaccesstospecificIPs,ensuringstrongpasswords,andmonitori

tostorestringsefliceflicyInmySql,ChooSetherightDataTypeBasedyOrneOrneEds:1)USEcharforFixed-LengthStstringStringStringSlikeCountryCodes.2)UseVarcharforvariable-lengtthslikenames.3)USETEXTCONTENT.3)

选择MySQL的BLOB和TEXT数据类型时,BLOB适合存储二进制数据,TEXT适合存储文本数据。1)BLOB适用于图片、音频等二进制数据,2)TEXT适用于文章、评论等文本数据,选择时需考虑数据性质和性能优化。

No,youshouldnotusetherootuserinMySQLforyourproduct.Instead,createspecificuserswithlimitedprivilegestoenhancesecurityandperformance:1)Createanewuserwithastrongpassword,2)Grantonlynecessarypermissionstothisuser,3)Regularlyreviewandupdateuserpermissions

mySqlStringDatatatPessHouldBechoseBeadeDataCharacteristicsAndUsecases:1)USECHARFORFIXED LENGTHSTRINGSTRINGSLIKECOUNTRYCODES.2)USEDES.2)usevarcharforvariable-lengtthstringstringstringstringstringstringstringslikenames.3)usebinaryorvarrinaryorvarinarydatalbonydatalgebgeenfopical.4)


热AI工具

Undresser.AI Undress
人工智能驱动的应用程序,用于创建逼真的裸体照片

AI Clothes Remover
用于从照片中去除衣服的在线人工智能工具。

Undress AI Tool
免费脱衣服图片

Clothoff.io
AI脱衣机

Video Face Swap
使用我们完全免费的人工智能换脸工具轻松在任何视频中换脸!

热门文章

热工具

SecLists
SecLists是最终安全测试人员的伙伴。它是一个包含各种类型列表的集合,这些列表在安全评估过程中经常使用,都在一个地方。SecLists通过方便地提供安全测试人员可能需要的所有列表,帮助提高安全测试的效率和生产力。列表类型包括用户名、密码、URL、模糊测试有效载荷、敏感数据模式、Web shell等等。测试人员只需将此存储库拉到新的测试机上,他就可以访问到所需的每种类型的列表。

Dreamweaver Mac版
视觉化网页开发工具

MinGW - 适用于 Windows 的极简 GNU
这个项目正在迁移到osdn.net/projects/mingw的过程中,你可以继续在那里关注我们。MinGW:GNU编译器集合(GCC)的本地Windows移植版本,可自由分发的导入库和用于构建本地Windows应用程序的头文件;包括对MSVC运行时的扩展,以支持C99功能。MinGW的所有软件都可以在64位Windows平台上运行。

SublimeText3 英文版
推荐:为Win版本,支持代码提示!

WebStorm Mac版
好用的JavaScript开发工具