This solution works good on my Win 7 PC, as well as my OSX 10.5 laptop
On Aug 17, 2:22 pm, Thomas Mueller <thomas.tom.muel...@gmail.com> wrote: > Hi, > > > Caused by: org.apache.lucene.store.LockObtainFailedException: Lock > > obtain timed out: simplefsl...@c:\Users\Clinton Hyde\mag-db\write.lock > > It looks like the Lucene index is already open, or the write.lock is > not removed after killing the process. or something like that (other process has it?) > > > if the error messages had said some of this, I'd have figured it out a lot > > sooner... > > So the problem was the object existed, but in a different schema? that was exactly it. It was my fault that it happened that way, I completely did not realize that was what was going on, it was mostly a result of evolved, rather than designed, SQL, so there was some ordering dependence that I was not recognizing--and the error msgs were very confusing. > This > is not a very common problem. However I will still add a feature > request for "If a database object was not found in the current schema, > but one with the same name existed in another schema, included that in > the error message." that would have been very helpful for me :) later today, or tomorrow, I will try this on my friend's server. > > Regards, > Thomas -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to h2-datab...@googlegroups.com. To unsubscribe from this group, send email to h2-database+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
