[mythtv] Ticket #6923: 0.21->trunk DB upgrade failed

[Michael T. Dean]

On 08/27/2009 02:51 AM, Warpme wrote:
> Michael T. Dean wrote:
>> On 08/26/2009 05:38 PM, MythTV wrote:
>>> #6923: 0.21->trunk DB upgrade failed
>>>
>>> Comment(by warpme):
>>>
>>>  Well,
>>>  My setup is:[[BR]]
>>>  -0.21-fixes production BE[[BR]]
>>>  -trunk test BE running under vmware[[BR]]
>>>
>>>  According to Your suggestions I do following:[[BR]]
>>>  -stop msql/mythbackend in trunk based test BE[[BR]]
>>>  -rsync DB files from running, production 0.21-fixes BE to test 
>>> BE[[BR]]
>>>  -start mysql on test BE[[BR]]
>>>  -launch mythtv-setup on test BE[[BR]]
>>>
>>>  Log attached...
>> Thank you for restoring the DB to get a clean "first-time upgrade" log.
>>
>> The log file seems to indicate that your 0.21-fixes database schema 
>> has been modified to include the default_authority column in the 
>> channelscan_dtv_multiplex table.  Since 0.21-fixes doesn't have a 
>> channelscan_dtv_multiplex table (it's created in DB schema update 
>> 1219--which yours went through without error because of the "IF NOT 
>> EXISTS" in the "CREATE TABLE" statement), your 0.21-fixes database 
>> schema has been modified.
>>
>> Are you, perhaps, running a version of 0.21-fixes that was patched 
>> with the patch at http://svn.mythtv.org/trac/ticket/5603, or any 
>> other patch that adds a channelscan_dtv_multiplex table? 
> Thx for quick replay !
> Well - I do not apply 5603.
> Infact only patches which I apply to my 0.21 are VDPAU/H264/AC3 related.
> It seems to be strange as in original 0.21 DB there is no 
> "channelscan_dtv_myltiplex" table at all, and "dtv_multiplex" table 
> hasn't colon "default_authority".
> After upgrade there is "channelscan_dtv_multiplex" table and also 
> colon "default_authority" is added to "dtv_multiplex" table.
> Maybe double presence of "default_authority" is root cause, or maybe 
> adding table "channelscan_dtv_myltiplex" is confused by existence of 
> "default_authority" in "dtv_multiplex"table ?
> Anyway - maybe uploading my original DB will be helpful for You ?
> If so, have we any kind drop-host for passing such 10M files ?
> br 

OK, since you didn't apply any patches which would have added that 
table, the most likely cause of this error is that your rsync-based 
restore did not delete the "extra" files from your partially-upgraded DB 
on your trunk host's database.  Therefore, the 
channelscan_dtv_multiplex.MY[ID] files were still there, so the table 
was in the schema--meaning this still isn't the "first" failure, but 
another failure caused by a "partially-upgraded" schema.

That still doesn't explain what happened the first time you tried to 
upgrade, but without the error message from the first failure, I can't 
even guess what failed.

If you'd like to try to get that first failure, please do a backup/DROP 
DATABASE/restore from your 0.21-fixes system, i.e. using: 
http://www.mythtv.org/wiki/Database_Backup_and_Restore .

Thanks,
Mike