- 新しい順
- 投票が多い順
- コメントが多い順
Hello.
When you mention the "Usage of old temporal type," it likely refers to the changes that happened with temporal types like DATETIME and TIMESTAMP between MySQL versions. In MySQL 5.6.4 and later, these types were changed to support fractional seconds. If your MySQL 5.7 installation was upgraded from an older version and the table was created before 5.6.4, then the table might be using the older format. This difference can cause issues when upgrading.
INNODB_SYS_TABLESPACES: This InnoDB system table provides metadata about tablespaces. If a table isn't listed here, it's typically a cause for concern. It suggests some form of inconsistency or corruption.
Before making any changes, verify the table for corruption using the CHECK TABLE command:
CHECK TABLE your_table_name;
If any issues are reported, they might need to be addressed before you continue.
Regards, Andrii
Lastly, if the problems persist or if you're concerned about potential data loss or corruption, consider seeking assistance from AWS team.
関連するコンテンツ
- 質問済み 6年前
AWS公式更新しました 3年前
Yes, it's about the "timestamp /* 5.5 binary format */" item.
The DB was created years and years ago, before 5.5. it was upgraded from 5.5 to 5.7 in 2021. I'm not able to verify if the upgrade to 5.6 was done in between, or it was jumped from 5.5 to 5.7 in one go.