Stanley Bradbury wrote:
Hi John -
When using a version 1.4.2 JVM or higher and the default Derby property
set you should not need to manually remove the db.lck file.
Just to reiterate if your JVM is higher that 1.4.2 then none of the
below applies. Unless there is a bug, Derby will only
Hi Mike,
Can you describe what it means that your program crashed? Did the
JVM
that was running it go down? Are you using network server, if so is it
possible your client program crashed but left the network server up and
still connected to database?
[JCT]
The program crashes when it
John C. Turnbull wrote:
I have just started to use Derby for configuration data for an
application and have found that whenever the app terminates unexpectedly
then Derby will not start the next time I start the application as it
complains that it’s already been opened. At the moment, I need
Hi Oystein,
Thanks for the reply. Comments inline.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday, 2 April 2007 18:13
To: Derby Discussion
Subject: Re: [n00b] Recovering from program crashes
Normally the lock file used to lock the database
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.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 3 April 2007 02:44
To: Derby Discussion
Subject: Re: [n00b] Recovering from program crashes
There is a file in the db directory db.lck that is created to prevent
dual booting. See
http
