Ad Widget

Collapse

1.3.4 DB Patch

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • gymv
    Junior Member
    • Oct 2006
    • 6

    #1

    1.3.4 DB Patch

    I tried to run the DB patch for MySQL to upgrade from 1.3.3 to 1.3.4 (upgrades/dbpatches/1.4/mysql/patch.sql) but I received the following message:

    ERROR 1054 (42S22) at line 135: Unknown column 'alarm_history' in 'field list'

    I thought it could be some mispelling error and then I renamed alarm_history to event_history in patch.sql and tried again (i did it because it seems to be the right name of the column, but I'm not sure about it) and then I got this message:

    ERROR 1050 (42S01) at line 180: Table 'events' already exists

    After the second error, I gave up and restored the original DB (wow! thanks god I had a backup ) . Then I saved only the data from following tables of the original DB:

    functions
    graphs
    graphs_items
    groups
    history* (this means all tables named historysomething)
    hosts*
    items*
    trends
    triggers

    After that, I created the 1.3.4 DB from create/data and create/schema directory and restored the data saved previously. The system seems to be working fine now, but even though I would like to know if this procedure may have missed something. Is there any other table that I should have saved before the procedure? Is there any new field that new tables may be missing?

    Thanks for your attention.

    Gus
  • Alexei
    Founder, CEO
    Zabbix Certified Trainer
    Zabbix Certified SpecialistZabbix Certified Professional
    • Sep 2004
    • 5654

    #2
    Originally posted by gymv
    I tried to run the DB patch for MySQL to upgrade from 1.3.3 to 1.3.4 (upgrades/dbpatches/1.4/mysql/patch.sql) but I received the following message:
    This patch is for upgrade from 1.1.x to 1.3.4 (pre1.4)! We do not offer patches for 1.3.x -> 1.3.y upgrades.
    Alexei Vladishev
    Creator of Zabbix, Product manager
    New York | Tokyo | Riga
    My Twitter

    Comment

    • monsieurcanard
      Member
      • Mar 2007
      • 40

      #3
      Hi Alexei,

      Perhaps it would be useful to add that information to a 'README' file or make it obvious by the patch's filename (e.g. 1.1-to-1.3-patch.sql). I too tried to run the SQL patch, thinking it would be from 1.3 to 1.4.

      Many thanks,
      Matt

      Comment

      Working...