Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Thu, 19 Apr 2012 18:30:40 +0000 (UTC)
From: "Kim Haase (Updated) (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <974021263.6890.1334860240634.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <729852461.30346.1334610137082.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (DERBY-5691) Document that  Write Caching  must be
 disabled to avoid possible database corruption
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DERBY-5691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kim Haase updated DERBY-5691:
-----------------------------

    Attachment: DERBY-5691.zip
                DERBY-5691.stat
                DERBY-5691.diff

Attaching DERBY-5691.diff, DERBY-5691.stat, and DERBY-5691.zip, with the following changes:

M       src/adminguide/cadminpreface23947.dita
M       src/adminguide/derbyadmin.ditamap
A       src/adminguide/cadmindbintegrity.dita

I decided to give the new topic a more positive title, "Maintaining database integrity". 

I also included some of the more general caveats from DERBY-5508 that didn't quite fit in that patch or that bear repeating. Hope that's okay.

Edits and additions are welcome -- thanks!

                
> Document that  Write Caching  must be disabled to avoid possible database corruption
> ------------------------------------------------------------------------------------
>
>                 Key: DERBY-5691
>                 URL: https://issues.apache.org/jira/browse/DERBY-5691
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>         Environment: Microsoft Windows
>            Reporter: Stan Bradbury
>            Assignee: Kim Haase
>              Labels: Write_caching
>         Attachments: DERBY-5691.diff, DERBY-5691.stat, DERBY-5691.zip
>
>
> Suggestion that we document a recommendation that Windows Write Caching be disabled on machines using Derby.
> The following article warns about Write Caching on Windows as a possbile source of database corruption:
>      http://support.microsoft.com/kb/281672
> It is possible that this could be the cause of some unexplained Derby corruptions identified after power failure of other system interupt.
> Links explaining how to disable Write Caching:
>   Win 2K: http://support.microsoft.com/kb/259716
>    Win 2008: http://support.microsoft.com/kb/324805
> From the Windows 2008 article:
> With some third-party programs, disk write caching has to be turned on or off. Additionally, turning disk write caching on may increase operating system performance; however, it may also result in the loss of information if a power failure, equipment failure, or software failure occurs. This article describes how to turn disk write caching on or off.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira