db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Mckenzie (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-4589) Corrupted database prevents startup and should be automatically repaired perhaps
Date Fri, 09 Dec 2011 01:04:40 GMT

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

Jeff Mckenzie commented on DERBY-4589:
--------------------------------------

If the database is completely empty and has no tables, why not just recreate the whole thing
from scratch?

You would only need a little flag somewhere for this. It gets written to once the database
is fully created and opens normally. If it is in the wrong state, delete and recreate the
database.

OTOH, if you have definitely identified the problem, carry on...



                
> Corrupted database prevents startup and should be automatically repaired perhaps
> --------------------------------------------------------------------------------
>
>                 Key: DERBY-4589
>                 URL: https://issues.apache.org/jira/browse/DERBY-4589
>             Project: Derby
>          Issue Type: Improvement
>          Components: Store
>    Affects Versions: 10.5.3.0
>         Environment: Windows 2000, SP4. J2SE 1.6
>            Reporter: Jeff Mckenzie
>            Assignee: Rick Hillegas
>             Fix For: 10.8.1.2, 10.9.0.0
>
>         Attachments: 2010-03.zip, Test_4589.java, Test_4589.java, derby-4589-01-ab-missingServiceProperties.diff,
derby-4589-01-ac-missingServiceProperties.diff
>
>
> I have found a database in my application that prevents startup due to it being corrupted.

> The driver reports that the database does not exist, even though it does. Then when my
app tries to create the database using ;create=true; on the URL it fails.
> I think this happened due to the app being killed in Task Manager while it was creating
the database.
> I have the database saved so that you can reproduce the problem. (I'm not sure if I can
attach it yet)

--
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