search

ekofedriyanto / common-schema

Automatically exported from code.google.com/p/common-schema
0 stars 0 forks source link

Percona Server components not installed on `Percona Server compatible` flavours #26

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Which version of common_schema are you using?
1.1

Which component is failing?
Percona Server components

What is the expected output? What do you see instead?
+-----------------------------------------------------------+
| complete                                                  |
+-----------------------------------------------------------+
| - Base components: installed                              |
| - InnoDB Plugin components: not installed                 |
| - Percona Server components: not installed                |
|                                                           |
| Installation complete. Thank you for using common_schema! |
+-----------------------------------------------------------+

Can you provide with sample data?
N/A

(As of version 1.1), please provide output of SELECT * FROM common_schema.status
MariaDB [(none)]>SELECT * FROM common_schema.status\G
*************************** 1. row ***************************
                       project_name: common_schema
                            version: 1.1
                           revision: 300
                       install_time: 2012-09-25 07:39:45
                    install_success: 1
          base_components_installed: 1
 innodb_plugin_components_installed: 0
percona_server_components_installed: 0
              install_mysql_version: 5.5.27-MariaDB-log
                   install_sql_mode: 
1 row in set (0.11 sec)

Please provide any additional information below.
Being a MariaDB server it has all the advantages of Percona Server.
I believe Percona Server components should also be installed on:
- MariaDB
- TokuDB for MariaDB

I'll be happy to assist in testing these as I work daily with them.

Original issue reported on code.google.com by gabriel....@brainient.com on 24 Sep 2012 at 8:48

GoogleCodeExporter commented 8 years ago 
However if I run the view creation code after this for both innodb_index_rows & 
 innodb_index_stats... it works fine.

Original comment by gabr...@e-radical.ro on 24 Sep 2012 at 9:04

GoogleCodeExporter commented 8 years ago 
Seems like the QueryScript execution does not function properly.

Can you please issue:

SET @s := "SHOW TABLES FROM INFORMATION_SCHEMA";
CALL common_schema.run(@s);

Original comment by shlomi.n...@gmail.com on 25 Sep 2012 at 4:30

GoogleCodeExporter commented 8 years ago 
Is this relates to Issue 25? I see you have submitted both in a short interval. 
Issue 25 explains issue 26, since it clearly fails on InnoDB Plugin + Percona 
Server install process.

Original comment by shlomi.n...@gmail.com on 25 Sep 2012 at 4:32

GoogleCodeExporter commented 8 years ago 
Yes they are related.

MariaDB [(none)]>SET @s := "SHOW TABLES FROM INFORMATION_SCHEMA";
Query OK, 0 rows affected (0.00 sec)

MariaDB [(none)]>CALL common_schema.run(@s);
+---------------------------------------+
| Tables_in_information_schema          |
+---------------------------------------+
| CHARACTER_SETS                        |
| CLIENT_STATISTICS                     |
| COLLATIONS                            |
| COLLATION_CHARACTER_SET_APPLICABILITY |
| COLUMNS                               |
| COLUMN_PRIVILEGES                     |
| ENGINES                               |
| EVENTS                                |
| FILES                                 |
| GLOBAL_STATUS                         |
| GLOBAL_VARIABLES                      |
| INDEX_STATISTICS                      |
| KEY_CACHES                            |
| 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                      |
| TABLE_STATISTICS                      |
| TRIGGERS                              |
| USER_PRIVILEGES                       |
| USER_STATISTICS                       |
| VIEWS                                 |
| INNODB_CMPMEM_RESET                   |
| INNODB_RSEG                           |
| INNODB_UNDO_LOGS                      |
| INNODB_CMPMEM                         |
| INNODB_SYS_TABLESTATS                 |
| INNODB_LOCK_WAITS                     |
| INNODB_INDEX_STATS                    |
| INNODB_CMP                            |
| INNODB_SYS_FOREIGN_COLS               |
| INNODB_CMP_RESET                      |
| INNODB_BUFFER_POOL_PAGES              |
| INNODB_TRX                            |
| INNODB_BUFFER_POOL_PAGES_INDEX        |
| INNODB_LOCKS                          |
| INNODB_BUFFER_POOL_PAGES_BLOB         |
| INNODB_SYS_TABLES                     |
| INNODB_SYS_FIELDS                     |
| INNODB_SYS_COLUMNS                    |
| FEEDBACK                              |
| INNODB_SYS_STATS                      |
| INNODB_SYS_FOREIGN                    |
| INNODB_SYS_INDEXES                    |
| XTRADB_ADMIN_COMMAND                  |
| INNODB_TABLE_STATS                    |
+---------------------------------------+
59 rows in set (0.16 sec)

Query OK, 0 rows affected (0.16 sec)

Original comment by gabr...@e-radical.ro on 25 Sep 2012 at 11:06

GoogleCodeExporter commented 8 years ago 
OK then, I'm closing this one, since it is direct consequence of issue 25.

Original comment by shlomi.n...@gmail.com on 26 Sep 2012 at 5:18