View Issue Details

This issue affects 1 person(s).
 4
IDProjectCategoryView StatusLast Update
20545Bug reportsOtherpublic2026-06-02 10:46
Reporterephe Assigned Tolajosarpad  
PrioritynoneSeverityblock 
Status assignedResolutionopen 
Product Version7.0.x 
Summary20545: Update db from 651 to 707 impossible - table duplicate
Description

Hi,
I'm trying to update limesurvey from 6.17.5 to 7.0.0 but doesn't work cause of "trying to create table that already duplicate".

Thx for any help

Steps To Reproduce

Steps to reproduce

  • Manually update limesurvey version 6.15.7 to 7.0.0
  • execute on server "# php /limesurvey-folder/applications/commands/console updatedb"

Expected result

Update db 651 to 707 successfull..

Actual result

Update db 651 to 707 : failed
CException: Please fix this error in your database and try again in /limesurvey/application/commands/UpdateDbCommand.php:51
Stack trace:
#0 /limesurvey/vendor/yiisoft/yii/framework/console/CConsoleCommandRunner.php(71): UpdateDBCommand->run()
#1 /limesurvey/vendor/yiisoft/yii/framework/console/CConsoleApplication.php(92): CConsoleCommandRunner->run()
#2 /limesurvey/htdocs/vendor/yiisoft/yii/framework/base/CApplication.php(185): CConsoleApplication->processRequest()
#3 /limesurvey/application/commands/console.php(77): CApplication->run()

TagsNo tags attached.
Attached Files
2026-06-02_08h35_25.png (1,103,005 bytes)
Bug heat4
Complete LimeSurvey version number (& build)limesurvey7.0.0+260526
I will donate to the project if issue is resolvedNo
Browserall
Database type & versionMariaDB - 10.11.14
Server OS (if known)Debian 12
Webserver software & version (if known)Apache/2.4.67 (Debian)
PHP VersionPHP 8.5.6 (cli) (built: May 14 2026 15:48:47) (NTS)

Users monitoring this issue

There are no users monitoring this issue.

Activities

ephe

ephe

2026-06-02 09:16

reporter   ~84976

Forgot tu submit all trace of the error... sry

#0 + ./application/helpers/update/updates/Update_700.php(1351): CDbCommand->execute()
#1 + ./application/helpers/update/DatabaseUpdateBase.php(47): LimeSurvey\Helpers\Update\Update_700->up()
#2 + ./application/helpers/update/updatedb_helper.php(119): LimeSurvey\Helpers\Update\DatabaseUpdateBase->safeUp()
#3 + ./application/helpers/update/update_helper.php(33): db_upgrade_all(651)
#4 + ./application/controllers/admin/DatabaseUpdate.php(35): CheckForDBUpgrades("yes")
#5 + ./unknown(0): DatabaseUpdate->db("yes")
#6 + ./vendor/yiisoft/yii/framework/web/actions/CAction.php(114): ReflectionMethod->invokeArgs(DatabaseUpdate, array("yes"))
#7 + ./application/core/SurveyCommonAction.php(86): CAction->runWithParamsInternal(DatabaseUpdate, ReflectionMethod, array("continue" => "yes", "sa" => "db"))
#8 + ./vendor/yiisoft/yii/framework/web/CController.php(308): SurveyCommonAction->runWithParams(array("continue" => "yes", "sa" => "db"))
#9 + ./vendor/yiisoft/yii/framework/web/CController.php(286): CController->runAction(DatabaseUpdate)
#10 + ./vendor/yiisoft/yii/framework/web/CController.php(265): CController->runActionWithFilters(DatabaseUpdate, array())
#11 + ./application/controllers/AdminController.php(204): CController->run("databaseupdate")
#12 + ./vendor/yiisoft/yii/framework/web/CWebApplication.php(282): AdminController->run("databaseupdate")
#13 + ./vendor/yiisoft/yii/framework/web/CWebApplication.php(141): CWebApplication->runController("admin/databaseupdate/sa/db")
#14 + ./vendor/yiisoft/yii/framework/base/CApplication.php(185): CWebApplication->processRequest()
#15 + ./index.php(161): CApplication->run()

lajosarpad

lajosarpad

2026-06-02 10:46

developer   ~84977

The table change format is

{{survey_123456}} -> {{responses_123456}}
{{survey_timings_123456}} -> {{timings_123456}}
{{old_survey_123456_202606021130}} -> {{old_responses_123456_202606021130}}
{{old_survey_123456_timings_202606021130}} -> {{old_timings_123456_202606021130}}

under normal conditions this would not create table duplicates. So if it did attempt to create a duplicate for you, then we need the following information:

  1. What is the name of the table that is attempted to be duplicated?
  2. What is the list of tablenames you have prior to the upgrade that contain "responses" or "timings" or "survey"?
  3. Did you have an earlier unsuccessful attempt to run the 700 script?
  4. What other information do you have that may be of importance to the problem?

Issue History

Date Modified Username Field Change
2026-06-02 09:14 ephe New Issue
2026-06-02 09:14 ephe File Added: 2026-06-02_08h35_25.png
2026-06-02 09:16 ephe Note Added: 84976
2026-06-02 09:16 ephe Bug heat 0 => 2
2026-06-02 10:05 tibor.pacalat Assigned To => lajosarpad
2026-06-02 10:05 tibor.pacalat Status new => assigned
2026-06-02 10:46 lajosarpad Note Added: 84977
2026-06-02 10:46 lajosarpad Bug heat 2 => 4