[mythtv-users] Broken Mythconverg - DBSchemaVer variable - how to recreate ?

Robert Rozman robert.rozman at comutel.si
Fri Oct 5 00:19:01 UTC 2007


Hi,

I get this weird error for 2 weeks now when starting mythbackend. It seems 
that I have corrupted settings table (it's empty) in mythconverg database. 
How to recreate it manually ?

Anyone has dump of this table ?

dcerouter_6097:~# mythbackend
2007-10-05 01:22:01.974 Using runtime prefix = /usr
2007-10-05 01:22:01.981 New DB connection, total: 1
2007-10-05 01:22:01.982 Connected to database 'mythconverg' at host: 
localhost
2007-10-05 01:22:01.984 Current Schema Version:
2007-10-05 01:22:01.984 Newest Schema Version : 1160
2007-10-05 01:22:01.985 New DB connection, total: 2
2007-10-05 01:22:01.985 Connected to database 'mythconverg' at host: 
localhost
2007-10-05 01:22:01.985 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.
2007-10-05 01:22:01.986 New DB connection, total: 3
2007-10-05 01:22:01.986 Connected to database 'mythconverg' at host: 
localhost
2007-10-05 01:22:01.987 Told to create a NEW database schema, but the 
database
already has 47 tables.
If you are sure this is a good mythtv database, verify
that the settings table has the DBSchemaVer variable.

2007-10-05 01:22:01.987 Database Schema upgrade FAILED, unlocking.
2007-10-05 01:22:01.987 Couldn't upgrade database to new schema


Thanks in advance,

regards,

Rob.



More information about the mythtv-users mailing list