You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently running owncloud 10.0.3/postgresql 9.6.6
Perform manual upgrade via occ with nextcloud 12.0.4
Expected behaviour
Ready-to-run nextcloud installation
Actual behaviour
Upgrade/Migration fails, leaves DB in unusable state.
2017-12-05T19:39:21+00:00 Set log level to debug
2017-12-05T19:39:21+00:00 Repair step: Repair MySQL collation
2017-12-05T19:39:21+00:00 Repair info: Not a mysql database -> nothing to do
2017-12-05T19:39:21+00:00 Repair step: Repair SQLite autoincrement
2017-12-05T19:39:21+00:00 Repair step: Copy data from accounts table when migrating from ownCloud
2017-12-05T19:39:21+00:00 Repair step: Drop account terms table when migrating from ownCloud
2017-12-05T19:39:21+00:00 Updating database schema
2017-12-05T19:39:22+00:00 Doctrine\DBAL\Exception\DriverException: An exception occurred while executing 'ALTER TABLE oc_filecache ALTER fileid TYPE SERIAL':
SQLSTATE[42704]: Undefined object: 7 ERROR: type "serial" does not exist
2017-12-05T19:39:22+00:00 Update failed
2017-12-05T19:39:22+00:00 Maintenance mode is kept active
2017-12-05T19:39:22+00:00 Reset log level
Server configuration
Operating system: Gentoo Linux
Web server: Apache2.4.27
Database: Postgresql 9.6.6
PHP version: PHP 5.6.32
Nextcloud version: 12.0.4
Updated from an older Nextcloud/ownCloud or fresh install: from owncloud 10.0.3
You were too fast I just wanted to edit the comment to sound less whiny ;).
What I would have loved to see is a patch to nextcloud 12 to run those changes during the 'normal' update procedure. That way I would not have had to manually figure out my postgres setup again and run those alterations manually.
This is a nonsense. When migrating from owncloud, you have to migrate to nextcloud 12 before bumping to the latest version. At the same time, nextcloud 12 is obsolete and buggy.
For updating/migrating 12 is still supported. But yeah it's on our list to create a more recent update path. But it's also kind of hard to make sure all edge cases are converted correctly because after nextcloud 12/owncloud 9.2/10 it diverged more and more
Maybe it makes more sense to promote v12 as a limited support version, only as a step in upgrade path? E.g. release a new version of 12.999.0 that is guaranteed to work with any PHP version (up to 7.4.x) and always have backports for anything that is needed for a migration to 12 to succeed, and nothing more.
Activity
foux commentedon Dec 14, 2017
I've got the same issue
theBlackDragon commentedon Dec 15, 2017
Ran into this issue as well. Rolled back to OwnCloud for now.
bobspct commentedon Dec 20, 2017
I've got the same issue
MorrisJobke commentedon Jan 2, 2018
@nickvergessen Mind to have a look?
nickvergessen commentedon Jan 4, 2018
It's an issue with bigint handling from doctrine on postgres:
#4504 (comment)
We fixed that for 13:
https://github.com/nextcloud/server/pull/6563/files#diff-e624a0e946331a052958be7dac537569
nsteinmetz commentedon Feb 11, 2018
@Haggl just did today a OC 10.0.4 to NC 12 migration and then NC 13 upgrade.
Had to do some query like described here : #4504 (comment)
Also had to do this one for clients synchronisation : #8084
MorrisJobke commentedon Feb 12, 2018
Correct - And upgrade from OC 10 is only possible via Nextcloud 12 and then an upgrade to 13.
ingwinlu commentedon Apr 9, 2018
yeah but you can not upgrade to 12 because of the missing table alterations....
nsteinmetz commentedon Apr 9, 2018
@ingwinlu you can do them before launching the upgrade ;-)
ingwinlu commentedon Apr 9, 2018
You were too fast I just wanted to edit the comment to sound less whiny ;).
What I would have loved to see is a patch to nextcloud 12 to run those changes during the 'normal' update procedure. That way I would not have had to manually figure out my postgres setup again and run those alterations manually.
I now upgraded to 12 successfully as well.
trifle commentedon May 2, 2018
Add one migration:
alter table oc_files_trash alter auto_id TYPE int;
Nowaker commentedon Apr 26, 2020
This is a nonsense. When migrating from owncloud, you have to migrate to nextcloud 12 before bumping to the latest version. At the same time, nextcloud 12 is obsolete and buggy.
nickvergessen commentedon Apr 26, 2020
For updating/migrating 12 is still supported. But yeah it's on our list to create a more recent update path. But it's also kind of hard to make sure all edge cases are converted correctly because after nextcloud 12/owncloud 9.2/10 it diverged more and more
Nowaker commentedon Apr 26, 2020
Maybe it makes more sense to promote v12 as a limited support version, only as a step in upgrade path? E.g. release a new version of 12.999.0 that is guaranteed to work with any PHP version (up to 7.4.x) and always have backports for anything that is needed for a migration to 12 to succeed, and nothing more.