Return-Path: 
 <derby-dev-return-114315-apmail-db-derby-dev-archive=db.apache.org@db.apache.org>
X-Original-To: apmail-db-derby-dev-archive@www.apache.org
Delivered-To: apmail-db-derby-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 7CE7510660
	for <apmail-db-derby-dev-archive@www.apache.org>;
 Thu, 20 Nov 2014 17:39:34 +0000 (UTC)
Received: (qmail 40511 invoked by uid 500); 20 Nov 2014 17:39:34 -0000
Delivered-To: apmail-db-derby-dev-archive@db.apache.org
Received: (qmail 40479 invoked by uid 500); 20 Nov 2014 17:39:34 -0000
Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:derby-dev-help@db.apache.org>
List-Unsubscribe: <mailto:derby-dev-unsubscribe@db.apache.org>
List-Post: <mailto:derby-dev@db.apache.org>
List-Id: <derby-dev.db.apache.org>
Reply-To: <derby-dev@db.apache.org>
Delivered-To: mailing list derby-dev@db.apache.org
Received: (qmail 40468 invoked by uid 99); 20 Nov 2014 17:39:34 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Nov 2014 17:39:34 +0000
Date: Thu, 20 Nov 2014 17:39:34 +0000 (UTC)
From: "Myrna van Lunteren (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <JIRA.12317580.1128460573000.545489.1416505174181@Atlassian.JIRA>
In-Reply-To: <JIRA.12317580.1128460573000@Atlassian.JIRA>
References: <JIRA.12317580.1128460573000@Atlassian.JIRA>
 <JIRA.12317580.1128460573000@arcas>
Subject: [jira] [Commented] (DERBY-600) Document that DB is booted in
 read-only mode if not able to create db.lck file
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


    [ https://issues.apache.org/jira/browse/DERBY-600?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D14219=
641#comment-14219641 ]=20

Myrna van Lunteren commented on DERBY-600:
------------------------------------------

Note that before committing I did confirm the behavior; after creating a da=
tabase, I made the database directory read-only, then tried to boot it and =
indeed it opened the database in read-only mode as reported in the boot mes=
sage in derby.log.

> 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: =C3=98ystein Gr=C3=B8vlen
>            Assignee: Myrna van Lunteren
>            Priority: Minor
>             Fix For: 10.12.0.0
>
>         Attachments: DERBY-600.diff, DERBY-600_2.diff, cdevdvlp20458.html=
, cdevdvlp20458.html
>
>
> I suggest adding the following to the Developer's Guide after "Double-boo=
ting system behavior":
> Booting a database in read-only mode
> If Derby is not able to create the db.lck file when booting a database, t=
he 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, t=
he 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=20
> </pre>
> See also "Creating Derby databases for read-only use"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)