"Smells" like database corruption, but I can't say for certain as there could be a couple things holding back.
- If a rogue thread that isn't killed has its finger on it, it could prevent further access, but that'd depend on whether you're doing a full file lock with that thread. - As mentioned, something at the OS level thinks something has an exclusive lock on the file. - What precisely is telling you the database is locked? Custom error handler, or can you access via the sqlite command line? Best bet, as mentioned, is to reboot and see what happens. If you still can't get access, I'm pointing my finger at corruption. On Fri, Feb 8, 2013 at 7:17 AM, Simon Slavin <[email protected]> wrote: > > On 8 Feb 2013, at 8:57am, Paul Sanderson <[email protected]> > wrote: > > > Is there a faster method for clearing a lock? > > SQLite does not use a persistent locking mechanism. It doesn't write > something to the file saying "this file is locked" and refuse to open a > file with that status. Lock status is maintained by the operating system > and rebooting the computer (if you can't find a simpler way) should unlock > everything. > > If you are getting an error message of some kind from a SQLite function, > tell us what it is and we may be able to help you. If your error message > is coming from your OS we probably can't. > > > Is there some method to ensure that if the indexing process is > interrupted > > that sqlite rolls back - I have jounalling on and journal mode is set to > > delete. > > As part of opening a database SQLite will automatically notice and > rollback all incomplete commands including indexing. > > Simon. > _______________________________________________ > sqlite-users mailing list > [email protected] > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
