View Issue Details

Jump to NotesJump to History
This bug affects 1 person(s).
 4
IDProjectCategoryView StatusDate SubmittedLast Update
09768Bug reportsComfortUpdatepublic2015-07-09 08:032015-08-04 08:40
Reporterwallingd Assigned Toc_schmitz  
PrioritynormalSeverityblock 
Status closedResolutionunable to reproduce 
Product Version2.06+ 
Summary09768: "Column already exists" error when upgrading DB, but no duplicate column found.
Description

Upon running the database upgrade to update to 2.06, the following error is reported:


An non-recoverable error happened during the update. Error details:
CDbCommand failed to execute the SQL statement: SQLSTATE[42S21]: Column already exists: 1060 Duplicate column name 'created'

Please fix this error in your database and try again

I have inspected every table, found two tables with single "created" columns, and have found no duplicate columns named "created"

Steps To Reproduce

Run comfort update to the point of database upgrade.

TagsNo tags attached.
Bug heat4
Complete LimeSurvey version number (& build)150629
I will donate to the project if issue is resolvedNo
BrowserIE 11
Database type & versionMSSQL
Server OS (if known)Windows 2012
Webserver software & version (if known)IIS
PHP Version5.4

Users monitoring this issue

There are no users monitoring this issue.

Activities

wallingd

wallingd

2015-07-31 07:48

reporter   ~32841

Reminder sent to: c_schmitz

Any information on this issue?

Thanks
c_schmitz

c_schmitz

2015-07-31 09:55

administrator   ~32843

What was your previous version?
Did you try multiple times to update DB or was this your first try?
wallingd

wallingd

2015-07-31 18:39

reporter   ~32860

I do not recall the previous version and none of the screens indicate the version (since I can't log in to the admin center). Is there a way to tell from the DB?

To my recollection, this was the first attempt to upgrade the DB.
c_schmitz

c_schmitz

2015-08-03 14:31

administrator   ~32867

Don't you have a database backup?
wallingd

wallingd

2015-08-03 19:51

reporter   ~32872

Yes, of course I took a full dump of the db. However I didn't think to check it prior to beginning the upgrade and it appears corrupt - it created so all is assumed well, right? However it appears to only contain lime_answers, so I don't think that's going to do me any good.

Perhaps at this point I should find and manually run the sql statements one by one to see which is erroring?
wallingd

wallingd

2015-08-04 06:34

reporter   ~32873

Used Neor Profiler to profile the SQL queries and figure out that it was the lime_participants table causing the collision on the Created, Modified, and Created_by columns. Deleted those columns, re-ran the DB upgrade and everything completed successfully. No other DB issues required correcting.

I note with interest that all DB upgrades were being completed in what appears to be a single transaction; it is odd the columns would exist in the first place.

Found a note that makes me believe I was upgrading from 1.96.

Regardless, my issue is resolved so my issue can be closed; not sure if there is an underlying bug in the upgrade process or not.

Issue History

Date Modified Username Field Change
2015-07-09 08:03 wallingd New Issue
2015-07-09 08:03 wallingd Status new => assigned
2015-07-09 08:03 wallingd Assigned To => c_schmitz
2015-07-31 07:48 wallingd Note Added: 32841
2015-07-31 09:55 c_schmitz Note Added: 32843
2015-07-31 09:55 c_schmitz Status assigned => feedback
2015-07-31 18:39 wallingd Note Added: 32860
2015-07-31 18:39 wallingd Status feedback => assigned
2015-08-03 14:31 c_schmitz Note Added: 32867
2015-08-03 14:31 c_schmitz Status assigned => feedback
2015-08-03 19:51 wallingd Note Added: 32872
2015-08-03 19:51 wallingd Status feedback => assigned
2015-08-04 06:34 wallingd Note Added: 32873
2015-08-04 08:40 c_schmitz Status assigned => closed
2015-08-04 08:40 c_schmitz Resolution open => unable to reproduce