Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Thu, 18 Oct 2012 19:16:06 +0000 (UTC)
From: "Knut Anders Hatlen (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <1262578244.65241.1350587766141.JavaMail.jiratomcat@arcas>
In-Reply-To: 
 <1762881484.10674.1305308027375.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (DERBY-5232) Put a stern README file in log and
 seg0 directories to warn users of corrpution they will cause if they touch
 files there
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/DERBY-5232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13479264#comment-13479264 ] 

Knut Anders Hatlen commented on DERBY-5232:
-------------------------------------------

Yes, messages.xml is the right place. They shouldn't use SQL states, but instead four letter message ids. See the constants in org.apache.derby.shared.common.reference.MessageId interface for examples. The SERVICE_PROPERTIES_DONT_EDIT message with id M001 is similar to the messages we want to add in this issue.
                
> Put a stern README file in log and seg0 directories to warn users of corrpution they will cause if they touch files there
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-5232
>                 URL: https://issues.apache.org/jira/browse/DERBY-5232
>             Project: Derby
>          Issue Type: Improvement
>          Components: Store
>    Affects Versions: 10.8.1.2
>            Reporter: Kathey Marsden
>            Assignee: Mamta A. Satoor
>         Attachments: DERBY5232_patch1_diff.txt, DERBY5232_patch1_stat.txt
>
>
> Users often on bad advice or desperation  touch or delete files in the log or seg0 directories (mostly log).
> I think it would be good for new databases and on upgrade that a file be created in these directories with a name like:
> TOUCHING_FILES_HERE_WILL_CORRUPT_DB_README.txt
> or some such to warn of the perils of doing this and the corrupting effects and how it can eliminate any possibility of salvage. It should also encourage users to make a zip backup of the database directory with no jvm currently accessing it before trying to do anything with the database if it appears to be already corrupt.  Also point to backup/restore documentation and encourage restore of a good backup into an empty directory if the database is corrupt.
> I'm not sure if it would help but it couldn't hurt.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira