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] Updated: (DERBY-4181) SQLState.LANG_IGNORE_MISSING_INDEX_ROW_DURING_DELETE during NsTest run
Date Mon, 27 Apr 2009 18:32:30 GMT

     [ https://issues.apache.org/jira/browse/DERBY-4181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kathey Marsden updated DERBY-4181:
----------------------------------

    Derby Info:   (was: [Regression])

My 10.3 workspace was picking up the Sun JVM, so that is why I did not see it with 10.3. 
I see the assert  on both 10.3 and trunk with:

java version "1.6.0"
Java(TM) SE Runtime Environment (build pwi3260sr3-20081106_07(SR3))
IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260-20081105_25433 (JIT
enabled, AOT enabled)
J9VM - 20081105_025433_lHdSMr
JIT  - r9_20081031_1330
GC   - 20081027_AB)
JCL  - 20081106_01

On 10.3  using the Sun JVM I didn't see it.
java version "1.6.0_01"
Java(TM) SE Runtime Environment (build 1.6.0_01-b06)
Java HotSpot(TM) Client VM (build 1.6.0_01-b06, mixed mode)



> 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