Document that DB is booted in read-only mode if not able to create db.lck file
------------------------------------------------------------------------------
Key: DERBY-600
URL: http://issues.apache.org/jira/browse/DERBY-600
Project: Derby
Type: Sub-task
Components: Documentation
Reporter: Øystein Grøvlen
Priority: Minor
Fix For: 10.2.0.0
I suggest adding the following to the Developer's Guide after "Double-booting
system behavior":
Booting a database in read-only mode
If Derby is not able to create the db.lck file when booting a database, the
database will be booted in read-only mode. This may happen due to lack of disk
space or access rights for the database directory. In this case, the boot
message in the error log will look like the following:
<pre>
2005-10-04 12:12:30.835 GMT:
Booting Derby version The Apache Software Foundation - Apache Derby - 10.2.0.0
alpha - (293288M): instance c013800d-0106-bb8c-12e6-00001672f894
on database directory sample in READ ONLY mode
</pre>
See also "Creating Derby databases for read-only use"
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
