@David,
It looks from the error log that you have
a) A corrupted secondary index -- idx3. (Other indexes need to be checked)
- So suggest running a CHECK TABLE for wc_miehr_mhpc`.`patient_pdups to see if any other index other than idx3 are corrupted
b) 130109 8:16:43 InnoDB: Error: trying to access tablespace 601060 page no. 1, InnoDB: but the tablespace does not exist or is just being dropped.
also suggests a corruption.
So,
1) Is the source -- 5.1.66 host -- fine? Does it have any related errors? You can run 'check table' there as well.
2) Also, provide the innobackupex (with its command line) logs and apply-log output.
@David,
It looks from the error log that you have
a) A corrupted secondary index -- idx3. (Other indexes need to be
checked)
- So suggest running a CHECK TABLE for miehr_mhpc` .`patient_ pdups to see if any other index
wc_
other than idx3 are corrupted
b) 130109 8:16:43 InnoDB: Error: trying to access tablespace
601060 page no. 1,
InnoDB: but the tablespace does not exist or is just being
dropped.
also suggests a corruption.
So,
1) Is the source -- 5.1.66 host -- fine? Does it have any related
errors? You can run 'check table' there as well.
2) Also, provide the innobackupex (with its command line) logs and apply-log output.