Bug #96637 | Clone fails on just upgraded server from 5.7 | ||
---|---|---|---|
Submitted: | 23 Aug 2019 12:30 | Modified: | 9 Dec 2019 19:39 |
Reporter: | Satya Bodapati (OCA) | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S3 (Non-critical) |
Version: | 8.0.17 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[23 Aug 2019 12:30]
Satya Bodapati
[23 Aug 2019 12:41]
Satya Bodapati
orphan 5.7 undo tablespace(in-mem) (*) I confirm the code being submitted is offered under the terms of the OCA, and that I am authorized to contribute it.
Contribution: orphan_57_undo.diff (text/x-patch), 819 bytes.
[23 Aug 2019 12:43]
Satya Bodapati
if ib::info() without error code is not allowed, please add that ;) And change to warn() based on your preference
[28 Aug 2019 12:05]
MySQL Verification Team
Hello Satya, my dear friend, How are you ???? I was analysing and testing this bug report and I do not see what method have you used to upgrade from 5.7 to 8.0. Please, describe that. However, I like both your analysis and your patch. Hence, I am verifying your bug as reported. Please, provide your answer regardless of this bug being verified. It will be useful to our developers. You should know that ...... Have a nice life !!!!
[9 Dec 2019 19:39]
Daniel Price
Posted by developer: Fixed as of the upcoming 8.0.20 release, and here's the changelog entry: After upgrading from MySQL 5.7 to MySQL 8.0, a CLONE INSTANCE operation failed with the following error: ERROR 3862 (HY000): Clone Donor Error: 1016 : Can't open file: './undo001'. The upgrade process left behind orphaned in-memory undo tablespaces. Thanks to Satya Bodapati for the contribution.
[10 Dec 2019 13:30]
MySQL Verification Team
Thank you, Daniel.
[18 Dec 2019 15:09]
Daniel Price
Posted by developer: Changelog entry moved to 8.0.19 release notes.
[18 Dec 2019 15:16]
MySQL Verification Team
Thank you, Daniel.