db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-5691) Document that Write Caching must be disabled to avoid possible database corruption
Date Fri, 27 Apr 2012 15:22:49 GMT

     [ 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-2.zip
                DERBY-5691-2.stat
                DERBY-5691-2.diff

Thank you, Kathey, for the great comments!

I'm attaching a second patch, DERBY-5691-2.diff, DERBY-5691-2.stat, and DERBY-5691-2.zip,
with the following changes:

M       src/adminguide/cadminpreface23947.dita
M       src/adminguide/derbyadmin.ditamap
A       src/adminguide/cadmindbintegrity.dita
M       src/devguide/cdevdgpref11181.dita
M       src/devguide/cdevdvlp14839.dita

I added the information you suggested to two topics in the Developer's Guide: one in the "Purpose
of this guide" topic in the preface and, since people don't always read the preface, in the
"Application development overview" topic where the book starts to get into substantive areas.
The language may need some changes, though.

I hope the changes to the new Admin Guide topic are satisfactory. I am most uncertain about
the fix to the runtime compression item.

Please let me know if further tweaks are needed.
                
> 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-2.diff, DERBY-5691-2.stat, DERBY-5691-2.zip, 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

        

Mime
View raw message