[
https://issues.apache.org/jira/browse/DERBY-4181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-4181:
----------------------------------
I also repro'd this on a 2 processor XP laptop, running IBM 1.6 SR3 jvm. I
verified that the affected index is not an "allow duplicates" index so not
similar to the other problems we have seen with that new index that allows
duplicate
null values in an otherwise unique index.
I repro'd running SANE classes and got:
org.apache.derby.shared.common.sanity.AssertFailure: ASSERT FAILED Index row
(8167710.5025663700,(591,88)) not found in conglomerateid 1185Current sca
n =
btree = BTREE: containerid = Container(0, 1185);nKeyFields =
2;nUniqueColumns = 2;allowDuplicates = false
scan direction = forward
(scan_state:SCAN_DONE
rh:null
key:null)
init_rawtran = 95000
init_hold = false
init_forUpdate = true
init_useUpdateLocks = false
init_scanColumnList = null
init_scanColumnList.size() = 0
init_template = col[0]=8168831.1746247970col[1]=(195,30)
init_startKeyValue = col[0]=8167710.5025663700col[1]=(591,88)
init_startSearchOperator = GE
init_qualifier[] = null
init_stopKeyValue = col[0]=8167710.5025663700col[1]=(591,88)
init_stopSearchOperator = GT
stat_numpages_visited = 3
stat_numrows_visited = 1
stat_numrows_qualified = 0
stat_numdeleted_rows_visited = 0^M
at
org.apache.derby.shared.common.sanity.SanityManager.THROWASSERT(SanityManager.java:162)^M
at
org.apache.derby.shared.common.sanity.SanityManager.THROWASSERT(SanityManager.java:147)^M
at
org.apache.derby.impl.sql.execute.IndexChanger.doDelete(IndexChanger.java:351)^M
at
org.apache.derby.impl.sql.execute.IndexChanger.delete(IndexChanger.java:544)^M
at
org.apache.derby.impl.sql.execute.IndexSetChanger.delete(IndexSetChanger.java:250)^M
at
org.apache.derby.impl.sql.execute.RowChangerImpl.deleteRow(RowChangerImpl.java:476)^M
at
org.apache.derby.impl.sql.execute.DeleteResultSet.deleteDeferredRows(DeleteResultSet.java:527)^M
at
org.apache.derby.impl.sql.execute.DeleteResultSet.open(DeleteResultSet.java:154)^M
at
org.apache.derby.impl.sql.GenericPreparedStatement.executeStmt(GenericPreparedStatement.java:416)^M
at
org.apache.derby.impl.sql.GenericPreparedStatement.execute(GenericPreparedStatement.java:297)^M
at
org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(EmbedStatement.java:1235)^M
at
org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(EmbedPreparedStatement.java:1648)^M
at
org.apache.derby.impl.jdbc.EmbedPreparedStatement.execute(EmbedPreparedStatement.java:1303)^M
at
org.apache.derby.impl.drda.DRDAStatement.execute(DRDAStatement.java:672)^M
at
org.apache.derby.impl.drda.DRDAConnThread.parseEXCSQLSTTobjects(DRDAConnThread.java:4280)^M
at
org.apache.derby.impl.drda.DRDAConnThread.parseEXCSQLSTT(DRDAConnThread.java:4084)^M
at
org.apache.derby.impl.drda.DRDAConnThread.processCommands(DRDAConnThread.java:1003)^M
at org.apache.derby.impl.drda.DRDAConnThread.run(DRDAConnThread.java:290)^M
> 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.
