[mythtv-users] No SD Update and SD Episode Numbers do not matchprevious recordings

[Cottrell, Eric]

> -----Original Message-----
> From: mythtv-users-bounces at mythtv.org 
> [mailto:mythtv-users-bounces at mythtv.org] On Behalf Of Cottrell, Eric
> Sent: Thursday, September 13, 2007 3:12 PM
> To: Discussion about mythtv
> Subject: Re: [mythtv-users] No SD Update and SD Episode 
> Numbers do not matchprevious recordings
> 
> 
> 
> 
<snip>
> > You can fix the programid problem after the fact, though
> > there may be other problems due to "restoring" an old DB onto 
> > a new schema.
> > 
> > Just run these updates on the mythconverg DB:
> > (first run mysql mythconverg -umythtv -pmythtv)
> > 
> > UPDATE recorded
> > SET programid=CONCAT(SUBSTRING(programid, 1, 2), 
> >                      '00', SUBSTRING(programid, 3)) 
> > WHERE length(programid) = 12;
> > 
> > UPDATE oldrecorded
> > SET programid=CONCAT(SUBSTRING(programid, 1, 2),
> >                      '00', SUBSTRING(programid, 3))
> > WHERE length(programid) = 12;
> > 
> > UPDATE program
> > SET programid=CONCAT(SUBSTRING(programid, 1, 2),
> >                      '00', SUBSTRING(programid, 3))
> > WHERE length(programid) = 12;
> 
> Thanks.  I will try this tonight.

That was not the problem.  It looks like Zap2It went to a 14 character
programid while I was still using version 0.16 with space for only 12
characters.  So while the new listing has a programid of EP000063550042,
the old recording has a programid of EP0000635500.  So I need to correct
the bad data as I get repeats.  Time to break open the SQL books.  I
have a nice graphical MySQL query program that may be useful.
> 
> > > Problem 2:
<snip>
> 
> I will try the command line tonight.  I did see 14 days when
> I ran it the first time.  Maybe I need to install or configure
> at or chron?

No mention of running MythFillDatabase in the log.  I put the direct
path in the setup screen and filled the log file entry to point to
/var/log/mythtv/mythfilldatabase.log.  On the Jobs page I increased the
number of concurrent jobs to 2.  I manually ran it and it was sucessful.

I have it setup to run between 2 and 5 AM.  I noticed last night on the
status page that the next suggested run was at 2:19 AM.  I noticed this
morning that the time of the last run had not changed but the time of
the next suggested run had changed to 9:53 AM.  I checked it at 10:00 AM
and the time of the last run still has not changed.  I forgot if the
next suggested time had changed.  I will look at it some more this
weekend.  Maybe it is this suggested run bug and I need to update to
later packages.

On a perhaps unrelated note I found that I have four sources specified
on this single tuner system because I did not do a delete all when stuff
was changed or upgraded.  I am going to correct that as well over the
weekend.

73 Eric