[
https://issues.apache.org/jira/browse/DERBY-5650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13229175#comment-13229175
]
Rick Hillegas commented on DERBY-5650:
--------------------------------------
Thanks for attaching derby.log, Deepika. The corruption first appeared with an
INSERT INTO EVENTS_TABLE statement, as you note above. Before that statement,
all I see in derby.log are boot and shutdown diagnostics. It appears that the
installation was using Derby 10.2.2.0 at first on 2011-07-21. About 8 hours
later the installation was brought down and rebooted with Derby 10.6.1.0. The
installation was rebooted a couple times and ran fine with 10.6.1.0 until the
first error occurred on 2011-11-03.
After that, the corruption choked a database backup on 2011-11-16. The INSERT
statement failed again on 2011-11-17, 2011-11-22, 2011-11-23, 2012-02-06, and
2012-02-21. The following corrupted pages (all in the same conglomerate) appear
in derby.log: 2953, 1936, 2914, 2125. I do not see any evidence that any other
conglomerates are corrupted. It is possible that you may be able to repair the
database (at least to the point that you can dump and reload it) by dropping
and recreating the indexes on EVENTS_TABLE.
The initial corruption occurred several months ago. This long afterward, we
generally don't have much success in figuring out what caused the original
problem. Did anything special happen on 2011-11-03 that you can remember?
Thanks,
-Rick
> ERROR XSDBB: Unknown page format at page Page(1936,Container(0, 1009)), page
> dump follows: Hex dump: 00000000:
> --------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5650
> URL: https://issues.apache.org/jira/browse/DERBY-5650
> Project: Derby
> Issue Type: Bug
> Affects Versions: 10.6.1.0
> Reporter: Deepika Kochhar
> Attachments: derby.log
>
>
> i am trying to insert values into the database table EVENTS_TABLE where i
> have 18 columns with EVENT_ID as Unique but can be null. Indexes for this
> table is EVENT_INDEX which points to EVENT_ID internally. Now at some point
> of insertion into this Table, i am getting "The statement was aborted because
> it would have caused a duplicate key value in a unique or primary key
> constraint or unique index identified by 'EVENT_INDEX' defined on
> 'EVENTS_TABLE'." error in my logs and in derby logs i am getting ERROR XSDBB:
> Unknown page format at page Page(1936,Container(0, 1009)), page dump follows:
> Hex dump: 00000000: error.
> Please let me know why this is happening and what is the meaning of this
> error.
--
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
