Ad Widget

Collapse

MySQL Error 1025 when loading schema

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • mauibay
    Junior Member
    • Jan 2008
    • 23

    #1

    MySQL Error 1025 when loading schema

    Aloha,

    I built version 1.4.4 from tarball on OpenSuse 10.3 without errors, but get a MySQL error when trying to load the schema:
    Code:
    mysql -D zabbix14 < create/schema/mysql.sql
    ERROR 1025 (HY000) at line 15: Error on rename of './zabbix14/slides' to './zabbix14/#sql2-3113-2' (errno: -1)
    I have tried both MySQL 5.2.45 and 5.2.51 and get the same behavior with both. I don't have any known problems with several other databases on the same system.

    I have dropped and recreated the database several times and even dumped/dropped/recreated the entire /var/lib/mysql directory while troubleshooting this, and also removed/reinstalled/updated MySQL itself. The error has not changed.

    Any advice would be very welcome!
  • joethesysadmin
    Junior Member
    • Feb 2008
    • 1

    #2
    If your setup is anything like mine

    I had my database set up to use each InnoDB table as a seperate file, via the following entry in /etc/my.cnf

    Code:
    [mysqld]
    innodb_file_per_table
    I had to comment that entry out, then restart the MySQL server daemon to get the schema to properly import.

    Comment

    • jpriceit
      Junior Member
      • Feb 2008
      • 12

      #3
      I am also having this problem with both 1.4.3 and 1.4.4 versions.

      I checked my my.cnf and I don't have the entry that joethesysadmin had, so I'm still out of luck.

      This is actually a reinstall of zabbix for me, but I've dropped the zabbix database as well as removed the user zabbix to start fresh. I'm following the install instructions from here:

      http://www.zabbix.com/downloads/ZABB...ual%20v1.4.pdf

      Comment

      • jpriceit
        Junior Member
        • Feb 2008
        • 12

        #4
        bump

        Comment

        • mauibay
          Junior Member
          • Jan 2008
          • 23

          #5
          I haven't found a specific solution yet, but I did get past the problem by returning to a default my.cnf which has all the innodb options commented out. So I'm not using the recommended second innodb file and might be facing some data size issues down the road if I don't find a correct solution.

          In the meantime, I've disabled about 90% of the tests in my templates, and significantly increased the intervals of all but a very few important values, so the amount of data I'm collecting is drastically reduced. It's just a workaround to diminish the impact of not using the recommended innodb options.

          Comment

          Working...