You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Jeff Mckenzie (JIRA)" <ji...@apache.org> on 2010/03/18 08:20:27 UTC
[jira] Updated: (DERBY-4589) Corrupted database prevents startup
and should be automatically repaired perhaps
[ https://issues.apache.org/jira/browse/DERBY-4589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeff Mckenzie updated DERBY-4589:
---------------------------------
Attachment: 2010-03.zip
This is a database that is empty, but is corrupted somehow.
Derby tries to create a new database because it doesn't see this database, but fails to create a new database, thus preventing the app from ever using it.
> 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
> Affects Versions: 10.5.3.0
> Environment: Windows 2000, SP4. J2SE 1.6
> Reporter: Jeff Mckenzie
> Attachments: 2010-03.zip
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.