[ https://issues.apache.org/jira/browse/DERBY-7113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17323865#comment-17323865 ]
Richard N. Hillegas commented on DERBY-7113: -------------------------------------------- If the problem returns after reloading a backup, then that indicates that you created the backup after the index was corrupted. On a database freshly loaded from the corrupt backup, what happens when you run the SYSCS_UTIL.SYSCS_CHECK_TABLE system function on the affected table? Dropping and re-creating the index is the fastest way to fix this problem. You should probably run SYSCS_UTIL.SYSCS_CHECK_TABLE on all of your tables to check their integrity too. Are you following all of the advice from this page of the Admin Guide: https://db.apache.org/derby/docs/10.15/adminguide/cadmindbintegrity.html > Index has value of column which no longer exists in the table > ------------------------------------------------------------- > > Key: DERBY-7113 > URL: https://issues.apache.org/jira/browse/DERBY-7113 > Project: Derby > Issue Type: Bug > Components: Network Server > Affects Versions: 10.8.3.0 > Environment: Linux with Java 8 - 8.0.6.25 > Reporter: Geraldine > Priority: Critical > > From time to time an Index keeps a value, which has been deleted from the > underlying table. > This results in an error is the row with the value is selected. > _SELECT ID from Some.TABLE WHERE IndexedColumn= 'Remembered Value';_ > _ID_ > _--------------------_ > _1680880176_ > _ERROR 0A000: The DRDA command parseSQLDIAGSTT is not currently implemented. > The connection has been terminated._ > If only the Indexed Column is selected, then the Query returns 0 rows and > produces no error - because just the index is searched. > The Query Plan shows the index being used. > Dropping and Recreating the index fixes the issue. However, I can reproduce > this by reloading a database backup. > -- This message was sent by Atlassian Jira (v8.3.4#803005)