Buy Percona ServicesBuy Now!

Column count of mysql.user is wrong. Expected 45, found 48.

Lastest Forum Posts - May 30, 2017 - 4:41pm
Debian 8 and ubuntu 16.04 (same percona server version). Versions:

ii percona-release 0.1-4.jessie all Package to install Percona gpg key and APT repo
ii percona-server-client-5.7 5.7.18-15-1.jessie amd64 Percona Server database client binaries
ii percona-server-common-5.7 5.7.18-15-1.jessie amd64 Percona Server database common files (e.g. /etc/mysql/my.cnf)
ii percona-server-server-5.7 5.7.18-15-1.jessie amd64 Percona Server database server binaries

This started to happen after upgrade to 5.7.18 (works fine on .17) - i can't edit permissions. Anything related to permissions (grant, create user, etc) will fail with "ERROR 1805 (HY000): Column count of mysql.user is wrong. Expected 45, found 48. The table is probably corrupted". And yes, i run mysql_upgrade after upgrade.

Current mysql.user table structure:

| Host | User | Select_priv | Insert_priv | Update_priv | Delete_priv | Create_priv | Drop_priv | Reload_priv | Shutdown_priv | Process_priv | File_priv | Grant_priv | References_priv | Index_priv | Alter_priv | Show_db_priv | Super_priv | Create_tmp_table_priv | Lock_tables_priv | Execute_priv | Repl_slave_priv | Repl_client_priv | Create_view_priv | Show_view_priv | Create_routine_priv | Alter_routine_priv | Create_user_priv | Event_priv | Trigger_priv | Create_tablespace_priv | ssl_type | ssl_cipher | x509_issuer | x509_subject | max_questions | max_updates | max_connections | max_user_connections | plugin | auth_string | password_expired | is_role | default_role | max_statement_time | password_last_changed | password_lifetime | account_locked |

Thanks in advance.

xtrabackup vs. MEB

Lastest Forum Posts - May 30, 2017 - 12:35pm
We have recently decided to end our MySQL Enterprise contract. We're currently testing a Percona cluster, and will likely switch to this architecture across the board if all goes well. My first step is to convert the script I use to populate the dev / test DBs with production data. It's currently largely using MySQL Enterprise Backup, with mysqldump to preserve some environment-specific schemas. I have some basic questions, as I get started:
First, looking through the documentation and examples, some use innobackupex, while others use xtrabackup. In the current version, is there a difference between these, and if so, what?

The current process backups up the environment-specific data, wipes out the existing data and logs, then creates a backup of productions, streams it across via ssh, restores it on the target, restores the preserved data, and re-deploys the stored procs / functions from SVN. When working with a cluster as the target, what's the most efficient process for doing this? Assume no other traffic is hitting it at the time, as we shut down access during a sync. If I refresh one machine and leave the others alone, will the changes correctly replicate across, or do I need to wipe them all?

Percona XtraBackup 2.4.7-2 is Now Available

Latest MySQL Performance Blog posts - May 30, 2017 - 9:53am

Percona announces the GA release of Percona XtraBackup 2.4.7-2 on May 29, 2017. You can download it from our download site and apt and yum repositories.

Percona XtraBackup enables MySQL backups without blocking user queries, making it ideal for companies with large data sets and mission-critical applications that cannot tolerate long periods of downtime. Offered free as an open source solution, Percona XtraBackup drives down backup costs while providing unique features for MySQL backups.

Bug Fixed:
  • Fixed build failure on Debian 9.0 (Stretch). Bug fixed #1678947.

Release notes with all the bugfixes for Percona XtraBackup 2.4.7-2 are available in our online documentation. Please report any bugs to the launchpad bug tracker.

Webinar May 31, 2017: Online MySQL Backups with Percona XtraBackup

Latest MySQL Performance Blog posts - May 30, 2017 - 9:40am

Please join Percona’s solution engineer, Dimitri Vanoverbeke as he presents Online MySQL Backups with Percona XtraBackup on Wednesday, May 31, 2017 at 7:00 am PDT / 10:00 am EDT (UTC-7).

Register Now

Percona XtraBackup is a free, open source, complete online backup solution for all versions of Percona Server, MySQL® and MariaDB®. Percona XtraBackup provides:

  • Fast and reliable backups
  • Uninterrupted transaction processing during backups
  • Savings on disk space and network bandwidth with better compression
  • Automatic backup verification
  • Higher uptime due to faster restore time

This webinar will discuss the different features of Percona XtraBackup, including:

  • Full and incremental backups
  • Compression, streaming, and encryption of backups
  • Backing up to the cloud (swift)
  • Percona XtraDB Cluster / Galera Cluster
  • Percona Server specific features
  • MySQL 5.7 support
  • Tools that use Percona XtraBackup
  • Limitations

Register for the webinar here.

Dimitri Vanoverbeke, Solution Engineer

At the age of seven, Dimitri received his first computer. Since then he has felt addicted to anything with a digital pulse. Dimitri has been active in IT professionally since 2003, when he took various roles from internal system engineering to consulting. Prior to joining Percona, Dimitri worked as a consultant for a leading open source software consulting firm in Belgium. During his career, Dimitri has become familiar with a broad range of open source solutions and with the devops philosophy. Whenever he’s not glued to his computer screen, he enjoys traveling, cultural activities, basketball and the great outdoors.

 

Xtrabackup replication recepe - missing the bin log file

Lastest Forum Posts - May 30, 2017 - 5:45am
Hi,

I'm trying to set up a somple master-slave replication with innobackupex according to recepe:

https://www.percona.com/doc/percona-...plication.html

All goes fine, except in when I get to step 5:
cat /var/lib/mysql/xtrabackup_binlog_info the xtrabackup_binlog_info file doesn't exist. Any suggestions on this?

Percona Monitoring and Management 1.1.4 is now available

Lastest Forum Posts - May 30, 2017 - 2:10am
Percona announces the release of Percona Monitoring and Management 1.1.4 on May 29, 2017.

For installation instructions, see the Deployment Guide.

This release includes experimental support for MongoDB in Query Analytics, including updated QAN interface.
Query Analytics for MongoDB


To enable MongoDB query analytics, use the mongodb:queries alias when adding the service. As an experimental feature, it also requires the --dev-enable option:


Code: sudo pmm-admin add --dev-enable mongodb:queries NOTE: Currently, it monitors only collections that are present when you enable MongoDB query analytics. Query data for collections that you add later is not gathered. This is a known issue and it will be fixed in the future. Query Analytics Redesign


The QAN web interface was updated for better usability and functionality (including the new MongoDB query analytics data). The new UI is experimental and available by specifying /qan2 after the URL of PMM Server.



NOTE: The button on the main landing page still points to the old QAN interface.

You can check out the new QAN web UI at https://pmmdemo.percona.com/qan2 New in PMM Server
  • PMM-724: Added the Index Condition Pushdown (ICP) graph to the MySQL InnoDB Metrics dashboard.
  • PMM-734: Fixed the MySQL Active Threads graph in the MySQL Overview dashboard.
  • PMM-807: Fixed the MySQL Connections graph in the MySQL Overview dashboard.
  • PMM-850: Updated the MongoDB RocksDB and MongoDB WiredTiger dashboards.
  • Removed the InnoDB Deadlocks and Index Collection Pushdown graphs from the MariaDB dashboard.
  • Added tooltips with descriptions for graphs in the MySQL Query Response Time dashboard.Similar tooltips will be gradually added to all graphs.
New in PMM Client
  • PMM-801: Improved PMM Client upgrade process to preserve credentials that are used by services.
  • Added options for pmm-admin to enable MongoDB cluster connections.
About Percona Monitoring and Management


Percona Monitoring and Management is an open-source platform for managing and monitoring MySQL and MongoDB performance. Percona developed it in collaboration with experts in the field of managed database services, support and consulting.

PMM is a free and open-source solution that you can run in your own environment for maximum security and reliability. It provides thorough time-based analysis for MySQL and MongoDB servers to ensure that your data works as efficiently as possible.

A live demo of PMM is available at pmmdemo.percona.com.

Please provide your feedback and questions on the PMM forum.

If you would like to report a bug or submit a feature request, use the PMM project in JIRA.

Percona Monitoring and Management 1.1.4 is now available

Latest MySQL Performance Blog posts - May 29, 2017 - 12:28pm

Percona announces the release of Percona Monitoring and Management 1.1.4 on May 29, 2017.

For installation instructions, see the Deployment Guide.

This release includes experimental support for MongoDB in Query Analytics, including updated QAN interface.

Query Analytics for MongoDB

To enable MongoDB query analytics, use the mongodb:queries alias when adding the service. As an experimental feature, it also requires the --dev-enable option:

sudo pmm-admin add --dev-enable mongodb:queries

NOTE: Currently, it monitors only collections that are present when you enable MongoDB query analytics. Query data for collections that you add later is not gathered. This is a known issue and it will be fixed in the future.

Query Analytics Redesign

The QAN web interface was updated for better usability and functionality (including the new MongoDB query analytics data). The new UI is experimental and available by specifying /qan2 after the URL of PMM Server.

NOTE: The button on the main landing page still points to the old QAN interface.

You can check out the new QAN web UI at https://pmmdemo.percona.com/qan2

New in PMM Server
  • PMM-724: Added the Index Condition Pushdown (ICP) graph to the MySQL InnoDB Metrics dashboard.
  • PMM-734: Fixed the MySQL Active Threads graph in the MySQL Overview dashboard.
  • PMM-807: Fixed the MySQL Connections graph in the MySQL Overview dashboard.
  • PMM-850: Updated the MongoDB RocksDB and MongoDB WiredTiger dashboards.
  • Removed the InnoDB Deadlocks and Index Collection Pushdown graphs from the MariaDB dashboard.
  • Added tooltips with descriptions for graphs in the MySQL Query Response Time dashboard.Similar tooltips will be gradually added to all graphs.
New in PMM Client
  • PMM-801: Improved PMM Client upgrade process to preserve credentials that are used by services.
  • Added options for pmm-admin to enable MongoDB cluster connections.
About Percona Monitoring and Management

Percona Monitoring and Management is an open-source platform for managing and monitoring MySQL and MongoDB performance. Percona developed it in collaboration with experts in the field of managed database services, support and consulting.

PMM is a free and open-source solution that you can run in your own environment for maximum security and reliability. It provides thorough time-based analysis for MySQL and MongoDB servers to ensure that your data works as efficiently as possible.

A live demo of PMM is available at pmmdemo.percona.com.

Please provide your feedback and questions on the PMM forum.

If you would like to report a bug or submit a feature request, use the PMM project in JIRA.

mysql 5.7 withc gtid innobackupex options for master backup and new slave

Lastest Forum Posts - May 29, 2017 - 8:04am
- Used innobackupex with this options to get a backup from the master:
innobackupex /var/backup/xtra --slave-info --safe-slave-backup

- The master and the (future) slave running mysql 5.7 with GTID:
# mysql -sre "show global variables"| grep gtid_mode
gtid_mode ON

- After moving the backup to the Slave and restoring it with:
innobackupex --apply-log /var/backups/xtra/2017-05-26_22-49-20/
innobackupex --copy-back /var/backups/xtra/2017-05-26_22-49-20/

- But Replicacion is getting errors:
Last_SQL_Error: Could not execute Write_rows event on table XXXXX; Duplicate entry 'XXX' for key 'PRIMARY', Error_code: 1062; handler error HA_ERR_FOUND_DUPP_KEY; the event's master log mysql-bin.002255, end_log_pos 1384983

My doubt is if the options --slave-info or --safe-slave-backup in a Master with GTID can cause this problems.

Thanks.
Visit Percona Store


General Inquiries

For general inquiries, please send us your question and someone will contact you.