Angela, I found a similar problem trying to move from Rivendell 2.5 (Schema 242) up to RD3.5 in that the the new machine thought the old database was corrupted and would not convert it. I still haven't been told how to repair that original database - but I have found a workaround that worked for me. I ran the original database through a Rivendell 2.19 which used schema 272 or so but was on CentOS 7 - and it converted just fine there - then restored that database in the new RD3.5 which took about 10 minutes but works great. Of course, with the CentOS shutdown I have not been able to "yum update rivendell" on any of my RD2.5/CentOS 6 machines so I was just lucky I had the RD2.19/CentOS7 machine (which has other issues). If you can get your hands in a RD2,19/CentOS 7 machine and use it as an intermediate I bet you can use that older DB,
I still have not heard from anyone about how to repair/rework/update these old RELIABLE databases. However, I have found the RD3.5 to be a sweet machine and worth the gyrations for the upgrade. Maybe someone will come up with something like RDDBCheck to do this stuff for Rivendell 3. Jesse Jones Broadcast Tech for KBNX, KBUB, KCXX, KJKB, KLTO, KPSM, KQMJ, KSZX, KTJK,and KXXU All in Central Texas
_______________________________________________ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
