-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade to 6.0.0 fails #6330
Comments
duplicate of #6313 |
A quick fix for me was to drop the tables oc_pictures_images_cache and oc_gallery_sharing. |
Table oc_pictures_images_cache from 5.0.0.14: Same table is 6.0.0: There's obviously a bug in the database scheme upgrade process. |
@bartv2 Can you have a look? |
The message looks like an incomplete SQL statement. |
could reproduce the issue with installing a stock OC5 on postgres, uploading a few files, ant then doing the migrate to OC6. Had defined DEBUG as true:
now
@bartv2 suspiciously looks like the backticks did not get replaced with the correct quotes ... \u203e is „ and \u201c is “ ... the correct quote is " the simple double quote ... |
nevermind the quotes are just part of the error message ... so this is more related to oc_jobs really not being present... |
@kabum is right, on PostgreSQL the generated upgrade SQL is |
linking this here owncloud-archive/3rdparty#64 (comment) |
Same issue on Debian 7.0 using the official repository with a postgresql database. upgrade just fail with the official 6.0 release. |
Ah - fixed later. Sorry for bugging. $currentVersion=OC_Appconfig::getValue('search_lucene', 'installed_version'); is correct in preupdate.php? |
I'm getting the oc_jobs error now when I upgrade from 5.0.13 to stable6, with SQLite (by checking out the corresponding tags in core, apps and 3rdparty) |
@butonic @DeepDiver1975 Any idea? |
I think I'm onto something: When the migration problem appeared for me, I had an older config.php with mysql DB settings but that I reset with installed: false and used sqlite. That caused the oc_jobs issue to appear. Then, when I deleted the config.php and started from scratch, and only manually added the apps_path, then migration works fine. |
strange |
My intuition tells me "table prefix". Need to verify this. Because it's probably the only extra DB setting that is used for SQLite. |
Hmm, just saw that this bug was marked as duplicate of #6294 but by rereading the first post, it seems to be related to pictures table. I'll switch over to that other bug that more explicitly states my issue. |
Is there any progress on this issue? Is there a workaround for the postrgres users? As far as I saw this problem also occured with the RC versions? Is there a fix now for the stable release? |
@brot I'm not sure but you can try upgrading from 5.0.13 to 6.0.0a (not 6.0.0) |
@PVince81 and where do I find the 6.0.0a download file? |
Here: http://owncloud.org/install/ |
This patch allowed me to get through the upgrade. Not sure if the database is in the correct state but it seems to work. This just skips the ALTER TABLE when the default value is blank. --- a/doctrine/dbal/lib/Doctrine/DBAL/Platforms/PostgreSqlPlatform.php
|
Not sure but could be related: owncloud-archive/3rdparty#65 (comment) |
Any update ? Did you have any success upgrading to 6.0.1 with Postgres ? |
For me the version 6.0.1 worked. Thanks |
Another update, another failure with postgres :-(
I just upgraded from 5.0.0.14 to 6.0.0. Maintance mode can't be left, because database schema upgrade doesn't finish.
Postgres.log:
ERROR: syntax error at end of input at character 60
STATEMENT: ALTER TABLE "oc_pictures_images_cache" ALTER uid_owner SET
owncloud.log:
{"app":"core","message":"Failed to update database structure (exception 'PDOException' with message 'SQLSTATE[42601]: Syntax error: 7 ERROR: synt
ax error at end of input\nLINE 1: ALTER TABLE "oc_pictures_images_cache" ALTER uid_owner SET \n
^' in /var/www/owncloud/3rdparty/doctrine/dbal/lib/Doctrine/DBAL/Connection.php:742\nStack trace:\n#0 [internal functi
on]: PDO->query('ALTER TABLE "oc...')\n#1 /var/www/owncloud/3rdparty/doctrine/dbal/lib/Doctrine/DBAL/Connection.php(742): call_user_func_array(Array, Array)\n#2 /var/www/owncloud/lib/private/db/mdb2schemamanager.php(152):
The text was updated successfully, but these errors were encountered: