[
https://issues.apache.org/jira/browse/DERBY-7113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17324898#comment-17324898
]
Geraldine commented on DERBY-7113:
----------------------------------
thanks for the responses...
to answer the Qs:
# Yes, the backup was taken when the index was corrpted.
# Running SYSCS_UTIL.SYSCS_CHECK_TABLE system returns 1 for this and all other
tables in the database. This is even when the corruption is in place. Also,
updating the statistics for the index did not resolve the issue. The only way
to fix the issue was to drop and recreate it.
# Regarding the advice in the link, I cannot say 100% that all this advice is
followed as I am not the admin of the system but I will share this.
I'm thinking in this case, the database knows that an issue exists... i.e. the
index returned something but when the actual data was searched, nothing was
found. I can see from the code that it throws an exception in this case. But
could it be handled better? Maybe with a message saying which index was being
used ?
> 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)
