Subject | Corrupted indexes still corrupt after restore |
---|---|
Author | Christian Gütter |
Post date | 2005-07-17T14:04:16Z |
Hi,
this is an issue from a german newsgroup:
during an update, someone received the following error when updating
a table:
internal gds software consistency check (partner index description not found
(175))
As this is an error that was often discussed before, I told the poster
to recreate all indexes and foreign key indexes related to the
table in question. This fixed the problem.
It was quite interesting for me that the poster mentioned that a
backup and restore did not fix the problem. AFAIU gbak pumps the data
from the backup file into a new file and then creates the indexes.
As the indexes were renewed during the restore, why did the original
poster still receive the "partner index description not found" error?
Thanks in advance for your answers!
Christian
this is an issue from a german newsgroup:
during an update, someone received the following error when updating
a table:
internal gds software consistency check (partner index description not found
(175))
As this is an error that was often discussed before, I told the poster
to recreate all indexes and foreign key indexes related to the
table in question. This fixed the problem.
It was quite interesting for me that the poster mentioned that a
backup and restore did not fix the problem. AFAIU gbak pumps the data
from the backup file into a new file and then creates the indexes.
As the indexes were renewed during the restore, why did the original
poster still receive the "partner index description not found" error?
Thanks in advance for your answers!
Christian