Kodi Community Forum

Full Version: ERROR: SQL: [MyVideos107] The table does not exist
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Hi Kodi

This error have been driving me nuts since I upgraded v16 - v17. I have finally fixed it but had to use my illustriousness skill. (i had to think, it hurt!)
I was so over the moon so I thought to create an account in the forum and post my "solution". The solution was actually simple but will skip to the relevant details.

Issue:
KODI does not progress from the splash screen.
My Kodi setup is as normal apart from advancedsettings has mysql (ofcourse).

kodi.log says:

ERROR: SQL: [MyVideos107] The table does not exist
Query: SELECT idVersion FROM version
ERROR: CJobWorker:Tonguerocess error processing job

The fix:
Duplicate the old MyVideos99 (or what ever MyVideosXX you have) to MyVideos107
Run your KODI again.
Steps:
on your mysql server
shell> mysqldump -u kodi -p MyVideos99 > bob.sql
shell> mysqladmin create MyVideos107 -u kodi -p
shell> mysql MyVideos107 < bob.sql -u kodi -p

I cannot explain why even though I the database is very small (1 entry). Hoping kodi specialist can perhaps explain.

Hope this helps

Moderators, please feel free to delete/correct my post.
Quote:kodi.log says:
If you were planning to educuate us, we always want to see the kodi.log ourselves, the WHOLE log and nothing but the log, so help us Kodi.
Also, which MySQL server are you using? Some versions seem to have quircks, hiccups. Perhaps your MyVideos99 database has some data corruption, preventing Kodi from doing a successful upgrade.

Another option is to do a video library export ('Separate files') from Kodi (don't forget to enable watched status etc), rename the current MyVideos99 database, restart Kodi for a fresh MyVideos107 database, and then import your video collection.
Are you kidding!, educate you.. I am simply but a humble kodi lover. I dare not to educate kodi-expert. Its like telling Prof. Hawking how to do his quantum gravity.

Anyhow answering the question. I am running MySQL version 5.7.19 at the moment. Unfortunately I cannot do the library export separate files as the NFS shares are RO. Regardless I'm not too fuss about Watched status and other things for now. I did suspected the MyVideos99 being corrupted, but it has been rebuilt since.


Here is kodi.log (the before):

@Karellen- Log Removed.

No logs allowed in the Forum. Pastebin only and link back here.
(2017-07-31, 06:43)iqaruzz Wrote: [ -> ]The fix:
Duplicate the old MyVideos99 (or what ever MyVideosXX you have) to MyVideos107
Run your KODI again.
Steps:
on your mysql server
shell> mysqldump -u kodi -p MyVideos99 > bob.sql
shell> mysqladmin create MyVideos107 -u kodi -p
shell> mysql MyVideos107 < bob.sql -u kodi -p

I cannot explain why even though I the database is very small (1 entry). Hoping kodi specialist can perhaps explain.

Hope this helps

Moderators, please feel free to delete/correct my post.

Your fix is nothing of the sort (I'm only posting this, so that nobody else follows your advice).

If your last working database is MyVideos99 and your new corrupted database is MyVideos107 then this means there was an error migrating the data from MyVideos99 to MyVideos107.

You CANNOT simply duplicate MyVideos99 as MyVideos107 - the reason the data is migrated in the first place is because the database schema is being changed during the migration, so MyVideos107 is not the same as MyVideos99. What you've now done is cause Kodi to migrate "MyVideos107" (your old MyVideos99 database) to v107 - what name it will use for the new database I'm not entirely sure (MyVideos107107?) - it might even repeatedly try to migrate your "MyVideos107" database every time Kodi starts...

What you should have done, and this is the only correct solution, is you should have dropped/deleted the corrupted MyVideos107 database and allowed Kodi to re-attempt the database migration from MyVideos99.
Ah, you are correct. The schema does change during migration.
Feel free to delete this thread to avoid false fix to the public.

but seems to work okay for me.