SQLITE database db-wal files

Dev Community Dev/API Corner
1

Hi, I use the SQLLite database to create external reports on stored media data. Today I see .db-wal (write-ahead logs) file with the plex.db file.

 

I'm not sure that 1) I have seen this before, and 2) it is preventing me from opening the .db for ad-hoc query. (I normally copy the .db file and work on that, not the "live" database)

 

Can anyone tell me whether write-ahead logs are normal in Plex and the best strategy for unlocking the db for ad-hoc queries? As an additional piece of info, Plex media server is working OK..

 

Many thanks,

 

James

2

Did you ever have any luck getting the DB to open? Thanks for the info.

Update:

Looks like if I copy over the -shm and the -wal files at the same time, then it will open fine. 

3

Hi, I use the SQLLite database to create external reports on stored media data. Today I see .db-wal (write-ahead logs) file with the plex.db file.

I'm not sure that 1) I have seen this before, and 2) it is preventing me from opening the .db for ad-hoc query. (I normally copy the .db file and work on that, not the "live" database)

Can anyone tell me whether write-ahead logs are normal in Plex and the best strategy for unlocking the db for ad-hoc queries? As an additional piece of info, Plex media server is working OK..

Many thanks,

James

That is what I do as well but always shut down Plex Media Server before copying the .db file out 

I do not worry about the wal file as I presume it just means that my query will not get the latest info with a few updates may still be in the wal file. Not been an issue for me

I use the free sqlite studio. 

4

It seems that with the last few PMS releases the write-ahead files are not committed back to the db when PMS is closing (at least on a mac).

This is not a problem as long as you let SQLite Studio work on a copy of the 3 files : db, db-shm and db-wal.

5

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.