[
https://issues.apache.org/jira/browse/DERBY-4181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12704405#action_12704405
]
Kathey Marsden commented on DERBY-4181:
---------------------------------------
This is what I discovered today regarding this issue:
It always seems to happen on record 36XXX even with no jit run. It just took 45
minutes to get there.
Reproduces with embedded. You can run with embedded by passing the "Embedded"
argument to the test.
Reproduces without backup. You can run with -Dderby.nstest.backupRestore=false
Reproduces without encryption.
Reproduces without Tester3 threads (was just doing selects) and without Tester2
threads (doing the same operation as Tester1 but getting a new connection each
time.)
Reproduces without updates (just inserts and deletes)
Reproduces with just one Tester1 thread, doing sequential insert and delete
operations.
Trying now with just one INIT thread (was 6) and it has been running for 10
minutes. So I am guessing the corruption is occurring with the mulithreaded
insert used to set up the test, but we don't see it until later when we try a
delete. If this runs ok for a while I will go back to multithreaded and put a
consistency check in after the inserts complete to verify this theory.
> 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.
