Announcement

Announcement Module
Collapse
No announcement yet.

Getting errors after mysql_upgrade

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

  • Getting errors after mysql_upgrade

    hi dudes,

    after upgrading from 5.1.58 to 5.1.60 and running mysql_upgrade I'm getting these errors:

    Quote:
    Looking for 'mysql' as: mysql
    Looking for 'mysqlcheck' as: mysqlcheck
    Running 'mysqlcheck' with connection arguments: '--socket=/home/mysql/mysql.sock' '--port=3306'
    Running 'mysqlcheck' with connection arguments: '--socket=/home/mysql/mysql.sock' '--port=3306'
    mysql.columns_priv OK
    mysql.db OK
    mysql.event OK
    mysql.func OK
    mysql.general_log
    Error : You can't use locks with log tables.
    status : OK
    mysql.help_category OK
    mysql.help_keyword OK
    mysql.help_relation OK
    mysql.help_topic OK
    mysql.host OK
    mysql.ndb_binlog_index OK
    mysql.plugin OK
    mysql.proc OK
    mysql.procs_priv OK
    mysql.servers OK
    mysql.slow_log
    Error : You can't use locks with log tables.
    status : OK
    mysql.tables_priv OK
    mysql.time_zone OK
    mysql.time_zone_leap_second OK
    mysql.time_zone_name OK
    mysql.time_zone_transition OK
    mysql.time_zone_transition_type OK
    mysql.user OK

    Repairing tables
    test.HAUq6
    Error : Table 'test.HAUq6' doesn't exist
    status : Operation failed
    test.HAUq6
    Error : Table 'test.HAUq6' doesn't exist
    status : Operation failed
    test.HAUq6
    Error : Table 'test.HAUq6' doesn't exist
    status : Operation failed
    test.HAUq6
    Error : Table 'test.HAUq6' doesn't exist
    status : Operation failed
    test.HAUq6
    Error : Table 'test.HAUq6' doesn't exist
    status : Operation failed
    test.HAUq6
    Error : Table 'test.HAUq6' doesn't exist
    status : Operation failed
    test.HAUq6
    Error : Table 'test.HAUq6' doesn't exist
    status : Operation failed
    test.HAUq6
    Error : Table 'test.HAUq6' doesn't exist
    status : Operation failed
    test.HAUq6
    Error : Table 'test.HAUq6' doesn't exist
    status : Operation failed
    in addition the file "mysql_upgrade_info" is not updated with the new version-nr.

    anyone have any idea?
    cya Alex

  • #2
    You probably have some junk in your data directory, such as an orphaned .frm file.

    Comment


    • #3
      Hmm... Did anyone figure this out?

      I just migrated from - Community 5.1.66 - to Percona Server 5.1.67 - and I can't get the "mysql_upgrade" to finish.

      Same style errors as reported above.

      ...
      (table_name).H1uË3
      Error : Table '(table_name).H1uË3' doesn't exist
      status : Operation failed
      (table_name).H1uË3
      Error : Table '(table_name).H1uË3' doesn't exist
      status : Operation failed
      (table_name).H1uË3
      Error : Table '(table_name).H1uË3' doesn't exist
      status : Operation failed
      ...

      Oddly - I also notice this appears to only be happening on some Wordpress databases - yet other Wordpress databases are check Ok properly.

      Thoughts?

      -Michael

      Comment


      • #4
        Hmm... ok... initial conclusion - this has nothing to do with the specific database being complained about.

        And it's failing at this level:

        # mysqlcheck --check-upgrade --auto-repair test

        All tables in the "test" database comeback to "OK" - but after the last table in the database says OK... THEN it fails.

        =======
        ...
        test.202_users_pref OK
        test.202_version OK

        Repairing tables
        test.H1uË3
        Error : Table 'test.H1uË3' doesn't exist
        status : Operation failed
        test.H1uË3
        Error : Table 'test.H1uË3' doesn't exist
        status : Operation failed
        test.H1uË3
        =======

        Based on the wacky munged characters - I wonder if this is a character set issue.

        # cat test/db.opt
        default-character-set=latin1
        default-collation=latin1_swedish_ci


        -Michael

        Comment


        • #5
          FYI... for now - I downgraded to Percona 5.1.66 ( as my DBs were all running Community 5.1.66 previously ).

          I get the same errors with Percona 5.1.66

          -Michael

          Comment


          • #6
            Wow - am I the only one in the universe who is still getting these errors?

            Hmm...

            -Michael

            Comment


            • #7
              The the crickets are still making noise on this one. NO ONE ELSE has seen or been able to fix this??

              Oh well...

              Suppose I could just go down the path of building a fresh 5.5.x - and moving all the DBs out of the 5.1.x box that has these errors.

              sigh. No rest for the weary.

              -Michael

              Comment


              • #8
                xaprb has given a hint on the cause, have you looked into that?

                Comment

                Working...
                X