Related to the fact that the error-producing search takes a very long time is the sometime complaint that a concordance search may take very long (in a large TM). Googling for вЂњDatabase is lockedвЂќ gives quite a few hits, related to SQLite, and it seems to be quite a common issue with other applications. (And delete the error message in the Messages window.) Then go back to the вЂњproblemвЂќ segment and confirm it. I have not tried re-indexing, but I have found that the following method works fine:Д¬ontinue to the next segment вЂ“ which then strangely is looked up in the TM without problem (regardless of whether there is a hit or no). My own experience is that this only happens with very large TMs, but then it can happen even if that is the only TM I use. вЂњIf I deactivate all other memories and only activate this вЂ›lockedвЂ™ memory, it works fine.вЂќ вЂњRe-indexing the TM helped to get that working.вЂќ If I deactivate all other memories and only activate this вЂ›lockedвЂ™ memory, it works fine.вЂќ I can simply recativate the affected memory and everything works fine until at some later point Studio again thinks it is вЂ›lockedвЂ™. So it looks like Studio is simply вЂ›running out of steamвЂ™ by the time it reaches the last memories in a list. вЂњThe affected TM in most cases seems to be the very last (or one of the last) in a list of вЂ“ say вЂ“ 6 or 7 memories. Several people have reported this problem, and various methods to solve it has been tried (this is taken from the invaluable TW_Users forum): Sometimes the first activation of a segment in a document results вЂ“ after a long time of searching the TM вЂ“ in this error message: вЂњAn error has occured whilst using the translation provider : The translation memory data file engine returned an error: The database file is locked.

Sdl trados studio forum