1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
|
# Create an empty data directory...
# Unzip 5_7_9_clean.zip to the created directory...
# Kill the server
############################################################################################
# Case 2: Attempt to start with invalid set of redo log files.
# 2A: InnoDB refuses to start if ib_logfile1 was removed
# 2B: InnoDB refuses to start if ib_logfile0 was removed
# 2C: InnoDB refuses to start if both redo files were removed
# NOTE: Ensure there was no attempt to check if redo is empty.
############################################################################################
# Hide the ib_logfile1...
# Case 2A: Start MySQL...
# Verify...
Pattern "Only one redo log file found" found
Pattern "innodb-unknown-compound-v" not found
# Restore the ib_logfile1...
############################################################################################
# Hide the ib_logfile0...
# Case 2B: Start MySQL...
# Verify...
Pattern "Missing ib_logfile0 in the directory" found
Pattern "innodb-unknown-compound-v" not found
# Restore the ib_logfile0...
############################################################################################
# Hide both redo log files (ib_logfile0 and ib_logfile1)...
# Case 2C: Start MySQL...
# Verify...
Pattern "Neither found .* subdirectory, nor .* files" found
Pattern "innodb-unknown-compound-v" not found
# Restore both redo log files (ib_logfile0 and ib_logfile1)...
############################################################################################
# Cleanup...
# restart
|
