Description:
Manual section "14.4.4.3. Identifying the File Format in Use" refers to
a table INNODB_SYS_TABLES within the db INFORMATION_SCHEMA :
http://dev.mysql.com/doc/refman/5.5/en/innodb-file-format-identifying.html
No such table exists within the standard 5.5.x MySQL install on Solaris.
Thus :
mysql> \s
--------------
/opt/mysql/mysql/bin/mysql Ver 14.14 Distrib 5.5.33, for solaris10 (sparc) using readline 5.1
Connection id: 27
Current database: information_schema
Current user: trend_sql@fep
SSL: Not in use
Current pager: stdout
Using outfile: ''
Using delimiter: ;
Server version: 5.5.33 MySQL Community Server (GPL)
Protocol version: 10
Connection: trend-dev-db via TCP/IP
Server characterset: utf8mb4
Db characterset: utf8
Client characterset: utf8mb4
Conn. characterset: utf8mb4
TCP port: 3306
Uptime: 1 day 17 hours 11 min 40 sec
Threads: 1 Questions: 209 Slow queries: 0 Opens: 51 Flush tables: 1 Open tables: 44 Queries per second avg: 0.001
--------------
mysql> use information_schema;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A
Database changed
mysql> show tables;
+---------------------------------------+
| Tables_in_information_schema |
+---------------------------------------+
| CHARACTER_SETS |
| COLLATIONS |
| COLLATION_CHARACTER_SET_APPLICABILITY |
| COLUMNS |
| COLUMN_PRIVILEGES |
| ENGINES |
| EVENTS |
| FILES |
| GLOBAL_STATUS |
| GLOBAL_VARIABLES |
| KEY_COLUMN_USAGE |
| PARAMETERS |
| PARTITIONS |
| PLUGINS |
| PROCESSLIST |
| PROFILING |
| REFERENTIAL_CONSTRAINTS |
| ROUTINES |
| SCHEMATA |
| SCHEMA_PRIVILEGES |
| SESSION_STATUS |
| SESSION_VARIABLES |
| STATISTICS |
| TABLES |
| TABLESPACES |
| TABLE_CONSTRAINTS |
| TABLE_PRIVILEGES |
| TRIGGERS |
| USER_PRIVILEGES |
| VIEWS |
| INNODB_BUFFER_PAGE |
| INNODB_TRX |
| INNODB_BUFFER_POOL_STATS |
| INNODB_LOCK_WAITS |
| INNODB_CMPMEM |
| INNODB_CMP |
| INNODB_LOCKS |
| INNODB_CMPMEM_RESET |
| INNODB_CMP_RESET |
| INNODB_BUFFER_PAGE_LRU |
+---------------------------------------+
40 rows in set (0.00 sec)
Therefore file format Barracuda can not be detected via the C API or
any other mechanism within MySQL 5.5.33
How to repeat:
mysql> \s
--------------
/opt/mysql/mysql/bin/mysql Ver 14.14 Distrib 5.5.33, for solaris10 (sparc) using readline 5.1
Connection id: 27
Current database: information_schema
Current user: trend_sql@fep
SSL: Not in use
Current pager: stdout
Using outfile: ''
Using delimiter: ;
Server version: 5.5.33 MySQL Community Server (GPL)
Protocol version: 10
Connection: trend-dev-db via TCP/IP
Server characterset: utf8mb4
Db characterset: utf8
Client characterset: utf8mb4
Conn. characterset: utf8mb4
TCP port: 3306
Uptime: 1 day 17 hours 15 min 27 sec
Threads: 1 Questions: 211 Slow queries: 0 Opens: 51 Flush tables: 1 Open tables: 44 Queries per second avg: 0.001
--------------
mysql> SELECT * FROM INFORMATION_SCHEMA.INNODB_SYS_TABLES;
ERROR 1109 (42S02): Unknown table 'INNODB_SYS_TABLES' in information_schema
mysql>
Suggested fix:
Implement table INNODB_SYS_TABLES within the information_schema db.
Description: Manual section "14.4.4.3. Identifying the File Format in Use" refers to a table INNODB_SYS_TABLES within the db INFORMATION_SCHEMA : http://dev.mysql.com/doc/refman/5.5/en/innodb-file-format-identifying.html No such table exists within the standard 5.5.x MySQL install on Solaris. Thus : mysql> \s -------------- /opt/mysql/mysql/bin/mysql Ver 14.14 Distrib 5.5.33, for solaris10 (sparc) using readline 5.1 Connection id: 27 Current database: information_schema Current user: trend_sql@fep SSL: Not in use Current pager: stdout Using outfile: '' Using delimiter: ; Server version: 5.5.33 MySQL Community Server (GPL) Protocol version: 10 Connection: trend-dev-db via TCP/IP Server characterset: utf8mb4 Db characterset: utf8 Client characterset: utf8mb4 Conn. characterset: utf8mb4 TCP port: 3306 Uptime: 1 day 17 hours 11 min 40 sec Threads: 1 Questions: 209 Slow queries: 0 Opens: 51 Flush tables: 1 Open tables: 44 Queries per second avg: 0.001 -------------- mysql> use information_schema; Reading table information for completion of table and column names You can turn off this feature to get a quicker startup with -A Database changed mysql> show tables; +---------------------------------------+ | Tables_in_information_schema | +---------------------------------------+ | CHARACTER_SETS | | COLLATIONS | | COLLATION_CHARACTER_SET_APPLICABILITY | | COLUMNS | | COLUMN_PRIVILEGES | | ENGINES | | EVENTS | | FILES | | GLOBAL_STATUS | | GLOBAL_VARIABLES | | KEY_COLUMN_USAGE | | PARAMETERS | | PARTITIONS | | PLUGINS | | PROCESSLIST | | PROFILING | | REFERENTIAL_CONSTRAINTS | | ROUTINES | | SCHEMATA | | SCHEMA_PRIVILEGES | | SESSION_STATUS | | SESSION_VARIABLES | | STATISTICS | | TABLES | | TABLESPACES | | TABLE_CONSTRAINTS | | TABLE_PRIVILEGES | | TRIGGERS | | USER_PRIVILEGES | | VIEWS | | INNODB_BUFFER_PAGE | | INNODB_TRX | | INNODB_BUFFER_POOL_STATS | | INNODB_LOCK_WAITS | | INNODB_CMPMEM | | INNODB_CMP | | INNODB_LOCKS | | INNODB_CMPMEM_RESET | | INNODB_CMP_RESET | | INNODB_BUFFER_PAGE_LRU | +---------------------------------------+ 40 rows in set (0.00 sec) Therefore file format Barracuda can not be detected via the C API or any other mechanism within MySQL 5.5.33 How to repeat: mysql> \s -------------- /opt/mysql/mysql/bin/mysql Ver 14.14 Distrib 5.5.33, for solaris10 (sparc) using readline 5.1 Connection id: 27 Current database: information_schema Current user: trend_sql@fep SSL: Not in use Current pager: stdout Using outfile: '' Using delimiter: ; Server version: 5.5.33 MySQL Community Server (GPL) Protocol version: 10 Connection: trend-dev-db via TCP/IP Server characterset: utf8mb4 Db characterset: utf8 Client characterset: utf8mb4 Conn. characterset: utf8mb4 TCP port: 3306 Uptime: 1 day 17 hours 15 min 27 sec Threads: 1 Questions: 211 Slow queries: 0 Opens: 51 Flush tables: 1 Open tables: 44 Queries per second avg: 0.001 -------------- mysql> SELECT * FROM INFORMATION_SCHEMA.INNODB_SYS_TABLES; ERROR 1109 (42S02): Unknown table 'INNODB_SYS_TABLES' in information_schema mysql> Suggested fix: Implement table INNODB_SYS_TABLES within the information_schema db.