db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4181) SQLState.LANG_IGNORE_MISSING_INDEX_ROW_DURING_DELETE during NsTest run
Date Mon, 27 Apr 2009 20:05:30 GMT

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

Myrna van Lunteren commented on DERBY-4181:
-------------------------------------------

For what it's worth, I ran a consistency check on the database, and it definitely falls over
on table NSTEST.NSTESTTAB:
-------------------
38000:The exception 'org.apache.derby.shared.common.sanity.AssertFailure: ASSERT
 FAILED last row on left page 226 > than first row on right page 109
left last row = col[0]=9094871101.2662800000col[1]=(160,43)col[2]=177right first
 row = col[0]=7784998.6583844800col[1]=(195,48)col[2]=144
BRANCH(226)(lev=1): num recs = 89
        left = 105;right = 109;parent = 1;isRoot = false;left child page = 54; last > first
of
BRANCH(109)(lev=1): num recs = 95
        left = 226;right = 202;parent = 1;isRoot = false;left child page = 40;'
was thrown while evaluating an expression.
-------------------------------

> SQLState.LANG_IGNORE_MISSING_INDEX_ROW_DURING_DELETE during NsTest run 
> -----------------------------------------------------------------------
>
>                 Key: DERBY-4181
>                 URL: https://issues.apache.org/jira/browse/DERBY-4181
>             Project: Derby
>          Issue Type: Bug
>          Components: Store
>    Affects Versions: 10.4.2.0, 10.5.1.0, 10.5.1.1, 10.6.0.0
>         Environment: Suse Linux 10, IBM 1.6 SR4
>            Reporter: Myrna van Lunteren
>         Attachments: run1serverlog.jar, serverlog.jar
>
>
> During the NsTest runs for 10.5.1.0 and 10.5.1.1 I initially ignored warnings showing
up in the server's derby.log file:
> WARNING: While deleting a row from a table the index row for base table row (594,12)
was not found in index with conglomerate id 1,185.  This problem has automatically been corrected
as part of the delete operation.
> However, I don't think this is a completely healthy warning, I think it indicates there
was corruption in the index.
> I'll investigate further.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message