Open-AudIT

What's on your network?
It is currently Mon Apr 23, 2018 11:50 am

All times are UTC + 10 hours




Post new topic Reply to topic  [ 6 posts ] 
Author Message
PostPosted: Thu Jul 27, 2017 2:06 am 
Offline
Contributor
User avatar

Joined: Thu Mar 02, 2006 4:41 am
Posts: 204
Location: Massachusetts
First, I backed up the mysql db, and also took a snapshot of the Windows VM that is my OA host. I ran the upgrade, everything finished without error. But when I go to the OA Community logon page, I get the upgrade box, select that, and it keeps failing with the following error:

A Database Error Occurred

Error Number: 1467

Failed to read auto-increment value from storage engine

INSERT INTO `oa_location` (SELECT NULL, `name`,`type`,`room`,`suite`,`level`,`address`,`suburb`,`city`,`district`,`region`,`area`,`state`,`postcode`,`country`,`tags`,`phone`,`picture`,`latitude`,`longitude`,`geo`,`comments`,`icon`, `group_id` FROM `oa_location` WHERE id = 1)

Filename: C:\xampplite\open-audit\code_igniter\system\database\DB_driver.php

Line Number: 330


If there isn't an easy fix, wondering if I should setup a new OA 2.0.3 system, and restore from the mysql backup to populate all of the data? I already reverted back to 1.12.10 via the snapshot, but can easily try the upgrade again if there is a fix for this error

_________________
Server Info: running on a CentOS 7 vm
OA Version: 2.0.6 @ 500 devices


Top
 Profile  
Reply with quote  
PostPosted: Thu Jul 27, 2017 2:36 am 
Offline
Moderator

Joined: Fri Jul 20, 2007 8:27 am
Posts: 1254
Do you have a way to view the structure of the oa_location table? Like phpmyadmin or something installed? It looks like the location table has a problem with the auto_increment id field. You would likely get an error in your 1.12.10 install if you tried to add a location.


Top
 Profile  
Reply with quote  
PostPosted: Thu Jul 27, 2017 3:10 am 
Offline
Contributor
User avatar

Joined: Thu Mar 02, 2006 4:41 am
Posts: 204
Location: Massachusetts
I do have MySQL Workbench. Is this the structure (sorry I'm not a very good dba)?

Table: oa_location
Columns:
id int(10) UN AI PK
name varchar(100)
type varchar(100)
room varchar(100)
suite varchar(100)
level varchar(100)
address varchar(100)
suburb varchar(100)
city varchar(100)
district varchar(100)
region varchar(100)
area varchar(100)
state varchar(100)
postcode varchar(10)
country varchar(100)
tags varchar(250)
phone varchar(20)
picture varchar(100)
latitude float(10,6)
longitude float(10,6)
geo varchar(200)
comments varchar(100)
icon varchar(100)
group_id int(10) UN

_________________
Server Info: running on a CentOS 7 vm
OA Version: 2.0.6 @ 500 devices


Top
 Profile  
Reply with quote  
PostPosted: Thu Jul 27, 2017 3:32 am 
Offline
Contributor
User avatar

Joined: Thu Mar 02, 2006 4:41 am
Posts: 204
Location: Massachusetts
Looking around just found some errors in the mysql.err file:

170314 8:59:37 InnoDB: MySQL and InnoDB data dictionaries are out of sync.
InnoDB: Unable to find the AUTOINC column id in the InnoDB table openaudit/attachment.
InnoDB: We set the next AUTOINC column value to the maximum possible value,
InnoDB: in effect disabling the AUTOINC next value generation.
InnoDB: You can either set the next AUTOINC value explicitly using ALTER TABLE
InnoDB: or fix the data dictionary by recreating the table.

170314 8:59:38 InnoDB: MySQL and InnoDB data dictionaries are out of sync.
InnoDB: Unable to find the AUTOINC column id in the InnoDB table openaudit/oa_location.
InnoDB: We set the next AUTOINC column value to the maximum possible value,
InnoDB: in effect disabling the AUTOINC next value generation.
InnoDB: You can either set the next AUTOINC value explicitly using ALTER TABLE
InnoDB: or fix the data dictionary by recreating the table.

170726 11:01:19 InnoDB: MySQL and InnoDB data dictionaries are out of sync.
InnoDB: Unable to find the AUTOINC column id in the InnoDB table openaudit/oa_change.
InnoDB: We set the next AUTOINC column value to the maximum possible value,
InnoDB: in effect disabling the AUTOINC next value generation.
InnoDB: You can either set the next AUTOINC value explicitly using ALTER TABLE
InnoDB: or fix the data dictionary by recreating the table.

_________________
Server Info: running on a CentOS 7 vm
OA Version: 2.0.6 @ 500 devices


Top
 Profile  
Reply with quote  
PostPosted: Thu Jul 27, 2017 5:07 am 
Offline
Moderator

Joined: Fri Jul 20, 2007 8:27 am
Posts: 1254
Yes, those would be bad. Maybe backup up, wipe db and restore would work? You may still need to fix the AUTO_INCREMENT value for the tables in question. I am also not a good DBA!


Top
 Profile  
Reply with quote  
PostPosted: Thu Jul 27, 2017 5:34 am 
Offline
Contributor
User avatar

Joined: Thu Mar 02, 2006 4:41 am
Posts: 204
Location: Massachusetts
Been upgrading year after year, probably time to start a brand new OA server with 2.0.3 (will probably go with Linux), will leave this older one running until I get everything working fine. thanks for checking this out

_________________
Server Info: running on a CentOS 7 vm
OA Version: 2.0.6 @ 500 devices


Top
 Profile  
Reply with quote  
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 6 posts ] 

All times are UTC + 10 hours


Who is online

Users browsing this forum: No registered users and 2 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Group