[
https://issues.apache.org/jira/browse/DERBY-600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14218729#comment-14218729
]
ASF subversion and git services commented on DERBY-600:
-------------------------------------------------------
Commit 1640644 from [~myrna] in branch 'docs/trunk'
[ https://svn.apache.org/r1640644 ]
DERBY-600; Document that DB is booted in read-only mode if not able to create
db.lck file
Modifying cdevdvlp20458.dita to reflect this behavior.
> Document that DB is booted in read-only mode if not able to create db.lck file
> ------------------------------------------------------------------------------
>
> Key: DERBY-600
> URL: https://issues.apache.org/jira/browse/DERBY-600
> Project: Derby
> Issue Type: Sub-task
> Components: Documentation
> Reporter: Øystein Grøvlen
> Assignee: Myrna van Lunteren
> Priority: Minor
> Attachments: DERBY-600.diff, DERBY-600_2.diff, cdevdvlp20458.html,
> cdevdvlp20458.html
>
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)
