On Thu, Aug 11 2005, David J. Hughes wrote:
>
> Hi Norbert,
>
> Please provide details about what software you are running (from this I
> can't tell if you are running 2.x or 3.x).
sorry for forgetting the necessary information :-(
mSQL server version 3.7
mSQL protocol version 23
mSQL connection lnxsrv-10 via TCP/IP
Target platform Linux-2.4.26-i686
> From a quick glance I could take a guess and assume this is a corrupted
> index. There's an index defined on the aufnr column and that'll be
> used during execution of this query. Has there been an issue on the
> box (like an OS panic or power failure) that could have caused updates
> to the index file to partially written?
We had a power failure some days ago and it could have some influence.
> To see if this is the problem
> simply drop and then re-create the index.
>
>
> DROP INDEX idx1 FROM auftrag \g
>
> CREATE UNIQUE INDEX idx1 ON auftrag (
> aufnr
> ) \g
This solved the problem !!! Thank you very much for your help. You
made my day :-)))
Cheers,
Norbert
--
Ceterum censeo | PGP encrypted mail preferred.
Redmond esse delendam. | PGP Key at www.MPA-Garching.MPG.de/~nog/
-----------------------------------------------------------------
This is the Mini SQL Mailing List operated by Hughes Technologies
To unsubscribe, go to http://www.Hughes.com.au/extras/email/
> This solved the problem !!! Thank you very much for your help. You
> made my day :-)))
OK, cool. Glad it worked out. Having a box drop it's power or having
the underlying OS bail out on you is a little hard to deal with. Well,
you can deal with it easily if you don't want any performance (sync
writes to the disk for each update etc). Just a rule of thumb for the
future : if the OS didn't get a chance to flush it's kernel buffers
then there's a good chance any active indicies will be corrupted.
But, as you can see, it's easy enough to recreate them. I'm glad to be
able to make your day ;-)
Bambi
..