polardbxengine/mysql-test/suite/innodb_undo/r/encrypt_explicit.result

56 lines
1.5 KiB
Plaintext

#
# wl9508: Show that explicit and implicit undo tablespaces can be encrypted.
#
use test;
CREATE table tab1(c1 int);
# create bootstrap file
# Stop the MTR default DB server
# Run the bootstrap command of datadir1
SELECT @@datadir;
@@datadir
MYSQLD_DATADIR1/
SHOW VARIABLES LIKE 'keyring_file%';
Variable_name Value
keyring_file_data key_file/my_keyfile
SELECT @@innodb_undo_log_encrypt;
@@innodb_undo_log_encrypt
1
CREATE UNDO TABLESPACE undo_003 ADD DATAFILE 'undo_003.ibu';
CREATE DATABASE nath;
use nath;
CREATE TABLE tab2(c1 int , c2 varchar(10)) Engine=InnoDB ENCRYPTION='Y';
INSERT INTO tab2 VALUES(2, 'VISH');
CREATE INDEX ix2 ON tab2(c2) ;
CREATE UNDO TABLESPACE undo_004 ADD DATAFILE 'undo_004.ibu';
ALTER UNDO TABLESPACE undo_003 SET INACTIVE;
ALTER UNDO TABLESPACE undo_004 SET INACTIVE;
DELETE FROM tab2;
DROP UNDO TABLESPACE undo_003;
DROP UNDO TABLESPACE undo_004;
DROP TABLE tab2;
DROP DATABASE nath;
# Stop the encrypt server
# restart: --datadir=OLD_DATADIR
SELECT @@datadir;
@@datadir
MYSQLD_OLD_DATADIR
use test;
DROP TABLE tab1;
#
# bug#29006275 : ENCRYPTION MASTER KEY IS GENERATED WITH BLANK UUID
#
# Stop the encrypt server
# Drop existing UNDO tablespaces
undo_001
undo_002
undo_003
undo_004
undo_005
undo_006
# Drop existing auto.cnf
auto.cnf
# Restart server with keyring plugin and innodb_undo_log_encrypt=ON
# Show that a master key with a blank Server UUID is not used.
SELECT * FROM performance_schema.keyring_keys where KEY_ID='INNODBKey--1';
KEY_ID KEY_OWNER BACKEND_KEY_ID