-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 31.10.2012 16:54, Richard Musil wrote: > I have made recently upgrade to 1.0 together with few projects. All > projects upgraded fine except one, which I interrupted in update > process. Now, whenever I try to do > > trac-admin <project> upgrade > > I receive error: > > The upgrade failed. Please fix the issue and try again. > OperationalError: no such table: cache > > Does anyone know, how I could "fix the issue"?
After being that * to stop a running db upgrade process, be prepared for some hard work. Least-cost route: Redo with another copy of your backup of that Trac environment. But I fear you don't have one, or you probably wouldn’t have asked that question here, right? (I wonder, if it is partly related to Trac's reliability, that people just run for upgrades and other modifications without a backup.) Everything else will get a lot harder. Just some thoughts: I can hardly guess, when exactly you interrupted the upgrade procedure. Detect the current db schema revision number (from Trac db table 'system'). Search the corresponding schema in the history of 'db_default' and compare it to the current state of your db. You should find out everything about the missing table and re-add it with appropriate definitions to relaunch the upgrade from there. Steffen Hoffmann -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlCRjxoACgkQ31DJeiZFuHeG4ACgzDkbRNWoGgzDEpcjne+8FRXH X0wAn1D1J/mrBPRt086ZCkO1aGr/CVvn =R/vU -----END PGP SIGNATURE----- -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
