Bug #75722 | MEB 3.11.1 Failed trying to flush for export | ||
---|---|---|---|
Submitted: | 2 Feb 2015 10:31 | Modified: | 10 Jun 2015 18:57 |
Reporter: | LACHEVRE JEREMY | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Enterprise Backup | Severity: | S2 (Serious) |
Version: | 3.11.1 | OS: | Linux |
Assigned to: | CPU Architecture: | Any | |
Tags: | Backup |
[2 Feb 2015 10:31]
LACHEVRE JEREMY
[2 Feb 2015 11:42]
MySQL Verification Team
Hello LACHEVRE JEREMY, Thank you for the report. Thanks, Umesh
[2 Feb 2015 11:47]
MySQL Verification Team
// How to repeat // 5.6.24 mysql> create database asn_sn; Query OK, 1 row affected (0.00 sec) mysql> use asn_sn Database changed mysql> create table ATEQFILTERMO select 1; Query OK, 1 row affected (0.01 sec) Records: 1 Duplicates: 0 Warnings: 0 mysql> create table ATEQMO$ATEQSUBSYSTEMMOLISTWRAPPER select 2; Query OK, 1 row affected (0.01 sec) Records: 1 Duplicates: 0 Warnings: 0 mysql> create table ATEQMO select 3; Query OK, 1 row affected (0.01 sec) Records: 1 Duplicates: 0 Warnings: 0 mysql> create table AteqMo_childrenAteqSubSystemList select 4; Query OK, 1 row affected (0.00 sec) Records: 1 Duplicates: 0 Warnings: 0 mysql> show tables; +-----------------------------------+ | Tables_in_asn_sn | +-----------------------------------+ | ATEQFILTERMO | | ATEQMO | | ATEQMO$ATEQSUBSYSTEMMOLISTWRAPPER | | AteqMo_childrenAteqSubSystemList | +-----------------------------------+ 4 rows in set (0.00 sec)
[2 Feb 2015 11:47]
MySQL Verification Team
// initiate backup [ushastry@ushastry]~/bugs/setups/meb-3-11-2-el7-x86-64bit: bin/mysqlbackup --user=root --include-tables=^asn_sn. --use-tts --backup-dir=/export/umesh/mysql-5.6.24/bkup --socket=/tmp/mysql_ushastry.sock --with-timestamp backup MySQL Enterprise Backup version 3.11.2 Linux-3.8.13-35.3.1.el7uek.x86_64-x86_64 [2014/12/04] Copyright (c) 2003, 2014, Oracle and/or its affiliates. All Rights Reserved. mysqlbackup: INFO: Starting with following command line ... bin/mysqlbackup --user=root --include-tables=^asn_sn. --use-tts --backup-dir=/export/umesh/mysql-5.6.24/bkup --socket=/tmp/mysql_ushastry.sock --with-timestamp backup mysqlbackup: INFO: mysqlbackup: INFO: MySQL server version is '5.6.24-enterprise-commercial-advanced-debug'. mysqlbackup: INFO: Got some server configuration information from running server. mysqlbackup: INFO: Skipping binlogs and relaylogs in case of TTS backup. IMPORTANT: Please check that mysqlbackup run completes successfully. At the end of a successful 'backup' run mysqlbackup prints "mysqlbackup completed OK!". 150202 12:45:05 mysqlbackup: INFO: MEB logfile created at /export/umesh/mysql-5.6.24/bkup/2015-02-02_12-45-05/meta/MEB_2015-02-02.12-45-05_backup.log -------------------------------------------------------------------- Server Repository Options: -------------------------------------------------------------------- datadir = /export/umesh/mysql-5.6.24/75718/ innodb_data_home_dir = innodb_data_file_path = ibdata1:12M:autoextend innodb_log_group_home_dir = /export/umesh/mysql-5.6.24/75718/ innodb_log_files_in_group = 2 innodb_log_file_size = 50331648 innodb_page_size = 16384 innodb_checksum_algorithm = innodb innodb_undo_directory = /export/umesh/mysql-5.6.24/75718/ innodb_undo_tablespaces = 0 innodb_undo_logs = 128 -------------------------------------------------------------------- Backup Config Options: -------------------------------------------------------------------- datadir = /export/umesh/mysql-5.6.24/bkup/2015-02-02_12-45-05/datadir innodb_data_home_dir = /export/umesh/mysql-5.6.24/bkup/2015-02-02_12-45-05/datadir innodb_data_file_path = ibdata1:12M:autoextend innodb_log_group_home_dir = /export/umesh/mysql-5.6.24/bkup/2015-02-02_12-45-05/datadir innodb_log_files_in_group = 2 innodb_log_file_size = 50331648 innodb_page_size = 16384 innodb_checksum_algorithm = innodb innodb_undo_directory = /export/umesh/mysql-5.6.24/bkup/2015-02-02_12-45-05/datadir innodb_undo_tablespaces = 0 innodb_undo_logs = 128 mysqlbackup: INFO: Unique generated backup id for this is 14228775053843719 mysqlbackup: INFO: Creating 14 buffers each of size 16777216. 150202 12:45:07 mysqlbackup: INFO: Full Backup operation starts with following threads 1 read-threads 6 process-threads 1 write-threads 150202 12:45:07 mysqlbackup: INFO: System tablespace file format is Antelope. 150202 12:45:07 mysqlbackup: INFO: Starting to copy all innodb files... 150202 12:45:07 mysqlbackup: INFO: Found checkpoint at lsn 1673093. 150202 12:45:07 mysqlbackup: INFO: Starting log scan from lsn 1672704. 150202 12:45:07 mysqlbackup: INFO: Copying log... 150202 12:45:07 mysqlbackup: INFO: Copying /export/umesh/mysql-5.6.24/75718/asn_sn/ATEQFILTERMO.ibd (Antelope file format). 150202 12:45:07 mysqlbackup: INFO: Copying /export/umesh/mysql-5.6.24/75718/asn_sn/ATEQMO.ibd (Antelope file format). 150202 12:45:07 mysqlbackup: INFO: Log copied, lsn 1673093. 150202 12:45:07 mysqlbackup: INFO: Copying /export/umesh/mysql-5.6.24/75718/asn_sn/ATEQMO@0024ATEQSUBSYSTEMMOLISTWRAPPER.ibd (Antelope file format). 150202 12:45:07 mysqlbackup: INFO: Copying /export/umesh/mysql-5.6.24/75718/asn_sn/AteqMo_childrenAteqSubSystemList.ibd (Antelope file format). 150202 12:45:07 mysqlbackup: INFO: Completing the copy of innodb files. 150202 12:45:07 mysqlbackup: INFO: Preparing to lock tables: Connected to mysqld server. 150202 12:45:07 mysqlbackup: INFO: Starting to lock all the tables... mysqlbackup: ERROR: mysql query: 'FLUSH TABLES asn_sn.ATEQFILTERMO,asn_sn.ATEQMO,asn_sn.ATEQMO@0024ATEQSUBSYSTEMMOLISTWRAPPER,asn_sn.AteqMo_childrenAteqSubSystemList FOR EXPORT': Not unique table/alias: 'ATEQMO' mysqlbackup: ERROR: Failed trying to flush for export. mysqlbackup failed with errors!
[2 Feb 2015 13:23]
LACHEVRE JEREMY
Thanks to reproduce the problem. When do you plan a correction? (3.11.2 ?) Thanks regards Lachevre Jeremy
[9 Feb 2015 11:11]
Jothir Ganesan
Bug 19471781 - FLUSH TABLE ERROR WHILE TAKING FULL BACKUP USING USE-TTS exists
[19 Feb 2015 10:47]
Sveta Smirnova
Posted by developer: Jothir, these bugs are different, because *this* bug does not use any special character in the pattern: /local/sql/meb/bin/mysqlbackup --defaults-file=/local/sql/etc/my.cnf --include-tables=^asn_sn. --use-tts Symbols "^" and "." are special symbols for regular expressions, not special characters in tables. I don't understand why MEB should fail in this case and how it is related to backticks.
[10 Jun 2015 18:57]
Daniel So
Added the following entry to the MySQL Enterprise Backup 3.12.1 changelog: "A backup failed with the error message “Failed trying to flush for export” if the names of any table mysqlbackup tried to back up contained special characters (spaces, dashes, periods, dollar signs, etc.). With this fix, table names with special characters are now supported."