Not the answer you need?
Register and ask your own question!

Percona Ver 8.0.19-10 issue Invalid column data type

giannisgzgiannisgz EntrantCurrent User Role Novice
Hi. I am using percona server for many years with a magento installation. Last January I upgrade to version 8.0.18-9. 
All was fine with my magento. But after I upgraded to latest version Ver 8.0.19-10 I am having an issue with reindex 2 particular tables. I get error:
Invalid column data type ""
I am searching for days what should be the issue because as I see in percona changelog not much changed from previous version.
I am suspecting that probably this is happening due to column data type smallint unsigned. In my table structure both smallint and int types are unsigned.
Although I changed that in my magento code I still get the error when trying to reindex the tables.
So first I want to ask if it is safe to revert back to version 8.0.18-9 without affecting my tables?
Second can anyone help me where or what to check so I solve my issue?

Answers

  • lorraine.pocklingtonlorraine.pocklington Percona Community Manager Legacy User Role Patron
    Hello @giannisgz
    First of all, if that's something that was working with the earlier version and now does not, it sounds like it could be a bug and at least should be investigated. Would you be able to gather together information about the case (table definitions, index definitions, environment data and so on) and report it to our engineering team's Jira system please? https://jira.percona.com That way you can keep track of the outcome of their investigations. If you can return and past the Jira link here, that would be great. 
    Next about reversion. Let me check in with our team on that. I just wanted you to know that we are looking into this for you. 
  • lorraine.pocklingtonlorraine.pocklington Percona Community Manager Legacy User Role Patron
    Right, regarding reversion. It's no longer supported to revert even minor versions, Marco wrote a blog post about this here: https://www.percona.com/blog/2020/01/10/mysql-8-minor-version-upgrades-are-one-way-only/ 
    Ultimately your answer is to do a logical dump and then reload. Unfortunately this relates to the new way things work in the upstream (Oracle MySQL) code. 
    I will see if I can get someone to advise on the troubleshooting, but please also raise the Jira? Thanks!
  • giannisgzgiannisgz Entrant Current User Role Novice
    Hello @giannisgz
    First of all, if that's something that was working with the earlier version and now does not, it sounds like it could be a bug and at least should be investigated. Would you be able to gather together information about the case (table definitions, index definitions, environment data and so on) and report it to our engineering team's Jira system please? https://jira.percona.com That way you can keep track of the outcome of their investigations. If you can return and past the Jira link here, that would be great. 
    Next about reversion. Let me check in with our team on that. I just wanted you to know that we are looking into this for you. 
    Hello and thank you for answer. I totally understood what you said but I don't know how I can help further in this. I am not a mysql expert unfortunately and I don't know how to gather the things you asked. If you could give me directions how to collect them I could post in Jira system. Now I don't know if it is appropriate to post something so general.
  • lorraine.pocklingtonlorraine.pocklington Percona Community Manager Legacy User Role Patron
    Let's see if I can find someone who can help with this. Thanks!
Sign In or Register to comment.

MySQL, InnoDB, MariaDB and MongoDB are trademarks of their respective owners.
Copyright ©2005 - 2020 Percona LLC. All rights reserved.