There is a file in the db directory db.lck that is created to prevent
dual booting. See
http://db.apache.org/derby/docs/10.2/devguide/cdevdvlp20458.html for
more info.
By removing that file you should be able to boot. However, make sure
that no other process is accessing the database. Derby will try to
delete this file itself. If it fails, it is an indication that some
other process has an open file descriptor for this file. Could it be
that a process that earlier has accessed the DB is hanging and not
actually removed until you reboot the DB?
--
Øystein
