Ad Widget

Collapse

Upgraded to 6.0.5 - shows Database history tables upgraded NO in gui, but we did?

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • sphen
    Junior Member
    • Dec 2013
    • 25

    #1

    Upgraded to 6.0.5 - shows Database history tables upgraded NO in gui, but we did?

    Followed all instructions in docs to upgrade the mysql history tables, running history_pk_prepare.sql, exporting the data and then re-importing to new tables and removing the old. all has been working great but noticed in the server summary that it shows:

    Database history tables upgraded No

    When i start up the server - the log does not say anything about the history tables needing update anymore. I do see this related to the database version on startup however:

    1131:20220622:131433.361 current database version (mandatory/optional): 06000000/06000002
    1131:20220622:131433.361 required mandatory version: 06000000

    Is there something else i can check specific to the history tables?

    Thanks!
  • tim.mooney
    Senior Member
    • Dec 2012
    • 1427

    #2
    Originally posted by sphen
    Followed all instructions in docs to upgrade the mysql history tables

    Database history tables upgraded No
    You don't say what version you upgraded from, but if it was a 4.x version, then the upgrade note for 5.0, 5.2, and 5.4 also apply, since you are effectively upgrading "through" those versions.

    See the comment about the extended range patch for the database at 5.0: https://www.zabbix.com/documentation...rade_notes_500

    Comment

    • sphen
      Junior Member
      • Dec 2013
      • 25

      #3
      sorry and thanks. should have been clear. was coming from 5.2. i know when i started the zabbix server on 6.0 before updating tables it would say that i could update the tables in the logs. now all seems fine in the logs but the gui still says no.

      Comment

      • sphen
        Junior Member
        • Dec 2013
        • 25

        #4
        maybe I missed that patch a long time ago - will review the notes for 5.0

        Comment

        • sphen
          Junior Member
          • Dec 2013
          • 25

          #5
          thanks tim.mooney - it was an older patch (double.sql) and an updated value in the ui front end. working!

          Comment

          Working...