Announcement Module
No announcement yet.

Invalid (Old?) table or database name bug

Page Title Module
Move Remove Collapse
Conversation Detail Module
  • Filter
  • Time
  • Show
Clear All
new posts

  • Invalid (Old?) table or database name bug

    Recently we are testing upgrade from Percona 5.0.86 to 5.1.45. We ran into a strange alert (warning).

    100504 0:42:58 [Note] /usr/local/Percona-XtraDB-5.1.45-1.0.6-10-Linux-2.6.18-164.1 5.1.el5-x86_64/libexec/mysqld: ready for connections.
    Version: '5.1.45-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Percona SQL Server (GPL), XtraDB 10, Revision 80

    100504 20:09:39 [Warning] Invalid (old?) table or database name '#sql2-3c32-51'

    I like to know if this is related to

    What is the impact and will it be fixed soon?


  • #2
    It might be related, but it could also be that you didn't do a clean shutdown or something like that. There could be a lot of reasons for this behavior.

    Try asking Oracle when it'll be fixed, because nobody outside Oracle has a clue ) But if you want, you can pay for a fix: Monty Program is offering a bug-fix support package, and so is Percona these days.