ABANDON option with the VALIDATE INDEX

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Hallo NG

Könnt Ihr mir mitteilen wie ich diese SQL Anweisung im Query Manager
umsetzen kann,
in meiner Humingbird Datenbank wird mir mitgeteilt das ich den Index mit der
ABANDON option with the VALIDATE INDEX
Neu bilden sollte, nur verstehe ich es nicht ganz, da ich ein SQL Beginner
bin.

Kann ich dies mit dem Query Manager durchführen?

Danke euch schon jetzt für die Infos..

Gruss
Jahn

Die Lösung was ich nicht ganz verstehe..
SearchServer - "SQLState 80972 ...The data has changed since the index used
to perform this search."
In SearchServer, if you create a table when the time on a machine is set
ahead of the actual time, when the searches are performed after the time is
corrected, you will receive the following error message:

"SQLSTATE: 80972, Native error: 0, error text
[Hummingbird][SearchServer]The data has changed since the index used to
perform this search."

Steps to reproduce:

1. Set the clock on your machine ahead of the actual time (for example, 2
minutes).
2. Run CRS001.FTE, INS001.FTE, and VAL001.FTE scripts from ExecSQL to create
the SUPPORT table.
3. Set the clock back to the actual time.
4. Perform a search from ExecSQL, and you will receive the following error
messages:

"C:\stkits\wnt\5.0\exec>execsql
select text_log from support where ft_cid =4;
CursorName = SQL_CUR00001
RowCount = 1
NumResultCols = 1: TEXT_LOG
values:
execsql: SQLFetch failed."

"SQLSTATE: 80972, Native error: 0, error text
[Hummingbird][SearchServer]The data has changed since the index used to
perform this search."

NOTE: The error message does not correctly reflect the problem. It is
possible that a machine's clock is off, or is ahead of the actual time, and
tables are created during that period. After the time is changed to the
correct time, all searches on the tables created when the machine is set to
the wrong time will display the "SQLState 80972" error message.



--------------------------------------------------------------------------------
Resolution:
To resolve this issue, you must perform a complete reindexing of all tables
using the ABANDON option with the VALIDATE
INDEX statement.



.

Relevant Pages