MySQL 5.6 Failure

I have the following in RPM_UPGRADE_HISTORY in /var/lib/mysql

MySQL RPM upgrade to version 5.6.10-1.linux_glibc2.5
'pre' step running at Fri Mar 15 15:41:26 EDT 2013

ERR file(s):
-rw-r----- 1 mysql root 1725 2013-03-15 13:45 /var/lib/mysql/mysql.err

I checked the error file to find this information:

```
2013-03-15 15:43:22 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2013-03-15 15:43:22 11993 [Note] Plugin 'FEDERATED' is disabled.
2013-03-15 15:43:22 11993 [Note] InnoDB: The InnoDB memory heap is disabled
2013-03-15 15:43:22 11993 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2013-03-15 15:43:22 11993 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-03-15 15:43:22 11993 [Note] InnoDB: CPU does not support crc32 instructions
2013-03-15 15:43:22 11993 [Note] InnoDB: Using Linux native AIO
2013-03-15 15:43:22 11993 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2013-03-15 15:43:22 11993 [Note] InnoDB: Completed initialization of buffer pool
2013-03-15 15:43:22 11993 [ERROR] InnoDB: auto-extending data file ./ibdata1 is of a different size 640 pages (rounded down to MB) than specified in the .cnf file: initial 768 pages, max 0 (relevant if non-zero) pages!
2013-03-15 15:43:22 11993 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system 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 files 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 careful: do not remove old data files which contain your precious data!
2013-03-15 15:43:22 11993 [ERROR] Plugin 'InnoDB' init function returned error.
2013-03-15 15:43:22 11993 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2013-03-15 15:43:22 119

DISCLAIMER : Not a Full Expert on MySQL 5.6

Looks like the InnoDB Plugin is complaining about the present ibdata1 file.

If data and index pages exist inside ibdata1, it's probably using Antelope as the innodb_file_format.

There are four(4) things you can try:
SUGGESTION #1 : UNINSTALL AND REINSTALL MySQL 5.6

• Uninstall MySQL

• mv /var/lib/mysql /var/lib/mysql_old

• Reinstall MySQL

SUGGESTION #2 : Using a cleaned-up datadir

mv /var/lib/mysql /var/lib/mysql_old
mkdir /var/lib/mysql
mkdir /var/lib/mysql/mysql
cp /var/lib/mysql_old /var/lib/mysql/mysql
chown -R mysql:mysql /var/lib/mysql/mysql
service mysql start

This will construct brand spanking new InnoDB Files

• /var/lib/mysql/ibdata1

• /var/lib/mysql/ib_logfile0

• /var/lib/mysql/ib_logfile1

SUGGESTION #3 : Switch innodb_file_format (May be risky)

This may be a little risky but add this to my.cnf

[mysqld]
innodb_file_format=Barracuda
innodb_file_format_max=Barracuda

and restart mysql
SUGGESTION #4 : GIVE IT A TRY !!!

StackExchange Database Administrators Q#36804, answer score: 7