Tag: MariaDB

Feed: Planet MySQL; Author: Marco Tusa; PREVIOUS POST ProxySQL in its versions up to 1.x did not natively support Percona XtraDB Cluster (PXC). Instead, it relied on the flexibility offered by the scheduler. This approach allowed users to implement their own preferred way to manage the ProxySQL behaviour in relation to the Galera events. From version 2.0 we can use native ProxySQL support for PXC.. The mechanism to activate native support is very similar to the one already in place for group replication. In brief it is based on the table [runtime_]mysql_galera_hostgroups and the information needed is mostly the same: ... Read More

Feed: Planet MySQL; Author: Severalnines; Migrating from Oracle to MySQL/Percona Server is not a trivial task. Although it is getting easier, especially with the arrival of MySQL 8.0 and Percona announced Percona Server for MySQL 8.0 GA. Aside from planning for your migration from Oracle to Percona Server, you must ensure that you understand the purpose and functionality for why it has to be Percona Server. This blog will focus on Migrating from Oracle to Percona Server as its specific target database of choice. There's a page in the Oracle website about SQL Developer Supplementary Information for MySQL Migrations which ... Read More

Feed: Planet MySQL; Author: Valeriy Kravchuk; More than 3 weeks passed since my previous review of public MySQL bug reports I am subscribed to, so it's time to present some of the bugs I've considered interesting in January, 2019.As usual, I'll review them starting from the oldest and try to summarize my feelings about these bugs at the end of this post. Here they are:Bug #93806 - "Document error about ON DUPLICATE KEY UPDATE". Years pass, but fine MySQL manual still does not explain some cases of InnoDB locking properly. Xiaobin Lin found yet another case that it does not explain ... Read More

Feed: MariaDB Knowledge Base Article Feed. Author: . Wrong create options There are several cases where a CREATE TABLE or ALTER TABLE statement that involves encryption on an InnoDB table can throw the following error: Error: 140 Wrong create options. You can usually execute SHOW WARNINGS to get more details about the cause of the error. For example: create table `table1` ( `id` int(4) primary key , `name` varchar(50)); ERROR 1005 (HY000): Can't create table `dba_test`.`table1` (errno: 140 "Wrong create options") show warnings; +---------+------+----------------------------------------------------------------------------+ | Level | Code | Message | +---------+------+----------------------------------------------------------------------------+ | Warning | 140 | InnoDB: innodb_encrypt_tables=OFF only ... Read More

Feed: MariaDB Knowledge Base Article Feed. Author: . In order to enable data-at-rest encryption for tables using the InnoDB or XtraDB storage engines, you first need to configure the Server to use an Encryption Key Management plugin. Once this is done, you can enable encryption by setting the innodb_encrypt_tables system variable to encrypt the InnoDB system and file tablespaces and setting the innodb_encrypt_log system variable to encrypt the InnoDB Redo Log. Setting these system variables enables the encryption feature for InnoDB and XtraDB tables on your server. To use the feature, you need to use the ENCRYPTION_KEY_ID table option to ... Read More

Feed: MariaDB Knowledge Base Article Feed. Author: . Disabling encryption is a little more complicated than turning off the relevant system variables. There are a couple different pieces to this. Disabling Encryption for Automatically Encrypted Tablespaces When an InnoDB tablespace has the ENCRYPTED table option set to DEFAULT and the innodb_encrypt_tables system variable is set to ON or FORCE, the tablespace's encryption is automatically managed by the background encryption threads. When you want to disable encryption for these tablespaces, you must ensure that the background encryption threads decrypt the tablespaces before removing the encryption keys. Otherwise, the tablespace remains encrypted ... Read More

Feed: MariaDB Knowledge Base Article Feed. Author: . Note: Columnstore.xml modifications you manually made are not automatically carried forward on an upgrade. These modifications will need to be incorporated back into .XML once the upgrade has occurred. The previous configuration file will be saved as /usr/local/mariadb/columnstore/etc/Columnstore.xml.rpmsave. If you have specified a root database password (which is good practice), then you must configure a .my.cnf file with user credentials for the upgrade process to use. Create a .my.cnf file in the user home directory with 600 file permissions with the following content (updating PASSWORD as appropriate): [mysqladmin] user = root password ... Read More

Feed: MariaDB Knowledge Base Article Feed. Author: . Key management and encryption plugins support using multiple encryption keys. Each encryption key can be defined with a different 32-bit integer as a key identifier. The default encryption key used by InnoDB to encrypt tablespaces is configured by setting the innodb_default_encryption_key_id system variable. For example: SET GLOBAL innodb_encryption_threads=4; SET GLOBAL innodb_encrypt_tables=ON; SET GLOBAL innodb_default_encryption_key_id=3; CREATE TABLE t (i int) ENGINE=InnoDB; When manually encrypting an InnoDB table, a different key can be chosen by adding the ENCRYPTION_KEY_ID table option to the CREATE TABLE statement. For example: CREATE TABLE t (i int) ENGINE=InnoDB ENCRYPTED=YES ... Read More

Feed: MariaDB Knowledge Base Article Feed. Author: . The innodb_encryption_threads system variable controls the number of threads that the InnoDB storage engine utilizes for its encryption-related background operations, which includes encrypting/decrypting InnoDB pages after key rotations or configuration changes and scrubbing InnoDB data to permanently delete it. Background Operations The encryption/decryption operations that are performed by the background encryption threads are: The latter two points mean that, whenever you change the configured value of innodb_encrypt_tables, then you must ensure that innodb_encryption_threads is set to a non-zero value, so that InnoDB can perform any necessary encryption or decryption operations in the ... Read More

Feed: Planet MySQL; Author: Severalnines; Since the concept of cloud was born, there has been strong growth in the number of migrations to this environment. However, not everything that shines is gold. As the demand grows, so does the costs. We can find ourselves in a situation where our monthly cloud expenses are very high and, in this case, it may make sense to migrate back to an on-prem environment. The costs may not be the only reason. There might be security or compliance requirements, or we may need to have more control of our systems. Knowing what happens at ... Read More