db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4181) SQLState.LANG_IGNORE_MISSING_INDEX_ROW_DURING_DELETE during NsTest run
Date Tue, 28 Apr 2009 00:07:30 GMT

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

Kathey Marsden commented on DERBY-4181:
---------------------------------------

I ran with IBM 1.6 SR3 with jit off on the server and the issue occurred after 45 minutes,
so it does not appear to be a JIT issue.

I ran 2 hours with IBM 1.5 (pwi32dev-20080315 (SR7)) on trunk and did not see the issue.

I ran with derby.language.logStatementText turned on and noticed that the failure occurred
when there was a concurrent attempt to update and delete of the same row from different threads.
 I will attach the log excerpt (log_excerpt_sample_assert.txt)

I tried to make a smaller program to reproduce this but ran into DERBY-4193 You can see my
attempt attached to that issue. ScanPosSaved.java.


> 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: log_excerpt_sample_assert.txt, 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