[mythtv-users] DB Error (Performing database upgrade from .19 to .20)

jacob jacob at heider.homelinux.net
Wed Sep 13 06:02:31 UTC 2006


On Tue, Sep 12, 2006 at 11:46:01PM -0400, Sdkovacs wrote:
> I am upgrading from .19 to .20 using ATRPMS on FC3. After using smart
> to upgrade the packages I rebooted the machine and this came up in
> mythbackend.log:
> 
> 006-09-12 23:32:10.508 MainServer::HandleAnnounce Monitor
> 2006-09-12 23:32:10.511 adding: localhost.localdomain as a client (events: 0)
> 2006-09-12 23:32:10.515 MainServer::HandleAnnounce Monitor
> 2006-09-12 23:32:10.517 adding: localhost.localdomain as a client (events: 1)
> 2006-09-12 23:33:23.155 MainServer::HandleAnnounce Monitor
> 2006-09-12 23:33:23.160 adding: localhost.localdomain as a client (events: 0)
> 2006-09-12 23:33:31.270 MainServer::HandleAnnounce Monitor
> 2006-09-12 23:33:31.274 adding: localhost.localdomain as a client (events: 0)
> 2006-09-12 23:36:59.912 Using runtime prefix = /usr
> 2006-09-12 23:37:00.848 New DB connection, total: 1
> 2006-09-12 23:37:00.950 Connected to database 'mythconverg' at host: localhost
> 2006-09-12 23:37:01.126 Current Schema Version: 1153
> 2006-09-12 23:37:01.171 Newest Schema Version : 1160
> 2006-09-12 23:37:01.243 New DB connection, total: 2
> 2006-09-12 23:37:01.316 Connected to database 'mythconverg' at host: localhost
> 2006-09-12 23:37:01.318 Setting Lock for Database Schema upgrade. If
> you see a long pause here it means the Schema is already locked and is
> being upgraded by another Myth process.
> 2006-09-12 23:37:01.345 New DB connection, total: 3
> 2006-09-12 23:37:01.357 Connected to database 'mythconverg' at host: localhost
> 2006-09-12 23:37:01.361 Upgrading to schema version 1154
> 2006-09-12 23:37:01.455 DB Error (Performing database upgrade):
> Query was: ALTER TABLE capturecard ADD diseqcid INT(10) UNSIGNED default NULL;
> Error was: Driver error was [2/1060]:
> QMYSQL3: Unable to execute query
> Database error was:
> Duplicate column name 'diseqcid'
> 
> new version: 1154
> 2006-09-12 23:37:01.469 Database Schema upgrade FAILED, unlocking.
> 2006-09-12 23:37:01.471 Couldn't upgrade database to new schema

Yeah, I got that too. Basically, I stopped the myth process, went into
the database and told it it had successfully ugraded to 1156 (which was
where it was dying) and let it finish upgrading. The final result wasn't
useable, so I dumped it, dropped, started myth and got a fresh (empty)
database. Then, I dumped that, and using vi and imediff2, I hand-migrated
my database the rest of the way. Extremely painful, and about 5 hours of
my evening, but better than not upgrading, as far as I'm concerned.

Sorry I don't have a more helpful suggestion. Depending on how much you
like SQL this might work for you.

Jacob


More information about the mythtv-users mailing list