• Welcome to the Lightroom Queen Forums! We're a friendly bunch, so please feel free to register and join in the conversation. If you're not familiar with forums, you'll find step by step instructions on how to post your first thread under Help at the bottom of the page. You're also welcome to download our free Lightroom Quick Start eBooks and explore our other FAQ resources.
  • Stop struggling with Lightroom! There's no need to spend hours hunting for the answers to your Lightroom Classic questions. All the information you need is in Adobe Lightroom Classic - The Missing FAQ!

    To help you get started, there's a series of easy tutorials to guide you through a simple workflow. As you grow in confidence, the book switches to a conversational FAQ format, so you can quickly find answers to advanced questions. And better still, the eBooks are updated for every release, so it's always up to date.

WAL and LOCK files

Status
Not open for further replies.

Steve

New Member
Joined
Aug 22, 2015
Messages
5
Location
Annapolis, MD
Lightroom Experience
Intermediate
Lightroom Version
Lightroom Version Number
The latest version on Creative Cloud
Operating System
  1. macOS 10.14 Mojave
I understand these are both temporary files open when LR is running. My Lightroom classic shut down when running, and I have an LRCAT file as well as the Lock and wal files, and am unable to open the LRCAT file. I understand I need to delete the LOCK file to re-open the Lightroom catalogue, My question is whether I also need to delete the wal file. Thank you. Steve
 
AFAIK, you can also delete the WAL file if Lightroom didn’t do that because of a crash. You can also leave it for now and restart Lightroom. If it’s still there when you next quit Lightroom, then it is clearly no longer used and can be deleted.
 
I have a feeling that Adobe's advice would be to leave the WAL file alone in this situation, i.e. do not delete it. The WAL file (Write Ahead Log) replaced the Journal file which was used in previous Lightroom versions, and definitely the advice for the Journal file was "do not delete". In theory, the WAL file could contain details of database transactions scheduled but not yet completed at the time of the crash, thus if the WAL file is still present when LR next starts it should be interrogated for those outstanding transactions.

But that's just my limited understanding, so I might not have got it quite right. It certainly wouldn't hurt to leave the file alone though.
 
LR has moved to the "write-ahead logging" (WAL) provided by newer versions of SQLite. This is supposed to make updates to the database faster. However if the Update Statement was to update 100 records and only 40 were updated before the crash the WAL file could become important to prevent a corrupted catalog down the road. As others have suggested . let LR clean it up on restart and only remove the WAL file manually after you have restarted successfully should it remain after the LR next successful shutdown.
 
Status
Not open for further replies.
Back
Top